Network initiated slice selection in wireless communication networks

Abstract

The present disclosure provides a method and apparatus for network initiated slice selection that includes receiving a first request indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, wherein the first request includes information associated with a second network slice to replace the first network slice, and wherein the first request is associated with a request for network initiated slice selection from an application function (AF), and transmitting, a second request toward an access management function (AMF) of the communication network for the AMF to initiate replacement of the first network slice with the second network slice. The present disclosure also provide a method and apparatus for an application function that includes providing a service to a user equipment via a first network slice of a communication network, sending, to the communication network, a request to replace the first network slice, wherein the request includes information comprising a service quality level associated with a second network slice that is to replace the first network slice, in response to receiving a notification from the communication network, an indication that the first network slice was replaced with a second network slice of the communication network, and providing the service to the user equipment via the second network slice.

Description

NETWORK INITIATED SLICE SELECTION IN WIRELESS COMMUNICATIONNETWORKSRELATED APPLICATIONS

[0001] This application claims the benefit of priority of Indian Provisional Patent Application 202441009739 filed on February 13, 2024, which is hereby incorporated by reference as if reproduced in its entirety.FIELD OF TECHNOLOGY

[0002] The present disclosure relates to network initiated slice selection in a wireless communication networks.BACKGROUND

[0003] Network slicing enables network resources of a physical network to be allocated into different, independent, logical, or virtual, networks, referred to as “network slices”. Each network slice is end-to-end 5G network that may be isolated from other network slices. Each network slice can deliver one or more services. The advantage of having network slices is that each network slice may be configured to meet the particular network requirements in terms of, for example, data rates, reliability, latency, and security requirements. Rather than a one-size fit all network, the different network slices provided in a 5G network, support different use cases or serve different industries that each have different network requirements while utilizing a single physical network.

[0004] Developments in network slicing in communication networks are desirable.SUMMARY

[0005] According to one aspect of an embodiment, the present disclosure provides a method for a policy control function (PCF) for performing network initiated slice selection that includes receiving a first request indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, wherein the first request includes information associated with a second network slice to replace the first network slice, and wherein the first request is associated with a request for network initiated slice selection from an application function (AF), and transmitting, a second request toward an access management function (AMF) of the communication network for the AMF to initiate replacement of the first network slice with the second network slice.

[0006] In an example, information associated with the second network slice comprises a service quality level for the second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater or less than a quality of service of the first network slice.

[0007] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0008] In an example, the method further includes determining based on the service quality level, the second network slice that satisfies the service quality level.

[0009] In an example, determining the second network slice includes transmitting a third request by the PCF to a network exposure function (NEF) or a unified data repository function (UDR) that includes the service quality level and requests that the NEF or UDR provide to the PCF the second network slice that satisfies the service quality level, and receiving a response to the third request from the NEF or UDR that identifies the second network slice that satisfies the service quality level.

[0010] In an example, information associated with the second network slice comprises an identifier of the second network slice that is to replace the first network slice determined by a network exposure function or by a unified data repository entity of the communication network or by the application function.

[0011] In an example, the second request transmitted towards the AMF includes the identifier of the second network slice that is to replace the first network slice.

[0012] In an example, the second request transmitted by the PCF to the AMF includes the service quality level for the second slice that is to replace the first slice.

[0013] In an example, the second request message transmitted by the PCF to the AMF indicates that the network slice replacement was initiated by the AF.

[0014] In an example, the first network slice is included in a bundle service, and the second network slice is another network slice included in the bundle service.

[0015] In an example, the first request is received by the PCF from a network exposure function (NEF) of the communication network, or a unified data management repository (UDR) of the communication network, or the AF.

[0016] According to another aspect of an embodiment, the present disclosure provides an apparatus that includes at least one processor, and at least one memory storinginstructions of a policy control function (PCF), wherein when the instructions are executed by the at least one processor, cause the apparatus to receive a first request indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, wherein the first request includes information associated with a second network slice to replace the first network slice, and wherein the first request is associated with a request for network initiated slice selection from an application function (AF), and transmit, a second request toward an access management function (AMF) of the communication network for the AMF to initiate replacement of the first network slice with the second network slice.

[0017] In an example, information associated with the second network slice comprises a service quality level for the second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater or less than a quality of service of the first network slice.

[0018] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0019] In an example, when the instructions are executed by the at least one processor, cause the apparatus to determine based on the service quality level, the second network slice that satisfies the service quality level.

[0020] In an example, the instructions that, when executed by the at least one processor, cause the apparatus to determine the second network slice includes instructions that, when executed by the at least one processor, cause the apparatus to transmit a third request by the PCF to a network exposure function (NEF) or a unified data repository function (UDR) that includes the service quality level and requests that the NEF or UDR provide to the PCF the second network slice that satisfies the service quality level, and receive a response to the third request from the NEF or UDR that identifies the second network slice that satisfies the service quality level.

[0021] In an example, information associated with the second network slice comprises an identifier of the second network slice that is to replace the first network slice determined by a network exposure function or by a unified data repository entity of the communication network or by the application function.

[0022] In an example, the second request transmitted towards the AMF includes the identifier of the second network slice that is to replace the first network slice.

[0023] In an example, the second request transmitted by the apparatus to the AMF includes the service quality level for the second slice that is to replace the first slice.

[0024] In an example, the second request message transmitted by the apparatus to the AMF indicates that the network slice replacement was initiated by the AF.

[0025] In an example, the first network slice is included in a bundle service, and the second network slice is another network slice included in the bundle service.

[0026] In an example, the first request is received by the apparatus from a network exposure function (NEF) of the communication network, or a unified data management repository (UDR) of the communication network, or the AF.

[0027] According to another aspect of an embodiment, the present disclosure provides a computer-readable medium storing instructions of a policy control function (PCF), wherein when the instructions are executed by at least one processor of an apparatus, cause the apparatus to receive a first request indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, wherein the first request includes information associated with a second network slice to replace the first network slice, and wherein the first request is associated with a request for network initiated slice selection from an application function (AF), and transmit, a second request toward an access management function (AMF) of the communication network for the AMF to initiate replacement of the first network slice with the second network slice.

[0028] In an example, information associated with the second network slice comprises a service quality level for the second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater or less than a quality of service of the first network slice.

[0029] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0030] In an example, when the instructions are executed by the at least one processor, cause the apparatus to determine based on the service quality level, the second network slice that satisfies the service quality level.

[0031] In an example, the instructions that, when executed by the at least one processor, cause the apparatus to determine the second network slice includes instructions that, when executed by the at least one processor, cause the apparatus to transmit a thirdrequest by the PCF to a network exposure function (NEF) or a unified data repository function (UDR) that includes the service quality level and requests that the NEF or UDR provide to the PCF the second network slice that satisfies the service quality level, and receive a response to the third request from the NEF or UDR that identifies the second network slice that satisfies the service quality level.

[0032] In an example, information associated with the second network slice comprises an identifier of the second network slice that is to replace the first network slice determined by a network exposure function or by a unified data repository entity of the communication network or by the application function.

[0033] In an example, the second request transmitted towards the AMF includes the identifier of the second network slice that is to replace the first network slice.

[0034] In an example, the second request transmitted by the apparatus to the AMF includes the service quality level for the second slice that is to replace the first slice.

