Intent driven dynamic and on-demand network slicing with automated topology creation and network digital twin

Abstract

A method, apparatus, and system for network slice instance topology design may be provided and may include, receiving, by a network service management function of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated design including outputting design phase feasibility result for the design; sending, by the network service management function, an input service profile and NSI / NSSI design guidance to a network slice management function (NSMF) of the network based on the design; and sending, by the network service management function, an input slice profile and NSSI design guidance to a network slice subnet management function (NSSMF) of the network based on the design.

Description

INTENT DRIVEN DYNAMIC AND ON-DEMAND NETWORK SLICING WITH AUTOMATED TOPOLOGY CREATION AND NETWORK DIGITAL TWINFIELD

[0001] The present disclosure relates to intent driven dynamic and on-demand network slicing with topology modelling and network digital twin.BACKGROUND

[0002] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0003] In the related art, network slicing may be performed in telecommunications networks (such as 5G) in order to multiplex physical networks into multiple logical networks (commonly referred to as “network slices”). Network slices may have a topology which may need to be designed, and network slices may need to be commissioned prior to service.

[0004] FIG. 1 illustrates a lifecycle diagram of a network slice instance according to the related art.

[0005] Referring to FIG. 1, in the preparation phase, a network slice instance does not exist. The preparation phase may include network slice design, network slice capacity planning, onboarding, and evaluation of the network functions, preparing the network environment and other necessary preparations required to be done before the creation of an network slice instance.

[0006] In the commissioning phase, network slice subnets and corresponding resources are deployed, provisioned and allocated in the Radio Access Network (RAN), Core Network andTransport Network but whose administrative state is locked. The creation of a network slice instance may include creation and / or modification of network slice instance constituents.

[0007] In the operation phase, the network slice is providing a service, or it is the service (in As a Service business model), and actions such as Slice Activation, De- Activation, Modification, Supervision and Reporting may be performed.

[0008] In the decommissioning phase, a network slice may be decommissioned from the associated service or as it is (in As a Service business model), including decommissioning of nonshared constituents if required and removing the network slice instance specific configuration from the shared constituents. After the decommissioning phase, the network slice instance is terminated and does not exist anymore.

[0009] In the related art, a typical procedure / workflow for designing and implementing the network slice (in the preparation and commissioning phases) may include steps of S101 Providing the slice requirements; S 102 Designing the slice topology based on the provided slice requirements, SI 03 Receiving / previ ewing a design result, SI 04 Providing a service profile, and SI 05 Slice Creation based on Slice topology design.SUMMARY

[0010] However, systems in the related art have the network slice design phase (e.g., the preparation phase) and the commissioning phase as separated phases in the workflow. With reference to FIG. 1, the design result in SI 03 may not necessarily be used when slice topology design and creation are performed at S105. This may lead to a gap between what is designed andwhat is commissioned with regards to the user intent and requirement fulfillment, along with risk in network failure. Furthermore, relying entirely on the network slice fesability check with or without resource reservation may not be sufficient for on-demand and dynamic network slicing.

[0011] Accordingly, there is a need for a system which can include network slice design creation and design verification in a closed-loop for network slicing.

[0012] According to example embodiments, a method, apparatus, and system for network slice instance topology design may be provided and may include: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.

[0013] According to embodiments, a network service management function may be provided and configured to: receive at least one input slice / service requirement; generate a networkslice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; preview the generated NSI and NS SI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; send an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and send an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design wherein the network service management function is one of an Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, .

[0014] According to embodiments at least one non-transitory computer-readable recording medium may be provided, having recorded thereon instructions executable to implement a method including: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidanceto a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.

[0015] Based on the above example embodiments, on-demand slicing with a closed-loop system may be achieved, which may ensure network slice quality and reliability more accurately based on user intent in any moment of time, and improve automation, thereby reducing capital and operational expenditures for running a telecommunications network .

[0016] Additional aspects will be set forth in part in the description that follows and, in part, will be apparent from the description, or may be realized by practice of the presented embodiments of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Features, aspects and advantages of certain exemplary embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0018] FIG. 1 illustrates a lifecycle workflow diagram for network slicing according to the related art;

