Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
NETWORK SLICE MANAGEMENT
Document Type and Number:
WIPO Patent Application WO/2018/089634
Kind Code:
A1
Abstract:
Embodiments of the present disclosure describe methods and apparatuses for network slice creation and management.

Inventors:
YAO YIZHI (US)
CHOU JOEY (US)
Application Number:
PCT/US2017/060861
Publication Date:
May 17, 2018
Filing Date:
November 09, 2017
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
INTEL IP CORP (US)
International Classes:
G06F9/50
Domestic Patent References:
WO2015191300A12015-12-17
Foreign References:
US20120233302A12012-09-13
Other References:
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)", 3GPP STANDARD; 3GPP TR 23.799, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V1.1.0, 31 October 2016 (2016-10-31), pages 1 - 104, XP002777525
Attorney, Agent or Firm:
MAKI, Nathan R. et al. (US)
Download PDF:
Claims:
CLAIMS

What is claimed is:

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a network slice management function ("NSMF") to:

process a request to create a network slice instance;

determine a network slice template associated with the network slice instance; and create the network slice instance based on the network slice template. 2. The one or more computer-readable media of claim 1, wherein the instructions, when executed, further cause the NSMF to:

select a network slice class from a plurality of network slice classes based on the request.

3. The one or more computer-readable media of claim 2, wherein individual network slice classes of the plurality of network slice classes support individual service categories.

4. The one or more computer-readable media of claim 2, wherein the instructions, when executed, further cause the NSMF to maintain a table of the plurality of network slice classes.

5. The one or more computer-readable media of any one of claims 1-4, wherein the instructions, when executed, further cause the NSMF to:

query available resources; and

determine, based on the available resources, whether a new network function or a modified network function is desired to support the network slice instance.

6. The one or more computer-readable media of claim 5, wherein the available resources include available physical resources and to query available resources the instructions, when executed, further cause the NSMF to:

query a manager for available resources, the manager to include a network manager, a domain manager, or an element manager.

7. The one or more computer-readable media of claim 5, wherein the available resources include virtualized resources and to query available resources the instructions, when executed, further cause the NSMF to:

query a network function virtualization orchestrator for available resources.

8. The one or more computer-readable media of any one of claims 1-4, wherein the instructions, when executed, further cause the NSMF to:

determine, based on the network slice template, a network function to support the network slice instance, the network function to be a physical network function or a virtual network function; and

determine requirements of an interface between the network function and the network slice instance.

9. The one or more computer-readable media of claim 8, wherein the instructions, when executed, further cause the NSMF to:

determine a security protection mechanism of the interface.

10. The one or more computer-readable media of any one of claims 1-4, wherein the instructions, when executed, further cause the NSMF to:

determine whether an existing network function is suitable to be a common network function for the network slice instance.

11. The one or more computer-readable media of any one of claims 1-4, wherein the instructions, when executed, further cause the NSMF to:

determine whether an existing network function can be upgraded to support the network slice instance.

12. The one or more computer-readable media of any one of claims 1-4, wherein the network slice template includes a common physical network function; a specific physical network function; a common virtualized network function; a specific virtualized network function; a supporting function; a relationship between a plurality of network functions; or a relationship between the network function and the supporting function.

13. An apparatus to implement a network slice management function ("NSMF"), the apparatus comprising:

network interface circuitry to receive a request to create a network slice instance; and processing circuitry, coupled with the network interface circuitry, to configure one or more network functions to support the network slice instance based on the request.

14. The apparatus of claim 13, wherein the processing circuitry is to determine a network slice template associated with the network slice instance and identify the one or more network functions based on the network slice template.

15. The apparatus of any one of claim 14, wherein the one or more network functions include a physical network function or a virtual network function.

16. The apparatus of claim 14, wherein the processing circuitry is to:

determine requirements of an interface between a network function of the one or more network functions and the network slice instance.

17. The apparatus of any one of claims 14-16, wherein the processing circuitry is further to:

generate a request to determine available resources;

cause the network interface circuitry to transmit the request;

receive a response to the request from the network interface circuitry, the response to include an indication of the available resources; and

determine, based on the available resources, whether a new network function or a modified network function is desired to support the network slice instance.

18. The apparatus of claim 17, wherein the available resources include available physical resources and the network interface circuitry is to: transmit the request to a network manager, a domain manager, or an element manager.

19. The apparatus of claim 17, wherein the available resources include virtualized resources and the network interface circuitry is to: transmit the request to a network function virtualization orchestrator.

20. The apparatus of any one of claims 14-16, wherein the processing circuitry is to: determine whether an existing network function is suitable to be a common network function for the network slice instance or whether an existing network function can be upgraded to support the network slice instance.

21. An apparatus to implement a trace management function, the apparatus comprising: means for generating a trace session activation request that includes an indication of a network slice instance;

means for transmitting the trace session activation request to a network function associated with the network slice instance; and

means for receiving a trace data report from the network function.

22. The apparatus of claim 21, wherein the trace session activation request includes trace control and configuration parameters that includes a network slice instance identity to indicate the network slice instance.

23. The apparatus of claim 21 or 22, wherein means for transmitting the trace session activation request is to transmit the transmit the trace session activation request to the network function through an element manager.

24. The apparatus of claim 21 or 22, wherein the apparatus provides a network manager or network slice management function.

25. The apparatus of claim 21 or 22, wherein generating and transmitting the trace session activation request is part of a management activation procedure for a signaling activation procedure.

Description:
NETWORK SLICE MANAGEMENT

Related Application

This application claims priority to U. S. Provisional Application number 62/421 ,101 filed November 11 , 2016 and to U. S. Provisional Application number 62/453,381 filed February 1, 2017. The specifications of both applications are hereby incorporated by reference in their entireties.

Field

Embodiments of the present disclosure generally relate to the field of networks, and more particularly, to apparatuses, systems, and methods for managing network slices in cellular networks.

Background

Network slicing enables an operator to create networks customized to provide optimized solutions for different market scenarios that demand diverse requirements in, for example, the areas of functionality, performance, and isolation.

Brief Description of the Drawings

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates a network in accordance with some embodiments.

Figure 2 illustrates a network architecture in accordance with some embodiments.

Figure 3 illustrates a network architecture in accordance with some embodiments.

Figure 4 illustrates a network architecture in accordance with some embodiments.

Figure 5 illustrates an example operation flow/algorithmic structure in accordance with some embodiments.

Figure 6 illustrates an example operation flow/algorithmic structure in accordance with some embodiments.

Figure 7 illustrates a network slice management architecture in accordance with some embodiments.

Figure 8 illustrates a message flow diagram in accordance with some embodiments.

Figure 9 illustrates an electronic device in accordance with some embodiments. Figure 10 illustrates hardware resources in accordance with some embodiments. Detailed Description

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure.

Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed or described operations may be omitted in additional embodiments.

For the purposes of the present disclosure, the phrases "A or B," "A and/or B," and "A/B" mean (A), (B), or (A and B).

