System and Method for Designing Network Slices

Abstract

The method includes receiving a selection of a network slice template from a list of one or more network slice templates; in response to the selection of the network slice template, receiving inputs for the network slice template, such as one or more of a network slice name, a network slice type, a network slice domain, a network slice resource sharing level, or a network slice coverage area; and creating, by the processor, a network slice based on the received inputs for the network slice template.

Description

Technical Field

[0001] This description relates to the design of network slices and systems and methods for using them.

Background Art

[0002] A cellular network is a telecommunications system for mobile devices (e.g., mobile phone devices) that communicate via radio waves through one or more local antennas at a cellular base station (e.g., a cell tower). The coverage area where services are provided is divided into small geographical areas called cells. Each cell is served by an individual low-power multi-channel transceiver and antenna at the cell tower. Mobile devices within a cell communicate on multiple frequencies assigned by the base station from a common pool of frequencies used by the cellular network and on individual frequency channels via the cell's antenna.

[0003] A radio access network (RAN) is part of a telecommunications system and implements radio access technology. The RAN exists between devices such as mobile phones, computers, or remote control machines and provides a connection to a core network (CN). Depending on the standard, mobile phones and other wireless-connected devices are variously known as user equipment (UE), terminal equipment (TE), mobile station (MS), etc.

Summary of the Invention

[0004] In some embodiments, the method includes receiving a selection of a network slice template from a list of one or more network slice templates; receiving, in response to the selection of a network slice template, one or more inputs to the network slice template, including a network slice name, network slice type, network slice domain, network slice resource sharing level, or network slice coverage area; and having a processor create a network slice based on the inputs received to the network slice template.

[0005] In some embodiments, the device includes a processor and memory which, when executed by the processor, stores instructions causing the processor to receive a selection of a network slice template from a list of one or more network slice templates, to receive one or more inputs to the network slice template in response to the selection of the network slice template, a network slice name, a network slice type, a network slice domain, a network slice resource sharing level, or a network slice coverage area, and to create a network slice based on the inputs received to the network slice template.

[0006] In some embodiments, a non-temporary computer-readable medium stores instructions that, when executed by a processor, cause the processor to receive a selection of a network slice template from a list of one or more network slice templates, receive one or more inputs to the network slice template in response to the selection of the network slice template, such as a network slice name, network slice type, network slice domain, network slice resource sharing level, or network slice coverage area, and create a network slice based on the inputs received to the network slice template. [Brief explanation of the drawing]

[0007] The aspects of this disclosure will be understood by reading the following detailed description in conjunction with the accompanying figures. In accordance with industry standard practice, various features are not depicted to scale. In some embodiments, the dimensions of various features have been arbitrarily increased or decreased for clarity of consideration.

[0008] [Figure 1] This is a diagrammatic representation of a system for Network Slice Design (NSD) in several embodiments. [Figure 2] This is a flowchart of a method for designing network slices, according to several embodiments. [Figure 3] This is a graphical user interface (GUI) for designing network slices, in several embodiments. [Figure 4] This is a GUI for designing network slices, with several embodiments. [Figure 5] This is a GUI for designing network slices, with several embodiments. [Figure 6] This is a GUI for designing network slices, with several embodiments. [Figure 7] This is a GUI for designing network slices, with several embodiments. [Figure 8] This is a GUI for designing network slices, with several embodiments. [Figure 9] This is a GUI for designing network slices, with several embodiments. [Figure 10] This is a GUI for designing network slices, with several embodiments. [Figure 11] This is a GUI for designing network slices, with several embodiments. [Figure 12] This is a GUI for designing network slices, with several embodiments. [Figure 13] This is a GUI for designing network slices, with several embodiments. [Figure 14] This is a GUI for designing network slices, with several embodiments. [Figure 15] This is a GUI for designing network slices, with several embodiments. [Figure 16] This is a high-function block diagram of a processor-based system according to some embodiments. [Modes for carrying out the invention]

[0009] The following disclosure provides many different embodiments or examples for implementing different features of the subject matter under consideration. For the sake of simplicity, examples of components, values, behaviors, materials, arrangements, etc., are described below. Naturally, these are examples and are not intended to be limiting. Other components, values, behaviors, materials, arrangements, etc., are contemplated. For example, forming a first feature on or above a second feature in the following description includes embodiments in which the first and second features are formed in direct contact, and further includes embodiments in which an additional feature is formed between the first and second features so that the first and second features are not in direct contact. In addition, the disclosure repeats reference numerals and / or letters in many examples. This repetition is for the sake of brevity and clarity and is not intended to define relationships between the various embodiments and / or configurations under consideration.

[0010] Furthermore, spatially relative terms such as directly below, downward, lower, upward, and above are used herein for explanatory purposes to describe the relationship between one element or feature and another element(s) or feature(s)(s) as shown in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation, in addition to the orientation shown in the figures. If the device is oriented in a different direction (e.g., rotated 90 degrees or in another direction), the spatially relative descriptors also used herein are interpreted accordingly.

[0011] In some embodiments, network slice designs are created via a graphical user interface (GUI) on a user interface (UI) as illustrated in the present disclosure.

[0012] Network slicing (or 5G network slicing) is a network architecture that enables the multiplexing of virtualized, independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end (E2E) network tailored to meet the diverse requirements demanded by a particular application. Therefore, this technology plays a leading role in supporting 5G mobile networks designed to efficiently encompass a large number of services with significantly different Service Level Requirements (SLRs). Realizing this service-oriented perspective of the network leverages the concepts of Software-Defined Networking (SDN) and Network Function Virtualization (NFV), enabling the implementation of flexible and scalable network slices on a common network infrastructure. Each network slice is managed by a Mobile Virtual Network Operator (MVNO). The infrastructure provider (owner of the telecommunications infrastructure) leases physical resources to MVNOs that share the underlying physical network. Due to the availability of allocated resources, the MVNO autonomously deploys multiple network slices customized for the various applications it provides to its users. In some embodiments, the MVNO and the infrastructure provider are the same entity, i.e., the service provider. In some embodiments, the service provider is the MVNO.

