5g slice subnet template for network slice provisioning

Abstract

Embodiments of the present disclosure relate to 5G slice subnet templates for network slice provisioning. Techniques are disclosed for defining a network slice template (NST) for provisioning a network slice based on one or more network slice subnet templates (NSSTs). For example, a network provisioning system obtains one or more NSSTs. The one or more NSSTs can include a domain-level NSST for a domain-specific network service or a root-level NSST for an end-to-end network service. The network provisioning system defines a NST based on the one or more NSSTs. The network provisioning system deploys a network slice according to the NST. In some examples, the network slice is a 5G communication network slice.

Description

[0001] This application claims the rights of US Patent Application No. 17 / 933,421, filed September 19, 2022, and GR Patent Application No. 20220100182, filed February 28, 2022, the entire contents of each of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to computer networking, and more specifically, to ordering and supplying communication services on a network. Background Technology

[0003] Computer networks have become ubiquitous, and the number of network applications, network-connected devices, and the types of network-connected devices are rapidly expanding. These devices now include computers, smartphones, Internet of Things (IoT) devices, vehicles, medical device factory equipment, and more. The 5G network architecture enhances the ability to provide communication services using Network Functions Virtualization (NFV). Dedicated networks can be created by combining the radio access network (RAN) of a mobile network operator with the core functions of 5G. For example, networks can be created for specific service level agreements (SLAs), special use cases, or other specific requirements. Examples of such networks include dedicated mobile networks, industrial networks, and dedicated networks for connected vehicles. Summary of the Invention

[0004] Generally, this disclosure describes techniques for on-demand service provisioning in a network (e.g., a 5G network). Using the techniques disclosed herein, an end user of a service can request a network operator to provision the service using a workflow that begins with selecting a service template that matches the service to be provided. The network service provider can provide a portal to the network provisioning system, wherein the portal presents visual cues via a user interface that visualizes the service provisioning process and receives user input that can be selected from the visualization in certain circumstances. In some aspects, the user can be a tenant (e.g., a customer) of a 5G mobile network operator. As an example, a tenant can be an enterprise customer of a mobile network operator. In some aspects, the user can be an administrator of a 5G network service provider.

[0005] Provisioning services in a 5G network domain can involve multiple services and multiple service providers. For example, provisioning end-to-end 5G network slices can involve providing network functionality to support network slices across multiple geographically distributed data centers (“multi-cloud”), and can also involve services provided and implemented across multiple network domains (“multi-domain”) such as radio access networks (RAN), transport networks, core network services, and service gateway interfaces (SGi). Different services and network domains may have different capabilities, functionalities, and service levels. Tenants may want to provision complete communication services to their owned or leased network infrastructure, and in some cases, provide related network slices. In existing systems, tenants may contact a mobile network operator (MNO) to request service provisioning. Network administrators may need to use various different configuration interfaces and configuration parameters to provision services. There can be considerable delays while tenants wait for the mobile network operator to provision services. This can frustrate tenants and result in a poor user experience. Furthermore, the complexity and diversity of interfaces and parameters can lead to significant errors during the provisioning process.

[0006] According to the technology disclosed herein, tenants (or network service providers with slices owned by providers) can initiate the provision of communication services on demand with predefined Service Level Agreements (SLAs) and Network Slice Templates (NSTs). Tenants can specify different attributes of the service, such as tracking region, compute cloud / data center, allowed subscribers, network slice selection policies, etc. End users can subscribe to communication services via a user interface that provides profile selections and visual cues for choosing tracking regions, subscribers, data centers, etc. The technology disclosed herein facilitates a service order creation process that end users can use to request on-demand provision of an end-to-end network, which can be created for specific SLAs, use cases, and user needs. In some respects, end users can be tenants of mobile network operators capable of providing communication services on demand.

[0007] Network service providers, such as mobile network operators, can leverage the technologies described herein to offer Network as a Service (NaaS) to their customers. For example, this technology can facilitate end-user and on-demand provisioning of dedicated mobile networks. Examples of such dedicated mobile networks include dedicated networks for connected vehicles, Internet of Things (IoT) networks, and networks for industry. In some aspects, network service providers can create network slices with QoS and other parameters on demand based on service orders generated by tenants or other end-users via an interface implementing the technologies described herein.

[0008] The technology disclosed herein includes a provisioning portal that facilitates the creation of service orders by network operator tenants and other customers. The user interface can guide users through a series of actions in a workflow that leads to the creation of a service order, which instructs the provisioning system to configure and deploy network services for the user. In some aspects, communication services can be localized to specific geographic areas by providing users with an interface to select components involved in the provision of communication services from a map. By enabling end users to perform on-demand provisioning of communication services, the technology disclosed herein can provide technical advantages over prior art systems. As a practical application of the technology described in this disclosure, network operator end-user tenants can use the provisioning portal to provision network operator communication services for their use. The provisioning portal can facilitate end-user ordering of network services and provide network services on demand without involving mobile network operator personnel. As a result, tenants may be able to receive the benefits of communication servers more quickly compared to existing systems. Furthermore, this may result in less overhead for mobile network operators. Additionally, this technology allows users to specify a localized geographic area for the service.

[0009] In one example, this disclosure describes a method comprising: obtaining one or more network slice subnet templates (NSSTs) by a processing circuitry system; defining a network slice template (NST) by the processing circuitry system based on the one or more NSSTs; and deploying network slices by the processing circuitry system according to the NSTs.

[0010] In another example, this disclosure describes a computing system including a processing circuitry having access to memory, the processing circuitry being configured to: obtain one or more network slice subnet templates (NSSTs); define network slice templates (NSTs) based on one or more NSSTs; and deploy network slices according to the NSTs.

[0011] In another example, this disclosure describes a method comprising: receiving, by a processing circuitry system, an indication of a first selection of one or more network functions; receiving, by the processing circuitry system, an indication of a second selection of one or more tags specifying the placement of the one or more network functions; defining a network slice subnet template (NSST) by the processing circuitry system and based on the first and second selections; storing, by the processing circuitry system, the defined NSST in a Service Management and Orchestration (SMO) catalog of NSSTs hosted by a database; receiving, by the processing circuitry system, an indication of a third selection of one or more NSSTs, the one or more NSSTs including the defined NSSTs; in response to the indication of the third selection, obtaining, by the processing circuitry system, one or more NSSTs from the SMO catalog; defining a network slice template (NST) by the processing circuitry system based on the one or more NSSTs; and deploying network slices by the processing circuitry system according to the NSTs.

[0012] Details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the specification, drawings, and claims. Attached Figure Description

[0013] Figure 1 This is a block diagram illustrating an example network system according to the technology of this disclosure.

[0014] Figure 2 This is a conceptual diagram of a user interface screen for adding network slice templates according to the technology disclosed herein.

[0015] Figures 3A-3G This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0016] Figure 4 This is a conceptual diagram of a user interface screen showing the status of a service order, based on the technology disclosed herein.

[0017] Figure 5 This is a flowchart illustrating the operation of a method for providing network services according to the technology of this disclosure.

[0018] Figure 6 This is a block diagram illustrating further details of an example of a computing device operating according to one or more technologies of this disclosure.

[0019] Figures 7A-7B This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0020] Figure 8 This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0021] Figures 9A-9B This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0022] Figures 10A-10F This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0023] Figures 11A-11C This is a conceptual diagram of a user interface screen for providing network services according to the technology disclosed herein.

[0024] Figure 12 This is a flowchart illustrating an operation for providing network services according to the technology of this disclosure. Detailed Implementation

[0025] Figure 1 This is a block diagram illustrating an example network system according to the technology of this disclosure. Figure 1 In the example shown, network system 100 includes a provisioning system 102, a provisioning portal 104, one or more radio access networks (RANs) 109, and a core 105. Provisioning system 104 provides communication services to customers of a network operator (e.g., a mobile network operator). As an example, a tenant may order communication services from a mobile network operator. The desired service may be described in a service order 112. Provisioning system 102 processes service orders and may allocate the communication infrastructure and resources required to provide the desired service to the tenant based on the information in service order 112.

[0026] In some aspects, resources associated with services to tenants can be provided or managed by the functions of core 105 and / or components of RAN 109. In some aspects, core 105 implements various discrete control plane and user plane functions of network system 100. In some aspects, core 105 includes 5G control plane functions such as Access Mobility Management Function (AMF) 152, Session Management Function (SMF) 153, Policy Control Function (PCF) 154, User Data Management (UDM) 155, Network Repository Function (NRF) 157, Authentication Server Function (AUSF) 156, and Network Slice Selection Function (NSSF) 159. AMF 152 can provide access mobility management services. SMF 153 can provide session management services. PCF 154 can provide policy control services. Unified Data Management (UDM) function 155 can manage network user data. AUSF 156 can provide authentication services. Network Repository Function (NRF) 157 can provide a repository that can be used to register and discover services in the network operator's network. The Network Slice Selection Function (NSSF) 159 can be used to select instances of available network slices for use by the User Equipment (UE) device 131. Core 105 may also include User Plane Functions (UPF) 158. UPF 158 can provide packet routing, forwarding, and other network data processing functions (e.g., Quality of Service, packet inspection, service optimization, etc.). Further details regarding the services and features offered by AMF 152, SMF 153, PCF 154, UDM 155, NRF 157, AUSF 156, NRF 157, UPF 158, and NSSF 159 can be found below: 3rd Generation Partnership Project 2021, Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Phase 2 (Revision 17), TS 23.501V17.0.0 (2021-03), the entire contents of which are incorporated herein by reference.