The description may use the phrases "in an embodiment," or "in embodiments," which may each refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," and the like, as used with respect to embodiments of the present disclosure, are synonymous.

Various embodiments describe a network slice management function ("NSMF") to support lifecycle management, configuration management, performance management, fault management, or security management for network slicing. Further embodiments also describe solutions to support subscriber or equipment trace for a network slice instance and network management solutions to support radio access network ("RAN") resource management between network slices.

Figure 1 illustrates a network 100 in accordance with various embodiments. The network 100 may be a next generation ("NG") system having a RAN 104, which may be an NG RAN that implements a new radio ("NR") access technology, and other network components part of, for example, an NG core network. The network 100 may be divided into three network slices: network slice A; network slice B; and network slice C. Each network slice may include common control plane ("CP") network functions ("NFs"), slice-specific CP NFs, and slice-specific or common user plane ("UP") NFs.

An NF may represent a pre-defined processing function in the network 100. An NF may be associated with defined functional behavior and interfaces. An NF may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or a virtualized function instantiated on appropriate physical resources.

A common CP NF may be a CP NF that is shared by more than one network slice. A common CP NF may include, for example, a mobility management ("MM") function, an authentication and authorization ("AU") function, and a non-access stratum ("NAS") proxy function.

A slice-specific CP NF may be a CP NF that is located on a non-shared network slice part. A slice-specific CP NF may be, for example, a session management ("SM") NF that is responsible for handling session-level SM context.

The NG RAN 104 may be coupled with a slice selection function ("SSF") 108 and common CP NFs 112. The SSF 108 and the common CP NFs 112 may be coupled with a subscriber repository 116. The SSF 108 may handle an initial attach request and new session establishment request from a user equipment ("UE"). The SSF 108 may select an appropriate network slice for a requesting UE based on the UE's subscription information, usage type, service type, or capabilities. The UE's subscription information and related information may be stored in the subscriber repository 116.

Network slice A may include the RAN 104, the common CP NFs 112, CP NFs for slice A 120 and UP NFs for slice A 124. Network slice B may include the RAN 104, the common CP NFs 112, CP NFs for slice B 128 and UP NFs for slice B 132. Network slice C may include the RAN 104, common CP NFs 136, CP NFs for slice C 140 and UP NFs for slice C 144.

Unless as otherwise described herein, the network 100 may be similar to the network described in Figure 6.1.1.1-1 of 3 rd Generation Partnership Project ("3GPP") Technical Report ("TR") 23.799 vl.1.0 (2016-10-31).

The network slices may be concepts used to describe system behavior that is implemented by a network slice instance ("NSI"). Management of the NSIs may be performed by an NSMF implemented as shown in, for example, Figures 2-4 in accordance with some embodiments. Figure 2 illustrates a network architecture 200 in accordance with some embodiments. The network architecture 200 may include an NFV management and orchestration (MANO) system 204 coupled with core-network ("CN") service system 208 as shown. Each module shown in the network architecture 200 may represent a module designed to provide discrete operations, including, for example, management, orchestration, and

communication operations, that are to facilitate provision of network services by the CN service system 208. As will be described, network service may be achieved through any combination of virtual network functions ("VNFs") and physical network functions ("PNFs"), which may be chained together.

The network service may be any type of service provided by network functions including core-network functions of a cellular network such as, but not limited to, a mobility management entity ("MME"), a packet data network gateway ("PGW"), a serving gateway ("SGW"), a policy charging and rules function ("PCRF"), a home location register ("HLR"), a visitor location register ("VLR"), a home subscriber server ("HSS"), a serving general packet radio service support node ("SGSN"), a gateway general packet radio service support node ("GGSN"), etc.

The modules of the network architecture 200 will be briefly described. However, unless otherwise described, operation of the modules of the network architecture 200 may be consistent with descriptions in European Telecommunications Standards Institute, ETSI, Group Specification, GS, NFV-Management and Orchestration, MAN, 001 VI .1.1 (2014- 12) or 3GPP TS 28.500 vl.2.0 (2016-09-20).

In general, various computer systems may be adapted to provide the operations described with respect to the modules of the architecture 200. Some specifically adapted computer systems are described herein with respect to modules implementing operations of various embodiments. However, operations described with respect to other modules may be performed by similar computer systems adapted based on the objectives and

implementation details associated with the particular modules.

The modules of the network architecture 200 are shown coupled with one another by various reference points. In some embodiments, specific implementations of the network architecture 200 may result in some of the modules being combined with others. In such cases, the reference point coupling the combined modules may be internalized.

In general, the NFV-MANO system 204 may provide management and orchestration operations to facilitate provision of virtualized network functions by the CN service system 208. The NFV-MANO system 204 may include a network function virtualization orchestrator ("NFVO") 212 coupled with a virtual network function manager ("VNFM") 216. While not specifically shown, the NFVO 212 may be further coupled with a number of data repositories such as, but not limited to, a network service ("NS") catalog, a virtual network function ("VNF") catalog, a network function virtualization ("NFV") instances repository, and an NFV infrastructure ("NFVI") resources repository.

The NFVO 212 may provide network service orchestration by coordinating the lifecycle of VNFs that jointly realize a network service. This may include managing the associations between different VNFs and the topology of a network service ("NS") and VNF forwarding graph descriptors ("VNFFGs") associated with the network service. It may be desirable for the NFVO 212 to be aware of all the resources available for reservation allocation at NFVI for an NS instance.

The NFVO 212 may be coupled with the VNFM 216 by an Or-Vnfm reference point. The VNFM 216 may be responsible for managing lifecycles of VNF instances. In various embodiments, the VNFM 216 may provide traditional management operations such as, but not limited to, fault management, configuration management, accounting management, performance management, and security management. The VNFM 216 may also provide scaling operations to change a configuration of virtualized resources. The scaling operations may include, but are not limited to, scaling up (for example, adding a central processing unit ("CPU")), scaling down (for example, removing a CPU or releasing some virtualized resources), scaling out (for example, adding a new virtual machine ("VM") instance), and scaling in (for example, shutting down and removing a VM instance).

The VNFM may be coupled with a virtualized infrastructure manager ("VIM") 220 by a Vi-Vnfm reference point. The VIM 220 may control and manage the NFVI resources, for example, compute, storage, and network resources used for NFV. In some embodiments, the VIM 220 may manage only a subset of one or more types of NFVI resources (for example, compute-only, storage-only, or networking-only). In other embodiments, the VIM 220 may manage a plurality of types of NFVI resources.

In addition to being coupled with the VNFM 216, the VIM 220 may also be coupled with the NFVO 212 by an Or-Vi reference point.

The CN system 208 may include an operations support system/business support system ("OSS/BSS") 236, which may be composed of one or more devices to manage and orchestrate legacy systems by providing functions such as, but not limited to, network inventory, service provisioning, network configuration, and fault management. The OSS/BSS 236 may have full end-to-end visibility of services provided by legacy network systems.