[0013] A UI is the space in which interaction between a human and a machine occurs. The purpose of this interaction is for the machine to simultaneously provide feedback of information that supports the operator's decision-making process, while also enabling effective operation and control of the machine from the human side. Examples include computer operating systems, hand tools, heavy equipment operator control, and modes of process control interaction. A UI includes one or more layers, including a Human-Machine Interface (HMI) that connects the machine to physical input hardware such as a keyboard, mouse, or gamepad, and output hardware such as a computer monitor, speaker, and printer. A device that implements an HMI is called a Human Interface Device (HID). Other terms for human-machine interface are Man-Machine Interface (MMI) and, when the machine in question is a computer, a human-computer interface. Additional UI layers may interact with one or more human senses, including haptic UI (touch), visual UI (sight), auditory UI (sound), olfactory UI (smell), equilibrium UI (balance), and gustatory UI (taste).

[0014] A GUI is a form of user interface that allows users to interact with electronic devices through graphical icons and audio indicators, such as primary notation, instead of text-based UIs, typed command labels, or text navigation. Actions in a GUI are typically performed by directly manipulating graphic elements. GUIs are used in many handheld mobile devices, such as MP3 players, portable media players, gaming devices, smartphones, and smaller home, office, and industrial control devices.

[0015] In other approaches, E2E network slice design involves several steps and is labor-intensive with manual design. In some embodiments, E2E network slice design becomes more efficient with a GUI that is operated by a user on the UI. In some embodiments, the UI provides the user with the ability to select various relevant aspects of network slice design. In some embodiments, the GUI is configured to design an E2E slice through the UI, the ability to select slice design parameters from the UI, and the ability to monitor the status of the network slice from the GUI.

[0016] The E2E principle is a design framework in computer networking. In a network designed according to this principle, ensuring specific application-specific functions such as reliability and security is to implement these functions at the communication end nodes of the network. Intermediate nodes such as gateways and routers that exist to establish the network can implement these to improve efficiency, but cannot guarantee end-to-end accuracy.

[0017] Network slice design remains a relatively new concept. In some embodiments, we consider GUI-based network slice design operations. These operations involve the user entering information such as the network slice name, slice type (enhanced Mobile Broadband (eMBB) or massive Internet of Things (mIoT) slice providing faster connectivity, higher throughput, and greater capacity for high-traffic areas such as stadiums, cities, and concert venues), domain (RAN, core, transport, etc.), selection of shared or non-shared slices, the slice's Public Land Mobile Network (PLMN) ID, and the slice's coverage area. Other operations include defining service profile parameters (such as latency, data rate, and mobility level) requested by the slice's northbound interface (e.g., internally within the system or manually by the user), and translating these service profile parameters into slice profile parameters that hold slice subnet parameter information for different network domain slice subnet instances (NSSIs) such as RANs, Transport Networks (TNs), and CN NSSIs. Other examples of service profile parameters include acceptable latency, the number of connected UEs, and the expected download and upload throughput from the slice. In some embodiments, in response to the input of service profile parameters, the user clicks a user input field configured to break down the service profile requirements into slice profile parameters. In some embodiments, the slice profile parameters are those expected from each domain (e.g., expected latency from the RAN domain).

[0018] The northbound interface of a component is an interface that enables the component to communicate with a higher-level component by using the southbound interface of the higher-level component. The northbound interface conceptualizes the lower-level details (e.g., data or functions) used by or within the component and enables the component to interface with the higher-level layer. The northbound interface is typically depicted above the component for which it is defined. The southbound interface decomposes concepts in the technical details specific to a single component of the architecture. The southbound interface is depicted at the bottom of the architecture overview.

[0019] In some embodiments, the user inputs a slice subnet profile via a GUI. The slice subnet profile includes subnets specific to a domain (such as RAN, CN, TN, etc.) (a segmented part of a larger network). A slice manager (a centralized software component that provides an interface for creating, modifying, monitoring, and deleting slices) makes an application programming interface (API, a type of software interface that provides services to other software) call to an orchestrator (an SDN controller that enables provisioning, updating, and managing the computing resources required for an application or service to be delivered via an API) to fetch information on the available subnets for each domain based on whether the subnet is shared or dedicated. A shared subnet is an already deployed subnet that is shared with other network slices. A dedicated subnet is a new subnet deployed for a dedicated slice.

[0020] In some embodiments, the user determines the feasibility of a network slice, such as whether a selected subnet is feasible to deploy, via a GUI. In a non-limiting example, for a shared subnet, there is a maximum number of slices that can be supported. Therefore, part of the feasibility check is determining whether the shared subnet exceeds the number of slices that can be supported.

[0021] In some embodiments, once a slice is deployed, the user determines compliance with a Service Level Agreement (SLA). For example, the user establishes parameters or key performance indicators (KPIs) for the slice to be monitored via a GUI, and the user selects a policy for an automated slice healing use case (e.g., when one or more network failures are detected, the system diagnostics automatically reconfigure the communication path to maintain system communication).

[0022] In some embodiments, the user previews and submits a designed network slice via a GUI. Furthermore, the user selects a network slice to preview and submit from a list of designed slices. In some embodiments, the user expands a slice via point-and-click (moving the pointer to a specific location on the screen (pointing), and then pressing a mouse button, usually the left button) to expand a completed slice. In a non-limiting example, the slice manager makes an API call to an orchestrator to expand the slice.

[0023] In some embodiments, the user opens the slice design UI and opens a list of available slice templates. The user selects a slice template and clicks the user selection field for "Create a new slice based on the slice template" (Create New Slice). Slice design begins, and the user enters information such as the type of slice. For example, whether the slice is of type eMBB, Ultra-Reliable Low-Latency Communication (URLLC (Ultra-Reliable Low-Latency Communication) for short packet data transmission used to meet both reliability and latency requirements), or Massive Machine Type Communication (mMTC used to connect a large number of devices such as Internet of Things (IoT) devices). The user further selects shared or dedicated slice subnets for each domain (RAN, CN, or TN) and coverage area of ​​the network slice.