[0019] FIG. 2 illustrates a lifecycle workflow diagram for network slicing according to an embodiment;

[0020] FIG. 3 illustrates a flowchart diagram for closed-loop network slice design and commissioning according to an embodiment;

[0021] FIG. 4 illustrates an example network slice object for design guidance according to an embodiment;

[0022] FIG. 5 illustrates a flowchart diagram for network slice design including digital twin according to an embodiment;

[0023] FIG. 6 illustrates a flowchart diagram for intent-driven network slice design according to an embodiment;

[0024] FIG. 7 illustrates a service view diagram for intent-driven network slice design according to an embodiment;

[0025] FIG. 8 illustrates an example method for designing and commissioning a network slice instance according to an embodiment;

[0026] FIG. 9 is a diagram of an example environment in which systems and / or methods, described herein, may be implemented; and

[0027] FIG. 10 is a diagram of example components of a device according to an embodiment.DETAILED DESCRIPTION

[0028] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations providedbelow, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part), and the order of one or more operations may be switched.

[0029] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0030] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.

[0031] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0032] According to embodiments, a method, apparatus, and system for network slice instance topology design may be provided and may include, receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.

[0033] Based on the above embodiments, on-demand slicing with a closed-loop system may be achieved, which may ensure on-demand network slice requirements fulfilment and network slice quality and reliability more accurately based on user intent, and improve automation, thereby reducing capital and operational expenditures for running a telecommunications network .

[0034] FIG. 2 illustrates a lifecycle workflow diagram for network slicing according to an embodiment.

[0035] Referring to FIG. 2, S201 Slice requirements, S202 Slice topology design, S203 Design result, and S205 Slice Creation based on Slice topology design may be similar to S 101 , S102, S103, and S105 described in FIG. 1 above. In S204, the design result received from the preparation phase in S203 may be provided as design guidance along with the service profde to the commissioning phase. Accordingly, Slice Creation based on Slice topology design in S205 will include design guidance from the preparation phase, and the gap between the preparation phase and commissioning phase (as in the related art) may be closed.

[0036] FIG. 3 illustrates a flowchart diagram for closed-loop network slice design and commissioning according to an embodiment. User 300, network service management function 310 (which may be one or more of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM)), Network Slice Design Function 320, Slice Topology Database 330, Network Slice Management Function (NSMF) 340, Network Slice Subnet Management Function (NSSMF) 350, and Network Function Management Functions (NFMF)s and Network Functions (NF)s 360 may be provided.

[0037] Prior to user 300 providing input, as a pre-requisite (step 0), existing network and network slice topology information may be retrieved by the Network Slice Design Function 320 from NSMF 340 and NSSMF 350. This information may be used by the Network Slice Design Function 320 while designing the network slice topology and configuration for a network slice instance and / or a network subnet slice topology and configuration for a network slice subnetinstance. The retrieved information about existing network and network slice topology and configurations can be stored in the Slice Topology Database.

[0038] At step 1, User 300 may provide input to the network service management function (BSS / SOM / CMSF) 310 in the form of an input slice / service requirement. For example, an input slice / service requirement may indicate a particular performance parameter which needs to be achieved by the network slice instance (e.g., latency and the like). According to embodiments, the input may be in the form of a service profile. User 300 may provide input via a variety of methods, for example, via a mobile terminal or computing device.

[0039] The network service management function (BSS / SOM / CMSF) 310 may interact with Network Slice Design Function 320 in order to design the network slice topology based on the received input slice / service requirement. Network Slice Design Function may also be in communication with Slice Topology Database 330 to store designed topology information (for example, designed topology information which follows a particular schema). The designed topology information in Slice Topology Database 330 may be stored in the form of an inventory. Network Slice Design Function 320 may also be used to design network slice subnet instances, network services and network functions. According to embodiments, Network Slice Design Function 320 may either design a Network Slice Instance or Network Slice Subnet Instance, or reuse and modify (if necessary) the existing instances taken from Slice Topology Database 330.