[0035] In an example, the second request message transmitted by the apparatus to the AMF indicates that the network slice replacement was initiated by the AF.

[0036] In an example, the first network slice is included in a bundle service, and the second network slice is another network slice included in the bundle service.

[0037] In an example, the first request is received by the apparatus from a network exposure function (NEF) of the communication network, or a unified data management repository (UDR) of the communication network, or the AF.

[0038] According to another aspect of an embodiment, the present disclosure provides a method performed by an application function, the method including providing a service to a user equipment via a first network slice of a communication network, sending, to the communication network, a request to replace the first network slice, wherein the request includes information comprising a service quality level associated with a second network slice that is to replace the first network slice, in response to receiving a notification from the communication network, wherein the notification includes an indication that the first network slice was replaced with a second network slice of the communication network, providing the service to the user equipment via the second network slice.

[0039] In an example, the service quality level for the second network slice indicates that a quality of service of the second network is to be greater than or less than a quality ofservice of the first network slice.

[0040] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0041] According to another aspect of an embodiment, the present disclosure provides an apparatus that includes at least one processor, and at least one memory storing instructions of an application function, wherein when the instructions are executed by the at least one processor, cause the apparatus to provide a service to a user equipment via a first network slice of a communication network, send, to the communication network, a request to replace the first network slice, wherein the request includes information comprising a service quality level associated with a second network slice that is to replace the first network slice, in response to receiving a notification from the communication network, wherein the notification includes an indication that the first network slice was replaced with a second network slice of the communication network, provide the service to the user equipment via the second network slice.

[0042] In an example, the service quality level for the second network slice indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice.

[0043] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0044] According to another aspect of an embodiment, the present disclosure provides a computer-readable medium storing instructions of an application function, wherein when the instructions are executed by at least one processor of an apparatus, cause the apparatus to provide a service to a user equipment via a first network slice of a communication network, send, to the communication network, a request to replace the first network slice, wherein the request includes information comprising a service quality level associated with a second network slice that is to replace the first network slice, in response to receiving a notification from the communication network, wherein the notification includes an indication that the first network slice was replaced with a second network slice of the communication network, provide the service to the user equipment via the second network slice.

[0045] In an example, the service quality level for the second network slice indicates that a quality of service of the second network is to be greater than or less than a quality ofservice of the first network slice.

[0046] In an example, the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

[0047] According to another aspect of an embodiment, the present disclosure provides a method performed by a network exposure function of a communication network, the method including receiving, from an application function or a policy control function (PCF), a first request for network initiated slice selection indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, the first request comprising a service quality level for a second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice, determining based on the service quality level, the second network slice that satisfies the service quality level, and transmitting, towards the PCF or a unified data repository (UDR) a second request for network initiated slice selection, the second request comprising an identifier of the second network slice.

[0048] According to another aspect of an embodiment, the present disclosure provides an apparatus that includes at least one processor, and at least one memory storing instructions of a network exposure function, wherein when the instructions are executed by the at least one processor, cause the apparatus to receive, from an application function or a policy control function (PCF), a first request for network initiated slice selection indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, the first request comprising a service quality level for a second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice, determine based on the service quality level, the second network slice that satisfies the service quality level, and transmit, towards the PCF or a unified data repository (UDR) a second request for network initiated slice selection, the second request comprising an identifier of the second network slice.

[0049] According to another aspect of an embodiment, the present disclosure provides a computer-readable medium storing instructions of a network exposure function, wherein when the instructions are executed by at least one processor of an apparatus, cause the apparatus to receiving, from an application function or a policy control function (PCF), a first request for network initiated slice selection indicating that a first network slice of thecommunication network for a user equipment (UE) is to be replaced, the first request comprising a service quality level for a second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice, determining based on the service quality level, the second network slice that satisfies the service quality level, and transmitting, towards the PCF or a unified data repository (UDR) a second request for network initiated slice selection, the second request comprising an identifier of the second network slice.

[0050] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached figures.

[0052] FIG. l is a schematic diagram showing a communication network in accordance with an aspect of an embodiment.

[0053] FIG. 2 is a schematic diagram showing network slices in a communication network in accordance with an aspect of an embodiment.

[0054] FIG. 3 is a flowchart showing a method in accordance with example embodiments.

[0055] FIG. 4 is a schematic diagram showing components of one or more of the example embodiments.

[0056] FIG. 5 through FIG. 7 are diagrams showing operations in a procedure in accordance with embodiments.DETAILED DESCRIPTION

[0057] For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the examples described herein. The examples may be practiced without these details. In other instances, well-known methods, procedures, and components are not described in detail to avoid obscuring the examples described. The description is not to be considered as limited to the scope of the examples described herein.

[0058] The present disclosure relates to network-initiated slice selection in a communication network, such as a communication network operating in accordance with the 3rdGeneration Partnership Program (3GPP) technical specifications for 5G which may be referred to herein as a “5G network”. Network-initiated slice selection is performed by a policy control function (PCF) of the communication network in response to a request originating from an application function (AF) hosted on an application server to replace a first network slice with a second network slice.

[0059] Reference is first made to FIG. 1, which shows a schematic representation of a communication network 100 that is configured to enable a user equipment (UE) 102 to communicate with one or more application servers (AS) 110 hosting third party application functions (AF) 112 via a data network 104. The communication network 100 comprises a radio access network 106 (e.g., a 5G-RAN otherwise referred to as a next generation (NG)- RAN) and a core network 108 (e.g., a 5G core network (5GC)) that operates based on the 5th generation radio access technology described in the 3rd Generation Partnership Project (3GPP) standard for new radio, which may be referred to herein as the “3GPP 5G standard”.

[0060] The radio access network 106 comprises one or more radio access network (RAN) nodes (otherwise referred to as base stations), such as a gNodeB (gNB). A radio access network node may comprise a central unit (e.g., gNB-CU) and one or more distributed units (e.g., one or more gNB-DUs) linked to the central unit (e.g., gNB-CU) by an Fl interface.

[0061] The core network 108 has a service-based architecture and comprises a plurality of network functions, including control plane network functions (NFs) and user plane network functions. The control plane network functions include an access and mobility function (AMF) 114, a trusted application function (AF) 116, an authentication server function (AUSF) 118, a binding support function (BSF) 120, a network exposure function (NEF) 122, a network slicing selection function (NSSF) 124, a policy control function (PCF) 126, a session management function (SMF) 128, a unified data repository (UDR) 130, and a united data repository (UDM) 134. The user plane network functions include the user plane function (UDF) 132. Other control plane network functions of the core network 108, such as a charging function (CHF), a network repository function (NRF), a network data analytics function (NWDAF), are not shown for ease of illustration. The functionalities of the network functions of the core network are well known to a personskilled in the art and hence are not described in detail. Although only one UPF 132 is shown in FIG. 1, a core network 108 may include a plurality of user plane functions (UPFs).

[0062] The AF 112 may be a non-trusted application function that must communication with the control plane network functions of the network core 108 via the NEF 122, whereas because AF 116 is a trusted AF, it is able to communicate with control plane network functions of the network core 108 directly, i.e., not via the NEF 122, and therefore is schematically shown as inside the core network 108 in FIG. 1.