[0024] In some embodiments, the user navigates from the slice template to a slice definition page where service profile SLA parameters are displayed. In some embodiments, the user modifies parameters such as latency from the UI. Once the user has reviewed the service profile parameters for the complete E2E network slice, the user points and clicks a user-selected button for Calculate, and the slice manager calculates the slice profile parameters for each domain (RAN, CN, and TN) to satisfy the service profile SLA. In a non-limiting example, in response to an SLA service profile latency of 10ms (for example, the SLA declares that the latency is 10ms or less), the service profile might be mapped to 3ms from the RAN, 3ms from the CN, and 4ms from the TN domain for a total of 10ms.

[0025] In some embodiments, the user navigates to a slice subnet profile UI page and selects either a domain-specific network service that has already been deployed (in response to the domain being shared) or a network service template (in response to the domain being dedicated and a new network service being deployed for this subnet). In response to the selection, the user points and clicks a user-selected button for feasibility to determine whether the selected network service is ready to serve the new network slice.

[0026] In some embodiments, the user navigates to the SLA GUI and selects which SLA parameters should be monitored for a given slice. The user then previews the SLA parameters for the given slice and submits the network slice for design. In response to the submission, the network slice is designed and displayed in the Network Slice Lifecycle Management (LCM) GUI. In some embodiments, the user navigates to the LCM slice GUI and selects the slice designed to deploy the designed slice.

[0027] In some embodiments, the slice manager initiates the deployment of each domain in the designed slice, and the deployment status is displayed on the GUI. Furthermore, once the slice is deployed, the status is updated on the GUI (for example, from inactive to active).

[0028] Figure 1 is a diagrammatic representation of a system for network slice design (NSD) 100 according to several embodiments.

[0029] The NSD system 100 includes a CN 102 that is communicatively connected to the RAN 104 via a TN 106 that is communicatively connected to base stations 108A and 108B (hereinafter referred to as base stations 108), which have antennas 110 that are radio-connected to UEs 112 located within geographic coverage cells 114A and 114B (hereinafter referred to as geographic coverage cells 114). The CN 102 includes one or more service providers 116, a KPI server 118, and an NSD module 120.

[0030] CN102 (also known as the backbone) is part of a computer network that interconnects networks and provides pathways for exchanging information between different local area networks (LANs) or subnetworks. In some embodiments, CN102 connects diverse networks within the same building, within different buildings in a campus environment, or across a wide geographical area.

[0031] In some embodiments, RAN104 is a Global System for Mobile Communication (GSM) RAN, GSM / EDGE RAN, Universal Mobile Telecommunications System (UMTS) RAN (UTRAN), Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Open RAN (O-RAN), or Cloud RAN (C-RAN). RAN104 resides between UE112 (e.g., a mobile phone, computer, or any remote control machine) and CN102. In some embodiments, for the purpose of simplified representation and consideration, RAN104 is C-RAN. In some embodiments, a Base Band Unit (BBU) replaces the C-RAN.

[0032] In traditional distributed cellular networks, the equipment at the bottom and top of base stations in cell sites is the BBU. The BBU is the radio equipment that links the UE to the CN and processes billions of bits of information per hour. Traditionally, BBUs were located in enclosures or shelters at the bottom of base stations. In contrast, C-RAN uses the large signal carrying capacity of optical fiber to concentrate a large number of BBUs in dedicated pool locations or at base stations. This reduces the number of devices at base stations and provides many other advantages, including lower latency.

[0033] In a hierarchical telecommunications network, TN106 of the NSD system 100 provides one or more intermediate links between CN102 and RAN104. The two main methods of mobile backhaul implementation are fiber-based backhaul and wireless point-to-point backhaul. Other methods, such as copper-based wireline, satellite communications, and point-to-multipoint wireless technologies, are being phased out as capacity and latency requirements become more stringent in 4G and 5G networks. Backhaul refers to the side of the network that communicates with the internet. The connection between base station 108 and UE112 begins with TN106 connected to CN102. In some embodiments, TN106 includes wired, optical fiber, and wireless components. The wireless section includes using microwave band, mesh, and edge network topologies that use high-capacity wireless channels to send packets to microwave or fiber links.

[0034] In some embodiments, base station 108 is a grid tower or freestanding tower, guyed tower, monopole tower, and concealed tower (e.g., a tower designed to resemble a tree, cactus, water tower, sign, lighting pole, and other types of structure). In some embodiments, base station 108 is a cellular-enabled mobile device site where antennas and electronic communication equipment are typically located on a radio mast, tower, or other raised structure to create a cell (or adjacent cell) in the network. The raised structure typically supports one or more antennas 110, as well as one or more sets of transmitters / receivers (transceivers), digital signal processors, control electronics, remote radio heads (RRHs), primary and backup power supplies, and shelters. Base stations are also known by other names such as base transceiver stations, mobile phone masts, or cell towers. In some embodiments, base stations are replaced by other edge devices configured to communicate wirelessly with the UE. The edge devices provide an entry point to a service provider CN, such as CN 102. Examples include routers, routing switches, Integrated Access Devices (IADs), multiplexers, and various Metropolitan Area Network (MAN) and Wide Area Network (WAN) access devices.

[0035] In at least one embodiment, the antenna(s) 110 is a sector antenna. In some embodiments, the antenna(s) 110 is a type of directional microwave antenna having a fan-shaped radiation pattern. In some embodiments, the radii of the fan are designed to be 60°, 90°, or 120°, with a few extra degrees to ensure superposition. Furthermore, sector antennas are mounted in multiples when wider coverage or omnidirectional coverage is required. In some embodiments, the antenna(s) 110 is a rectangular antenna, sometimes called a panel antenna or radio antenna, used to transmit and receive radio waves or data between a mobile device or other device and a base station. In some embodiments, the antenna(s) 110 is a circular antenna. In some embodiments, the antenna(s) 110 operates at microwave or ultra-high frequency (UHF) frequencies (300 MHz to 3 GHz). In other examples, the antenna(s) 110 are selected based on their size and directional characteristics. In some embodiments, the antenna(s) 110 (one or more) is a MIMO (Multiple Input, Multiple Output) antenna that transmits and receives two or more data signals simultaneously over the same radio channel by utilizing multipath propagation.