[0040] At step 2, the design result may be provided back to the user in the form of a preview, along with a design phase feasibility check result. The result may be displayed to the user 300, for example, in a graphical user interface or as a listed report. The design phase feasibility check may be performed by analyzing current network topology and resource availability basedon information available in the central inventory and comparing it to the requirements of the designed network slice topology. According to embodiments, the design phase feasibility check may be a separate check from a commissioning phase feasibility check which is performed by NSMF 340 or NSSMF 350 (based on queries sent to the Radio Access Network (RAN) and cloud platform for a real capability check)..

[0041] At step 3, the network service management function (BSS / SOM / CMSF) initiate the NSI and NSSI commissioning / allocation phase by sending a NSI allocation request to the NSMF. In addition to the existing input parameter defined in 3GPP TS28.531, which is the input service profile, a design guidance is included in the request. During the commissioning stage, NSMF 340 may make decisions about either re-using the existing network slices, or creating new network slices by using both the input service profile and network slice instance design guidance (taken from the designing phase as received from the network service management function (BSS / SOM / CMSF) 310).

[0042] At step 4, NSMF initiate NSSI commissioning / allocation phase by sending a NSSI allocation request to the NSSMF. In addition to the existing input parameter defined in 3GPP TS28.531, which is the input slice profile, a NSSI design guidance including previous designed NSSI topology and configuration information is included in the request also. During the commissioning stage, NSSMF 350 may make decisions about either re-using the existing network slice subnets, or creating new network slice subnets by using both an input slice profile and network slice subnet instance design guidance.

[0043] As a result of the commissioning stage, the real slice topology entities (NSIs and NS Sis) may be built based on the above. Management service Managed Object Instances (MnSMOI) related to the new network slice instances (NSI) and Network Slice Subnet Instances (NSSI) are created during the commissioning phase (as defined, for example, in 3GPP 28.451 Section5.2.2). MOIs may be stored locally in NSMF 340 and NSSMF 350 which maintain the management interface and related information / data models for management purposes. It should be appreciated that the MnS MOIs which are stored are different than the designed topology stored in the Slice Manager Inventory (Slice Topology Database 330). Nevertheless, according to some embodiments, the same information model may be used.

[0044] FIG. 4 illustrates an example information model of the design guidance according to an embodiment. The same network slice NRM (network resource model) which is used in network slicing related MnS procedures (e.g., slice commissioning / decommissioning, activation / deactivation, and modification procedures) may be re-used for modelling the designed slice topology and configurations generated during the slice design phase. The same information / data model may be used to model the designed slice topology stored in the slice manager inventory in the slice topology database 330. According to embodiments, synchronization may be performed between a central inventory in the network service management function, and the slice manager inventory 330 (for example, in the background using a TMF based service API of the central inventory, nevertheless the exact implementation details may be implemented appropriately by a person skilled in the art).

[0045] Referring back to FIG. 4, the class structure of the network slice object is shown with the class object hierarchy. Networkslice instance may be associated with 0-to-many ServiceProfile instance(s), and a top-level NetworkSliceSubnet instance which self-contains 0-to- many domain level (e.g. CN and RAN domains) NetworkSliceSubnet instances, and 0-to-manyNetworkSliceController instances. . A NetworkSliceSubnet instance may also be associated withO-to-many SliceProfile instance(s), NetworkService instance(s) and NetworkSliceSubnetController instance(s). A NetworkSliceSubnet instance may also contains 0- to-many ManagedFunction instances and EP Transport instances. A ManagedFunction may be associated with 0-to-many virtual network function (VNF) instance(s). A NetworkService may contains 0-to-many virtual network function (VNF) instance(s). Nevertheless, it should be appreciated that the class structure is an example and that other class arrangements / child objects may be included depending on the particular implementation.

[0046] For example, in the design guidance modelled by the information model in FIG. 4, Networkslice instance can point to a new Network Slice Instance (NSI) to be created or an existing NSI to be re-used. NetworkSliceSubnet instance can point to a new NSSI to be created or an existing NSSI to be reused. ManagedFunction instance can point to a new network function to be created, or existing network function to be reused. VNF instance can point to a new network function deployment to be created (not illustrated) for the slice or an existing network function deployment may be reused and modified.