The OSS/BSS 236 may be coupled with the NFVO 212 by an Os-Ma-nfvo reference point. The OSS/BSS 236 may include, or be coupled with, a network manager ("NM") 238 that is coupled with one or more element managers ("EMs") including, for example, EM 244, EM 248, and EM 252. The NM 238 may primarily deal with network configuration (for example, configuring network routing tables), testing, and traffic analysis. The NM 238 may provide a package of end-user functions with the responsibility for the management of the network supported by the EMs. The NM 238 may support fault, configuration, accounting, performance, and security ("FCAPS") management and service (for example, data service, voice service, etc.) functions of the network architecture 200. The NM 238 may initiate lifecycle management of NSs and VNFs through interaction with the NFV- MANO 204.

The EMs may be responsible for FCAPS management functionality for associated network functions and may participate in lifecycle management functionality for VNFs. Each EM may be associated with one or more network functions. As shown, EM 244 may be included in a network element ("NE") 256 that provides a physical network function ("PNF"); EM 248 may be included in a domain manager ("DM") 260; and EM 252 may be included in a VNF 264. The EM 248 may be associated with a PNF provided by NE 268 and may also be associated with VNF 272.

The VNFs 264 and 272 may be software implementations of network functions that are capable of running on NFVI 276. The NFVI 276 may represent the hardware (for example, compute, storage, and networking circuitry) and software (for example, hypervisors) components that collectively provide the infrastructure resources where the VNFs 264 and 272 are deployed. In some embodiments, the NFVI 276 may also include partially virtualized NFs that have part of their functionality virtualized and other parts embodied in a PNF (for example, built in silicon) due to, for example, physical constraints or vendor design choices.

The NFVI 276 may be coupled with the VIM 220 by an Nf-Vi reference point. The Nf-Vi reference point may support the exchange of VM management messages to provide/update VM resources allocation, migrate/terminate VMs, manage connections between VMs, etc. The EMs associated with VNFs, and the VNFs themselves, may be coupled with the VNFM 216 in order to collaborate with the VNFM 216 to perform functions that rely on exchanges of information regarding the NFVI resources associated with the VNF 264. The EMs may be coupled with the VNFM 216 by a Ve-Vnfm-em reference points and the VNFs may be coupled with the VNFM 216 by Ve-Vnfm-vnf reference points. The Ve- Vnfm-vnf reference point may support the exchange of messages that provide VNF instantiation, queries, updates, scaling, verification, configuration, etc.

In this embodiment, the NSMF 240 is included in the NM 238. Implementing the NSMF 240 in the NM 238 may be desired if NFs composing a network slice instance are from different vendors. In this manner, the NSMF 240 may be capable of managing the lifecycle of NSIs distributed throughout a variety of EMs controlled by the NM 238. Figure 3 illustrates a network architecture 300 in accordance with some embodiments. The network architecture 300 may be similar to network architecture 200 with like-named components being interchangeable. However, in network architecture 300, the NSMF 340 may be located in DM 360, rather than in NM 338. Locating the NSMF 340 in the domain manager 360 may be desirable if all of the NFs composing an NSI are from a common vendor.

Figure 4 illustrates a network architecture 400 in accordance with some embodiments. The network architecture 400 may be similar to network architecture 200 with like-named components being interchangeable. However, in network architecture 400, the NSMF 440 may be located in a network slice manager and orchestrator ("NSMO") 442, rather than in the NM 438. The NSMO 442 may be coupled with an NM 438 and NFVO 412.

Integrating the NSMF 440 into the NSMO 442 can reduce the interactions between NM 438 and NFVO 412 and improve the reliability and efficiency of the whole system.

Figure 5 illustrates in operation flow/algorithmic structure 500 in accordance with some embodiments. The operation flow/algorithmic structure 500 may be employed by an NSMF, for example, NSMF 240, 340, or 440, to support NSI management as described herein. In particular, in accordance with some embodiments, the operation

flow/algorithmic structure may be employed by an NSMF to create an NSI.

The operation flow/algorithmic structure 500 may include, at 504, processing a request to create an NSI. In some embodiments, the NSMF may receive the request from an operator or a management entity. For example, an operator may determine that a UE is to consume services related to a particular service category associated with a network slice. The operator may then perform a manual operation to request an NSI be created to facilitate provision of the services. Alternatively, the NSMF may automatically generate a request to create the NSI. In various embodiments, the request may include information associated with the NSI. For example, the request may include an NSI identifier, an indication of a service category to be running on the NSI, capacity requirements, coverage (for example, a serving area), performance requirements (for example, throughput per user/device, end-to-end ("E2E") latency, etc.), etc. In some embodiments, the request may include an NSI identifier that identifies the NSI and indicates, for example, a relationship between the NSI and a network service instance.

The operation flow/algorithmic structure 500 may further include, at 508, determining a network slice template associated with the NSI. In some embodiments, the NSMF may obtain the network slice template from a local repository. In other embodiments, the NSMF may generate and send a request to another device to receive the network slice template from a remote repository. In various embodiments, the network slice template that is determined by the NSMF may be uploaded to the NSMF based on a specific request from the NSMF. In alternative embodiments, the network slice template that is determined by the NSMF may be uploaded to the NSMF without a request from the NSMF.

The network slice template, which may also be referred to as a network slice topology, may include information that may be used to create a network slice instance. For example, the network slice template may include information about an NSI including, for example: common physical network functions and specific network functions; common virtualized network functions and specific virtualized network functions; additional supporting functions (for example, security functions); relationships between network functions; and relationships between network functions and supporting functions.

The operation flow/algorithmic structure 500 may further include, at 512, creating the NSI based on the network slice template. As will be described in further detail below, creation of the NSI may include determining which existing network functions may be modified to be used with the new NSI and which network functions need to be installed or otherwise created. The NSMF may query one or more network components to make these determinations.

Upon determining the existing network functions to be modified and the network functions to be installed, the NSMF may send requests to various network components to configure the network functions to support the NSI.

The operation flow/algorithmic structure 500 may further include, at 516, responding to the requestor with result of creation of the NSI. The response may indicate that the NSI has been successfully created and is ready to support UE services. Alternatively, the response may indicate that the NSI has not been successfully created and may include one or more error codes or other reasons that prevented the successful creation of the NSI. Figure 6 illustrates an operation flow/algorithmic structure 600 in accordance with some embodiments. The operation flow/algorithmic structure 600 may be employed by an NSMF, for example, NSMF 240, 340, or 440, to support NSI management as described herein. In particular, in accordance with some embodiments, the operation

flow/algorithmic structure may be employed by an NSMF to create an NSI. Some or all of operation flow/algorithmic structure 600 may be implemented within, or as a supplement to, operation flow/algorithmic structure 500.

The operation flow/algorithmic structure 600 may include, at 604, processing a request to create an NSI. The processing of the request at 604 may be similar to processing of the request at 504 described with respect to Figure 5.

The operation flow/algorithmic structure 600 may further include, at 608, determining one or more network functions required to support the NSI. The NSMF may determine the network functions required to support the NSI based on the information included in the request received at 604. Additionally/alternatively, the NSMF may determine the network functions required to support the NSI based on a network slice template such as that described above with respect to 508 of Figure 5.