[0063] Each control plane network function of the core network 108 may provide one or more services to other control plane network functions of the core network 108 and expose their one or more services through service based interfaces (SBIs) that may be implemented as application programming interfaces (APIs). Each control plane NF can also register itself and the services it supports (e.g., the services it offers to other network functions) to the NRF of the core network 108. The NRF may be used by any network function to discover other network functions (or instances of NFs) and the services the other NFs support (e.g., services the other NFs provide). Any control plane NF may consume (e.g., use) the services provided and exposed by another control plane NF. A control plane NF that consumes a service of another network function is generally referred to as a network function service consumer. A control plane network function that provides and exposes one or more of its services is referred to as a network function service producer.

[0064] In order to support different network requirements that may be desired for different third party applications or services, that may have different network requirements, multiple “network slices” may be created on the common physical infrastructure of a communication network, such as the communication network 100 described previously.

[0065] Network slices are virtualized and independent end-to-end networks that are formed by allocating resources of a communication network, such as communication network 100, to different network slices in order to customize each network slice for a particular use or service, for example.

[0066] For example, a network slice may be configured for enhanced mobile broadband (eMBB) communications (e.g., may be configured to have a relatively large bandwidth over the air interface of the communication network to enable large datathroughput), whereas another network slice may be configured for massive machine type communication (mMTC) (e.g., may be configured for communication with a large number of internet of things (loT) devices that periodically transmit data), whereas still another network slice may be configured for ultra-reliable low latency communication (URLLC) (e.g., may be configured with extremely low latency and high reliability, and potentially high security, for use in drone control or remote robotic surgery contexts).

[0067] By allocating resources of the underlying physical communication network, such as communication network 100 described previously, network slices are configured with their own security rules and performance characteristics, within the limits imposed by the underlying physical communication network to meet the network requirements related to the context for which the network slice is created to service.

[0068] Each network slice is uniquely identified by a single-network slice selection assistance information (S-NSSAI). A particular UE, such as UE 102, may be subscribed to one or more network slices of the communication network. Subscription information of a UE is stored in a UDM, such as UDM 134, and the subscription information of a UE includes one or more S-NSSAIs of the network slices to which the UE is subscribed to.

[0069] Before a UE, such as UE 102, requests establishment of a data session (e.g., a protocol unit (PDU) session) in order to effect data transfers between the UE and an application function hosted or running on an application server, such as the AF 112 on the application server 110 described previously, the UE is provided with an identifier (e.g., S- NSSAI) of each respective network slice the UE is allowed to access. An AMF, such as AMF 114, upon receipt of a registration request from the UE, determines which network slices (e.g., at least one of) of the one or more slices the UE subscribed to the UE is allowed to access and provides the identifier of each respective network slice the UE is allowed to access as a list of identifiers of allowed network slices, which is generally referred to as “allowed NS SAI”. The allowed NS SAI may include one or more, up to a maximum of eight, S-NSSAIs to which the UE is subscribed to, and includes at least one default S-NSSAI. In addition, UE route selection policy (URSP) rules are provided to a UE by the PCF, such as PCF 116. The URSP rules includes a set of rules that map a set of applications to one or more S-NSSAI, which inform a UE which network slice and data network name (DNN) the UE should use when requesting the establishment of a PDU session for a certain application. For a particular application, the UE utilizes the mapping set out in the URSP rules and the allowed NSSAI to determine a network slice that ismapped to the application based on the URSP rules and is allowed based on the allowed NSSAI, then requests to establish a PDU session on that network slice. If an application is mapped to multiple S-NSSAI, the URSP rules may be used by the UE to determine which network slice is highest in priority, next highest in priority, and so forth, such that the UE request establishment of a PDU session on the network slice that is highest in priority, according to the URSP rules, and that is included in the allowed NSSAI. For example, if the highest priority network slice is not included in the allowed NSSAI, then the UE will check if the next highest priority network slice is included in the allowed NSSAI, and so forth. The URSP rules may indicate that one of the S-NSSAI is a default network slice of the bundle service and the PDU session is to be established the network slice indicated as a default network slice, provided that that the identifier of the default network slice (e.g., the S-NSSAI of the default network slice) is included in the allowed NSSAI.

[0070] Conventionally, a network slice that a UE is to use for communicating with an application function (e.g., for transmitting data to and for receiving data from) can only be changed in very limited circumstances, for example, when the network slice becomes congested or becomes unavailable. This process for changing network slices is referred to “network slice replacement” and is set out in clause 5.15.19 of V18.0 3GPP TS 23.501.

[0071] In network slice replacement set out in clause 5.15.19 of V18.0 3GPP TS 23.501, either a NSSF, such as NSSF 124, or a PCF, such as PCF 126, of the communication network determines that a network slice that the UE is using has become congested or unavailable based on information received from an 0AM entity or analytics received from a NWDAF). In response to determining that the network slice has become congested or unavailable, the NSSF or PCF, as the case may be, sends a notification to an AMF, such as AMF 114, or the 0AM itself notifies the AMF, that instructs the AMF perform network slice replacement. In response to the notification, the AMF sends a message to the UE that includes a mapping of the S-NSSAI that the PDU session is connected to and an alternative S-NSSAI, and the UE establishes a new PDU session using the alternative S-NSSAI.

[0072] A third party application may have more than one network slice associated with it for providing a service to UEs. The plurality of network slices that are associated with a third party application for providing a service to a UE or group of UEs is referred to as a “bundle service”. Network slices of a bundle service are configured by an operation and maintenance (0AM) entity of a communication network, such as the communicationnetwork 100. The particular network slices that are to be included in a bundle service would be provided in a service level agreement (SLA) between an operator of the communication network and the operator of the third party application.

[0073] As noted above, currently network slice replacement in communication networks is limited to circumstances in which a network slice has been determined to be congested or unavailable by the NSSF, PCF, or an 0AM entity. However, when a third party application function is associated with a bundle service, it may be desirable for the third party application function hosted or running on an application server, such as the application function 112 of the application server 110 described with reference to FIG. 1, to instruct or request a UE to change from using one network slice of the bundle service to another network slice of the bundle service.

[0074] The present disclosure provides for network initiated slice selection that enables a third party application function, such as AF 112, to request that network slice replacement. In this disclosure, network initiated slice selection refers to network slice replacement that is initiated for reasons other than because a network slice is determined to be congested or unavailable as provided in clause 5.15.19 of V18.0 3GPP TS 23.501, for example, because the third party application function has requested network slice replacement.

[0075] FIG. 2 shows a schematic view of an example communication network 200 which includes two network slices 202 and 204 of a bundle service associated with an application function (AF) 220 hosted on an application server 218. As discussed previously, NFs of a core network 206 and RAN resources are allocated to the network slices 202 and 204 such that network slice 202 has a plurality of control plane NFs 208 and a user plane network function, UPF 210, and network slice 204 has a plurality of control plane NFs 212 and a user plane network function, UPF 214. The core network 206 shown in the example communication network 200 has a NEF 216 that is common to both network slices 202 and 204. In other examples, each network slice 202 and 204 may each have its own NEF. The application server (AS) 218 includes (e.g., hosts) an AF 220 and connects to the core network 106 via a data network (DN) 222. AUE 224 communicates on the control plane with the core network 206 via the RANs 226 and 228 and communicates with the AF 220 on the user plane via the RANs 226 and 228 and the UPFs 210 and 214. Although each of the network slices 202 and 204 are shown in FIG. 2 with separate NFs and RANs, it is understood that these may be virtual NFs and RANs that maybe provided by allocating resources of a shared physical infrastructure of a communication network, such as communication network 100 described previously with reference to FIG.1.