[0047] In the case where a VNF instance already points to an existing network function deployment to be reused, the VNF instance may contain a reference to the existing network function deployment already in the central inventory. In the case where the VNF instance points to a new network function deployment to be created, the VNF instance should contain deployment information (for example, a Data Center and cluster to deploy the NF deployment) as well as other deployment artifacts and whatever is needed to deploy a new NF. The VNF instance should contain a reference to the existing node cluster already in the central inventory.

[0048] . In case where the ManagedFunction instance points to an existing network function to be reused, the ManagedFuncton instance may contain a reference to the existing network function already in the central inventory. It may also contain the Operations and Maintenance (0AM) attributes to be modified to the existing network function. In case where the ManagedFunction instance points to a new network function to be created, the ManagedFuncton instance should contains the associated VNF instances realizing the network function. It may also contain the 0AM attributes to be configured to the new network function, .

[0049] FIG. 5 illustrates a flowchart diagram for network slice design including digital twin according to an embodiment. User 500, network service management function (BSS / SOM / CMSF) 510, Network Slice Design Function 520, NSMF 540, NSSMF 550, NFMF and NFs 560 may be similar to their counterparts in FIG. 3 above. Accordingly, similar descriptions may be omitted for improved readability.

[0050] Network Digital Twin 530 is introduced. In particular, Network Digital Twin 530 may be a digital replica of the underlined network in FIG. 5 (e.g., NSMF 540, NSSMF 550, and NFMF and NFs 560). The digital replica may also include the real network management system and any other NFs.

[0051] Initially, Network Digital Twin 530 may be synchronized with the state of the real network. In step 0, existing network and slice topology, configuration and Key Performance Indicator (KPI) info may be retrieved by Network Slice Design Function 520 and Network Digital Twin 530. During step 1 in which the user 500 inputs slice / service requirement, user 500 may give new service profile / requirements during the design phase. Network service management function (BSS / SOM / CMSF)510 may automatically derive a new slice topology and configurations usingNetwork Slice Design Function 520 to fulfill the new service requirements based on the existing slice and network topology information in Network Digital Twin 530. A new network slice topology design may be generated and configurations may be firstly applied to Network Digital Twin 530 in order to test the feasibility and verify the performance.

[0052] Network Digital Twin 530 may also be used for what-if analysis and iterative optimization with the digital twin. That is, after a first NSI and NSSI design are generated and tested on the digital twin, modifications may be made to generate a second NSI and NSSI design and tested again on the digital twin, which may be updated to reflect the current network conditions. Accordingly, the user 500 may be able to achieve a higher degree of parameter tuning since the virtual digital twin can be used to optimize system performance.

[0053] If user 500 is satisfied with the previewed network slice topology in step 2, the iterative optimization using the digital twin can be stopped and commissioning phase can be triggered (steps 3-4 which are similar to their respective counterparts with reference to FIG. 3 above).

[0054] FIG. 6 illustrates a flowchart diagram for intent-driven network slice design according to an embodiment. Network service management function (BSS / SOM / CMSF) 610, Network Slice Design Function 620, Network Digital Twin 630, NSMF 640, NSSMF 650, NFMF and NFs 660 may be similar to their counterparts in FIG. 3 above. Accordingly, similar descriptions may be omitted for improved readability.

[0055] App 600 is introduced. In particular, App 600 may be used to interpret a high-level user intent into a service and slice requirement (e.g., a network slice directed for online gaming mode may be a high-level intent and App 600 may interpret it as requiring higher bandwidth andlower latency than a regular network slice). According to embodiments, a API / SDK 611 may be used as a standardized northbound API to 3rdparty applications by the network service management function (BSS / SOM / CMSF) 610. Accordingly, network slice design and digital twin function of Network Slice Design Function 620 and Network Digital Twin 630 may be used to automatically derive low-level slice and NF configurations to fulfill the high-level intent. Thus, dynamic slicing and intent driven may be achieved in this configuration.

[0056] According to embodiments, network service management function (BSS / SOM / CMSF) 610 may constantly monitor service demand changes and current system performance measurements and KPIs, then automatically drive service requirement and service planning changes and drive the slice configuration changes to adapt to the new demand, performance measurement, KPIs analytic data can be provided from core, application services, andnetwork data analytics function (NWDAF) 670) as enriched data input. Since no user is necessarily required in such a configuration, a fully automated closed-loop system may be achieved (e.g., no human in the loop). Thus, on-demand and intent driven network slicing may be achieved in this case.