[0027] In some examples, RAN 109 includes radio units (RUs) located at various cellular network sites (“cell sites”), as well as distributed units (DUs) and centralized units (CUs). Each RU consists of a LO PHY and an RF transmitter. The LO PHY component can be implemented using dedicated hardware for high-performance packet processing.

[0028] The RU can connect to the DU via a fronthaul network. The fronthaul network connects the LO PHY and HI PHY, and is used by the RU and DU to implement the 5G F2 interface. The DU manages packet transmissions via the RU. In some cases, this packet transmission conforms to the Common Packet Radio Interface (CPRI) and / or Enhanced CPRI (eCPRI) standards, or conforms to IEEE 1914.3. The DU can implement Radio Link Control (RLC), Media Access Control (MAC), and the HI PHY layer. The DU is controlled at least partially by the CU.

[0029] The DU can connect to the CU via the midhaul network, and both the DU and CU can use the midhaul network to implement the 5G F1 interface. The CU can implement the Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers. The CU connects to the core 105 via the backhaul network. Each of the midhaul and backhaul networks can be a wide area network (WAN).

[0030] RAN 109 may include gNodeB 102. In some examples of the radio access network 109 of network system 100, gNodeB 102 includes CU 136 and DU 134. CU 136 may support multiple DUs to implement multiple gNodeBs. In addition, a single DU 134 may support one or more RUs.

[0031] Any DU may or may not be located at a cellular site that includes multiple RUs supported by the DU. One DU may be located at a cellular site, while other DUs may be located at a local data center and collectively support multiple RUs. Network system 100 may have a radio access network 109 comprising thousands of cellular sites and gNodeBs.

[0032] Radio access network 109 connects to core 105 to exchange packets with data network 140. Core 105 may be a 5G core network, and data network (DN) 140 may represent, for example, one or more service provider networks and services, the Internet, third-party services, one or more IP-VPNs, IP-Multimedia Subsystems, combinations thereof, or other networks or combinations of networks.

[0033] Supply portal 104 provides an interface for client device 101 to supply communication services. In some aspects, supply portal 104 may present user interface 106, which presents user interface elements (e.g., screens, menus, maps, etc.) as part of a workflow for supplying communication services. In some aspects, the user interface and workflow may be an "end-to-end" workflow, such that when the workflow is completed, sufficient information is available to the supply portal to create a service order 112 that can be used by supply system 102 to supply the desired communication services.

[0034] Client device 101 may be an end-user computing device that receives user interface 106 elements to be presented to a user operating client device 101 via a display coupled to client device 101. In some aspects, client device 101 may be operated by a tenant of a mobile network operator and used to subscribe to desired communication services. In other aspects, client device 101 may be operated by personnel of a mobile network operator and used to supply communication services to tenants or for use by the mobile network operator. For example, a mobile network operator may use a provisioning portal to supply slices to carry voice services, web browsing services, or other types of services.