In some embodiments, determination of the network function required to support the NSI may be based on a network slice class of the NSI.

In some embodiments, the NSMF may maintain a table of network slice classes with individual network slice classes to support individual service categories. The table may provide, for each network slice class, an index, a service category label, common NF classes, specific NF classes, end-to-end (E2E) interface requirements, and security requirements. Table 1 is an example of a table of network slice classes in accordance with some embodiments.

1 Auto-driving • Session • SGW - Throughput per Isolated from Internet

Management Release user/device: 50M bps

Entity - • NR Release E2E latency: 1 ms

Release • PDG -

• Mobility Release

Management

Entity -

Release

• Distributed

Unit of NR - version

2 Ultra- • Session • Mobility Throughput per Fully isolated by broadband Management Management user/device: 50G bps firewall with other service Element Entity - E2E latency: 15 ms Network slices

(SME) Release

Release • SGW -

Release

• NR Release

• PDG -

Release

3 City • Session • SGW - Throughput per Isolated from Internet

Surveillance Management Release user/device: 1M bps

Element • NR Release - E2E latency: 20 ms

(SME) • PDG -

Release Release

Table 1

In some embodiments, the NSMF may select a network slice class from a plurality of network slice classes of Table 1 based on the information in the request or network slice template. The selected network slice class may include the NFs required to support the NSI requested at 604. The NFs may be provided as PNFs or VNFs.

In some embodiments, the NSMF may determine requirements of interfaces between the NFs and the NSI. The requirements may be, for example, related to an interface

bandwidth, tolerable latency, packet loss rate, etc.

In some embodiments, the NSMF may determine security protection mechanisms of the interfaces between the NFs and the NSI. The security protection mechanisms may include, for example, a firewall type and deployment design or special hardware/firmware security capabilities.

The interface requirements and security protection mechanisms may be determined based on information in the request, table of network slice classes, network slice template, etc. The operation flow/algorithmic structure 600 may further include, at 612, querying available resources. After receiving the request at 604 and determining the NFs needed to support the NSI, the NSMF may generate and send one or more queries to determine resources available to be used for the NSI.

The NSMF may query one or more EMs for resource information about available physical resources used to, for example, deploy PNFs. The EMs may be queried directly by the NSMF. Alternatively, the NSMF may send queries to the EMs through an NM.

While embodiments discuss the NSMF querying an EM about available physical resources, other embodiments may use queries to other managers, for example, DM or NM.

As used herein, a manager (for example, EM, DM, or NM) may include the manager itself or its related function. For example, a reference to a network manager may include a network management function, a network function manager, a network function management function, etc.

The resource information queried and returned may include information about an amount of each type of resource, supported NFs (with versions), security features supported by hardware/firmware of the resources, etc. The available physical resources may be spare resources that are not currently being used. Alternatively, the available physical resources may be resources that are used, but still include some spare capacity that can be used for a new or upgraded network function.

The NSMF may query one or more NFVOs for resource information about available virtualized resources used to, for example, deploy VNFs. The resource information queried and returned may include information about each type of resource (for example, compute, storage, or networking resources), security features supported by

hardware/firmware of the resources, etc.

The operation flow/algorithmic structure 600 may further include, at 616, determining whether new or modified network functions are desired to provide the network function requested at 604.

In some embodiments, the NSMF may check to determine whether any existing network functions (for example, VNFs or PNFs) are suitable to be used as a common network function for the NSI. In some embodiments, the existing network functions may be suitable to be used as a common network function for the NSI without modification. In other embodiments, the existing network functions may need to be upgraded or scaled out in order to be suitable to be used as a common network function for the NSI. The NSMF may generate and send one or more queries to a DM or an NM, which may return information about existing network functions and their suitability for use as a common network function.

The NSMF may determine that new NFs are desired to provide any common NFs for which a suitable existing network function is not available. Furthermore, the NSMF may determine that new NFs are desired to provide any slice-specific NFs needed for the NSI.

The operation flow/algorithmic structure 600 may further include, at 620, acquiring software images of any new or modified network functions determined to be desired at 616. In various embodiments, the software image may be a serialized copy of an entire state of a network function (for example, a PNF or VNF) stored in a non-volatile form such as a file. The software image may be acquired from a vendor, repository, EM, etc. The NSMF may acquire a software image of a network function to be created or upgraded by generating and sending a request to a manager, for example, an NM, a DM, or an EM. The NSMF may also acquire software images of any security functions (for example, firewalls) that are to be used to support the new or modified network functions, either directly or through their interfaces. The NSMF may acquire the software images of the security functions from a repository managed by a network component or from security function providers such as, for example, a security manager.

The NSMF may acquire a software image of a security function to be created or upgraded by generating and sending a request to a manager, for example, an NM or a security manager.

The operation flow/algorithmic structure 600 may further include, at 624, creating the NSI requested at 604.

The NSMF may create the NSI by generating and causing one or more requests to be sent to a DM/EM/security manager ("SM") to install or upgrade software of the

network/security functions on an available physical resources. In various embodiments, the SM may be in parallel with the NM, or part of the NM.

The requests may be sent directly to the DM/EM/SM or through an NM. The request may include the information (for example, file location, etc.) related to software images of the network/security functions to be installed or upgraded on the available physical resources. The requests may further include a quantity of function instances to be installed/upgraded or a boundary of the resources (for example, range of resource pool, coverage boundary, etc.). The NSMF may receive a result of an installation of the network/security function from the DM/EM/SM, directly or through the NM.

The NSMF may create the NSI by additionally/alternatively generating and causing one or more requests to be sent to an NFVO to install or upgrade software of the network/security functions on available virtualized resources. The request may be sent directly to the NFVO or through the NM. Similar to the request sent to the DM/EM/SM, the request sent to the NFVO may include the related software images of the network/security functions to be installed or upgraded on the available virtualized resources, a quantity of function instances to be installed/upgrade, or boundary of the resources. The NSMF may receive a result of the installation of the network/security function from the NFVO, directly or through the NM.

In some embodiments, the NSMF may request the NFVO to install or upgrade software of the network/security functions by using newly-defined network slice operations or, alternatively, by reusing or repurposing existing network service operations. For example, the NSMF may request the NFVO to install software of a new network/security function on available virtualized resources by using a new network slice operations or by reusing a network service operations.

Existing network service operations that may be reused or repurposed include, but are not limited to, network service descriptor ("NSD") management operations (for example, on- board NSD, enable NSD, etc.) and NS management operations (for example, create NS identifier, instantiate NS, update NS, scale NS, etc.), and the VNF Package management operations (for example, on-board VNF package, enable VNF package, etc.) defined in ETSI Industry Standard Group ("ISG") NFV Interfaces and Architecture ("IFA") documents such as NFV-IFA013 v2.1.1 (2016-10-17).