[0057] According to embodiments, service API’s 680 may be provided. Further platform services can be provided, for example, for policy management, Artificial Intelligence / Machine Learning workflow, Conflict Mitigation, Analytics, App life cycle management (LCM) , Data Management (DME), Service Management (SME), and others.

[0058] FIG. 7 illustrates a service view diagram of the intent-driven network slice design (e.g., example embodiment shown in Fig. 6), according to an embodiment. Intent Driven Management Service 710(producer / consumer) , Network Slice Design Service 730, NetworkDigital Twin Service 740, AI / ML Workflow Service 750, NSM Service 760, NSSM Service 770, NFM Service 780 and NF Management Service (MnS) 790 may be provided.

[0059] According to embodiments, a user 700 (e.g. operator) may provide a high-level user intent by consuming the service provided by the Intent Driven Management Service. 3rdparty App 720 may consume the application service provided by the Intent Driven Management Service 710 via a standard API. The application is used to interpret the high-level user intent into a service and slice requirement. Accordingly, network slice design and digital twin services may be consumed by the Intent Driven Management Service 710 and the App 720 (indirectly via the application API) to automatically derive low-level slice and NF configurations to fulfill the high-level intent.

[0060] According to embodiments, Network Service Management Service 710 may constantly monitor service demand changes and current system performance measurements and KPIs by consuming the NSM 760, NSSM 770, NFM 780 and NF management 790 services.

[0061] According to embodiments, Network Service Management Service 710, after generate a slice design including designed NSIs and NSSIs, initiate NSI and NSSI allocations by consuming the services provided by the NSM and NSSM services. Service profiles, slice profiles, NSI and NSSI design guidance may be passed to the NSM and NSSM services in the NSI and NSSI allocation requests.

[0062] FIG. 8 illustrates an example method 800 for designing and commissioning a network slice instance according to an embodiment.

[0063] At operation S801, the Network Service Management Function (NSMF) may receive at least one slice / service requirement. As explained above, this may be a service profile. According to embodiments, the slice / service requirement may be received from an application,wherein the application is configured to interpret a high-level intent received from a user into the slice / service requirement.

[0064] At operation S802, NSMF generates NSI topology design based on at least one slice / service requirement using a network slice design function. According to embodiments, generating the NSI topology design may be further based on a slice topology database storing existing NSI topology designs. Prior to this step, the NSMF may have already receive existing network information, slice topology information, and KPI information, and generating the NSI topology design may be based on said information. In addition, a network digital twin may have also been previously generated by the NSMF and generating the NSI topology design may be further based on iterative design using the network digital twin.

[0065] At operation S803, NSMF previews NSI topology design including outputting a design phase feasibility result for the NSI topology design.

[0066] At operation S804, NSMF sends an input service profile and NSI design guidance to a network slice management function (NSMF) of the network based on the NSI topology design. Upon receipt, the NSMF may be configured to build a physical slice based on the input service profile and the NSI guidance.

[0067] At operation S805, NSMF may send an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI topology design. Upon receipt, the NSSMF may be configured to build a physical slice subnet based on the input slice profile and NSSI design guidance. The NSI design guidance and NSSI design guidance may be provided in a network slice object (such as the one illustrated in FIG. 4 above).

[0068] Based on the above embodiments, on-demand slicing with a closed-loop system may be achieved, which may ensure network slice quality and reliability more accurately based on user intent, and improve automation, thereby reducing capital and operational expenditures for running a telecommunications network .

[0069] FIG. 9 is a diagram of an example environment 900 in which systems and / or methods, described herein, may be implemented. As shown in FIG. 9, environment 900 may include a user device 910, a platform 920, and a network 930. Devices of environment 900 may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections. In embodiments, any of the functions and operations described with reference to FIGS. 2-9 above may be performed by any combination of elements illustrated in FIG. 9.

[0070] User device 910 includes one or more devices capable of receiving, generating, and storing, processing, and / or providing information associated with platform 920. For example, user device 910 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device. In some implementations, user device 910 may receive information from and / or transmit information to platform 920.