[0035] Supply portal 104 can be communicatively coupled to client device 101 and supply system 102. Figure 1 In the example shown, provisioning portal 104 executes in a computing environment, which may be provided by a cloud service provider or at a branch office of an MNO. However, provisioning portal 104 may execute in other environments. Provisioning portal 104 may be a component of provisioning system 102. Furthermore, provisioning portal 104 may be a component of a server or other computing device in a data center (e.g., a mobile network operator's data center). Additionally, in various examples, this document attributes some operations to provisioning system 102 or provisioning portal 104 that may be performed by provisioning system 102 or provisioning portal 104.

[0036] In some aspects, the communication services provided by Provisioning Portal 104 include network slicing. In a 5G network environment, network slicing is a network architecture that facilitates the creation of multiple virtualized and independent logical networks that are multiplexed on the same physical network infrastructure. Network slices can be logically isolated from other network slices and can be customized to meet the service level expectations of applications that may be established by Service Level Agreements (SLAs). Figure 1 In the example shown, supply system 102 can create network slices on the access network of a mobile network operator and allocate them to data network 140.

[0037] In some respects, mobile network operators can create network slice templates 111. Network slice template 111 can be a blueprint defining various network slice attributes used to configure the network slice. For example, network slice template 111 can define the networks and services used by the slice, as well as the interfaces with these networks and services. Network slice templates can be used to create slices that can be customized for specific purposes. For example, network slice template 111 may include templates for creating network slices that carry video streaming, templates for creating network slices that carry cloud gaming network services, templates for creating network slices that carry artificial intelligence services, and so on.

[0038] According to the technology disclosed herein, a mobile network operator can create a network slice subnet template 113. The network slice subnet template 113 can be a blueprint defining various network slice subnet attributes used to configure the network slice subnet. For example, one or more network slice subnet templates 113 can be used to define the networks and services used by the slice subnet and the interfaces with these networks and services. One or more network slice subnet templates 113 can be used to define different parts of a network slice. As described in more detail below, an end-to-end network slice can be defined from a network slice template 111, which in turn can be defined from various configured network slice subnet templates 113.

[0039] Figure 2 This is a conceptual diagram of a user interface screen for adding network slice templates according to the technology disclosed herein. Figure 2 Combining Figure 1 This can be discussed from several perspectives. For example, mobile network operators can use slice template screen 202 to define network slice templates for tenants to use when ordering and supplying communication services. In some aspects, slice template screen 202 can be provided by the user interface 106 of supply portal 104. Figure 2 In the example shown, interface screen 202 includes graphical elements representing components used to implement network slicing, including network functions 204A-204E, interfaces 206A-206F, and connections 208A-208C. In some aspects, function 204 can be any of functions 152-159 of core 105. Slicing template screen 202 can provide a user interface to incorporate network functions 204A-204E and network interfaces 206A-206F into a network slice template. Slicing template screen 202 can also be used to create and display connections 208 between interface 204 and function 206. Provisioning portal 104 can obtain available functions, interfaces, and other network infrastructure elements used when defining network slice templates from network topology 115 in database 108.

[0040] Users can utilize the slice template screen 202 to add slice components (such as function 204 and interface 206) to the network slice definition using control 210. After adding function 204 and interface 206 to the network slice template, users can use the interface provided in screen 202 to connect the function to the interface. Figure 2 In the example shown, NRF function 204A is connected to N4 interface 206A, AMF function 204D is connected to N4 interface 206A and N3 interface 206D, and UPF interface 204E is connected to N4 interface 206A, N1 interface 206B, and N6 interface 206E. Interface 206F can be a virtual network connecting multiple network functions. Figure 2In the example shown, management interface 206F can be a virtual network with management capabilities that connect multiple networks. Once a network slice template is created, it can be used as a blueprint for creating video stream slices.

[0041] In some respects, the slice template screen 202 can be used to assign one or more labels to function 204. Figure 2 In the example shown, NRF function 204A is labeled “edge”, AMF function 204D is labeled “low CPU”, and UPF function 204E is labeled “core”. Figure 2 The other functions 204 shown are also assigned labels. During the deployment of slices created using templates, provisioning system 102 can use the labels of functions 204 to match the functions used by the supplied slices to network infrastructure such as compute clouds or compute nodes. For example, a function with the label “edge” may indicate that it is desirable (or even mandatory) for provisioning system 102 to assign that function to resources in an edge compute cloud. For example, it may be desirable for NRF function 204A to be available with low latency, making it more desirable for provisioning system 102 to position NRF function 204A at the edge of the network slice infrastructure. In this case, NRF function 204A has been assigned the “edge” label. As another example, the “core” label may indicate that it is desirable for network functions to be assigned to resources closer to the core of the 5G network slice. For example, User Plane Function (UPF) 204 carries data between the data network and user equipment, and it may be desirable to position UPF 204 closer to the data network (e.g., closer to the core). Other location-related labels may include “region” or “country”. The "Low CPU" label indicates that the feature does not require high-performance processing power and can therefore be allocated to resources utilizing low-performance processors. The "SmartNIC" label indicates that the feature should be deployed to compute nodes with SmartNICs. Other labels may indicate the type of orchestration system used to deploy the tagged feature, such as "OpenShift," "OpenStack," or "Kubernetes." If the data center or cloud cannot support the capability associated with the label, the data center or cloud cannot host the tagged feature and may not be selectable by the user in the portal user interface 106.

[0042] In some respects, users can utilize the slice template screen 202 to obtain further information from the components displayed on screen 202. Figure 2In the example shown, the user has selected UPF function 204E, and in response, the supply portal 104 displays an information box 212 on screen 202 regarding UPF function 204E, including information related to the interface of UPF function 204E. Information box 212 may include control elements (e.g., buttons, menus, etc.) to configure the selected element (in this example, UPF function 204E), remove the selected element, or preview the selected element. In some aspects, in response to the selection of a preview control element, the supply portal 104 displays the constituent network functions, configuration, and interface of the selected element. If the element currently has no constituent elements, the preview control element can be disabled.

[0043] After a user has defined a network slice template, for example using screen 202, the user can assign a name to the network slice template and save it as one of the network slice templates 111 in the database 108 for later use in the on-demand provisioning of services facilitated by the network system 100.

[0044] return Figure 1 Database 108 may also include service template 110. Mobile network operators may define (possibly using user interface 106) service template 110. Service template 110 may include various templates with predefined network service attributes suitable for various types of communication services. For example, service template 110 may include templates with predefined attributes suitable for network slices designed to carry enhanced mobile broadband (eMBB) network services, massive machine-type communication (mMTC) services, ultra-reliable and low-latency communication (URLLC) network services, video streaming network services, augmented reality / virtual reality network services, cloud gaming network services, etc. Network service attributes may include tags identifying the characteristics of components of the network service, core or other functions used to provide the communication service, the interface used by the communication service, SLA, throughput, latency characteristics, uplink and downlink limits, the maximum number of user equipment (UE) devices allowed by the service, service priority, maximum number of sessions supported by the service, etc. Service templates can be used as blueprints for on-demand provisioning of communication services. For example, a mobile network operator's tenant can select a service template as described below to perform on-demand ordering and provisioning of communication services with attributes defined by the selected template.

[0045] Figures 3A-3G This is a conceptual diagram of a user interface screen for on-demand ordering and provisioning of communication services, based on the technology disclosed herein. (To be combined with...) Figure 1 To discuss from all aspects Figures 3A-3G The user interface screen. Generally speaking, Figures 3A-3GThe user interface screen is part of a workflow that a mobile network operator's tenant (or the mobile network operator itself) can execute to request on-demand provision of communication services. Figures 3A-3G The user interface screen shown in the example can be provided by user interface 106 to client device 101 for display on client device 101.

[0046] Figure 3A This is a conceptual diagram illustrating a service template selection screen 302 according to the technology of this disclosure. In some aspects, the service template selection screen includes template icons 304A-304H (collectively referred to as "template icons 304"), each representing a different service template defined in service template 110. In some aspects, the template icons may include the template name, template description, network slice template specified by the service template, priority of the network service offered, and service type. Users who wish to have new communication services offered can utilize user interface 106 to select one of the template icons 304 that most closely represents the type of communication service the user wishes to have offered.

[0047] The service template selection screen 302 includes a control interface element 310, which includes user interface elements that cause the supply portal 104 to perform actions when selected. For example, control interface element 310 includes an "Add Template" component that, when selected, causes the supply portal 104 to display a user interface for configuring a new service template. Other components of control interface element 310 may enable the supply portal 104 to apply filters to service templates 304 and / or search for specific service templates 304.

[0048] Figure 3B This is a conceptual diagram illustrating a service template definition screen 318 according to the technology of this disclosure. Figure 3B In the example shown, in response to Figure 3A The selection of template icon 304B,

[0049] The service template definition screen 318 is shown. Service template definition screen 318 displays the attributes of the selected service template. Examples of these attributes include the priority of the network service carried by the network slice created using the template (e.g., "20") and the type of network service carried by the network slice (e.g., "eMBB"). These attributes may also include service level attributes.

[0050] For example, in Figure 3BIn the example shown, the template specifies the maximum latency (e.g., "100ms"), the maximum number of UEs for the communication service (e.g., "100"), and the maximum number of Protocol 0 Data Unit (PDU) sessions for the communication service (e.g., "5000"). Other SLA attributes that can be specified include the minimum and maximum uplink throughput of the network slice (e.g., "100Mbps" and "300Mbps" respectively), the minimum and maximum downlink throughput of the network slice (e.g., "100Mbps" and "300Mbps" respectively), and the maximum uplink and downlink throughput per UE device (e.g., 5 "100Mbps" and "100Mbps" respectively).

[0051] The service template definition screen may include an edit user interface element 322 and an order user interface element 320. In response to the selection of the edit user interface element 322, the UI 106 of the supply portal 104 may present various attributes that the user can use to change provided by the selected service template.

[0052] The supply portal's UI 1060 can present further user interface screens in response to the selection of order user interface element 320, continuing the service order workflow. In some respects, the supply portal 104 can provide tenants with estimated costs for services supplied based on the selected template. For example, a communication service supplied using a service template specifying attribute values ​​for high throughput and / or low latency communication services can be priced higher than a communication service supplied using a service template that does not specify attribute values ​​for high throughput and / or low latency communication services.

[0053] 5 Figure 3C This is a conceptual diagram illustrating the general information section 326 of a service order definition screen 324 according to the technology of this disclosure. The UI 106 of the supply portal 104 can respond to a user selection of the "order" user interface element 320 on the client device 101. Figure 3B The service order definition screen 324 is then presented to the client device 101. The general information section 326 includes fields allowing the user to provide a communication service name 328 and a description 334 for the communication service to be provided. Furthermore, the general information section 326 includes fields that can be used to modify the attributes of the communication service from default information provided by the service template. For example, the general information section 326 may include a service type field 329, which can be used to change the service type of the communication service to be provided from the default information provided by the selected template. Similarly, the network slice template field 330 can be used to change the network slice template from the default information provided in the service template. The service template field 332 can be used to change the service template of the communication service to be provided to a different service template.

[0054] Figure 3DThis is a conceptual diagram illustrating the general slice information section 336 of a service order definition screen 324 according to the technology of this disclosure. The general slice information section 336 includes fields that allow the user to modify SLA-related attributes of the network slice to be supplied for the communication service. For example, the general slice information section 326 may include user interface elements that allow the user to modify SLA-related attributes from default information provided by a network slice template associated with a service template. Figure 3D In the example shown, these attributes include priority, maximum latency, maximum UE, maximum PDU sessions, minimum and maximum uplink throughput, minimum and maximum downlink throughput, maximum uplink throughput per UE, and maximum downlink throughput per UE.

[0055] Figure 3E This is a conceptual diagram illustrating a tracking area selection screen 340 for a service order according to the technology of this disclosure. Generally, a tracking area is a collection of one or more mobile network cells within a region, grouped together to help reduce the overhead involved in managing the UE. For example, when a UE moves from one cell in a tracking area to another cell in the same tracking area, a handshake protocol can be avoided. A network slice can be associated with multiple tracking areas. The tracking area selection screen 340 of UI 106 provides a selection mechanism for the tracking areas associated with network slices that will be provided as part of a communication service. For example, a tenant might want to localize the location where communication services are provided to its subscribers and can achieve this by selecting the desired tracking area from the selection screen 340. Figure 3E In the example shown, the tracking area selection screen 340 displays a map 342 showing tracking areas 344 within the region. Users can utilize the tracking area selection screen 340 to select one or more tracking areas 344 to include in a network slice to be provided for communication services.

[0056] The tracking area selection screen 340 includes a legend 346 illustrating various aspects of the tracking area 344 shown on the screen. As an example, legend 346 shows color-coded bars that can indicate the alarm status and severity associated with the tracking area. The tracking area selection screen 340 also includes a control menu 348 with interface elements for selecting the tracking area 344 within a region, zooming in or out of the map, etc. In some aspects, users can use the area selection tool 349 to select a mobile network operator's tracking area, located within a region bounded by a rectangle formed using the area selection tool 349. As an example, a tenant might expect to provide dedicated communication services within or near the stadium. The tenant can use the area selection tool 349 to define the desired area around the stadium on a map 342.

[0057] Figure 3FThis is a conceptual diagram illustrating a subscriber screen 350 for service orders according to the technology disclosed herein. The subscriber screen 350 of UI 106 can display a list 352 of subscribers associated with the tenant providing the communication services. The tenant can select from the list the subscribers who will be granted access to the communication services provided by the tenant. Figure 3F In the example shown, subscriber set 354 is selected to be granted access to the communication service once it is supplied.

[0058] Figure 3G This is a conceptual diagram illustrating a computing cloud selection screen 360 for service orders according to the technology disclosed herein. Figure 3G In the example shown, the computing cloud selection screen 360 displays a map 362, which shows icons 364 representing computing clouds and / or data centers within a region. In some respects, the computing clouds and / or data centers displayed on map 362 may be limited to those previously accessed via… Figure 3E The tracking area selection screen 340 selects the computing cloud and / or data center within the tracking area. The user can utilize the computing cloud selection screen 360 to select one or more icons 364 representing the computing cloud and / or data center that will provide computing resources to perform workloads involved in providing the communication services to be supplied. For example, workloads may include radio access network (RAN) functions, core 105 functions, etc. The user can select the computing cloud based on the desired characteristics of the communication service. For example, if low latency is desired for end users, the user can select the icon 364 representing the edge cloud. Furthermore, the user can select an icon representing the core cloud to locate the centralized unit (CU) near the core cloud, and can select an icon representing the edge cloud to locate the distributed unit (DU) at the edge cloud. In some aspects, the computing cloud may have labels indicating its characteristics. For example, the computing cloud may have labels indicating whether it is an edge computing cloud or a core computing cloud. Additionally, labels may indicate the processing power of the computing cloud. Other labels may indicate other characteristics of the computing cloud. Mobile network operators may assign such labels to computing clouds.

[0059] The computing cloud selection screen 360 may include a legend 366 that provides information about elements on map 362. As an example, legend 346 shows color-coded bars that can indicate the alert status and severity associated with the computing cloud shown on map 362. Computing Cloud Selection

[0060] Screen 360 also includes a control menu 368, which provides user interface elements such as icons 364 and 5 for selecting regions, zooming in or out of the map, etc.

[0061] return Figure 1 In some respects, Figures 3A-3GThe screen shown can be used to complete a workflow for collecting information from users about communication services that will be provided on demand by the mobile network operator. This information can be used to create a service order 112 that can be processed by the provisioning system 102 to provide the desired communication services.

[0062] Placement unit 120 can provide the information in service order 112 as input to the placement algorithm (also known as the homing algorithm) executed by placement unit 120, which can determine the tracking area selected by the user and the placement communication service elements (e.g., CU and DU) within the computing cloud as described above. In some aspects, placement unit 120 is based on network slice elements.

[0063] Associated tags are used to place communication service elements. As an example, the placement algorithm can match the attributes of the communication service specified in the service order with tags associated with infrastructure elements and compute cloud elements in the network slice template. For instance, placement unit 120 might attempt to place a DU whose attributes indicate a need for low-latency communication services in a DU located at the user-selected edge cloud. Placement unit 120 can use other characteristics and attributes to determine communication...

[0064] The placement of network resources used by the service. For example, placement unit 120 can use tags associated with each computing cloud whose service scope can be defined (e.g., edge, region, country). Furthermore, placement unit 120 can utilize tags specifying container runtimes (e.g., Kubernetes, OpenStack, etc.) to constrain workload placement to resources supporting the specified container runtime. Additionally, workloads in the communication services to be deployed...

[0065] When the placement unit has characteristics indicating a need (or expectation) for a smart NIC, it can utilize tags indicating that network resources include smart NICs. Furthermore, the placement unit 120 can consider affinity constraints. For example, the placement unit can attempt to place the CU in the same cloud (or cloud provider) as the DU.

[0066] In some respects, Figure 3G The computing cloud selection screen 360 can be an optional part of the workflow. In these respects, the placement algorithm of placement unit 120 can be automatically included via... Figure 3E The tracking region selection screen 340 selects the computing cloud and data center within the tracking region. In some respects, users can optionally use the computing cloud selection screen 360 to provide more granular selection of the computing cloud and / or data center.

[0067] In some respects, deployment unit 120 can generate a cost estimate for users associated with the communication service to be provided. This estimate can be provided to the user, who can then use it to determine whether the communication service should be deployed by deployment unit 122.

[0068] In some aspects, placement unit 120 can determine whether there is a feasible placement for the communication service elements required to supply the communication service. If such a feasible placement exists, the placement details can be provided as input to deployment unit 122, which can perform the supply of the communication service based on service order 112 and the placement determined by placement unit 120. If no feasible placement exists, the placement details can be used... Figures 3A-3G If the workflow collects parameters and information regarding the feasible placement of the communication service, then the provisioning portal 104 can notify the user that the communication service cannot be deployed as specified. The user can then return to... Figures 3A-3G The screen can be modified to modify parameters so that the feasibility of communication services regarding the placement of network resources can be re-determined by the placement unit 120.

[0069] exist Figure 3E and Figure 3G The example workflow screen shown provides the user with a map view of the tracking area and the computing cloud. Alternatively, or as an alternative, a list view of the tracking area and the computing cloud can be provided.

[0070] Figure 4 This is a conceptual diagram of a user interface screen illustrating a service order history, based on the technology disclosed herein. Figure 4 In the example shown, the service order history screen 402 includes orders already received for deployment unit 122 ( Figure 1 A list of processed service orders (404). The service order history indicates whether a service order has been received but not yet processed, is currently being processed, has been completed, or has failed to process.

[0071] Figure 5 This is a flowchart illustrating an example operation of a supply portal according to one or more technologies of this disclosure. The supply portal may receive a selection of a service template for a network service attribute of a specified communication service from a client device (505). Next, the supply portal may receive a selection of one or more tracking regions (510). Next, the supply portal may receive a selection of one or more computing clouds and / or data centers (515). Next, the supply portal may generate a service order based on the communication service, one or more tracking regions, and the network service attributes of one or more computing clouds (520). Next, the supply system may supply the communication service according to the service order (525).

[0072] Figure 6This is a block diagram illustrating further details of an example of a computing device operating according to one or more technologies of this disclosure. Figure 6 Specific examples of a server or other computing device 600 may be shown, which includes one or more processors 602 for executing any one or more of the provisioning portal 104, placement unit 120, deployment unit 122, or any other system, application, node software, or module described herein. Other examples of the computing device 600 may be used in other instances. Although for illustrative purposes... Figure 6 The device is shown as a standalone computing device 600, but a computing device may include one or more processors or other suitable computing environments for executing software instructions and, for example, need not include... Figure 6 Any component or system shown with one or more elements (e.g., communication unit 606; and in some examples, components such as storage devices 608 may not be located in the same location as other components or in the same chassis). Figure 6 As shown in a specific example, computing device 600 includes one or more processors 602, one or more input devices 604, one or more communication units 606, one or more output devices 612, one or more storage devices 608, and a user interface (UI) device 610. In one example, computing device 600 also includes one or more applications 622 and an operating system 616 executable by computing device 600. Each of components 602, 604, 606, 608, 610, and 612 is coupled (physically, communicatively, and / or operatively) for inter-component communication. In some examples, communication channel 614 may include a system bus, network connection, inter-process communication data structure, message bus, or any other method for transmitting data. As an example, components 602, 604, 606, 608, 610, and 612 may be coupled through one or more communication channels 614.

[0073] In one example, processor 602 is configured to implement functional and / or procedural instructions for execution within computing device 600. For example, processor 602 may be a processing circuitry system capable of processing instructions stored in storage device 608. Examples of processor 602 may include any one or more of a microprocessor, controller, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or equivalent discrete or integrated logic circuitry system.

[0074] One or more storage devices 608 may be configured to store information within computing device 600 during operation. In some examples, storage device 608 is described as a computer-readable storage medium. In some examples, storage device 608 is temporary memory, meaning that the primary purpose of storage device 608 is not long-term storage. In some examples, storage device 608 is described as volatile memory, meaning that storage device 608 does not maintain its stored contents when the computer is turned off. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory known in the art. In some examples, storage device 608 is used to store program instructions executed by processor 602. In one example, storage device 608 is used by software or an application running on computing device 600 to temporarily store information during program execution.

[0075] In some examples, storage device 608 also includes one or more computer-readable storage media. Storage device 608 can be configured to store a larger amount of information than volatile memory. Storage device 608 can also be configured for long-term storage of information. In some examples, storage device 608 includes non-volatile storage elements. Examples of such non-volatile storage elements include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM).

[0076] In some examples, computing device 600 also includes one or more communication units 606. In one example, computing device 600 uses communication unit 606 to communicate with external devices via one or more networks, such as one or more wired / wireless / mobile networks. Communication unit 606 may include a network interface card, such as an Ethernet card, an optical transceiver, an RF transceiver, or any other type of device capable of transmitting and receiving information. In some examples, computing device 600 uses communication unit 606 to communicate with external devices.

[0077] In one example, computing device 600 also includes one or more user interface devices 610. In some examples, user interface devices 610 are configured to receive input from a user via haptic, audio, or video feedback. Examples of the multiple user interface devices 610 include presence-sensitive displays, mice, keyboards, voice response systems, cameras, microphones, or any other type of device used to detect commands from the user. In some examples, presence-sensitive displays include touch-sensitive screens.

[0078] The computing device 600 may also include one or more output devices 612. In some examples, the output device 612 is configured to provide output to a user using tactile, audio, or video stimuli. In one example, the output device 612 includes a presence-sensitive display, a sound card, a video graphics adapter card, or any other type of device for converting signals into an appropriate form that is understandable to humans or machines. Other examples of the output device 612 include a speaker, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD), or any other type of device that can generate understandable output to a user.