[0036] In some embodiments, UE112 is a computer or computing system. In addition, or instead, UE112 has a liquid crystal display (LCD) such as a user interface (UI) 1622 (Figure 16) that provides a touchscreen interface with digital buttons and a keyboard, or with physical buttons along with a physical keyboard, or a light-emitting diode (LED) or organic light-emitting diode (OLED) screen interface. In some embodiments, UE112 connects to the internet and interconnects with other devices. In addition, or instead, UE112 incorporates a built-in camera, voice and video phone call capabilities, video games, and Global Positioning System (GPS) functionality. In addition, or instead, UE runs an operating system (OS) that allows the installation and execution of third-party applications specialized for specific functions.In some embodiments, UE112 is a computer (such as a tablet computer, netbook, digital media player, digital assistant, graphing calculator, handheld game console, handheld personal computer (PC)), laptop, mobile internet device (MID) , personal digital assistant (PDA) , pocket calculator , portable media player , or ultra-mobile PC), mobile phone (such as a camera phone , feature phone , smartphone , phablet , etc.), digital camera (such as a digital camcorder or digital still camera (DSC) , digital video camera (DVC) , or front camera , etc.), pager , personal navigation device (PND) , wearable computer (such as a calculator watch , smartwatch , head-mounted display , earphone , or biometric device , etc.), or smart card.

[0037] In some embodiments, the geographic coverage cell 114 includes shape and size. In some embodiments, the geographic coverage cell 114 is a macrocell (covering 1 km to 30 km), a microcell (covering 200 m to 2 km), or a picocell (covering 4 m to 200 m). In some embodiments, the geographic coverage cell is circular, elliptical (Figure 1), fan-shaped, or lobular, but the geographic coverage cell 114 can be almost any shape or size. The geographic coverage cell 114 represents the geographic area to which the antenna 110 and UE 112 are configured to communicate. Coverage depends on several factors, including terrain (i.e., mountains) and buildings, technology, radio frequency, and, most importantly for two-way telecommunications, the sensitivity and transmission efficiency of the UE 112. Some frequencies provide better area coverage, while others penetrate obstacles such as urban buildings better. The ability of the UE to connect to the base station depends on the signal strength.

[0038] A service provider (single or plural) 116 is an entity, vendor, customer, or organization that sells bandwidth or network access to subscribers (users) by providing direct internet backbone access to an Internet service provider, typically to its network access point (NAP). Service providers are sometimes called backbone providers, internet providers, or vendors. Service providers include telecommunications companies, data carriers, wireless communication providers, internet service providers, and cable television operators that provide high-speed internet access.

[0039] The KPI server 118 generates both forecast and live network data. Live network data (KPIs, UE / cell / drive test minimization (MDT) traces, and crowdsourced data) enables modeling of network traffic, hotspot identification, and radio signal propagation. RF drive testing is a method for measuring and evaluating the coverage, capacity, and quality of service (QoS) of mobile radio networks such as RAN104. This technique consists of using a vehicle equipped with mobile radio network air interface measurement equipment that detects and records a wide variety of physical and virtual parameters of mobile cellular services in each geographic area. By measuring how radio network subscribers are experiencing things in an area, radio carriers can make network-oriented changes to provide better coverage and service to customers. Drive testing generally consists of a mobile vehicle equipped with drive test measurement equipment. This equipment is a highly specialized electronic device that is typically coupled to a mobile handset (UE) from an Original Equipment Manufacturer (OEM). This ensures that the measurements are realistic and correspond to the actual user experience. In the case of mobile networks, the crowdsourcing methodology leverages the participants' cloud (e.g., mobile subscribers) to collect network measurements manually or automatically via mobile apps, or directly from the network using call tracing.

[0040] UE / cell / MDT traces collected in the Operations Support System (OSS) or via dedicated tools provide user-level information to the service provider(s) 116. Once geographically located, the UE / cell / MDT traces are used to enhance path loss calculations and prediction plots, and to identify and locate problem areas and traffic hotspots. The KPI server 118 enables the service provider(s) 116 to use the UE / cell / MDT traces in conjunction with the NSD module 120 for network optimization.

[0041] In some embodiments, the NSD module 120 is configured to allow a user to design one or more network slices. In some embodiments, network slice design is GUI-based. In some embodiments, these operations include the user entering information such as the network slice name, slice type (eMBB (Enhanced Mobile Broadband) or mIoT (Massive Internet of Things) slice that provides faster connectivity, higher throughput, and more capacity to high-traffic areas such as stadiums, cities, and concert venues), domain (RAN, core, transport, etc.), selection of shared or non-shared slice, the slice's Public Land Mobile Network (PLMN) ID, and the slice's coverage area. Other operations include defining service profile parameters (holding the inherent requirements of the communication service instance, such as latency, data rate, and mobility level) as required by the slice's northbound interface (e.g., internally within the system or manually from the user), and translating the service profile parameters into slice profile parameters (holding slice subnet parameter information for different network domain slice subnet instances (NSSIs), such as RAN, transport network (TN), and CN NSSI).

[0042] Figure 2 is a flowchart of Method 200 for designing network slices, according to several embodiments.

[0043] Figures 3 to 15 show graphical user interfaces (GUIs) 300 to 1500 for designing network slices, according to several embodiments.

[0044] In some embodiments, the NSD method 200 describes process tasks for network slice design. While the operations of the NSD method 200 are considered and illustrated as having a specific sequence, each operation of the NSD method 200 is configured to be performed in any order unless otherwise specified. The NSD method 200 is implemented as a set of operations, such as operations 202 through 220. Furthermore, to facilitate understanding of the NSD method 200, it is discussed with reference to Figures 3 through 15.

[0045] In operation 202 of the NSD method 200, the NSD module 120 receives input from the user to initiate network slice design. In some embodiments, the user is presented with a GUI 300 indicating that the network slice design application is starting. The process proceeds from operation 202 to operation 204.