[0071] Platform 920 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, platform 920 may include a cloud server or a group of cloud servers. In some implementations, platform 920 may be designed to be modular such that certain software components may be swapped in or out depending on a particular need. As such, platform 920 may be easily and / or quickly reconfigured for different uses.

[0072] In some implementations, as shown, platform 920 may be hosted in cloud computing environment 922. Notably, while implementations described herein describe platform 920 as being hosted in cloud computing environment 922, in some implementations, platform 920 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0073] Cloud computing environment 922 includes an environment that hosts platform 920. Cloud computing environment 922 may provide computation, software, data access, storage, etc., services that do not require end-user (e.g., user device 910) knowledge of a physical location and configuration of system(s) and / or device(s) that hosts platform 920. As shown, cloud computing environment 922 may include a group of computing resources 924 (referred to collectively as “computing resources 924” and individually as “computing resource 924”).

[0074] Computing resource 924 includes one or more personal computers, a cluster of computing devices, workstation computers, server devices, or other types of computation and / or communication devices. In some implementations, computing resource 924 may host platform 920. The cloud resources may include compute instances executing in computing resource 924, storage devices provided in computing resource 924, data transfer devices provided by computing resource 924, etc. In some implementations, computing resource 924 may communicate with other computing resources 924 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0075] As further shown in FIG. 9, computing resource 924 includes a group of cloud resources, such as one or more applications (“APPs”) 924-1, one or more virtual machines (“VMs”)924-2, virtualized storage (“VSs”) 924-3, one or more hypervisors (“HYPs”) 924-4, or the like.

[0076] Application 924-1 includes one or more software applications that may be provided to or accessed by user device 910. Application 924-1 may eliminate the need to install and execute the software applications on user device 910. For example, application 924-1 may include software associated with platform 920 and / or any other software capable of being provided via cloud computing environment 922. In some implementations, one application 924-1 may send / receive information to / from one or more other applications 924-1, via virtual machine 924-2.

[0077] Virtual machine 924-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 924-2 may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by virtual machine 924-2. A system virtual machine may provide a complete system platform that supports execution of a complete operating system (“OS”). A process virtual machine may execute a single program, and may support a single process. In some implementations, virtual machine 924-2 may execute on behalf of a user (e g., user device 910), and may manage infrastructure of cloud computing environment 922, such as data management, synchronization, or long-duration data transfers.

[0078] Virtualized storage 924-3 includes one or more storage systems and / or one or more devices that use virtualization techniques within the storage systems or devices of computing resource 924. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administratorsmanage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and / or performance of non-disruptive file migrations.

[0079] Hypervisor 924-4 may provide hardware virtualization techniques that allow multiple operating systems (e.g., “guest operating systems”) to execute concurrently on a host computer, such as computing resource 924. Hypervisor 924-4 may present a virtual operating platform to the guest operating systems and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.

[0080] Network 930 includes one or more wired and / or wireless networks. For example, network 930 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and / or a combination of these or other types of networks.

[0081] The number and arrangement of devices and networks shown in FIG. 9 are provided as an example. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown in FIG. 9. Furthermore, two or more devices shown in FIG. 9 may be implementedwithin a single device, or a single device shown in FIG. 9 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of environment 800 may perform one or more functions described as being performed by another set of devices of environment 800.

[0082] FIG.10 illustrates an embodiment of a device 1000. As shown in FIG. 1010, the device 1000 processor 1010, a memory 1020, a storage component 1030, an input component 1040, an output component 1050, a communication interface 1060, and a bus 1070.

[0083] The processor 1010, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 1010 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 1010 may be a Central Processing Unit (CPU)a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0084] Memory 1020 includes a non-transitory computer readable medium. Memory 1020 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 1010. The memory 1020 comprises machine-readable instructions which are executable by the processor 1010. These machine-readable instructions when executed by the processor 1010 cause the processor 1010 to perform one or more method steps of an embodiment described above.

[0085] Storage component 1030 stores information and / or software related to the operation and use of the device 1000. For example, storage component 1030 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0086] Input component 1040 is configured to receive information, such as user input. For example, the input component 1040 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 1040 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0087] Output component 1050 is configured to provide output information from the device 1000. For example, the output component 1050 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).