[0079] Computing device 600 may include operating system 616. In some examples, operating system 616 controls the operation of components of computing device 600. For example, in one example, operating system 616 facilitates communication between one or more applications 622, access network intelligent controller 102 and / or access network agent 624 and processor 602, communication unit 606, storage device 608, input device 604, user interface device 610 and output device 612.

[0080] Application 622 may also include program instructions and / or data executable by computing device 600. Example application 622 executable by computing device 600 may include applications and / or other software for implementing the capabilities described above. For example, application 622 may include applications associated with supply portal 104, placement unit 120, and deployment unit 122.

[0081] Figures 7A-7B This is a conceptual diagram of a user interface screen for providing network services according to the technology of this disclosure. In some examples, Figures 7A-7B The user interface screen can be made by Figure 1 UI 106 presentation.

[0082] Network templates or blueprints are fundamental building blocks for network slices used in services such as private 5G mobile, augmented reality (AR), virtual reality (VR), cloud gaming, and massive Internet of Things (MIoT). These templates include essential information such as the network function descriptor (NFD), network slice subnet template (NSST), network links, configurations, SLA attributes, etc. These slice / slice-subnet templates, along with the GSMA Common Network Slice Template (GST) or Network Slice Type (NEST) attributes, are used to deploy network slices. Designing network templates or blueprints can be complex due to the need to handle multiple components, network configurations, and interconnect links. With the advent of 5G and NFV (Network Functions Virtualization), the telecom community has long needed a robust design studio that provides the ability to design arbitrary and meaningful network blueprints with topology and feasibility support. Other systems may use different visual styles and do not offer drag-and-drop functionality. Such other systems do not support cloud affinity tags for locating and placing network functions. Furthermore, other systems lack a real-time feedback loop to validate the topology and feasibility of the designed templates.

[0083] Based on the technology disclosed herein, devices, systems, and methods are described that provide users with the ability to design and manage slice templates or blueprints in interactive and visual design studios. The systems disclosed herein provide a user interface that enables users to design multiple templates, including:

[0084] Domain-level Network Slice Subnet Templates (NSSTs). A domain-level NSST is a set of one or more network function descriptors or NSSTs interconnected in a complex topology for domain-specific services.

[0085] Root-level network slice subnet template (or end-to-end network slice template). A root-level NSST is a set of NSSTs (RAN, core, transport network (TN)) that provide end-to-end services.

[0086] The system described in this paper provides a user interface that enables users to design arbitrary and meaningful network blueprints using topology and feasibility aids. In some examples, the system can provide drag-and-drop functionality for designing NSSTs. Furthermore, the system can cloudify affinity tags for the placement and allocation of network functions. In some examples, the system can provide a real-time feedback loop to verify the topology and feasibility of the designed template.

[0087] Figure 7A This is a conceptual diagram of a user interface screen for adding slice templates for use in providing web services, based on the technology disclosed herein. In some examples, Figure 7A The user interface screen can be made by Figure 1 UI 106 presentation. Figure 7AThe example shows a scenario where a user adds a slice template for slicing a video stream. For example... Figure 7A As shown, users can select one or more components for use within the N1 interface of a slice defined by a slice template. In some examples, Figure 7A The user interface allows users to add components from multiple component lists, including the "General" list and the "Service" list.

[0088] Figure 7B This is a conceptual diagram of a user interface screen for adding slice templates for use in providing web services, based on the technology disclosed herein. In some examples, Figure 7B The user interface screen can be made by Figure 1 The UI 106 presentation. (Example) Figure 7B As shown, the user can select one or more components for use within each of the N4, N1, N2, N3, N6, and Mix interfaces of the slice defined by the slice template. In some examples, Figure 7B The user interface allows users to add components from multiple component lists, including a "Features" list, a "Slice Subnet" list, and a "Label" list.

[0089] Figure 8 This is a conceptual diagram of a user interface screen for providing network services according to the technology of this disclosure. Specifically, Figure 8 A conceptual diagram of a user interface screen for adding slice templates for use in a provisioning web service, according to the technology of this disclosure, is shown. In some examples, Figure 8 The user interface screen can be made by Figure 1 The UI 106 presentation. (Example) Figure 7B As shown, the user can select one or more components for use within each of the N1, N2, N3, N4, and N6 interfaces of the slice defined by the slice template. In some examples, Figure 8 The user interface allows users to add components from multiple component lists, including the "General" list and the "Service" list.

[0090] Figures 9A-9B This is a conceptual diagram of a user interface screen for providing network services according to the technology of this disclosure. In some examples, Figures 9A-9B The user interface screen can be made by Figure 1 UI 106 presentation.

[0091] The user interface described in this article provides a design studio that enables administrators to design and configure intent-based slice templates in complex topologies with a simple and streamlined solution. Using this studio, administrators can combine, connect, and configure network functions, slice subnets, and network links.

[0092] As described in this article, administrators can use the Design Studio provided by UI 106 to create domain-specific slice-subnet templates by importing and interconnecting NFD and / or other slice-subnet templates using network links (with or without slice support). For example, administrators can use the Design Studio provided by UI 106 to create end-to-end slice templates by importing and interconnecting domain-specific slice-subnet templates (with or without slice support).

[0093] In some examples, the Design Studio provided by UI 106 can offer a user interface that allows users to import Virtualized Network Functions (VNFs), Cloud-Native Network Functions (CNFs) (sometimes referred to as containerized network functions), and Physical Network Functions (PNFs) from the Network Function Descriptor Inventory, and to import pre-designed slice-subnet templates from the Template Inventory. In some examples, the Design Studio provided by UI 106 can offer a user interface that allows users to configure network links to interconnect network functions and / or slice-subnet templates. In some examples, the Design Studio provided by UI 106 can offer a user interface that allows users to add cloud affinity tags to network functions for home and placement during deployment. In some examples, the Design Studio provided by UI 106 can offer a user interface that allows users to add individual networks and connect network functions to them using interfaces. In some examples, the Design Studio provided by UI 106 can offer a user interface that allows users to zoom in or out. Furthermore, the Design Studio can offer the ability to display a “mini-map” of the entire design while allowing users to focus on specific parts of the design.

[0094] Figure 9A This is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 9A The example shows a sliced ​​subnet template for video streaming RAN services. Figure 9A As shown, users can import, export, or clear one or more templates. Furthermore, users can select one or more components to use within each of the N4, N1, N2, N3, N6, and Mix interfaces of the slice subnet defined by the slice subnet template.

[0095] Figure 9B This is a conceptual diagram of a user interface screen for adding network functionality to a sliced ​​subnet template for use in providing network services, based on the technology disclosed herein. Figure 9B As shown, users can... Figure 9A Add network functionality to the slice subnet template. Figure 9B The user interface allows users to define one or more interfaces, properties, or labels for network functions.

[0096] In other examples, the techniques disclosed herein implement a user interface screen for adding slice templates to video stream slices. In this example, the user can select a slice subnet template for use within each of the N4, N1, N2, N3, N6, and Mix interfaces of the slice defined by the slice template.

[0097] In some examples, the techniques disclosed herein provide user interface screens for testing or validating slice templates used in provisioning network services. After the user provides general information and configuration of the slice template, the user interface can test or validate the configuration before allowing the user to deploy slices based on the slice template. In some examples, the user interface can provide the user with a list of errors or warnings based on the results of slice template validation.

[0098] Figures 10A-10F This is a conceptual diagram of a user interface screen for providing network services according to the technology of this disclosure. In some examples, Figures 10A-10F The user interface screen can be made by Figure 1 UI 106 presentation.

[0099] In some examples, Figures 10A-10C The user interface enables users to design multi-domain slices or slice subnets. In some examples, UI 106 provides a design studio, which allows users to design slice templates or slice subnet templates for multiple domains such as RAN, core, transport network, and value-added services (e.g., IP Multimedia Subsystem (IMS)). Figures 10A-10C The user interface shows an example of a domain-specific slice subnet that can be designed as described in this article.

[0100] In some examples, the techniques disclosed herein enable user interface screens to add slice subnet templates used in the provisioning network services. Specifically, such a user interface can display templates for RAN slice subnets that include Open RAN (O-RAN) network functions and near-real-time RAN Intelligent Controllers (near-RT RICs).

[0101] Figure 10A This is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 10A The examples illustrate sample slice subnet templates for 5G core slice subnets that include 5G core network functions. In some examples, the user interface described herein enables users to design complete 5G core slice subnets. For example... Figure 10A As shown, the design studio provided by UI 106 enables users to design 5G core slice subnets (Level 1-) by importing one or more network functions.

[0102] Figure 10BThis is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 10B The example shows a sample of a value-added service slice subnet template for the IMS core subnet.

[0103] Figure 10C This is a conceptual diagram of a user interface screen for editing a network slice template according to the technology disclosed herein. Figure 10C The example shows a sample network slice template for eMBB video stream network slicing. For example... Figure 10C As shown in the example, users can design slice templates via UI 106 to provide end-to-end services by connecting domain-specific slice subnets all the way from the RAN to the core and then to the IMS.

[0104] In some examples, Figure 10D-10F The user interface enables users to design multi-level slices or slice subnets. In some examples, the design studio provided by UI 106 allows users to create hierarchical templates by importing slice subnets within slice subnets. In some examples, users can design complete O-RAN slice subnets. For example, users can design O-RAN slice subnets (Level 1) via UI 106 by importing one or more network functions.

[0105] Figure 10D This is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 10D The example shows a sample slice subnet template for O-RAN cellular slice subnets. Figure 10D An example of a hierarchical O-RAN slice subnet is shown. For example, Figure 10D The user interface allows users to break down O-RAN network functions into multiple slice subnet templates to achieve sharing, template reusability, etc., instead of importing all network functions into a single template.

[0106] Figure 10E This is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 10E The example shows a slice subnet template for O-RAN edge slice subnets.

[0107] Figure 10F This is a conceptual diagram of a user interface screen for adding sliced ​​subnet templates for use in providing network services, based on the technology disclosed herein. Figure 10F The example shows a slice subnet template for a fully sliced ​​O-RAN subnet. In some examples, users can import templates like the one above. Figure 10D and 10EThe slice subnet template defines the slice subnet to design the O-RAN fully slice subnet (Level 2 subnet) via UI 106.

[0108] In some examples, the user interface described herein enables users to design hierarchical 5G core slice subnets. Instead of importing all network functions into a single template, the design studio provided by UI 106 allows users to break down 5G core network functions into multiple slice subnet templates for sharing, template reusability, and more. For example, the techniques disclosed herein can enable the user interface to add slice subnet templates for use in provisioning network services. For example, a 5G core data plane slice subnet includes data plane network functions in the 5G core. A 5G core management plane slice subnet includes management plane network functions in the 5G core. A complete 5G core slice subnet (Level 2 slice subnet). In some examples, users can design a complete 5G core slice subnet via UI 106 by importing slice subnets defined by the 5G core data plane slice subnet and the 5G core management plane slice subnet of this example.

[0109] Figures 11A-11C This is a conceptual diagram of a user interface screen for providing network services according to the technology of this disclosure. In some examples, Figures 11A-11C The user interface screen can be made by Figure 1 UI 106 presentation.