[0046] In operation 204 of NSD method 200, the NSD module 120 presents a list of slice templates. In Figure 4, the GUI 400 displays the slice template list 402. In some embodiments, each network slice in the slice template list 402 includes status (e.g., active or inactive), name, slice service type (e.g., eMBB, uRLLC, mIoT, or custom), service category (e.g., home automation, high-speed train, etc.), domain (RAN, TN, CN, or E2E), vendor, version, shared (or unshared), creation date, and last modified date. The term template refers to a common feature of software applications that defines a unique, non-executable file format specifically intended to allow its application process to proceed from operation 204 to operation 206.

[0047] In operation 206 of the NSD method 200, the NSD module 120 receives user input indicating the selection of a slice template. In Figure 4, the user points to a slice template, for example, slice template 404, and then clicks the slice template. A user selection button 406 labeled "Create a new slice" pops up, and the user clicks the user selection button 406 to begin the process of creating a new slice using the selected slice template. The process proceeds from operation 206 to operation 208.

[0048] In operation 208 of NSD method 200, the GUI 500 is presented, and the user enters slice information. In Figure 5, the user enters the slice name in user input field 502, selects the slice type (e.g., eMBB or URLLC type of the slice) from user selection field 504, selects the domain from user selection field 506, and selects whether the slice is shared or dedicated from user selection field 508. For example, the user selects a shared or dedicated slice subnet for each domain (RAN in user selection field 508A, core in user selection field 508B, or transport in user selection field 508C), and selects the coverage area of ​​the network slice in user selection field 510. The process proceeds from operation 208 to operation 210.

[0049] In operation 210 of the NSD method 200, the GUI 600 is presented, and the user configures network slice information. In Figure 6, the slice parameter GUI 600 presents the service profile SLA parameter 602, which is configured for the user to modify as needed. In a non-limiting example, the user modifies the expected latency in the user selection field 604 to conform to the network slice specifications (e.g., set to 300ms). Once the user has determined all the service profile parameters in the parameter field 602 for the complete end-to-end network slice, the user points and clicks the user selection button 606 for calculation. The slice manager calculates the slice profile parameters (shown in the slice profile box 608) for each domain (RAN, CORE, and transport) to satisfy the service profile SLA. The process proceeds from operation 210 to operation 212.

[0050] In operation 212 of NSD method 200, the GUI 700 is presented, and the user selects a subnet profile, such as an already deployed domain-specific network service (shared network service or dedicated network service). In Figure 7, the user navigates to the slice subnet profile GUI 700 and selects either an already deployed domain-specific network service (e.g., network services 702 and 704 where the domain is shared) or a network service template (where the domain is dedicated) by pointing and clicking the user selection field 706. In a non-limiting example, in response to the network slice subnet of RAN domain 708 being shared, an already deployed network slice subnet can be retrieved and selected for use. In some embodiments, a network service is selected for the network slice subnet. Continuing the non-limiting example, the network service for the RAN domain, such as ABC, is an identifier for the network service from the deployed RAN domain. Continuing the non-limiting example, in core domain 710, the user can select a template name as a new network service deployed for core domain 710 by clicking the user selection field 706.

[0051] In Figure 8, after the user clicks the user selection field 706 labeled "Select," the GUI 800 is presented, and the user is presented with a network service selection popup box 802. As shown in box 804, each of the network services is selected, such as the User Plane Function (UPF), which is responsible for packet routing and forwarding, packet inspection, quality of service (QoS) processing, and external protocol data unit (PDU) sessions for interconnecting data networks (DNs) in the 5G architecture; the Network Repository Function (NRF), which acts as a central service discovery broker for all network functions (Network Functions (NFs)) within the 5G core; or the Session Management Function (SMF), which is responsible for interacting with isolated data planes, creating, updating, and deleting PDU sessions, and managing the session context with the UPF. In a non-limiting example, the user selects the UPF (highlighted) and, within the user input field 806 labeled "Shared," is presented to the user with an indication (e.g., True) that the UPF network service is shared.

[0052] Instead, in Figure 9, GUI 900 highlights NRF and displays false, indicating that the NRF network service is not shared, but is presented in the user input field 806 as shared. Thus, the user fills in the dedicated network service template 902. The user selects a network service template in the user selection field 904 of the NS template. In response to the selection of a network service template (e.g., UPF NST Sample 2), the user is presented with network functions to select.

[0053] Figure 10 presents a GUI 1000 with network services included in each domain (RAN, core, and transport). Once each domain includes network services, the user points and clicks the Feasibility user selection field 1002, and the NSD module 120 determines whether the selected network services are ready to serve a new network slice. In some embodiments, in response to the user clicking the Feasibility user selection field 1002, the NSD module 120 determines whether it is feasible to deploy the selected subnet as part of a new network slice (for example, in the case of a shared subnet, whether there is a maximum number of slices that one subnet can support, or whether the new core network services are deployable).

[0054] In Figure 11, GUI 1100 is presented when the feasibility test fails for one or more domains (e.g., RAN domains). The user selects a different slice subnet by clicking the user selection field 1102 for Network Slice Subnet Name, and then re-checks the feasibility by clicking the user selection field 1002 for Feasibility. In a non-limiting example, in Figure 11, the feasibility of RAN domain 708 fails, meaning that the selected network service is not supported in the new network slice. As a result, the user can click the user selection field 1102 to select a different RAN subnet from list 1104, and then rerun the feasibility test.

[0055] Figure 12 shows the GUI 1200 when the feasibility test is successful for each domain. The user clicks the user selection button 1202 for Next to expand the network slice. The process proceeds from operation 212 to operation 214. In a non-restrictive example, in response to the successful feasibility check, a network slice can be created using each selected domain subnet 1204.

[0056] In operation 214 of method 200, the GUI 1300 is presented (Figure 13), and the user selects SLA parameters, such as the parameters shown in parameter box 1302, that should be monitored for the slice. The user searches for the selected domain from the parameters in the user input field 1306 for search. In some embodiments, the user drags and drops the parameter / KPI 1308 into parameter box 1302. Furthermore, in response to the slice being expanded and the selection of the parameters or KPIs to be monitored (box 1302), the user selects a policy from the user selection field 1304 for policy name, for the slice auto-healing use case. Auto-healing is the ability to automatically detect disabled access points and restore the wireless network (e.g., by increasing the coverage area formed by nearby access points, restarting network functions, etc.). The process proceeds from operation 214 to operation 216.