If the network service operations are reused then, to create a network slice instance, the NSMF may request an NFVO to create and instantiate one or more network services to support the network slice instance. In another example, the NSMF may request the NFVO to scale or upgrade an existing network service instance to support the network slice instance. The request to scale or upgrade an existing network service instance may be a request to add a PNF or VNF to the existing NSI. The NSMF may request the NFVO to add VNF or PNF to the existing NSI by reusing a network service update operation consistent with that described in in ETSI ISG NFV IFA documents such as, but not limited to, NFV-IFA007 v2.1.1 (2016-10-18), NFV-IFAv2.1.1 (2016-10-18), NFV-IFA006 v2.1.1 (2016-04-20), NFV-IFA005 v2.1.1 (2016-04-21), or NFV-IFA013. In some embodiments, the NSMF may include, in the request to scale or upgrade, an indication of a relationship between a network slice instance and a network service instance. For example, a network service instance may be mapped to one or more network slice instances, or a network slice instance may be mapped to one or more network service instances.

The NFVO may instantiate, scale, or upgrade the network/security functions to the suitable virtualized resources (meeting capacity, interface, and security requirements) together with the VNFM, VIM, and NFVI. In some embodiments this instantiation, scaling, or upgrading may be requested by the NSMF and may be achieved by reusing a mechanism specified in the above-noted NFV-IFA documents.

After the appropriate network/security functions have been installed/upgraded, the NSMF may request the manager (for example, the NM, DM, EM, or security manager) to configure the specific network functions, common network functions, or security functions to form the NSI. For example, the NSMF may send configuration information to the managing node to allow the managing node to configure: interfaces to connect the network functions; or user device types or identifiers that are allowed to register, connect with, or use the NSI; etc.

After the functions are configured to form the NSI, the NSMF may send a report to the requestor (for example, operator, management entity, or process of the NSMF itself) that the NSI has been created and is available.

After creation, an NSI may offer specific communication services to end users. End-users may get different experiences from the services supported by different NSIs. In some situations, end-users may not be satisfied by service supported by a specific NSI.

Therefore, it may be desirable for an operator to determine the reason that an NSI does not meet expectations of an end user.

In some embodiments, one RAN node may support multiple NSIs. The RAN may support policy enforcement between slices according to service level agreements. The RAN may be free to apply best radio resource management policies for the service level agreement in place to each supported slice.

Embodiments provide network management solutions to support RAN resource management between slices. In particular, the various embodiments provide details related to providing subscriber and equipment trace functionality to a network slice instance; a framework on network slice management; and policy configuration for RAN resource management between slices.

Figure 7 provides a network slice management architecture ("NSMA") 700 in accordance with some embodiments. The NSMA 700 may include an NSMF 704 coupled with a service management function ("SMF") 708. The NSMF 704 and the SMF 708 may be disposed in an operator's domain. The NSMF 704 may be similar to, and substantially interchangeable with, another NSMF described herein including, but not limited to, NSMF 240, NSMF 340, and NSMF 440.

In some embodiments, the SMF 708 may be co-located with the NSMF 704 in a common device. In other embodiments, the SMF 708 may be disposed in a device that is separate from the device that hosts the NSMF 704.

The SMF 708 may be coupled with a customer 712. The customer 712 may be a third- party service provider or a service department of the operator, in which case the customer 712 may also be disposed in the operator's domain.

The SMF 708 may receive service requirements from the customer 712 and may manage, in whole or in part, services provided by the operator. The services may be a 3GPP service running on an NSI, or the NSI itself.

The SMF 708 may convert the service requirements received from the customer 712 into network requirements such as, but not limited to, network type, network capacity, quality of service ("QoS") requirements, and geographical location. The SMF 708 may provide the network requirements to the NSMF 704.

The NSMF 704 may be coupled with one or more network functions ("NFs") to manage and orchestrate the NSI based on the network requirements received from the SMF 708. The NFs may be outside of the operator's domain; however, in some embodiments, the NFs may be disposed within the operator's domain.

In some embodiments, an operator may wish to trace subscriber or equipment for a network slice instance. This may, for example, provide the operator with information regarding why an NSI meets or fails to meet expectations of an end user. Message flow 800 of Figure 8 illustrates a trace operation to support network slicing in accordance with some embodiments.

The message flow 800 diagrams messages and operations performed by a trace management function ("TMF") 804 and one or more NF(s) 808. The TMF 804 may be disposed in an NSMF, for example, NSMF 704, or another entity such as, for example, an EM or NM. The messages of the message flow 800 may be exchanged directly between the TMF 804 and the NF(s) 808 or through one or more other entities, for example, through an EM.

The TMF 804 may generate and transmit a trace session activation ("TSA") request 812 to the NFs 808. The TSA request 812 may identify an NSI for which a subscriber or equipment is to be traced. The NSI may be indicated by including a network slice instance ID in trace control and configuration parameters. The TSA request 812 may be generated and transmitted as part of a management activation procedure or a signaling activation procedure.

In some embodiments, a first NF of the NF(s) 808 may receive the TSA request 812 and determine that the trace control and configuration parameters should be propagated to one or more other NFs of the NF(s) 808. In this case, the first NF may forward some or all of the parameters, along with the network slice instance ID, to the one or more other NFs. At 816, the NF(s) 808 may detect a trigger event and begin recording trace data for the subscriber and equipment served by the indicated network slice instance. In some embodiments, the trigger events may be defined in the trace control and configuration parameters. In some embodiments, the trigger events may include, for example, receipt of a service request message that corresponds to a mobile-originated call or short message service ("SMS"); sending of a paging request message that corresponds to a mobile- terminated call/SMS; receipt of a location update request message that corresponds to an attach or location-update procedure; receipt of a detached indication message that corresponds to a detach procedure; receipt of a handover or relocation required message that corresponds to a handover; etc. The trigger events and trace data could be similar to those specified in 3 GPP TS 32.422 vl3.0.0 (2015-06) except with respect to NS provided by 5 G networks.

The NF(s) 808 may generate and send a trace data ("TD") report 820 to a trace collection entity of, or in communication with, the TMF 804. The TD report 812 may include the trace data, or data derived therefrom, recorded for the indicated NSI.

In this manner, a trace session may be activated to trace subscriber or equipment for a specific network slice instance. This activation may be through management activation or signaling activation. A network function of a network slice instance may then record and report the trace data for a specific network slice instance.

In some embodiments, a RAN node supporting multiple network slice instances may receive a policy from an operator that defines resource management between the network slice instances. The policy may be based on a service level agreement. See, for example, clause 8.1 of 3GPP TR 38.801 vO.4.0 (09-13-2016). In some embodiments, an NSMF may provide, for each NSI, a service level agreement ("SLA"), or information pertaining thereto, to a RAN node. For example, the NSMF or Policy Management function may configure a RAN node with a policy for resource management for each NSI. The policy may indicate, for example, relative priorities between NSIs supported by the RAN node. The policy may be generated or configured by the NSMF, Policy Management function, a network function management function, a network management function, an EM, a DM, an NM, or the RAN node itself. The policy may be based on one or more SLAs that respectively correspond to the NSIs supported by the RAN node. The SLAs may be configured through a network function management function, a network management function, an NM, a DM or an EM, for example.