[0076] In the example shown in FIG. 2, the identifier of network slice 202 (e.g., S- NSSAI of network slice 202) is included in the allowed NSSAI as the default slice, and there is a PDU session 230 established on the default network slice 202 between the UE 224 and the service provide by the AF 220. At some point, the AF 220 determines that the PDU session 230 should be switched from network slice 202 to network slice 204 and sends a request 232 to the NEF 216, which forwards the request 234 to the control plane NFs of the network slice 202 which then sends the command 236 to the UE 224 to request establishment of a new PDU session on network slice 204.

[0077] In the example shown, the AF 220 is a non-trusted AF 220 to the core network 206, and therefore the request 232 is sent to the NEF 216, where the AF can be authenticated, before the NEF 216 sends the request to a control plane NF at 234. However, in other examples, the AF 220 may an AF trusted by the core network 206, such as AF 112 described previously, in which examples the AF 220 may send the request 232 directly to a control plane NFs 208 rather than via the NEF 216 as shown in FIG. 2.

[0078] Referring now to FIG. 3, a flow chart showing an example method or process of performing network initiated slice selection is shown. The example method or process may be performed by a PCF of a communication network such as, for example, the PCF 126 of the communication network 100 described previously, by a NEF, such as the NEF 122 of the communication network 100 described previously, or by a UDR, such as the UDR 130 of the communication network described previously.

[0079] In examples in which the method or process is performed by the PCF, the PCF optionally sends bundle service information to the AMF at 301. The bundle service information may be obtained by the PCF from a UDM. The bundle service information optionally sent at 301 may include subscription information for the UE that is stored in a UDM that identifies a first network slice and an alternative second network slice as belonging to a bundle service. The bundle service that includes the first network slice and the second network slice may be established based on a SLA between an operator of the communication network and an operator of the third-party application function, as described previously. The bundle service information optionally sent at 301 may indicate that the first network slice is a default or initial network slice of the bundle service.

[0080] Additionally, or alternatively, the bundle service information may optionally indicate that a status of the first network slice of the bundle service is activated and / or that a status of the second network slice of the bundle service is deactivated in cases in which an activation status is stored for the network slices. The bundle service information may optionally be sent at 301 to the AMF during a UE registration procedure in which a UE to which the bundle service information relates registers with the communication network.

[0081] At 302, a first request is received. The first request indicates that a first network slice of a communication network for a UE is to be replaced by another network slice in the bundle service. The first request received at 302 is associated with a request made by an AF, such as AF 112 of AF 114 of the communication network 100 described previously with reference to FIG. 1, to the network core, such as core network 108. The request from the AF may be received by other NF s, and passed along as the first request received at 302, or the request from the AF may be the first request received at 302, which is received directly from the AF.

[0082] In one example, the first request may be received at 302 at a PCF from a UDR or a NEF, such as the UDR 130 and the NEF 122 of the example communication network 100 described previously, or may be received directly from a trusted AF of or hosted on an application server, such as AF 114 described previously. In another example, the first request may be received at 302 at a NEF from a non-trusted AF of or hosted on an application server, such as AF 112 described previously. In another example, the first request may be received at 302 at a UDR from an NEF or directly from a trusted AF of an application server.

[0083] The first request may include information that explicitly identifies a second network slice that is to replace the first network slice. The second network slice may be included in a bundle service that includes the first network slice. The information included in the first request explicitly identifies the second slice may be, for example, an identifier of the second network slice, for example, a S-NSSAI of the second network slice.

[0084] Optionally, when the information included in the first request does not explicitly identify the second slice to be used to replace the first slice, a determination of the second slice may be made at 304. The determination at 304 may be made with reference to the subscription information and / or the bundle service information of the UE.

[0085] In an example, the first request may include a service quality level that analternative network slice (e.g., a second network slice) must satisfy to replace the first network slice. The service quality level may, for example, be indicated as a quality of service parameter, or set of quality of service parameters, that an alternative network slice (e.g., a second network slice) must satisfy if it is to replace the first network slice. The quality of service parameter(s) may indicate that the quality of service of the alternative network slice (e.g., the second network slice) that is to replace the first network slice should be greater than or, alternatively, less than the quality of service of the first slice. In this example, the determination of the alternative network slice (e.g., the second network slice) that is to replace the first network slice may be made based on information indicative of the service quality level that is included in the first request. The information indicative of the service quality level may be utilized to determine an alternative network slice (e.g., a second network slice) of the network slices included in the bundle service that has and / or meets and / or satisfies the service quality level.

[0086] The determination at 304 may be made by the NF that receives the first request, i.e., the PCF, or the UDR, or the NEF as the case may be, by identifying a second network slice included in the subscription information, or the allowed NSS Al, or the bundle service information for the UE that has and / or meets and / or satisfies the service quality level. This determination may be made based on internal configuration of the PCF, or the UDR, or the NEF as the case may be.

[0087] In another example, the NF that receives the first request, i.e., the PCF, or the UDR, or the NEF as the case may be, may make the determination at 304 by sending a further message or request to another NF, the further message or request including the service quality level included in the first request and a request to return the identity of a network slice that is included in the subscription information, or the allowed NSSAI, or the bundle service information for the UE and that has and / or meets and / or satisfies the service quality level, then receiving back a response message in response to the further message or request that identifies the second network slice. For example, the further message or request may include a command instructing the receiving NF to determine a suitable network slice in the subscription information, or the allowed NSSAI, or the bundle service information, for the UE that has and / or meets and / or satisfies the service quality level, the response message may include the S-NSSAI of the determined suitable second slice.

[0088] For example, if the first request is received at the PCF, the PCF may message the UDR or the NEF requesting that a suitable network second slice be identified. If thefirst request is received at the NEF, the NEF may message the PCF or the UDR requesting that a suitable second network slice be identified. If the first request is received at the UDR, the UDR may message the PCF or the NEF requesting that a suitable second network slice be identified.

[0089] At 306, a second request is transmitted to an AMF, such as the AMF 114 of the communication network 100 described previously with reference to FIG. 1. The second request includes a command for the AMF to initiate replacement of the first network slice.

[0090] If the first request received at 302 identified the second network slice that is to replace the first network slice, or if the second slice was optionally determined at 304, then the second request may identify the second network slice. For example, the second request may include the S-NSSAI of the second slice.

[0091] Alternatively, if the first request included information indicative of a service quality level that an alternative network slice that is to replace the first slice must satisfy, and the optional determination of a suitable second network slice was not performed at 304, then the second request may include the information indicative of the service quality level that was included in the first request. In this case, the AMF determines the second network slice that is to replace the first network slice, either by determining, itself, a second slice based on the subscription information, or the allowed NSSAI, or the bundle service information for the UE that has and / or meets and / or satisfies the service quality level, or by sending a further message to another NF requesting that that other NF determine a suitable second network slice based on the subscription information, or the allowed NSSAI, or the bundle service information as described previously.