[0088] Communication interface 1060 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 1060 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 1000 and other devices. In other words, the standard of the communication interface 1060 is not limited.

[0089] The bus 1070 acts as an interconnect between the processor 1010, the memory 1020, the storage component 1030, the input component 1040, the output component 1050, and thecommunication interface 1060 of the device 1000. The bus 1070 may include a wired interconnection or a wireless interconnection.

[0090] The number and arrangement of components shown in FIG. 1010 are provided as an example. In practice, device 1000 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 1010. Additionally, or alternatively, a set of components (e.g., one or more components) of device 1000 may perform one or more functions described as being performed by another set of components of device 1000. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 1000 in communication with one another.

[0091] In embodiments, any one of the operations or processes of FIGS. 2-8 may be implemented by or using any one of the elements illustrated in FIGS. 9 and 10. It is understood that other embodiments are not limited thereto, and may be implemented in a variety of different architectures (e.g., bare metal architecture, any cloud-based architecture or deployment architecture such as Kubernetes, Docker, OpenStack, etc ).

[0092] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0093] Some embodiments may relate to a system, a method, and / or a computer readable medium at any possible technical detail level of integration. Further, one or more of the above components described above may be implemented as instructions stored on a computer readable medium and executable by at least one processor (and / or may include at least one processor). Thecomputer readable medium may include a computer-readable non-transitory storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out operations.

[0094] The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0095] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise coppertransmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0096] Computer readable program code / instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a standalone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

[0097] These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks.

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

[0099] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a microservice(s), module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, and computer readable medium may include additionalblocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0100] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it being understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0101] Various further respective aspects and features of embodiments of the present disclosure may be defined by the following items:Item [I]: A method including: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), CommunicationService Management Function (CSMF) or Self-Order Management(SOM) of a network, at leastone input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.Item [2] The method according to Item [1], wherein the NSMF is configured to build a network slice instance (NSI) based on the input service profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.Item [3] The method according to any one of Items

[0001] -[2], wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.Item [4] The method according to any one of Items [l]-[3], wherein the method further includes: receiving, by the network service management function, existing network information,slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topology design is further based on at least one of the existing network information, slice topology information, or KPI information.Item [5] The method according to any one of Items

[0001] -[4], wherein generating the NSI and NSSI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.Item [6] The method according to any one of Items [l]-[5], wherein the method further includes: generating, by the network service management function, a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.Item [7] The method according to any one of Items

[0001] -[6], wherein the at least one input slice / service requirement is received from an application, wherein the application is configured to interpret a high-level intent received from a user into at least one input slice / service requirement.Item [8] An network service management function configured to: receive at least one input slice / service requirement; generate a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; preview the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design;send an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and send an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design wherein the network service management function is one of an Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or SelfOrder Management(SOM) of a network, .Item [9] The network service management function according to Item [8], wherein the NSMF is configured to build a network slice instance (NSI) based on the input service profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.Item

[0010] The network service management function according to any one of Items [8]-[9], wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.Item

[0011] The network service management function according to any one of Items [8]-

[0010] , further configured to: receive existing network information, slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topology design is further based on at least one of the existing network information, slice topology information, or KPI information.Item

[0012] The network service management function according to any one of Items [8]-[l 1], wherein generating the NSI and NSSI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.Item

[0013] The network service management function according to any one of Items [8]-

[0012] , further configured to: generate a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.Item

[0014] The network service management function according to any one of Items [8]-

[0013] , wherein the at least one input slice / service requirement is received from an application, wherein the application is configured to interpret a high-level intent received from a user into at least one input slice / service requirement.Item

[0015] At least one non-transitory computer-readable recording medium having recorded thereon instructions executable to implement a method including: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Managem ent(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / servicerequirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profde and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profde and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.Item

[0016] The at least one non-transitory computer-readable recording medium according to Item

[0015] , wherein the NSMF is configured to build a network slice instance (NSI) based on the input service profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.Item

[0017] The at least one non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0016] , wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.Item

[0018] The at least one non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0017] , wherein the method further includes: receiving, by the network service management function, existing network information, slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topologydesign is further based on at least one of the existing network information, slice topology information, or KPI information.Item