Embodiments described herein may be implemented into a system using any suitably configured hardware or software. Figure 9 illustrates, for one embodiment, example components of an electronic device 900. In embodiments, the electronic device 900 may be, implement, be incorporated into, or otherwise be a part of a RAN, an EM, an NM, a DM, an NSMF, a security manager, an NF, an SMF, or some other device.

In some embodiments, the electronic device 900 may include processing circuitry 902 coupled with network interface circuitry 904 for communicating over a wired interface (for example, an X2 interface, an SI interface, and the like).

As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

The processing circuitry 902 may include one or more processors. For example, the processing circuitry 902 may include circuitry such as, but not limited to, one or more single-core or multi-core processors 902a. The processor(s) 902a may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, digital signal processors, etc.). The processors 902a may be coupled with or may include computer-readable media 902b (also referred to as "CRM 902b," "memory 902b," "storage 902b," or "memory /storage 902b") and may be configured to execute instructions stored in the CRM 902b to enable various applications, tasks, threads, or operating systems to run on the electronic device 900.

The CRM 902b for one embodiment may include any combination of suitable volatile memory or non-volatile memory. The CRM 902b may include any combination of various levels of memory /storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.). The CRM 902b may be shared among the various processors or dedicated to particular processors.

In some embodiments, the CRM 902b may include logic to implement an NSMF or SMF to execute lifecycle management of the network slice instance, execute performance management of a network slice instance, or execute fault management of a network slice instance as described herein.

Components of the processing circuitry 902 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.

The network interface circuitry 904 may be one or more computer hardware components that connect electronic device 900 to one or more network elements, such as one or more servers within a core network via a wired connection. To this end, the network interface circuitry 904 may include one or more dedicated processors or field programmable gate arrays ("FPGAs") to communicate using one or more network communications protocols such as X2 application protocol ("AP"), SI AP, Stream Control Transmission Protocol

("SCTP"), Ethernet, Point-to-Point ("PPP"), Fiber Distributed Data Interface ("FDDI"), or any other suitable network communications protocols.

In some embodiments, the electronic device 900 may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. For example, the electronic device 900 may implement the flow/structure 500 of Figure 5 or the flow/structure 600 of Figure 6. In general, the processing circuitry 902 may construct messages for transmission, process received messages to determine attribute values or other information, and cause transmission of the messages by providing the generated message to the network interface circuitry 904. The network interface circuitry 904 may send/receive the messages over appropriate network connections.

Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory /storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. For embodiments where node virtualization (for example, network function virtualization ("NFV")) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.

The processors 1010 (for example, a CPU, a reduced instruction set computing ("RISC") processor, a complex instruction set computing ("CISC") processor, a graphics processing unit ("GPU"), a digital signal processor ("DSP") such as a baseband processor, an application specific integrated circuit ("ASIC"), a radio-frequency integrated circuit ("RFIC"), another processor, or any suitable combination thereof) may include, for example, a processor 1012 and a processor 1014. The processors may correspond to any processors of processing circuitry 902 or network interface circuitry 904 of Figure 9. The memory /storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 1020 may include, but are not limited to, any type of volatile or non-volatile memory such as dynamic random access memory ("DRAM"), static random-access memory ("SRAM"), erasable programmable read-only memory ("EPROM"), electrically erasable programmable read-only memory ("EEPROM"), Flash memory, solid-state storage, etc. The memory /storage devices 1020 may correspond to CRM 902b of Figure 9.

The communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008. For example, the communication resources 1030 may include wired communication components (for example, for coupling via a Universal Serial Bus ("USB")), cellular communication components, near-field communication ("NFC") components, Bluetooth® components (for example, Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.

The instructions 1050 may cause the processors 1010 to perform the operation

flow/algorithmic structure 500, 600 or other operations of an EM, NM, or VNFM described herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (for example, within the processor's cache memory), the memory /storage devices 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any

combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory /storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.

The resources described in Figure 10 may also be referred to as circuitry. For example, communication resources 1030 may also be referred to as communication circuitry 1030. Some non-limiting examples are provided below.

Example 1 includes one or more computer-readable media having instructions that, when executed by one or more processors, cause a network slice management function

("NSMF") to: process a request to create a network slice instance; determine a network slice template associated with the network slice instance; and create the network slice instance based on the network slice template.

Example 2 includes the one or more computer-readable media of example 1 or any other example, wherein the instructions, when executed, further cause the NSMF to: select a network slice class from a plurality of network slice classes based on the request.

Example 3 includes the one or more computer-readable media of example 2 or any other example, wherein individual network slice classes of the plurality of network slice classes support individual service categories.

Example 4 includes the one or more computer-readable media of example 2 or any other example, wherein the instructions, when executed, further cause the NSMF to maintain a table of the plurality of network slice classes.

Example 5 includes the one or more computer-readable media of any one of examples 1 -4 or any other example, wherein the instructions, when executed, further cause the NSMF to: query available resources; and determine, based on the available resources, whether a new network function or a modified network function is desired to support the network slice instance.

Example 6 includes the one or more computer-readable media of example 5 or any other example, wherein the available resources include available physical resources and to query available resources the instructions, when executed, further cause the NSMF to: query a manager for available resources, the manager to include a network manager, a domain manager, or an element manager.

Example 7 includes the one or more computer-readable media of example 5 or any other example, wherein the available resources include virtualized resources and to query available resources the instructions, when executed, further cause the NSMF to: query a network function virtualization orchestrator for available resources.

Example 8 includes the one or more computer-readable media of any one of examples 1-7 or any other example, wherein the instructions, when executed, further cause the NSMF to: determine, based on the network slice template, a network function to support the network slice instance, the network function to be a physical network function or a virtual network function; and determine requirements of an interface between the network function and the network slice instance.

Example 9 includes the one or more computer-readable media of example 8 or any other example, wherein the instructions, when executed, further cause the NSMF to: determine a security protection mechanism of the interface.

Example 10 includes the one or more computer-readable media of any one of examples 1-

9 or any other example, wherein the instructions, when executed, further cause the NSMF to: determine whether an existing network function is suitable to be a common network function for the network slice instance.

Example 11 includes the one or more computer-readable media of any one of examples 1-

10 or any other example, wherein the instructions, when executed, further cause the NSMF to: determine whether an existing network function can be upgraded to support the network slice instance.

Example 12 includes the one or more computer-readable media of any one of examples 1- 11 or any other example, wherein the network slice template includes a common physical network function; a specific physical network function; a common virtualized network function; a specific virtualized network function; a supporting function; a relationship between a plurality of network functions; or a relationship between the network function and the supporting function.

Example 13 includes the one or more computer-readable media of example 12 or any other example, wherein the network slice template includes a supporting function that comprises a security function.

Example 14 includes the one or more computer-readable media of any one of examples 1- 13 or any other example, wherein the instructions, when executed, further cause the NSMF to: respond, to a source of the request, with a result of creation of the network slice instance.

Example 15 includes the one or more computer-readable media of any one of examples 1- 14 or any other example, wherein the instructions, when executed, further cause the NSMF to: automatically generate the request to create the network slice instance.

Example 16 includes the one or more computer-readable media of any one of examples 1- 14 or any other example, wherein the request is received from an operator or a management entity.

Example 17 includes the one or more computer-readable media of any one of examples 1- 16 or any other example, wherein the request includes an indication of a service category, capacity requirements, coverage, or performance requirements.

Example 18 include the one or more computer-readable media of any one of examples 1- 17 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to acquire a software image of a network function to be created or upgraded, wherein the manager is a network manager, domain manager, or element manager; request the manager to install or upgrade the network function on an available physical resource based on the software image; and receive a result of the install or upgrade of the network function from the manager.

Example 19 includes the one or more computer-readable media of any one of examples 1- 18 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to acquire a software image of a supporting function to be created or upgraded, wherein the manager is a network manager or a security manager; request the manager to install or upgrade the supporting function on an available physical resource based on the software image; and receive a result of the install or upgrade of the supporting function from the manager.

Example 20 includes the one or more computer-readable media of example 19 or any other example, wherein the supporting function is a security function and the instructions, when executed, further cause the NSMF to: cause the request to be sent to a security manager through a network manager; and receive the result from the network manager. Example 21 includes the one or more computer-readable media of any one of examples 1- 20 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a network function virtualization orchestrator to create and instantiate one or more network services to support the network slice instance. Example 22 includes the one or more computer-readable media of any one of examples 1- 21 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a network function virtualization orchestrator to instantiate a network function on an available virtualized resource to provide the network function; and receive a result of the instantiation of the network function from the network function virtualization orchestrator.

Example 23 includes the one or more computer-readable media of any one of examples 1- 21 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a network function virtualization orchestrator to scale or upgrade a network service instance; and receive a result of the request to scale or update from the network function virtualization orchestrator, wherein the request to scale or upgrade is a request to add a physical network function or a virtual network function to an existing network slice instance.

Example 24 includes the one or more computer-readable media of any one of examples 1- 23 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a network function virtualization orchestrator to upgrade an existing network function on a virtualized resource; and receive a result of the upgrade of the existing network function from the network function virtualization orchestrator.

Example 25 includes the one or more computer-readable media of any one of examples 1-

24 or any other example, wherein the request includes a network slice instance identifier to identify the network slice instance.

Example 26 includes the one or more computer-readable media of example 25 or any other example, wherein the network slice instance identifier is to indicate a relationship between the network slice instance and a network service instance.

Example 27 includes the one or more computer-readable media of any one of examples 1-

26 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to configure a specific network function, a common network function, or a supporting function to form the network slice instance, wherein the manager is a network manager or a security manager. Example 28 includes the one or more computer-readable media of any one of examples 1-

27 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to configure an interface to enable the network function to be connected; network function capacity; interface bandwidth; or allowed user device type or identifiers.

Example 29 includes the one or more computer-readable media of any one of examples 1- 28 or any other example, wherein the NSMF is located in a network manager, a domain manager, or a network slice manager or orchestrator.

Example 30 includes a network slice management function ("NSMF") having circuitry to: execute lifecycle management of a network slice instance; execute performance management of a network slice instance; or execute fault management of a network slice instance.

Example 31 includes an apparatus to implement a network slice management function ("NSMF"), the apparatus comprising: network interface circuitry to receive a request to create a network slice instance; and processing circuitry, coupled with the network interface circuitry, to configure one or more network functions to support the network slice instance based on the request.

Example 32 includes the apparatus of example 31 or any other example, wherein the processing circuitry is to determine a network slice template associated with the network slice instance and identify the one or more network functions based on the network slice template.

Example 33 includes the apparatus of example 32 or any other example, wherein the one or more network functions include a physical network function or a virtual network function.

Example 34 includes the apparatus of example 32 or 33 or any other example, wherein the processing circuitry is to: determine requirements of an interface between a network function of the one or more network functions and the network slice instance.

Example 35 includes the apparatus of any one of examples 31-34 or any other example, wherein the processing circuitry is further to: generate a request to determine available resources; cause the network interface circuitry to transmit the request; receive a response to the request from the network interface circuitry, the response to include an indication of the available resources; and determine, based on the available resources, whether a new network function or a modified network function is desired to support the network slice instance.

Example 36 includes the apparatus of example 35 or any other example, wherein the available resources include available physical resources and the network interface circuitry is to: transmit the request to a network manager, a domain manager, or an element manager.

Example 37 includes the apparatus of example 35 or any other example, wherein the available resources include virtualized resources and the network interface circuitry is to: transmit the request to a network function virtualization orchestrator.

Example 38 includes the apparatus of any one of examples 31-37 or any other example, wherein the processing circuitry is to: determine whether an existing network function is suitable to be a common network function for the network slice instance.

Example 39 includes the apparatus of any one of examples 31-38 or any other example, wherein the processing circuitry is further to: determine whether an existing network function can be upgraded to support the network slice instance.

Example 40 includes the apparatus of any one of examples 31-39 or any other example, wherein the processing circuitry is to cause the network interface circuitry to transmit a response with a result of creation of the network slice instance.

Example 41 includes a method of operating a network slice management function

("NSMF"), the method comprising: processing a request to create a network slice instance; determining a network slice template associated with the network slice instance; and creating the network slice instance based on the network slice template.

Example 42 includes the method of example 41 or any other example, further comprising: selecting a network slice class from a plurality of network slice classes based on the request.

Example 43 includes the method of example 42 or any other example, wherein individual network slice classes of the plurality of network slice classes support individual service categories.

Example 44 includes the method of example 42 or any other example, further comprising maintaining a table of the plurality of network slice classes.

Example 45 includes the method of any one of examples 41-44 or any other example, further comprising: querying available resources; and determining, based on the available resources, whether a new network function or a modified network function is desired to support the network slice instance.

Example 46 includes the method of example 45 or any other example, wherein the available resources include available physical resources and querying available resources comprises: querying a manager for available resources, the manager to include a network manager, a domain manager, or an element manager. Example 47 includes the method of example 45 or any other example, wherein the available resources include virtualized resources and querying available resources comprises: querying a network function virtualization orchestrator for available resources. Example 48 includes the method of any one of examples 41-47 or any other example, further comprising: determining, based on the network slice template, a network function to support the network slice instance, the network function to be a physical network function or a virtual network function; and determining requirements of an interface between the network function and the network slice instance.

Example 49 includes the method of example 48 or any other example, further comprising: determining a security protection mechanism of the interface.

Example 50 includes the method of any one of examples 41-49 or any other example, further comprising: determining whether an existing network function is suitable to be a common network function for the network slice instance.

Example 51 includes the method of any one of examples 41-50 or any other example, further comprising: determining whether an existing network function can be upgraded to support the network slice instance.

Example 52 includes the method of any one of examples 41-51 or any other example, wherein the network slice template includes a common physical network function; a specific physical network function; a common virtualized network function; a specific virtualized network function; a supporting function; a relationship between a plurality of network functions; or a relationship between the network function and the supporting function.

Example 53 includes the method of example 52 or any other example, wherein the network slice template includes a supporting function that comprises a security function. Example 54 includes the method of any one of examples 41-53 or any other example, further comprising: responding, to a source of the request, with a result of creation of the network slice instance.

Example 55 includes the method of any one of examples 41-54 or any other example, further comprising: automatically generating the request to create the network slice instance.

Example 56 includes the method of any one of examples 41-54 or any other example, wherein the request is received from an operator or a management entity. Example 57 includes the method of any one of examples 41-56 or any other example, wherein the request includes an indication of a service category, capacity requirements, coverage, or performance requirements.

Example 58 includes the method of any one of examples 41-57 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to acquire a software image of a network function to be created or upgraded, wherein the manager is a network manager, domain manager, or element manager; request the manager to install or upgrade the network function on an available physical resource based on the software image; and receive a result of the install or upgrade of the network function from the manager.

Example 59 includes the method of any one of examples 41-58 or any other example, wherein to create the network slice instance the instructions, when executed, further cause the NSMF to: request a manager to acquire a software image of a supporting function to be created or upgraded, wherein the manager is a network manager or a security manager; request the manager to install or upgrade the supporting function on an available physical resource based on the software image; and receive a result of the install or upgrade of the supporting function from the manager.

Example 60 includes the method of example 59 or any other example, wherein the supporting function is a security function and the method further comprises: causing the request to be sent to a security manager through a network manager; and receiving the result from the network manager.

Example 61 includes the method of any one of examples 41-60 or any other example, wherein creating the network slice instance comprises: requesting a network function virtualization orchestrator to create and instantiate one or more network services to support the network slice instance.

Example 62 includes the method of any one of examples 41-61 or any other example, wherein creating the network slice instance comprises: requesting a network function virtualization orchestrator to instantiate a network function on an available virtualized resource to provide the network function; and receiving a result of the instantiation of the network function from the network function virtualization orchestrator; or requesting a network function virtualization orchestrator to scale or upgrade a network service instance; and receiving a result of the request to scale or update from the network function virtualization orchestrator. Example 63 includes the method of example 62 or any other example, wherein requesting the network function virtualization orchestrator to scale or upgrade comprises: requesting the network function virtualization orchestrator to add a physical network function or a virtual network function to an existing network slice instance.

Example 64 includes the method of any one of examples 41-63 or any other example, wherein creating the network slice instance comprises: requesting a network function virtualization orchestrator to upgrade an existing network function on a virtualized resource; and receiving a result of the upgrade of the existing network function from the network function virtualization orchestrator.

Example 65 includes the method of any one of examples 41-64 or any other example, wherein the request includes a network slice instance identifier to identify the network slice instance.

Example 66 includes the method of example 65 or any other example, wherein the network slice instance identifier is to indicate a relationship between the network slice instance and a network service instance.

Example 67 includes the method of any one of examples 41-66 or any other example, wherein creating the network slice instance comprises: requesting a manager to configure a specific network function, a common network function, or a supporting function to form the network slice instance, wherein the manager is a network manager or a security manager.

Example 68 includes the method of any one of examples 41-67 or any other example, wherein creating the network slice instance comprises: requesting a manager to configure an interface to enable the network function to be connected; network function capacity; interface bandwidth; or allowed user device type or identifiers.

Example 69 includes the method of any one of examples 41-68 or any other example, wherein the NSMF is located in a network manager, a domain manager, or a network slice manager or orchestrator.

Example 70 includes a method of implementing a trace management function, the method comprising: generating a trace session activation request that includes an indication of a network slice instance; transmitting the trace session activation request to a network function associated with the network slice instance; and receiving a trace data report from the network function. Example 71 includes the method of example 70 or any other example, wherein the trace session activation request includes trace control and configuration parameters that includes a network slice instance identity to indicate the network slice instance.

Example 72 includes the method of example 70 or 71 or any other example, further comprising: transmitting the trace session activation request to the network function through an element manager.

Example 73 includes the method of any one of examples 70-72 or any other example, wherein the method is performed by a network manager or network management function. Example 74 includes the method of any one of examples 70-73 or any other example, wherein generating and transmitting the trace session activation request is part of a management activation procedure for a signaling activation procedure.

Example 75 includes a method of implementing a network function, the method comprising: receiving a trace session activation request that includes an indication of a network slice instance; detecting a trigger event; recording trace data based on said detection of the trigger event; and transmitting, to a trace collection entity, a trace data report that includes the recorded trace data.

Example 76 includes the method of example 75 or any other example, wherein the trace session activation request includes trace control and configuration parameters that includes a network slice instance identity to indicate the network slice instance.

Example 77 includes the method of example 75 or 76 or any other example, wherein the trace session activation request is received from an element manager or network function management function.

Example 78 includes the method of any one of examples 74-77 or any other example, further comprising: propagating one or more trace parameters for a trace session to a network function.

Example 79 includes a method of implementing a service management function ("SMF"), the method comprising: receiving service requirements from a customer, the service requirements relating to a service running on a network slice instance or the network slice instance itself; converting the service requirements to network requirements; and transmitting the network requirements to a network slice management function ("NSMF"). Example 80 includes the method of example 79 or any other example, wherein both the SMF and the NSMF are disposed in an operator's domain. Example 81 includes the method of example 79 or 80 or any other example, wherein the network requirements include a network type, and network capacity, a quality of service requirement, or geographical location.

Example 82 includes the method of any one of examples 79-81 or any other example, wherein transmitting the network requirements to the NSMF is to facilitate management and orchestration of the network slice instance by the NSMF.

Example 83 includes a method of implementing a network slice management function ("NSMF"), the method comprising: receiving network requirements from a service management function ("SMF"); and creating, managing, or orchestrating a network slice instance based on the network requirements.

Example 84 includes the method of example 83 or any other example, wherein both the SMF and the NSMF are disposed in an operator's domain.

Example 85 includes the method of example 83 or 84 or any other example, wherein the network requirements include a network type, and network capacity, a quality of service requirement, or geographical location.

Example 86 includes the method of any one of examples 83-85 or any other example, further comprising: configuring a radio access network ("RAN") node with a policy for resource management for a plurality of network slice instances supported by the RAN node.

Example 87 includes the method of example 86 or any other example, wherein the policy indicates relative priorities between individual network slice instances of the plurality of network slice instances.

Example 88 includes the method of example 86 or 87 or any other example, wherein the policy is based on a service level agreement.

Example 89 includes one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 41-88 or any other example, or any other method or process described herein.

Example 90 includes an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 41-88 or any other example, or any other method or process described herein.

Example 91 includes an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method described in or related to any of examples 41-88 or any other example, or portions thereof.

The description herein of illustrated implementations, including what is described in the Abstract, is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. While specific implementations and examples are described herein for illustrative purposes, a variety of alternate or equivalent embodiments or implementations calculated to achieve the same purposes may be made in light of the above detailed description, without departing from the scope of the present disclosure, as those skilled in the relevant art will recognize.