[0092] In an example, the second request may include an indication that network slice replacement was initiated by an AF of or hosted on an application server. This indication may indicate to the AMF that the network slice replacement is not performed due to congestion or unavailability of the first network slice.

[0093] The AMF may initiate the replacement of the first network slice by messaging the UE and, in some examples, a SMF, such as the SMF 128 described previously, in any suitable manner, for example, by sending control plane signaling (e.g., a NAS message). For example, the AMF may initiate the network slice replacement by messaging the UE and the SMF in accordance with the network slice replacement procedure set out in clause 5.15.19 of V18.0 3GPP TS 23.501.

[0094] In network slice the replacement procedure set out in clause 5.15.19 of V18.0 3GPP TS 23.501 the AMF sends slice replacement information to the UE and to a SMF. The SMF will replace the PDU sessions that are already established by the UE and the UE will request establishment of a new PDU session using the alternative network slice, i.e., the second network slice.

[0095] In some situations, a network slice of a bundle service may also be intended to provide the UE with access to multiple applications, (e.g., access to services provided by multiple applications) which may be referred to as a non-dedicated network slice, or nonapplication specific network slice. In such situations, a direct disabling of non-dedicated or non-application specific network slice by performing network slice replacement, i.e., the first network slice in the above-described method or process, may lead to problems for the other applications that the UE is accessing via that network slice.

[0096] In such cases, the initial or default network slice, or any other non-dedicated or non-application specific network slice of the bundle service (e.g., any network slice that is not specifically assigned to a given application function that provides one or more services), may be aliased to generate a new, dedicated network slice or application specific network slice, that has the same network slice instance (NSI), i.e., the same network properties, as the non-dedicated or non-application specific network slice, but has a unique S-NSSAI. In this case, for the particular application, rather than using the initial or default, non-dedicated or non-application specific network slice, the UE uses the aliased, dedicated or application specific network slice. Then, if a network initiated slice selection process is performed, such as the process described with reference to FIG. 3, the other applications that utilize the bundle services will not be affected by the slice replacement.

[0097] The aliased network slice(s) may be configured through an initial agreement between the operator of the communication network and the operator of the application service that includes virtual alias network slice(s) with the same SLA as the initial or default network slice.

[0098] The PDU session on the first network slice prior to the beginning of the method or process described above with reference to FIG. 3 may have been established by a request sent by the UE based on URSP rules received by the UE during registration of UE with the communication network (e.g., included in the UE context received in a registration accept message sent by the AMF when the registration request of the UE is accepted). The URSP rules may prioritize the first network slice as the initial or defaultnetwork slice over other network slices included in a bundle service.