[0110] In some examples, Figures 11A-11C The user interface shown enables the orchestration and placement of network functions across large-scale heterogeneous infrastructures. For example, in a telecommunications environment, there may be 10,000 to 100,000 cloud-hosted slice workloads, depending on network coverage. Each of these clouds may have its own attributes, such as domain (e.g., cellular, edge, region, country, etc.), location, capacity (e.g., compute, storage, etc.), or other attributes not explicitly described herein. During slice orchestration, administrators can deploy network functions to these clouds to provide services. Due to the scale and heterogeneity of the infrastructure, providing placement logic for these network functions can be a complex task.

[0111] This article describes a design studio provided by UI 106 that offers users a simple way to add placement logic by enabling them to add tags to network features. In some examples, the tags follow "name:value" semantics, such as "cloud domain: edge", "cloud domain: country", "location: CA", or "location: NYC".

[0112] In addition, users can attach attributes such as cloud affinity or anti-affinity to web functions using tags provided by UI 106. Users can attach these tags to web functions during design time, and provisioning system 102 can parse the tags to place these web functions during orchestration.

[0113] In some examples, users can import CNF descriptors (CNFD) or PNF descriptors (PNFD) from the Network Functions (NF) catalog. Each NF in the NF catalog can include predefined placement properties, or users can define such placement properties during design time in the design studio provided by UI 106.

[0114] In some examples, users can define additional NF-specific placement attributes or labels. As an example, a user can specify that for the first NSST, the first NF will be placed at the edge of the EMEA region. To define this standard for the first NSST, the user can add a first label "Cloud Domain: Edge" and a second label "Location: EMEA" to the network function in the first NSST via UI 106.

[0115] In some examples, UI 106 can automatically determine which NFs or sub-NSSTs can coexist in the same cloud or share the same placement criteria, eliminating the need for users to specify such criteria. Therefore, users can design logical NSSTs with one or more NFs and / or one or more sub-NSSTs via UI 106, each potentially sharing (or not sharing) the same placement attributes. At instantiation, the Service Management and Orchestration (SMO) of Provisioning System 102 determines the placement of each NF based on NF-specific user-defined tags, cloud topology, available resources, hardware requirements, SLA requirements, etc. In some examples, the SMO uses such criteria to determine the optimal or best placement of each NF within the NSST.

[0116] Figure 11A This is a conceptual diagram of a user interface screen for adding slice templates for use in providing web services, based on the technology disclosed herein. Figure 11A The examples show sample slice templates for video stream slicing. In some examples, the user interface allows users to add components from multiple component lists, including a "General" list and a "Service" list. For example... Figure 11A As shown in the example, by hovering the cursor over the “UPF” element, UI 106 can present a window displaying the element’s properties, such as a list of interfaces associated with the “UPF” element.

[0117] Figure 11B This is a conceptual diagram of a user interface screen for adding slice templates for use in providing web services, based on the technology disclosed herein. Figure 11B The example shows how to add network functionality to a slice template. For example... Figure 11B As shown, users can... Figure 11A Add network functionality to the slice template. Figure 11B The user interface allows users to define one or more interfaces, properties, or tags for network functions. Figure 11B In the example, the user interface allows the user to define one or more interfaces, the name of each interface, and the network link for each interface.

[0118] Figure 11C This is a conceptual diagram of a user interface screen for adding slice templates for use in providing web services, based on the technology disclosed herein. Figure 11C The example shows how to add network functionality to a slice template. For example... Figure 11C As shown, users can... Figure 11A Add network functionality to the slice template. Figure 11C The user interface allows users to define one or more interfaces, properties, or tags for network functions. Figure 11C In the example, the user interface allows the user to define one or more labels, the value of each label, the key of each label, the description of each label, the identifier of the user who created each label, and the total number of objects associated with each label.

[0119] In some examples, the techniques disclosed herein implement a user interface for adding network functionality to a slice template. The user interface allows users to define one or more interfaces, properties, or labels for network functionality. In some examples, the user interface provides a "filter" element that allows users to define one or more rules for labels. In some examples, the user interface enables users to define one or more interfaces, properties, or labels using one or more Boolean operators. In some examples, UI 106 enables users to define a "cloud" field with the value "edge" and a "location" field with the value "EMEA". The use of the Boolean operator "AND" requires both the "cloud" and "location" fields to be satisfied.

[0120] In some examples, UI 106 enables the implementation of pre-configured templates. For instance, slice or service administrators can design services from scratch via UI 106 by importing network function and / or network slice subnet templates. Furthermore, users can import existing templates for standard Cloud Service Profile (CSAR) packages via UI 106 and store them in the DB108 inventory.

[0121] In some examples, the design studio provided by UI 106 offers a basic set of pre-designed and configured templates to assist users in template design. In some examples, the pre-designed templates may include basic eMBB CN (core network) NSST, basic eMBB RAN (radio access network) NSST, or basic 5G NST, etc. Using such pre-designed templates allows users to start with a basic topology and configuration, rather than starting from scratch. In some examples, UI 106 enables users to customize the pre-designed templates by adding, removing, or updating network functions, network links, or other configurations to achieve the desired topology or design.

[0122] In some examples, the Design Studio provided by UI 106 allows users to perform real-time template validation of slices and slice subnet templates. For instance, the Design Studio provided by UI 106 can provide real-time feedback on the correctness and feasibility of templates. Therefore, UI 106 can help users identify misconfigurations and suggest remedial measures during design time.

[0123] In some examples, UI 106 may perform the following steps during design-time validation. UI 106 converts a user-defined template into a Topology and Orchestration Specification for Cloud Applications (TOSCA) format. UI 106 then sends the template to the validator service. In some examples, UI 106 sends the template to the validator service at regular intervals or when adding or configuring new components. Upon receiving the template, the validator service performs checks and updates the designer view provided by UI 106 with the results. If the validator service identifies an error, UI 106 displays one or more warning icons on each added element with the detected error. Furthermore, UI 106 may indicate the reason or explanation for each warning.

[0124] In some examples, the design studio provided by UI 106 can offer enhanced service eligibility and feasibility. For instance, UI 106 enables slice administrators to perform service pre-order eligibility checks to verify the technical suitability and feasibility of a designed template to be deployed on the provided infrastructure. As part of the design workflow, users can provide GSMA GST / NEST attributes, such as uplink / downlink throughput, service area, maximum number of UEs / PDUs, etc. Once the user has designed the template and configured it using the GST attributes, the slice administrator can select the verification function via UI 106, where a feasibility request for the template is sent to the orchestrator. In response to receiving the feasibility request, the orchestrator creates a deployment plan (homing and placement) and performs eligibility checks on the infrastructure to meet SLA requirements. The orchestrator sends the results of the feasibility test to UI 106 for display to the user. This workflow provided by the system described herein allows slice administrators to verify the feasibility of designed templates without actually deploying the slices.

[0125] In some examples, UI 106 can use one or more colors to represent one or more elements of a network slice, sub-slice, or service designer. In some examples, UI 106 can select one or more colors based on severity, or it can indicate more or fewer components, networks, network functions, and labels than shown in the preceding examples. In some examples, UI 106 can use one or more interactive or non-interactive diagrams to present visualizations of one or more aspects of a network slice, cloud, or cell tower. In some examples, UI 106 can present dynamic visualizations representing multiple network functions and provide an interface that allows users to drag and drop individual network functions. In some examples, UI 106 may include one or more customizable containers that allow users to visualize labels or other functional details. As mentioned above, UI 106 can provide one or more basic, pre-designed, and configured templates to assist users in template design.

[0126] In some examples, UI 106 can provide real-time feedback on the correctness and feasibility of the designed template. Therefore, slice administrators can perform service subscription eligibility checks via UI 106 to verify the technical suitability and feasibility of deploying the design template on the provided infrastructure without deploying the template itself.

[0127] In some examples, UI 106 uses Scalable Vector Graphics (SVG) technology and a graphics layout library to allow users to create configurable and dynamic layouts. The visualization of the UI technology and graphics layout library provided by the user interface described in this paper is not available using other methods previously. Furthermore, the user interface described in this paper allows users to customize tag details and network details for templates used for network slices, sub-slices, or services.

[0128] According to the technology disclosed herein, the UI 106 of the supply portal 104 can provide a user interface that enables users of client device 101 to execute basic end-to-end network slices with multi-cloud and multi-domain support (RAN, transport network, core, SGI). The technology described herein enables UI 106 to provide a service designer interface that users can use to design complete services and network slices and store the designed services and network slices in a database.

[0129] 0 Furthermore, the techniques described in this article enable UI 106 to provide a slice designer interface.

[0130] The slice designer interface can use cloud topology information when instantiating network slices to place network slice subnets on the appropriate cloud based on the (cloud and NSST) affinity tag and cloud topology information.

[0131] In one example, a user, such as an administrator of a network service provider, can import a CNFD or PNFD into the NF catalog via 5UI 106, where each NF can have its own placement requirements. For example, each NF can include an "application descriptor" for use in tag-based CNF placement in a multi-cloud environment. In some examples, users can define additional NF-specific placement attributes or tags.

[0132] In some examples, users can design logical NSSTs (e.g., RAN, core) via UI 106 by grouping domain-specific NFs and / or 0 sub-NSSTs together and connecting them to logical links in the data plane and control plane. For example, users can design a logical RAN NSST consisting of RU, DU, CU sub-NSSTs (CU-UP, CU-CP) and near-RT RICs with their connectivity requirements via UI 106.