[0057] In operation 216 of method 200, the designed network slice 1402 is displayed in GUI 1400 (Figure 14) for user review. After previewing network slice 1402, including service information 1404 and automation policy 1406, the user clicks the user-selected field 1408, "Submit," after determining that the information is correct. In response to the click of the user-selected field 1408, GUI 1500 (Figure 15) is displayed along with a list of network slices 1502. In some embodiments, in response to the user clicking the user-selected field 1408, network slice 1402 from GUI 1400 is listed on GUI 1500 (Figure 15) along with a list of network slices 1502. The process proceeds from operation 216 to operation 218.

[0058] In operation 218 of method 200, the user expands a designed network slice by clicking the desired network slice in the list of network slices 1502, which displays a popup box 1504 of GUI 1500. The user expands a designed slice by clicking the user select button 1506 to expand. In some embodiments, a slice manager (not shown) makes an API call to an orchestrator (not shown) and the designed slice is expanded. The process proceeds from operation 218 to operation 220.

[0059] In operation 220 of method 200, the status of the designed slice is updated. As seen in status column 1508, the status of the network slice is updated from designed to deployed. Other statuses include running, activation failed, and deployment failed. In some embodiments, the slice is labeled "designed" in response to the slice being successfully submitted and listed. GUI 1500 captures the status of the slice in status column 1508, slice name column 1510, generated slice ID column 1512, slice service type column 1514, slice creation date column 1516, and other appropriate slice details within the scope of the embodiment.

[0060] In some embodiments, the user can click the caret in the user selection field 1518 to rotate and expose a table containing the subnet details of the slice (such as NSSI status, NSSI, and domain). In some embodiments, in response to the user expanding the slice, the slice manager (not shown) performs a feasibility check again to determine if there is available space in the network slice subnet.

[0061] Figure 16 is a block diagram of a network slice design (NSD) processing circuit 1600 according to some embodiments. In some embodiments, the NSD processing circuit 1600 is a general-purpose computing device including a hardware processor 1602 and a non-temporary computer-readable storage medium 1604. In particular, the storage medium 1604 is encoded, i.e., stored, in computer program code 1606, i.e., a set of executable instructions such as algorithms or methods 200. The execution of instructions 1606 by the hardware processor 1602 represents (at least in part) a network slice design application that implements part or all of the methods described herein (hereinafter, the described processes and / or methods).

[0062] The processor 1602 is electrically coupled to the computer-readable storage medium 1604 via the bus 1608. The processor 1602 is also electrically coupled to the I / O interface 1610 via the bus 1608. The network interface 1612 is also electrically connected to the processor 1602 via the bus 1608. The network interface 1612 is connected to the network 1614 so that the processor 1602 and the computer-readable storage medium 1604 connect to external elements via the network 1614. The processor 1602 is configured to execute computer program code 1606 encoded in the computer-readable storage medium 1604 so that the NSD processing circuit 1600 can be used to execute part or all of the described process and / or method. In one or more embodiments, the processor 1602 is a Central Processing Unit (CPU), a multiprocessor, a distributed processing system, an Application Specific Integrated Circuit (ASIC), and / or a suitable processing unit.

[0063] In one or more embodiments, the computer-readable storage medium 1604 is an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, the computer-readable storage medium 1604 includes semiconductor or solid-state memory, magnetic tape, removable computer diskette, random-access memory (RAM), read-only memory (ROM), rigid magnetic disk, and / or optical disk. In one or more embodiments using an optical disk, the computer-readable storage medium 1604 includes compact disk-read-only memory (CD-ROM), compact disk-read / write (CD-R / W), and / or digital video disc (DVD).

[0064] In one or more embodiments, the storage medium 1604 stores computer program code 1606 configured to enable the NSD processing circuit 1600 to perform part or all of the described process and / or method. In one or more embodiments, the storage medium 1604 also stores information such as relaxation algorithms that facilitate the performance of part or all of the described process and / or method.

[0065] The NSD processing circuit 1600 includes an I / O interface 1610. The I / O interface 1610 is coupled to an external circuit. In one or more embodiments, the I / O interface 1610 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor directional keys for transmitting information and commands to the processor 1602.

[0066] The NSD processing circuit 1600 also includes a network interface 1612 coupled to the processor 1602. The network interface 1612 enables the NSD processing circuit 1600 to communicate with a network 1614 to which one or more other computer systems are connected. The network interface 1612 includes wireless network interfaces such as BLUETOOTH®, WIFI, WiMAX, GPRS, or WCDMA®, or wired network interfaces such as ETHERNET, USB, or IEEE-864. In one or more embodiments, part or all of the described process and / or method is performed within two or more NSD processing circuits 1600.

[0067] The NSD processing circuit 1600 is configured to receive information via the I / O interface 1610. The information received via the I / O interface 1610 includes one or more instructions, data, design rules, and / or other parameters for processing by the processor 1602. The information is transferred to the processor 1602 via the bus 1608. The NSD processing circuit 1600 is configured to receive information related to the UI 1622 via the I / O interface 1610. The information is stored in the computer-readable medium 1604 as the user interface (UI) 1622.

[0068] In some embodiments, part or all of the described process and / or method is executed as a standalone software application for execution by a processor. In some embodiments, part or all of the described process and / or method is executed as a software application that is part of an additional software application. In some embodiments, part or all of the described process and / or method is executed as a plug-in to a software application.

[0069] In some embodiments, the process is implemented as a function of a program stored on a non-temporary computer-readable recording medium. Examples of non-temporary computer-readable recording media include, but are not limited to, one or more external / removable and / or internal / built-in storage or memory units such as optical discs such as DVDs, magnetic disks such as hard disks, and semiconductor memory such as ROMs, RAMs, and memory cards.

[0070] In some embodiments, the method includes receiving a selection of a network slice template from a list of one or more network slice templates; receiving, in response to the selection of a network slice template, one or more inputs to the network slice template, including a network slice name, network slice type, network slice domain, network slice resource sharing level, or network slice coverage area; and having a processor create a network slice based on the inputs received to the network slice template.