[0019] The at least one non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0018] , wherein generating the NSI and NS SI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.Item

[0020] The at least one non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0019] , wherein the method further includes: generating, by the network service management function, a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.

[0102] It can be understood that numerous modifications and variations of the present disclosure are possible in light of the above teachings. It will be apparent that within the scope of the appended clauses, the present disclosures may be practiced otherwise than as specifically described herein.

Claims

WHAT IS CLAIMED IS1. A method comprising: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.

2. The method as claimed in claim 1, wherein the NSMF is configured to build a network slice instance (NSI) based on the input service profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.

3. The method as claimed in claim 1, wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.

4. The method as claimed in claim 1, wherein the method further comprises: receiving, by the network service management function, existing network information, slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topology design is further based on at least one of the existing network information, slice topology information, or KPI information.

5. The method as claimed in claim 1, wherein generating the NSI and NSSI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.

6. The method as claimed in claim 1, wherein the method further comprises: generating, by the network service management function, a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.

7. The method as claimed in claim 1, wherein the at least one input slice / service requirement is received from an application, wherein the application is configured to interpret a high-level intent received from a user into at least one input slice / service requirement.

8. An network service management function configured to: receive at least one input slice / service requirement; generate a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; preview the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; send an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and send an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design wherein the network service management function is one of an Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, .

9. The network service management function as claimed in claim 8, wherein the NSMF is configured to build a network slice instance (NSI) based on the input service profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.

10. The network service management function as claimed in claim 8, wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.

11. The network service management function as claimed in claim 8, further configured to: receive existing network information, slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topology design is further based on at least one of the existing network information, slice topology information, or KPI information.

12. The network service management function as claimed in claim 8, wherein generating the NSI and NSSI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.

13. The network service management function as claimed in claim 8, further configured to: generate a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.

14. The network service management function as claimed in claim 8, wherein the at least one input slice / service requirement is received from an application, wherein the application is configured to interpret a high-level intent received from a user into at least one input slice / service requirement.

15. At least one non-transitory computer-readable recording medium having recorded thereon instructions executable to implement a method comprising: receiving, by a network service management function which may be one of a Operations Support System (OSS), Business Support System (BSS), Communication Service Management Function (CSMF) or Self-Order Management(SOM) of a network, at least one input slice / service requirement; generating, by the network service management function, a network slice instance (NSI) and network slice subnet instance (NSSI) topology and configuration design based on the at least one input slice / service requirement using a network slice design function; previewing, by the network service management function, the generated NSI and NSSI topology design including outputting a design phase feasibility result for the NSI and NSSI topology design; sending, by the network service management function, an input service profile and NSI and NSSI design guidance to a network slice management function (NSMF) of the network based on the NSI and NSSI topology design; and sending, by the network service management function, an input slice profile and network slice subnet instance (NSSI) design guidance to a network slice subnet management function (NSSMF) of the network based on the NSI and NSSI topology design.

16. The at least one non-transitory computer-readable recording medium as claimed in claim 15, wherein the NSMF is configured to build a network slice instance (NSI) based on the inputservice profile and NSI design guidance, and wherein the NSSMF is configured to build the NSSI based on the input slice profile and NSSI design guidance.

17. The at least one non-transitory computer-readable recording medium as claimed in claim 15, wherein the NSI design guidance and NSSI design guidance are provided in a network slice design information model.

18. The at least one non-transitory computer-readable recording medium as claimed in claim 15, wherein the method further comprises: receiving, by the network service management function, existing network information, slice topology and configuration information, and key performance indicators (KPI) information, wherein generating the NSI and NSSI topology design is further based on at least one of the existing network information, slice topology information, or KPI information.

19. The at least one non-transitory computer-readable recording medium as claimed in claim 15, wherein generating the NSI and NSSI topology design is further based on a slice topology database storing existing NSI and NSSI topology designs.

20. The at least one non-transitory computer-readable recording medium as claimed in claim 15, wherein the method further comprises:generating, by the network service management function, a network digital twin which is a digital replica of the network, wherein generating the NSI and NSSI topology design is further based on iterative design using the network digital twin.

Images