[0133] In some examples, users can define additional NF-specific placement attributes or labels via UI 106. For example, a user can define an attribute for an NSST that requires the NSST's NF to be placed at the edge. In some examples, UI 106 can automatically determine whether an NF and its child NSSTs can coexist in the same cloud and share the same placement criteria, eliminating the need for the user to make such a determination. UI 106 thus allows users to design logical NSSTs with one or more NFs or child NSSTs that may or may not share the same placement attributes. Then, at instantiation, SMO can determine the optimal or best placement for each NF based on NF-specific user-defined labels, cloud topology, available resources, hardware requirements, SLA requirements, etc. The designed NSSTs are stored in the SMO NSST directory in database 108 and can be used to include in other NSST or NST designs.

[0134] In some examples, users can design logical NSTs (end-to-end slices) by combining one or more NSSTs via UI 106. The designed NSTs are stored in the SMO NST catalog in database 108 and can be included in communication service templates.

[0135] In some examples, users define one or more communication services by combining one or more NSTs with a service profile or SLA. The designed CSTs are stored in the SMO CST catalog in database 108 and are available for ordering.

[0136] In some examples, the tag management elements of UI 106 can be modified to use severity colors, include additional features to show more components, or manage network lines, network functions, or tags. In some examples, tag management visualizations can be used in any interactive and non-interactive graphs related to network slices, cloud, or cell towers. The tag management visualizations described in this paper provide a dynamic way to assign and filter network functions. Furthermore, tag-based filtering allows users to visualize and manage network functions, interfaces, and network links. In some examples, tag management uses SVG technology and a graphical layout library to allow for configurable and dynamic layouts. In some examples, the tag management techniques described in this paper include backend placement algorithms. This visualization, combining UI technology and a graphical layout library, provides users with a mechanism for understanding network slices and network slice subnet deployments that was previously unavailable.

[0137] Figure 12 This is a flowchart illustrating operations for providing network services according to the technology of this disclosure. In some examples, Figure 12 The operations shown can be performed by Figure 1 The UI of the supply portal 104 and 106 Figure 1The network system 100 is implemented through the supply system 102.

[0138] The UI 106 of the provisioning portal 104 provides a user interface for adding network slice templates 111 for use in provisioning network services. For example, UI 106 receives instructions (1202) from a first user, such as an administrator, regarding a first selection of one or more network functions 204. Furthermore, UI 106 receives instructions (1204) from the first user regarding a second selection of one or more labels specifying the placement of one or more network functions. The provisioning system 102 can define NSST 113 (1206) based on the first and second selections. For example, NSST 113 can specify the selected one or more network functions and their placement, such that NSST 113 defines a pre-configured portion of the network slice. The provisioning portal 104 stores the defined NSST 113 in an SMO directory hosted by database 108 (1208).

[0139] UI 106 receives an instruction (1210) from a second user, such as a mobile network operator, for a third selection of one or more NSSTs 113. In this example, the one or more selected NSSTs 113 include the NSSTs 113 defined above based on the first and second selections. Provisioning system 102 obtains one or more NSSTs 113 from the SMO catalog of database 108 in response to the instruction for the third selection (1212). Each NSST 113 defines a portion of a network slice. Provisioning system 102 may define an NST 111 based on one or more NSSTs 113, where the NST 111 defines an end-to-end network slice. Deployment unit 122 of provisioning system 102 deploys the network slice according to the NST 111 (1216).

[0140] The following examples illustrate one or more aspects of this disclosure.

[0141] Example A1. A method includes: obtaining one or more network slice subnet templates (NSSTs) by a processing circuitry system; defining a network slice template (NST) by the processing circuitry system based on the one or more NSSTs; and deploying network slices by the processing circuitry system according to the NSTs.

[0142] Example A2. According to the method of Example A1, obtaining one or more NSSTs includes: obtaining one or more domain-level NSSTs for a domain-specific network service; or obtaining one or more root-level NSSTs for an end-to-end network service.

[0143] Example A3. A method according to any combination of Examples A1 to A2, wherein obtaining one or more NSSTs includes obtaining one or more of the following by a processing circuitry system: Radio Access Network (RAN) domain NSST; 5G core domain NSST; Transport Network domain NSST; Value-added Services domain NSST; or Enhanced Mobile Broadband (EMBB) domain NSST.

[0144] Example A4. Obtaining one or more NSSTs according to any combination of Examples A1 to A2 includes: obtaining the NSST of each of a plurality of domains by the processing circuitry system; and defining the domain NSST by the processing circuitry system based on the NSST of each of the plurality of domains.

[0145] Example A5. According to the method of Example A4, wherein obtaining the NSST of each of the multiple domains includes: obtaining the Open Radio Access Network (O-RAN) cellular NSST by a processing circuitry system; obtaining the O-RAN edge NSST by a processing circuitry system; and wherein defining the domain NSST includes defining the O-RAN full NSST based on the O-RAN cellular NSST and the O-RAN edge NSST.

[0146] Example A6. According to the method of Example A4, wherein obtaining the NSST of each of the multiple domains includes: obtaining the 5G core data plane NSST by the processing circuitry system; obtaining the 5G core management plane NSST by the processing circuitry system; and wherein defining the domain NSST includes defining the 5G core complete NSST based on the 5G core data plane NSST and the 5G core management plane NSST.

[0147] Example A7. A method according to any combination of Examples A1 to A6, wherein obtaining one or more NSSTs includes: presenting one or more pre-configured NSSTs to a user via a user interface by a processing circuitry system; receiving input from the user by the processing circuitry system and via the user interface; and modifying one or more pre-configured NSSTs with the input to obtain one or more NSSTs.

[0148] Example A8. According to the method of Example A7, one or more pre-configured NSSTs include at least one of the following: Basic Enhanced Mobile Broadband (eMBB) Core Network (CN) NSST; Basic Enhanced Mobile Broadband (eMBB) Radio Access Network (RAN) NSST; or Basic 5G NST.

[0149] Example A9. A method based on any combination of Examples A1 to A8, wherein defining an NST includes receiving from a user via a user interface an instruction to select one or more labels specifying one or more criteria, and wherein deploying a network slice includes selecting one or more network functions from a plurality of network functions identified by one or more NSTs for inclusion within the deployed network slice, wherein the selected one or more network functions satisfy one or more criteria specified by one or more labels.

[0150] Example A10. According to the method of Example A9, one or more criteria of one or more tags include one or more of the following: the cloud used to deploy network slices; or the region used to deploy network slices.

[0151] Example A11. The method according to any combination of Examples A1 to A10 also includes verifying the NST by the processing circuit system.

[0152] Example A12. According to the method of Example A11, wherein validating the NST includes: converting the NST into a Topology and Orchestration Specification (TOSCA) format for cloud applications by a processing circuitry system; sending the converted NST to a validator service by the processing circuitry system; receiving one or more warnings for the NST from the validator service by the processing circuitry system; and displaying one or more warnings to a user via a user interface by the processing circuitry system.

[0153] Example A13. A method based on any combination of Examples A1 to A12, wherein importing one or more NFDs includes at least one of the following: one or more Virtualized Network Functions (VNFs); one or more Cloud-Native Network Functions (CNFs); or one or more Physical Network Functions (PNFs).

[0154] Example A14. A method according to any combination of Examples A1 to A13, further comprising: presenting a user interface by a processing circuitry system, the user interface showing representations of one or more network links, one or more network functions, one or more networks, one or more NSSTs, and NSTs; receiving, by the processing circuitry system and via the user interface, a first input from a user to configure one or more network links to interconnect one or more network functions; receiving, by the processing circuitry system and via the user interface, a second input from a user to add one or more network functions to one or more networks; wherein obtaining one or more NSSTs includes receiving, via the user interface, a third input to add one or more networks to one or more NSSTs; and wherein defining an NST includes receiving, via the user interface, a fourth input to add one or more NSSTs to an NST.

[0155] Example B1. A method comprising: receiving a first selection of one or more network functions by a processing circuit system and from a user; receiving a second selection of one or more tags specifying the location of the one or more network functions by the processing circuit system and from the user; defining a network slice subnet template by the processing circuit system based on the first and second selections; and storing the defined network slice subnet template in a service management and orchestration (SMO) catalog of network slice subnet templates hosted by a database by the processing circuit system.

[0156] Example B2. The method according to Example B1 further includes: a third selection of one or more network slice subnet templates from an SMO directory of network slice subnet templates received by the processing circuitry system and from a user; and a network slice template defined by the processing circuitry system based on the third selection; and the defined network slice template stored by the processing circuitry system in an SMO directory of network slice templates hosted by a database.

[0157] Example B3. The method according to Example B2 further includes: a fourth selection of one or more network slice templates from an SMO directory of network slice templates received by the processing circuit system from a user; and a communication service template defined by the processing circuit system based on the fourth selection; and the defined communication service template stored by the processing circuit system in an SMO directory of communication service templates hosted by a database.

[0158] Example B4. The method according to Example B3 further includes: a fifth selection of one or more communication service templates from an SMO catalog of communication service templates by a processing circuit system and from a user; and deployment of one or more communication services by the processing circuit system based on the selected one or more communication service templates.

[0159] Example B5. The method according to any of Examples B1 to B4 further includes: deploying one or more communication services according to the defined network slice subnet template.