[0071] In some embodiments, the method further includes causing a processor to output a graphical user interface (GUI) via a user interface (UI) that includes a list of one or more network slice templates configured to design a network slice; updating the GUI which includes user input fields for creating a new slice; and updating the GUI which is configured to receive input to a network slice template in response to a selection of a network slice template from the list of one or more network slice templates, including a first user input field configured to receive a network slice name, a second user input field configured to receive a network slice type, a third user input field configured to receive a network slice domain, a fourth user input field configured to receive a network slice resource sharing level, or a fifth user input field configured to receive a network slice coverage area.

[0072] In some embodiments, the method further includes updating a GUI that includes one or more user selection fields configured to be modified to design a network slice service profile, each user selection field representing a modifiable domain parameter, in response to receiving user input for one or more of the first to fifth user input fields.

[0073] In some embodiments, the method further includes converting each modifiable domain parameter for each network slice domain identified in a third user input field into slice profile parameters.

[0074] In some embodiments, the method further includes updating a GUI that includes one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet, in response to the conversion of each modifiable domain parameter for each network slice domain identified in a third user input field to a slice profile parameter.

[0075] In some embodiments, each network slice subnet user selection field includes subnets that have been determined to be available for each domain.

[0076] In some embodiments, the method further includes determining whether one or more user-selected domain-specific subnets are deployable in response to the selection of domain-specific subnets for each domain.

[0077] In some embodiments, the method further includes updating a GUI containing a list of parameters for user-selected KPIs, which are monitored as network slices are deployed, in response to the selection of a domain-specific subnet, for each parameter or key performance indicator (KPI).

[0078] In some embodiments, the GUI further includes a sixth user selection field configured to allow the user to select an automated healing policy for the detected fault.

[0079] In some embodiments, the method further includes unpacking network slices.

[0080] In some embodiments, the device includes a processor and memory which, when executed by the processor, stores instructions causing the processor to receive a selection of a network slice template from a list of one or more network slice templates, to receive one or more inputs to the network slice template in response to the selection of the network slice template, a network slice name, a network slice type, a network slice domain, a network slice resource sharing level, or a network slice coverage area, and to create a network slice based on the inputs received to the network slice template.

[0081] In some embodiments, the instruction further causes the processor to output a graphical user interface (GUI) via a user interface (UI) containing a list of one or more network slice templates configured to design a network slice, to create a new slice, and to update the GUI which includes a user input field for "Create a new slice", in response to the user input field for "Create a new slice" being selected by the user, the GUI which includes a first user input field configured to receive a network slice name, a second user input field configured to receive a network slice type, a third user input field configured to receive a network slice domain, a fourth user input field configured to receive a network slice resource sharing level, and a fifth user input field configured to receive a network slice coverage area.

[0082] In some embodiments, the instruction further causes the processor to update a GUI containing one or more user selection fields configured to be modified to design a network slice service profile, each user selection field representing a modifiable domain parameter, in response to receiving user input for one or more of the first to fifth user input fields.

[0083] In some embodiments, the instruction further causes the processor to convert each modifiable domain parameter for each network slice domain identified in the third user input field into slice profile parameters.

[0084] In some embodiments, the instruction further causes the processor to update a GUI that includes one or more network slice subnet user selection fields configured to allow the user to select domain-specific subnets in response to the conversion of each modifiable domain parameter for each network slice domain identified in a third user input field to slice profile parameters.

[0085] In some embodiments, a non-temporary computer-readable medium stores instructions that, when executed by a processor, cause the processor to receive a selection of a network slice template from a list of one or more network slice templates, receive one or more inputs to the network slice template in response to the selection of the network slice template, such as a network slice name, network slice type, network slice domain, network slice resource sharing level, or network slice coverage area, and create a network slice based on the inputs received to the network slice template.

[0086] In some embodiments, the instruction further causes the processor to output a graphical user interface (GUI) via a user interface (UI) containing a list of one or more network slice templates configured to design a network slice, to create a new slice, and to update the GUI which includes a user input field for "Create a new slice", in response to the user input field for "Create a new slice" being selected by the user, the GUI which includes a first user input field configured to receive a network slice name, a second user input field configured to receive a network slice type, a third user input field configured to receive a network slice domain, a fourth user input field configured to receive a network slice resource sharing level, and a fifth user input field configured to receive a network slice coverage area.

[0087] In some embodiments, the instruction further causes the processor to update a GUI containing one or more user selection fields configured to be modified to design a network slice service profile, each user selection field representing a modifiable domain parameter, in response to receiving user input for one or more of the first to fifth user input fields.

[0088] In some embodiments, the instruction further causes the processor to convert each modifiable domain parameter for each network slice domain identified in the third user input field into slice profile parameters.

[0089] In some embodiments, the instruction further causes the processor to update a GUI that includes one or more network slice subnet user selection fields configured to allow the user to select domain-specific subnets in response to the conversion of each modifiable domain parameter for each network slice domain identified in a third user input field to slice profile parameters.

[0090] The above outlines some features of embodiments so that those skilled in the art may better understand aspects of the disclosure. Those skilled in the art should understand that the disclosure will readily be used as a basis for designing or modifying other processes and structures to perform the same objectives and / or achieve the same advantages of the embodiments described herein. Those skilled in the art should also understand that such equivalent configurations will not depart from the spirit and scope of the disclosure, and that various changes, substitutions, and modifications will be made herein without departing from the spirit and scope of the disclosure.

Claims

1. Receiving a selection of a network slice template from a list of one or more network slice templates for a network, In response to the selection of the aforementioned network slice template, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network slice coverage area One or more of these, receiving input to the network slice template, Obtaining at least one domain-specific network service, wherein the at least one domain-specific network service is already deployed in the network, and obtaining the at least one domain-specific network service includes (a) information regarding whether the at least one domain-specific network service is shared or dedicated, and (b) information regarding performance parameters for each domain of the at least one domain-specific network service, wherein the at least one domain-specific network service includes a radio access network (RAN) domain, a core domain, or a transport domain. Obtaining a selection from at least one domain-specific network service, The processor creates a network slice based on the received input to the network slice template and the selection from the at least one domain-specific network service. Methods that include...