[0099] In another example, the subscription information of a UE (e.g., the bundle service information for a UE) may be configured to include an activation status for the slices in a bundle service. In this way, what would otherwise be the initial or default network slice would have its activation status indicated as active, and other network slices of the bundle service may have their activation statuses indicated as deactivated. The subscription information may optionally include a flag that indicates which network slice is the initial or default network slice of the bundle service. When subscription information is sent to the UE by the AMF during an initial registration of the UE with the communication network (e.g., the AMF), the AMF can determine the bundle service for the UE and details about the network slices and can configure the activation statuses of the network slices such that initial or default network slice is set to active and the other slices are set to inactive, i.e., via including identifiers (e.g., S-NSSAIs) of active network slices in the allowed NSSAI and excluding deactive identifiers of inactive network slices from the Allowed NSSAI. When a request for network slice selection is received by an UDM, the AMF may be notified and, in response, the UDM changes the information about the statuses of the network slices included in the bundle service in the subscription information to indicate that the first network slice as being inactive (or deactivated) and to indicate that the second network slice that is to replace the first network slice is active.[000100] It is understood that a method or process of network initiated slice selection back to the first network slice from the second network slice may be performed in the same manner as described above if, for example, at a later time the AF determines that the first network slice should be utilized again.[000101] Referring to FIG. 4, a schematic diagram illustrating various physical and logical components of an exemplary apparatus 400 for a communication network in accordance with an embodiment is shown. Although an example embodiment of the apparatus 400 is shown and discussed below, other embodiments may be used to implement examples disclosed herein, which may include components different from those shown. Although FIG. 4 shows a single instance of each component of the apparatus 400, there may be multiple instances of each component shown.[000102] The apparatus 400 includes one or more processors 402, such as a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a dedicated logic circuitry, a graphics processingunit (GPU), a tensor processing unit, a neural processing unit, a dedicated artificial intelligence processing unit, a hardware accelerator, or combinations thereof. The one or more processors 402 may collectively be referred to as a processor 402.[000103] The apparatus 400 also includes one or more memories 104 (collectively referred to as "memory 404"), which may include a volatile or non-volatile memory (e.g., a flash memory, a random-access memory (RAM), and / or a read-only memory (ROM)). The non-transitory memory 404 may store instructions for execution by the processor 402. In some embodiments, instructions 406 of a PCF and / or a UDR and / or a NEF described herein may be stored in the memory 404, and the instructions 406 may be executed by the processor 402 to perform the actions or operations of the methods described herein. The memory 404 may include other instructions for execution by the processor 402, such as instructions of other network functions of a communication network, such as those described above.[000104] The apparatus 400 may also include one or more network interfaces 408 for connecting to a network, such as a data network, or other apparatuses of the core network or the access networks described herein.[000105] In some examples, the apparatus 400 may also include one or more electronic storage units (not shown), such as a solid state drive, a hard disk drive, a magnetic disk drive and / or an optical disk drive. In some examples, one or more datasets and / or modules may be provided by an external memory (e.g., an external drive in wired or wireless communication with the computing system 100) or may be provided by a transitory or non- transitory computer-readable medium. Examples of non-transitory computer readable media include a RAM, a ROM, an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a CD-ROM, or other portable memory storage. The storage units and / or external memory may be used in conjunction with memory 404 to implement data storage, retrieval, and caching functions of the apparatus 400.[000106] The components of the apparatus 400 may communicate with each other via a bus. In some embodiments, the apparatus 400 may be a processing system implementing functionality of the PCF and / or UDR and / or NEF described herein. In some embodiments, the apparatus 400 may be distributed computing system and may include multiple computing devices in communication with each other over a data network, as well as optionally one or more additional components. The various operations described hereinmay be performed by different computing devices of a distributed computing system in some embodiments. In some embodiments, the apparatus 400 a cloud computing system or may be a virtual machine provided by a cloud computing system.[000107] In one example, above described method or process for network initiated slice selection may be performed by the PCF using conventional external parameter provisioning procedure for example, the external parameter provisioning procedure for cases targeting individual UE where UE address set out in clause 4.15.6.9.2 of V18.0 3GPP TS 23.502, the external parameter provisioning procedure for cases targeting individual UE where UE address is known to the AF set out in clause 4.15.6.9.3 ofV18.0 3GPP TS 23.502, the external parameter provisioning for cases targeting individual UE where UE address is not known to the AF set out in clause 4.15.6.9.3 of V18.0 3GPP TS 23.502 sets out, and the external parameter provisioning for cases targeting changes per slice or service set out in clause 4.16.6 of V18.0 3GPP TS 23.502.[000108] Referring now to FIG. 5, operations of a procedure in accordance with an example embodiment are shown in which network initiated slice selection is initiated by an AF 112 of an application server utilizing external parameter provisioning per network slice or service as set out in clause 4.16.6 of 3GPP TS 23.502. Messages are sent between the AF 112, an NEF 502, a UDR 504 at which the UDM 506 stores subscription information, a PCF 508, an AMF 114, a RAN 106 and a UE 102.[000109] In the operations shown, the PCF 508 sends bundle service information to the AMF 114 at 509. The bundle service information sent at 509 may include subscription information for the UE 102 that is stored at the UDM 506 that includes an identifier of network slice 1 and an identifier of an alternative network slice 2 as belonging to a bundle service. The bundle service that includes network slice 1 and network slice 2 may be established based on a SLA between an operator of the communication network and an operator of the application function providing a service, as described previously. The bundle service information sent at 509 may include information that indicates that network slice 1 is a default network slice or initial network slice of the bundle service, and / or may, optionally, include information that indicates status of network slice 1 is active and / or that a status of network slice 2 is inactive. The bundle service information may be sent at 509 as part of a UE registration procedure in which the UE 102 registers with the communication network, which UE registration procedure may include additional steps not shown in FIG. 5, but understood to a person skilled in the art. For example, the AMF 114may provide allowed NSSAI including the active / default slice of the bundle and excluding the alternative slice 2 of the bundle service.[000110] At 501, the UE operates on a first network slice (illustrated as slice 1) at 510 to access a service provided by the AF 112. In other words, at 501, the UE is using a first network slice (e.g., slice 1) to communicate with the AF 112. At 512, the AF creates a network initiated slice selection request. The AF 112 sends the network initiated slice selection request 514 to the NEF 502 as a Nnef_Service Parameter_Create Request, a Nnef Service Parameter Update Request or a Nnef Service Paramter Delete Request.The request 514 may include a service quality level of a network slice for a network slice that is to replace the first network slice as described previously. Alternatively, the request 514 may identify a second network slice (illustrated as slice 2) via which the AF is to provide the service to the UE. For example, the request may include an identifier of a network slice (e.g., S-NSSAI of slice 2). If the request 514 includes a service quality level, the NEF 502 may optionally determine 516 a second network slice (e.g., slice 2) based on the service quality level based on a configuration at the NEF 502 or by querying the UDR 504 for a second network slice (e.g., slice 2) that satisfies the service quality level.[000111] The NEF 502 forwards the network initiated slice selection request to the UDM 506 via a Nudm_SDM_Get message 518. The message 518 may indicate to the UDM 506 that the network (e.g., slice 1) is to be replaced with a second network slice (e.g. slice 2), or can be a command to replace the network (e.g., slice 1) in accordance with the service quality level.[000112] At 520, the specific parameter requested by the AF 112, in this case the network initiated slice selection request, is authorized, i.e., the AF 112 has been determined to be authorized to request network initiated slice selection. If the message 518 includes a service quality level, the UDR 504 may optionally determine 522 a second network (e.g., slice 2) based on the service quality level and the bundle service information of the UE.[000113] Optionally, in examples in which the subscription information stored in the UDR or UDM include an activation status, as described previously, the UDR 504 or UDM 506 may perform a storing and / or updating and / or removing operation 524 to update the subscription information such that the status of network slice 1 (e.g., slice 1) is changed to inactivated and that status of network slice 2 (e.g., slide 2) is changed to activated.[000114] After authorization at 520, the NEF 502 sends a response 524 to the AF 112confirming that the network slice replacement request is authorized using a Nnef Service Parameter Create response if the request 514 was a Nnef Service Parameter Create request, a Nnef Service Parameter Update response if the request was aNnef Service Parameter Update request, or a Nef Service Parameter Delete response if the request 514 was a Nnef Service Parameter Delete request.[000115] The UDR 504 sends a notification (e.g., a Nudr_DM_Notify notification) 526 to the PCF 508. The notification 526 may indicate to the PCF 508 that the network slice (e.g., slice 1) is to be replaced with a second network slice (e.g., slice 2), or can be a command to replace the network slice (e.g., slice 1) in accordance with the service quality level. If the notification 526 includes a service quality level, the PCF 508 may optionally determine 528 a second network (e.g., slice 2) that is to replace the network based on the service quality level and a configuration at the PCF 508 or by sending a query to the UDR 504 or the NEF 502 for a second network slice that satisfies the service quality level.[000116] In response to receiving the notification 526, the PCF 508 sends a network slice replacement message 530 to the AMF 114 that includes a command that instructs or requests the AMF 114 to perform network slice replacement. If the notification 526 identifies the second network (e.g., slice 2) (i.e., the notification includes an identifier of the second network slice (e.g., a S-NSSAI of slice 2)), or if the PCF 508 determines the second network slice (e.g., slice 2) at 528, then the command instructs or requests the AMF 114 to replace the network slice (e.g., slice 1) with the second network slice (e.g., slice 2). Otherwise, the command instructs or requests the AMF to perform network slice replacement of the first network slice (e.g., slice 1), which case the AMF 114 will determine the slice 2 based on internal configuration or by inquiring the UDR 504.[000117] The AMF 114 may initate the replacement of the network slice (e.g., slice 1) using any suitable procedure including, for example, the network slice replacement procedure set forth in clause 5.15.19 of V18.0 3GPP TS 23.501 by providing network slice replacement information to the UE 102 and a SMF. At 532, the UE 102 communicates with the AF using the second network slice (e.g. slice 2) instead of the first network slice (e.g., slice 1) by, for example, after requesting establishment of a new PDU session on the second network (e.g., slice 2_. The UE 102 then communicates with the AF 112 and the AF communicates with the UE 102 (e.g., provides a service to the UE 102) on the second network slice (e.g., slice 2) at 534.[000118] Referring now to FIG. 6, operations of a procedure in accordance with anotherexample embodiment are shown in which network initiated slice selection is initiated by an AF 112 of or hosted on an application server utilizing external parameter provisioning per UE when the UE address is known to the AF as set out in clause 4.15.6.9.2 of V18.0 3GPP TS 23.502. Messages are sent between the AF 112, an NEF 602, a UDR 604 at which the UDM 606 stores subscription information, a PCF 608, an AMF 114, a RAN 106 and a UE 102.[000119] In the operations shown, the PCF 608 optionally sends bundle service information to the AMF 114 at 609, which may be substantially similar to the bundle service information described previously with reference to 509 of FIG. 5 and is therefore not further described here. The UE 102 operates (e.g., is communicating with the AF 112 via a first network slice (illustrated as slice 1) at 610 to access a service provided by the AF 112. At 612, the AF creates a network initiated slice selection request. The AF 112 sends the network initiated slice selection request to the NEF 602 as aNnef AMPolicy Authorization request 614. The request 614 may include a service quality level of a network slice which is to replace the first network slice as described previously. Alternatively, the request may identify a second network slice (illustrated as slice 2) which the AF requests to replace the first network slice the UE is currently operating on. For example, the request may include an identifier of a second network slice (e.g., a S-NSSAI of the second network slice) that the AF is requesting to replace the first network slice.[000120] At 616, the NEF 602 queries a binding state function (BSF) of the communication network, such as BSF 120 of the communication network 100 described previously with reference to FIG. 1, to obtain the identity of PCF of that is serving UE 102.[000121] If the request 614 includes a service quality level, the NEF 602 may optionally determine 618 the second network slice (e.g., slice 2) that is to replace the first network slice based on the service quality level and internal configuration at the NEF 602 or by inquiring the UDR 604.[000122] The NEF 602 sends the network initiated slice selection request to the PCF 608 via a Npcf_AMPolicy Authorization message 620. The message 620 may include an indication to the PCF 608 that the first network slice (e.g., slice 1) is to be replaced with a second network slice (e.g., slice 2), or can be a command to replace the first network slice (e.g., slice 1) in accordance with the service quality level.[000123] After sending the message 620 to the PCF 608, the NEF 602 sends anotification 624 to the AF 112 confirming the request 614 has been authorized by the NEF. The notification may be sent as a Nnef AMPolicy Authorization Notification message.[000124] If the message 620 includes a service quality level, the PCF 608 may optionally determine 626 a second network slice (e.g., slice 2) that is to replace the first network slice based on the service quality level and a configuration at the PCF 608 or by querying the UDR 604 or the NEF 602 for a second network slice (e.g., slice 2) that satisfies the service quality level.[000125] In response to receiving the message 620, the PCF 608 sends a network slice replacement message 628 to the AMF 114 that includes a command that instructs or requests the AMF 114 to perform network slice replacement. If the notification 620 identifies the second network slice (e.g., includes an identifier (e.g., S-NSSAI) of slice 2), or if the PCF 608 determines the second network slice (e.g., slice 2) that is to replace the first network slice at 626, then the message 628 may command the AMF 114 to replace the first network (e.g., slice 1) with the second network slice (e.g., slice 2). The command or instruction sent by the PCF to the AMF 114 may include the identifier (e.g., S-NSSAI) of the second network slice that is to replace the first network slice. Otherwise, the message 628 will command the AMF 114 to perform network slice replacement of the first network slice (e.g., slice 1), in which case the AMF 114 will determine the second network slice (e.g., slice 2) that is to replace the first network slice based on a pre-existing configuration at the PCF or by querying the UDR 604 for a second network slice (e.g., slice 2) that satisfies the service quality level.[000126] The AMF 114 may initiate the replacement of the first network slice (e.g., slice 1) using any suitable procedure including, for example, performing a network slice replacement in accordance with clause 5.15.19 of V18.0 3GPP TS 23.501. At 630, the UE 102 utilizes the second network slice (e.g., slice 2) instead of the first network slice (e.g., slice 1 )by, for example, establishing a new PDU session on the second network slice (e.g., slice 2). The UE 102 operates on the second network slice (e.g., slice 2) at 632. In other words, the UE 102 uses the second network slice (e.g., slice 2) to communicate with the AF 112.[000127] Referring now to FIG. 7, operations of a procedure in accordance with an example embodiment are shown in which network initiated slice selection is initiated by an AF 112 of or hosted on an application server utilizing external parameter provisioning per UE when the UE address is not known to the AF 112 as set out in clause 4.15.6.9.3 of3GPP VI 8.0 TS 23.502. Messages are sent between the AF 112, an NEF 702, a UDR 704 at which the UDM 706 stores subscription information, a PCF 708, an AMF 114, a RAN 106 and a UE 102.[000128] In the operations shown, the PCF 708 optionally sends bundle service information to the AMF 114 at 709, which may be substantially similar to the bundle service information described previously with reference to 509 of FIG. 5 and is therefore not further described here. The UE operates on a first network (illustrated as slice 1) at 710 to access a service associated with the AF 112. In other words, at 710, the UE uses a first network slice (e.g., slice 1) to communicate with AF 112. At 712, the AF generates a network initiated slice selection request. The AF 112 sends the network initiated slice selection request 714 to the NEF 702 as a Nnef_AMInfluence_Create Request or a NeF AMInfluence Update Request. The network initiated slice selection request 714 may include a service quality level of a second network slice which is as described previously. Alternatively, the network initiated slice selection request 714 may include an identifier of a second network slice (e.g., slice 2) which the AF 112 is requesting the network to change to (e.g., the AF 112 is requesting that the UE operate on or use to communicate with the AF 112). If the network initiated slice selection request 714 includes a service quality level, the NEF 702 may optionally determine 716 a second network slice (e.g., slice 2) that is to replace the first network slice based on the service quality level and an internal configuration at the NEF 702 or by querying the UDR 704 a second network slice (e.g., slice 2) that satisfies the service quality level.[000129] The NEF 702 sends the network initiated slice selection request to the UDR 704 as a Nudm DM Create and / or Nudm DM Creat Update Request at 718. The request 718 may indicate to the UDR 704 that the first network slice (e.g., slice 1) is to be replaced with a second network slice (e.g., slice 2), or can be a command to replace the first network slice (e.g., slice 1) with a second network slice (e.g., slice 2) that satisifies the service quality level. At 720, the UDR 704 sends to the NEF 702 a Nudm_DM_Create Response (if the NEF sent a a Nudm DM Create Request at 718) or a Nudm_DM_Update Response (if the NEF sent Nudm_DM_Creat Update Request at 718).[000130] The UDR 704 sends a notification (e.g., a Nudr_DM_Notify notification) at 722 to the PCF 708. The notification sent at 722 may indicate to the PCF 708 that the first network slice (e.g., slice 1) is to be replaced with a second network slice (e.g., slice 2), or can be a command to replace the first network slice (e.g., slice 1) with a second networkslice (e.g., slice 2) that satisfies the service quality level. If the notification 722 includes a service quality level, the PCF 708 may optionally determine 724 a slice 2 based on the service quality level based on internal configuration at the PCF 708 or by inquiring the UDR 704 or the NEF 702.[000131] After notification 722 is sent by the UDR 704 to the PCF 708, the NEF 702 sends a response 726 to the AF 112 confirming the network slice replacement using a Nnef_AMInfluence_Create or a Update Nnef_AMInfluence_Create Response message.[000132] In response to receiving the notification 722, the PCF 708 sends a network slice replacement message 728 to the AMF 114 that includes a command that instructs or requests the AMF 114 to initiate network slice replacement. If the notification 728 identifies the second network slice (e.g., includes an identifier of the second network slice, such as a S-NSSAO of the second network slice (e.g., slice 2), or if the PCF 708 determines the second network slice (e.g., slice 2) that is to replace the first network slice at 724, then the message 728 may command the AMF 114 to initiate replacement of the first network slice with the second network slice (e.g., initiate replacement of slice 1 with slice 2). Otherwise, the message 728 will include a command which indicates to the AMF to initiate network slice replacement of the first network slice (e.g., slice 1), in which case the AMF 114 will determine the second network slice (e.g., slice 2) of, for example, the bundle service that is to replace the first network slice (e.g., slice 1) based on a configuration at the AMF 114 or by querying the UDR 704 for a second network slice (e.g., slice 2) that satisfies the service quality level.[000133] The AMF 114 may initiate replacement of the first network slice (e.g., slice 1) using any suitable procedure including, for example, the network slice replacement set forth in clause 5.15.19 of V18.0 3GPP TS 23.501. At 730, the UE 102 operates on (e.g., utilizes) the second network slice (e.g. slice 2) instead of the first network slice (e.g., slice 1) to communicate with the AF 112 by, for example, requesting establishment of a new PDU session on the second network slice (e.g., slice 2). The UE 102 operates on (e.g., utilizes) the second network slice (e.g., slice 2) at 732 to communicate with the AF 112.[000134] Although the example embodiments described with reference to FIG. 5 through FIG. 7 include a request for network slice replacement being received at a NEF from an AF 112, it is understood that in such example embodiments, the requests could be from a “trusted application function” or “trusted AF”, such as AF 116 of the core network 108 described previously, in which case such requests would not be received at a NEF, butdirectly from the trusted AF to another control plane NF that the NEF is shown in the example embodiments in FIG. 5 through FIG. 7 sends the request to including, for example, the UDM 506 in example shown in FIG. 5, or the PCF 608 in the example shown in FIG. 6, and the UDR 704 in the example shown in FIG. 7.[000135] Embodiments of the present disclosure enable an application function (AF) of a communicate network to initiate a change from a first network slice to a second network slice of a communication network in order to improve the quality of service of a service that is provided by the AF to UEs via the communication network. For example, the AF may request initiating a change of network slices to load balance when, for example, the amount of data being transmitted in providing the services to the UEs using different network slices form a bundle service is unbalanced.[000136] Embodiments of the present invention including functions, processes, and operations, may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this application, a “memory” or “computer-readable medium” may be any non-transitory media or means that contains, stores, communicates, propagates or transports the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.[000137] Reference to, where relevant, “computer-readable medium”, “computer program product”, “tangibly embodied computer program” etc., or a “processor” or “processing circuitry” etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialized circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc.[000138] As used in the present disclosure, the term “circuitry”, for example in the hardware processing circuitry that may be used to implement the UPF or the SMF inaccordance with certain embodiments of the present disclosure, may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (iii) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in the present disclosure, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.[000139] The functions, processes, and operations described herein may be performed in a different order, or may be performed concurrently with each other, or a combination thereof. Furthermore, one or more of the functions, processes, and operations may be optional or may be combined. It will be appreciated that the flow diagram shown in FIG. 3 and the various embodiments described with reference to FIG. 3, are examples only. Various operations and processes depicted therein may be omitted, may be reordered, may be combined, or a combination of reordered and combined.[000140] Advantageously, embodiments of the present disclosure provide for network initiated slice selection in which an AF is able to initiate slice replacement such that slice replacement may be performed for reasons other than that a slice is congested or is unavailable. Some embodiments of the present disclosure rely on existing procedures, such as external parameter provisions of the current 3GPP standard for 5G, and without requiring dynamic modifications of the URSPs, such that network initiated slice selection may be performed on existing UEs.[000141] The scope of the claims should not be limited by the preferred embodiments setforth in the examples but should be given the broadest interpretation consistent with the description as a whole.

Claims

Claims1. A method performed by a policy control function (PCF) for performing network initiated slice selection, the method comprising: receiving a first request indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, wherein the first request includes information associated with a second network slice to replace the first network slice, and wherein the first request is associated with a request for network initiated slice selection from an application function (AF); and transmitting, a second request toward an access management function (AMF) of the communication network for the AMF to initiate replacement of the first network slice with the second network slice.

2. The method according to claim 1, wherein information associated with the second network slice comprises a service quality level for the second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater or less than a quality of service of the first network slice.

3. The method according to claim 2, wherein the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

4. The method according to claim 2 or 3, the method further comprising determining based on the service quality level, the second network slice that satisfies the service quality level.

5. The method according to claim 4, wherein determining the second network slice comprises: transmitting a third request by the PCF to a network exposure function (NEF) or a unified data repository function (UDR) that includes the service quality level and requests that the NEF or UDR provide to the PCF the second network slice that satisfies the service quality level; and receiving a response to the third request from the NEF or UDR that identifies the second network slice that satisfies the service quality level.

6. The method according to claim 1, wherein information associated with the second network slice comprises an identifier of the second network slice that is to replace the first network slice determined by a network exposure function or by a unified data repository entity of the communication network or by the application function.

7. The method according to any one of claims 4-6, wherein the second request transmitted towards the AMF includes the identifier of the second network slice that is to replace the first network slice.

8. The method according to any one of claims 2 or 3, wherein the second request transmitted by the PCF to the AMF includes the service quality level for the second slice that is to replace the first slice.

9. The method according to any one of claims 1 to 8, wherein the second request message transmitted by the PCF to the AMF indicates that the network slice replacement was initiated by the AF.

10. The method according to any one of claims 1 to 9, wherein the first network slice is included in a bundle service, and the second network slice is another network slice included in the bundle service.

11. The method according to any one of claims 1 to 10, wherein the first request is received by the PCF from a network exposure function (NEF) of the communication network, or a unified data management repository (UDR) of the communication network, or the AF.

12. A method performed by an application function, the method comprising: providing a service to a user equipment via a first network slice of a communication network; sending, to the communication network, a request to replace the first network slice, wherein the request includes information comprising a service quality level associated with a second network slice that is to replace the first network slice; and in response to receiving, from the communication network a notification that includes an indication that the first network slice was replaced with a second network sliceof the communication network, providing the service to the user equipment via the second network slice.

13. The method according to claim 12, wherein the service quality level for the second network slice indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice.

14. The method according to claim 13, wherein the service quality level comprises a set of quality of service parameters that the second network slice is to satisfy.

15. A method performed by a network exposure function of a communication network, the method comprising: receiving, from an application function or a policy control function (PCF), a first request for network initiated slice selection indicating that a first network slice of the communication network for a user equipment (UE) is to be replaced, the first request comprising a service quality level for a second network slice, wherein the service quality level indicates that a quality of service of the second network is to be greater than or less than a quality of service of the first network slice; determining based on the service quality level, the second network slice that satisfies the service quality level; transmitting, towards the PCF or a unified data repository (UDR) a second request for network initiated slice selection, the second request comprising an identifier of the second network slice.

16. An apparatus comprising: at least one processor; at least one memory storing instructions of a policy control function (PCF), wherein when the instructions are executed by the at least one processor, cause the apparatus to perform the method of any of claims 1 to 11.

17. An apparatus comprising: a policy control function (PCF) configured to perform the method of any of claims 1 to11.

18. An apparatus comprising: at least one processor; at least one memory storing instructions of application function, wherein when the instructions are executed by the at least one processor, cause the apparatus to perform the method of any of claims 12 to 14.

19. An apparatus comprising: an application function configured to perform the method of any of claims 12 to 14.

20. An apparatus comprising: at least one processor; at least one memory storing instructions of a network exposure function, wherein when the instructions are executed by the at least one processor, cause the apparatus to perform the method of claim 15.

21. An apparatus comprising: a network exposure function configured to perform the method of claim 15.

22. A computer program comprising instructions, wherein when the computer program is run on an apparatus, the apparatus is caused to perform the method of any of claims 1 to 15.

23. A computer-readable medium comprising instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform the method of any of claims 1 to 15.

Images