[0160] Example B6. A system comprising a processing circuitry configured to: receive from a user a first selection of one or more network functions; receive from the user a second selection of one or more tags placed on the one or more network functions; define a network slice subnet template based on the first and second selections; and store the defined network slice subnet templates in a Service Management and Orchestration (SMO) catalog of network slice subnet templates hosted by a database.

[0161] Example B7, based on the system in B6, is configured to execute the methods of any of Examples B1 through B5.

[0162] The techniques described in this disclosure can be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the described techniques can be implemented within one or more programmable processors, including one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuit systems (ASICs), field-programmable gate arrays (FGAs), or any other equivalent integrated or discrete logic circuit systems, and any combination of these components. The terms "processor" or "processing circuit system" generally refer to any of the aforementioned logic circuit systems, alone or in combination with other logic circuit systems, or any other equivalent circuit system. Control units, including hardware, can also execute one or more of the techniques of this disclosure.

[0163] Such hardware, software, and firmware can be implemented within the same device or in separate devices to support the various operations and functions described in this disclosure. Furthermore, any described unit, module, or component can be implemented together or separately as discrete but interoperable logical devices. Describing different features as modules or units is intended to highlight different functional aspects and does not necessarily mean that such modules or units must be implemented by separate hardware or software components. Rather, the functionality associated with one or more modules or units can be performed by separate hardware or software components, or integrated within common or separate hardware or software components.

[0164] The techniques described in this disclosure can also be implemented or encoded in a computer-readable medium containing instructions, such as a computer-readable storage medium. Instructions embedded or encoded in a computer-readable medium can cause a programmable processor or other processor to perform the method, for example, when the instructions are executed. Computer-readable media can include non-transitory computer-readable storage media and transient communication media. Tangible and non-transitory computer-readable storage media can include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, hard disk, CD-ROM, floppy disk, magnetic tape cassette, magnetic media, optical media, or other computer-readable storage media. The term "computer-readable storage medium" refers to a physical storage medium, not a signal, carrier, or other transient medium.

Claims

1. A computer networking method, comprising: The processing circuitry system obtains one or more network slice subnet templates (NSSTs), wherein obtaining the one or more NSSTs includes: Obtaining the NSST for each of a plurality of domains, wherein obtaining the NSST for each of the plurality of domains includes: Obtain the 5G core data plane NSST; Obtain the 5G core management plane NSST; and Define a domain NSST based on the NSST for each of the plurality of domains, wherein defining the domain NSST includes: defining a 5G core complete NSST based on the 5G core data plane NSST and the 5G core management plane NSST; The processing circuitry system defines a network slice template (NST) based on one or more NSSTs; and The processing circuitry system deploys network slices according to the NST.

2. The method of claim 1, wherein obtaining the one or more NSSTs comprises: Obtain one or more domain-level NSSTs for a domain-specific network service; or Obtain one or more root-level NSSTs for end-to-end network services.

3. The method according to claim 1, wherein obtaining the NSST for each of the plurality of domains comprises: Obtain the NSST for each of the multiple first domains, and Obtaining the one or more NSSTs also includes: Obtaining the NSST for each of a plurality of second fields, wherein obtaining the NSST for each of the plurality of second fields includes: Obtaining open radio access network (O-RAN) cellular NSST; and Obtain O-RAN edge NSST; and A domain NSST is defined based on the NSST for each of the plurality of second domains, wherein defining the domain NSST for each of the plurality of second domains includes: defining the O-RAN full NSST based on the O-RAN cellular NSST and the O-RAN edge NSST.

4. The method according to any one of claims 1 to 3, wherein obtaining the one or more NSSTs comprises: One or more pre-configured NSSTs are presented to the user by the processing circuitry system and via a user interface; Input is received from the user by the processing circuitry system and via the user interface; as well as The processing circuitry system modifies the one or more pre-configured NSSTs using the inputs to obtain the one or more NSSTs.

5. The method of claim 4, wherein the one or more pre-configured NSSTs comprise at least one of the following: Basic Enhanced Mobile Broadband (eMBB) Core Network CN NSST; Basic Enhanced Mobile Broadband (eMBB) Radio Access Network RAN ​​NSST; or Basic 5G NST.

6. The method according to any one of claims 1 to 3, wherein defining the NST comprises: The user receives instructions from the user via a user interface to select one or more labels that specify one or more criteria, and Deploying the network slice includes selecting one or more network functions identified by the one or more NSSTs for inclusion within the deployed network slice, wherein the selected one or more network functions meet the one or more criteria specified by the one or more tags.

7. The method according to any one of claims 1 to 3, wherein obtaining the one or more NSSTs comprises: Import one or more Network Function Descriptors (NFDs), wherein the one or more NFDs include at least one of the following: One or more Virtualized Network Functions (VNFs); One or more Cloud Native Networking Functions (CNFs); or One or more Physical Network Functions (PNFs); and The one or more NSSTs are defined based on the one or more NFDs.

8. The method according to any one of claims 1 to 3, further comprising: The processing circuitry presents a user interface that shows representations of one or more network links, one or more network functions, one or more networks, the one or more NSSTs, and the NST. The processing circuitry receives, via the user interface, a first input from the user to configure the one or more network links to interconnect the one or more network functions; as well as The processing circuitry system receives, via the user interface, a second input from the user to add the one or more network functions to the one or more networks; Obtaining the one or more NSSTs includes: receiving a third input from the user via the user interface to add the one or more networks to the one or more NSSTs, and The definition of the NST includes receiving a fourth input from the user via the user interface to add one or more NSSTs to the NST.

9. A computer network system comprising a processing circuitry having access to a memory, the processing circuitry being configured to: Obtain one or more Network Slice Subnet Templates (NSSTs), wherein, in order to obtain the one or more NSSTs, the processing circuitry is configured to: Obtain the NSST for each of a plurality of domains, wherein, in order to obtain the NSST for each of the plurality of domains, the processing circuitry is configured as follows: Obtain the 5G core data plane NSST. Obtaining 5G core management plane NSST; as well as A domain NSST is defined based on the NSST for each of the plurality of domains, wherein, in order to define the domain NSST, the processing circuitry is configured to define a 5G core complete NSST based on the 5G core data plane NSST and the 5G core management plane NSST. Based on the one or more NSST definitions, a network slice template NST is defined; as well as Network slicing is deployed according to the NST.

10. The system of claim 9, wherein, in order to obtain the one or more NSSTs, the processing circuitry is configured to: Obtain one or more domain-level NSSTs for domain-specific network services; or Obtain one or more root-level NSSTs for end-to-end network services.

11. The system according to claim 9, In order to obtain the NSST for each of the plurality of domains, the processing circuitry is configured to obtain the NSST for each of the plurality of first domains, and In order to obtain the one or more NSSTs, the processing circuitry is configured as follows: The processing circuitry is configured to obtain the NSST for each of the plurality of second domains as follows: Obtain Open Radio Access Network (O-RAN) cellular NSST; Obtain the O-RAN edge NSST, and A domain NSST is defined based on the NSST for each of the plurality of second domains, wherein, in order to define the domain NSST for each of the plurality of second domains, the processing circuitry is configured to define the O-RAN full NSST based on the O-RAN cellular NSST and the O-RAN edge NSST.

12. The system according to any one of claims 9 to 11, wherein, in order to obtain the one or more NSSTs, the processing circuitry is configured to: Present one or more pre-configured NSSTs to the user via a user interface; Receive input from the user via the user interface; as well as Modify the one or more pre-configured NSSTs using the input to obtain the one or more NSSTs.

13. The system of claim 12, wherein the one or more pre-configured NSSTs comprise at least one of the following: Basic Enhanced Mobile Broadband (eMBB) Core Network CN NSST; Basic Enhanced Mobile Broadband (eMBB) Radio Access Network RAN ​​NSST; or Basic 5G NST.

14. The system according to any one of claims 9 to 11, In order to define the NST, the processing circuitry is configured to receive from a user via a user interface an instruction to select one or more tags specifying one or more criteria, and In order to deploy the network slice, the processing circuitry is configured to select one or more network functions identified by the one or more NSSTs for inclusion in the deployed network slice, wherein the selected one or more network functions meet the one or more criteria specified by the one or more tags.

15. The system according to any one of claims 9 to 11, wherein, in order to obtain the one or more NSSTs, the processing circuitry is configured to: Import one or more Network Function Descriptors (NFDs), wherein the one or more NFDs include at least one of the following: One or more Virtualized Network Functions (VNFs); One or more Cloud Native Networking Functions (CNFs); or One or more Physical Network Functions (PNFs); and The one or more NSSTs are defined based on the one or more NFDs.

16. A computer networking method, comprising: The processing circuitry system receives an indication of a first selection of one or more network functions. The processing circuitry system receives an indication of a second selection of one or more tags specifying the placement of the one or more network functions; The processing circuitry system defines a network slice subnet template (NSST) based on the first and second selections. The processing circuitry system stores the defined NSSTs in a service management and orchestration SMO catalog hosted by a database; The processing circuitry system receives an indication for a third selection of one or more NSSTs, the one or more NSSTs including the defined NSSTs; In response to the instruction for the third selection, the processing circuitry obtains the one or more NSSTs from the SMO catalog; The processing circuitry system defines a network slice template (NST) based on one or more NSSTs. as well as The processing circuitry system deploys network slices according to the NST.

Images