2. The processor outputs a graphical user interface (GUI) via a user interface (UI) that includes the list of one or more network slice templates configured to design network slices, The GUI is updated to include a user input field for creating a new slice, In response to the selection of one or more network slice templates from the list, A first user input field configured to receive the network slice name, A second user input field configured to receive the aforementioned network slice type, A third user input field configured to receive the aforementioned network slice domain, A fourth user input field configured to receive the network slice resource sharing level, or A fifth user input field configured to receive the aforementioned network slice coverage area. Updating one or more of the GUIs configured to receive input to the network slice template, The method according to claim 1, further comprising:

3. In response to receiving user input for one or more of the first to fifth user input fields, The method according to claim 2, further comprising updating the GUI to include one or more user-selected fields configured to be modified to design a network slice service profile, each user-selected field representing a modifiable domain parameter.

4. The method according to claim 3, further comprising converting each modifiable domain parameter for each network slice domain identified in the third user input field into slice profile parameters.

5. In response to the conversion of each modifiable domain parameter for each network slice domain identified in the third user input field to the slice profile parameter, The method according to claim 4, further comprising updating the GUI to include one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet.

6. The method according to claim 5, wherein each network slice subnet user selection field includes subnets that have been determined to be available for each domain.

7. The method according to claim 5, further comprising determining whether one or more user-selected domain-specific subnets are deployable in response to the selection of domain-specific subnets for each domain.

8. In response to the selection of the domain-specific subnet, The method according to claim 7, further comprising updating the GUI to include a list of parameters for KPIs configured to be selected by the user, which are monitored when the network slice is deployed.

9. The aforementioned GUI, The method according to claim 8, further comprising a sixth user selection field configured to allow the user to select an automatic healing policy for the detected fault.

10. To deploy the aforementioned network slice The method according to claim 1, further comprising:

11. Processor and A memory, which, when executed by the processor, the processor, Receive a selection of a network slice template from a list of one or more network slice templates for the network. In response to the selection of the aforementioned network slice template, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network slice coverage area One or more of these receive input to the network slice template, The method involves obtaining at least one domain-specific network service, the at least one domain-specific network service being already deployed in the network, and the method of obtaining the at least one domain-specific network service includes obtaining (a) information regarding whether the at least one domain-specific network service is shared or dedicated, and (b) information regarding performance parameters for each domain of the at least one domain-specific network service, the at least one domain-specific network service including a radio access network (RAN) domain, a core domain, or a transport domain. To obtain a selection from at least one domain-specific network service, Based on the received input to the network slice template and the selection from at least one domain-specific network service, a network slice is created. The memory that stores the instructions and A device equipped with the following features.

12. The instruction further tells the processor: A graphical user interface (GUI) is output by the user interface (UI), which includes the list of one or more network slice templates configured to design network slices. Update the GUI to include a user input field for creating a new slice. In response to the user input field for creating the aforementioned new slice being selected by the user, A first user input field configured to receive the network slice name, A second user input field configured to receive the aforementioned network slice type, A third user input field configured to receive the aforementioned network slice domain, A fourth user input field configured to receive the network slice resource sharing level, A fifth user input field configured to receive the network slice coverage area and This includes updating the GUI, The apparatus according to claim 11.

13. The instruction further tells the processor: In response to receiving user input for one or more of the first to fifth user input fields, The apparatus according to claim 12, which updates the GUI, the GUI comprising one or more user selection fields configured to be modified to design a network slice service profile, each user selection field representing a modifiable domain parameter.

14. The apparatus according to claim 13, wherein the instruction further causes the processor to convert each modifiable domain parameter for each network slice domain identified in the third user input field into slice profile parameters.

15. The apparatus according to claim 14, wherein the instruction further causes the processor to update the GUI, which includes one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet in response to the conversion of each modifiable domain parameter for each network slice domain identified in the third user input field to the slice profile parameter.

16. When executed by the processor, the processor will Receive a selection of a network slice template from a list of one or more network slice templates for the network. In response to the selection of the aforementioned network slice template, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network slice coverage area One or more of these receive input to the network slice template, The method involves obtaining at least one domain-specific network service, the at least one domain-specific network service being already deployed in the network, and the method of obtaining the at least one domain-specific network service includes obtaining (a) information regarding whether the at least one domain-specific network service is shared or dedicated, and (b) information regarding performance parameters for each domain of the at least one domain-specific network service, the at least one domain-specific network service including a radio access network (RAN) domain, a core domain, or a transport domain. To obtain a selection from at least one domain-specific network service, Based on the received input to the network slice template and the selection from at least one domain-specific network service, a network slice is created. A non-temporary, computer-readable medium that stores instructions.

17. The instruction further tells the processor: A graphical user interface (GUI) is output by the user interface (UI), which includes the list of one or more network slice templates configured to design network slices. Update the GUI to include a user input field for creating a new slice. In response to the user input field for creating the aforementioned new slice being selected by the user, A first user input field configured to receive the network slice name, A second user input field configured to receive the aforementioned network slice type, A third user input field configured to receive the aforementioned network slice domain, A fourth user input field configured to receive the network slice resource sharing level, A fifth user input field configured to receive the network slice coverage area and This includes updating the GUI, The non-temporary computer-readable medium according to claim 16.

18. The instruction further tells the processor: In response to receiving user input for one or more of the first to fifth user input fields, A non-temporary computer-readable medium according to claim 17, which updates the GUI, comprising one or more user-selected fields configured to be modified to design a network slice service profile, each user-selected field representing a modifiable domain parameter.

19. The instruction further tells the processor: The non-temporary computer-readable medium according to claim 18, which converts each modifiable domain parameter for each network slice domain identified in the third user input field into slice profile parameters.

20. The instruction further tells the processor: In response to the conversion of each modifiable domain parameter for each network slice domain identified in the third user input field to the slice profile parameter, A non-temporary computer-readable medium according to claim 19, which causes the GUI to update, including one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet.

Images