SYSTEM AND METHOD FOR DESIGN OF NETWORK SLICES - Patent application

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 same. [Background technology]

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

[0003] A radio access network (RAN) is a part of a telecommunications system that implements radio access technologies. The RAN resides between devices such as mobile phones, computers, or remote control machines and provides connectivity to a Core Network (CN). Depending on the standard, mobile phones and other wirelessly 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; 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.

[0005] In some embodiments, an apparatus includes a processor and a memory storing instructions that, when executed by the processor, cause the processor to receive a selection of a network slice template from a list of one or more network slice templates, and in response to the selection of the network slice template, receive inputs for the network slice template, 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 create a network slice based on the received inputs for the network slice template.

[0006] In some embodiments, a non-transitory computer-readable medium storing 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, and in response to the selection of the network slice template, receive 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 create a network slice based on the received inputs for the network slice template. [Brief description of the drawings]

[0007] Aspects of the present disclosure can be understood from the following detailed description when read in conjunction with the accompanying drawings. In accordance with standard industry practice, various features are not drawn to scale. In some embodiments, dimensions of various features have been arbitrarily increased or decreased for clarity of discussion.

[0008] [Figure 1] 1 is a diagrammatic representation of a system for Network Slice Design (NSD), in accordance with some embodiments. [Diagram 2] FIG. 1 is a flow diagram of a method for designing a network slice according to some embodiments. [Diagram 3] 1 is a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 4] 1 is a GUI for designing network slices according to some embodiments. [Diagram 5] 1 is a GUI for designing network slices according to some embodiments. [Figure 6] 1 is a GUI for designing network slices according to some embodiments. [Figure 7] 1 is a GUI for designing network slices according to some embodiments. [Figure 8] 1 is a GUI for designing network slices according to some embodiments. [Figure 9] 1 is a GUI for designing network slices according to some embodiments. [Figure 10] 1 is a GUI for designing network slices according to some embodiments. [Figure 11] 1 is a GUI for designing network slices according to some embodiments. [Figure 12] 1 is a GUI for designing network slices according to some embodiments. [Figure 13] 1 is a GUI for designing network slices according to some embodiments. [Figure 14] 1 is a GUI for designing network slices according to some embodiments. [Figure 15] 1 is a GUI for designing network slices according to some embodiments. [Figure 16] FIG. 2 is a high-level block diagram of a processor-based system according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The following disclosure provides many different embodiments or examples for implementing different features of the subject matter under discussion. To simplify the disclosure, examples of components, values, operations, materials, arrangements, and the like are described below. Of course, these are examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, and the like are contemplated. For example, forming a first feature on or over a second feature in the following description includes embodiments in which the first feature and the second feature are formed in direct contact, and further includes embodiments in which an additional feature is formed between the first feature and the second feature such that the first feature and the second feature cannot be in direct contact. In addition, the disclosure repeats reference numbers and / or letters in many examples. This repetition is for brevity and clarity, and is not intended to dictate a relationship between the various embodiments and / or configurations under discussion.

[0010] Additionally, spatially relative terms such as underneath, below, lower, above, above, etc. are used herein for convenience of description to describe the relationship of one element or feature to another element(s) or feature(s) as illustrated in the figures. The spatially relative terms are intended to encompass different orientations of the device during use or operation in addition to the orientation illustrated in the figures. When a device is otherwise oriented (rotated 90 degrees or at other orientations), the spatially relative descriptors also used herein are interpreted accordingly.

[0011] In some embodiments, the network slice design is created via a Graphical User Interface (GUI) on a User Interface (UI) according to an example of the present disclosure.

[0012] Network slicing (or 5G network slicing) is a network architecture that allows 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. For this reason, the technology plays a leading role in supporting 5G mobile networks designed to efficiently encompass a multitude of services with significantly different Service Level Requirement (SLR). The realization of this service-oriented view of the network leverages the concepts of Software-Defined Networking (SDN) and Network Function Virtualization (NFV), which enable 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 the MVNOs, which share the underlying physical network. Depending on the availability of allocated resources, the MVNO autonomously deploys multiple network slices customized for the various applications offered 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 where interaction between humans and machines occurs. The purpose of this interaction is to allow effective operation and control of the machine from the human side while the machine simultaneously feeds back information that aids the operator's decision-making process. Examples include the interaction aspects of computer operating systems, hand tools, heavy equipment operator control, and process control. A UI includes one or more layers, including a Human-Machine Interface (HMI) that interfaces the machine with physical input hardware such as a keyboard, mouse, or gamepad, and output hardware such as a computer monitor, speakers, and printer. Devices that implement an HMI are called Human Interface Devices (HIDs). Other terms for a 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 of the human senses, including haptic UI (touch), visual UI (vision), 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 notations instead of text-based UIs, typed command labels, or text navigation. Actions in a GUI are usually performed by direct manipulation of graphical 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 is made more efficient with a GUI operated by a user on the UI. In some embodiments, the UI provides the user with the ability to select various relevant aspects of the network slice design. In some embodiments, the GUI is configured to design the E2E slice via 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 certain application-specific features, such as reliability and security, is achieved by implementing these features in the communicating end nodes of the network. Intermediate nodes, such as gateways and routers, that exist to establish the network, may implement these to improve efficiency, but cannot guarantee end-to-end correctness.

[0017] Network slice design is still a new concept. In some embodiments, GUI-based network slice design operations are considered. These operations include a user inputting information such as network slice name, slice type (enhanced Mobile BroadBand (eMBB) or massive Internet of Things (mIoT) slices that provide faster connections, higher throughput, and more capacity for high traffic areas such as stadiums, cities, and concert venues), domain (RAN, core, transport, etc.), shared or non-shared slice selection, Public Land Mobile Network (PLMN) ID of the slice, and slice coverage area. Other operations include defining service profile parameters (such as latency, data rate, and mobility level) required by the slice northbound interface (e.g., system internal or manual from a user) and translating the service profile parameters into slice profile parameters that hold slice subnet parameter information for different network domain slice subnet instances (NSSIs) (e.g., RAN, Transport Network (TN), and CN NSSIs). Other examples of service profile parameters include acceptable latency, number of connected UEs, and expected download and upload throughput from the slice. In some embodiments, in response to the service profile parameters being entered, the user clicks a user input field configured to split the service profile requirements into slice profile parameters. In some embodiments, the slice profile parameters are expected from each domain (e.g., expected latency from the RAN domain, etc.).

[0018] A component's northbound interface is an interface that allows the component to communicate with a higher-level component using the higher-level component's southbound interface. Northbound interfaces abstract the lower-level details (e.g., data or functionality) used by or within the component and allow the component to interface with higher-level layers. Northbound interfaces are typically drawn at the top of the component where they are defined. Southbound interfaces break down concepts primarily in technical details specific to a single component of the architecture. Southbound interfaces are drawn at the bottom of the architectural overview.

[0019] In some embodiments, the user inputs a slice subnet profile via a GUI. The slice subnet profile includes domain (RAN, CN, TN, etc.) specific subnets (segmented portions of a larger network). The slice manager (a centralized software component that provides an interface to create, modify, monitor, and delete slices) makes an application programming interface (API is a type of software interface that provides services to other software) call to the orchestrator (which allows the SDN controller to provision, update, and manage the computing resources required to deliver an application or service via APIs) to fetch information of 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, via a GUI, determines the feasibility of the network slice, such as whether the selected subnet is viable to be deployable. In a non-limiting example, for a shared subnet, there is a maximum number of slices that are supported. Thus, part of the feasibility check is to determine whether the shared subnet exceeds the number of slices that are supported.

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

[0022] In some embodiments, the user previews and sends the designed network slices via a GUI. Furthermore, the user selects the network slice to preview and send from a list of designed slices. In some embodiments, the user deploys the slices 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) and deploys the completed slice. In a non-limiting example, the slice manager makes an API call to the orchestrator to deploy the slice.

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

[0024] In some embodiments, the user navigates to a slice definition page where the service profile SLA parameters from the slice template 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 on a user-selected button for Calculate, and the slice manager calculates the slice profile parameters for each domain (RAN, CN, and TN) to meet the service profile SLA. In a non-limiting example, in response to a 10 ms SLA service profile latency (e.g., the SLA states that the latency is 10 ms or less), the service profile may be mapped to 3 ms from the RAN, 3 ms from the CN, and 4 ms from the TN domain for a total of 10 ms.

[0025] In some embodiments, a user navigates to a slice subnet profile UI page, and the user selects an already deployed domain-specific network service (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 on a user-selected button, Viability, to determine whether the selected network service is ready to provide service to the new network slice.

[0026] In some embodiments, a user navigates to an SLA GUI, where the user 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 a Network Slice LifeCycle Management (LCM) GUI. In some embodiments, the user navigates to an LCM slice GUI and selects the designed slice to deploy the designed slice.

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

[0028] FIG. 1 is a diagrammatic representation of a system for network slice design (NSD) 100, in accordance with some embodiments.

[0029] The NSD system 100 includes a CN 102 communicatively connected to a RAN 104 via a TN 106 communicatively connected to base stations 108A and 108B (hereinafter base stations 108) having antennas 110 wirelessly connected to UEs 112 located within geographic coverage cells 114A and 114B (hereinafter geographic coverage cells 114). The CN 102 includes one or more service provider(s) 116, a KPI server 118, and an NSD module 120.

[0030] The CN 102 (also known as a backbone) is the portion of a computer network that interconnects networks and provides a pathway for exchanging information between different local area networks (LANs) or sub-networks. In some embodiments, the CN 102 ties together diverse networks within the same building, different buildings in a campus environment, or across a large geographic area.

[0031] In some embodiments, the RAN 104 is a Global System for Mobile Communication (GSM) RAN, a GSM / EDGE RAN, a Universal Mobile Telecommunications System (UMTS) RAN (UTRAN), an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), an Open RAN (O-RAN), or a Cloud-RAN (C-RAN). The RAN 104 resides between the UE 112 (e.g., a mobile phone, a computer, or any remote control machine) and the CN 102. In some embodiments, for purposes of simplified representation and discussion, the RAN 104 is a 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 the base station at the cell site 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. The BBU is traditionally located in an enclosure or shelter located at the bottom of the base station. 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 base stations. This reduces the amount of equipment at the base station and provides many other benefits including less latency.

[0033] In a hierarchical telecommunications network, the TN 106 of the NSD system 100 comprises the intermediate link(s) between the CN 102 and the RAN 104. 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 the base station 108 and the UE 112 begins with the TN 106, which is connected to the CN 102. In some embodiments, the TN 106 includes wireline, fiber optic, 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, the base station 108 is a lattice or free-standing tower, guyed tower, monopole tower, and concealed tower (e.g., towers designed to resemble trees, cacti, water towers, signs, light poles, and other types of structures). In some embodiments, the 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 structure that is elevated to create a cell (or adjacent cells) in the network. The elevated structure typically supports an antenna(s) 110 and one or more sets of transmitters / receivers (transceivers), digital signal processors, control electronics, Remote Radio Heads (RRHs), primary and backup power sources, and shelters. Base stations are known by other names such as base transceiver stations, mobile phone masts, or cell towers. In some embodiments, the base station is replaced by other edge devices configured to wirelessly communicate with the UEs. The edge devices provide an entry point into a service provider CN, such as the 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 are sector antennas. In some embodiments, the antenna(s) 110 are a type of directional microwave antenna with a sector-shaped radiation pattern. In some embodiments, the sector is designed to have a 60°, 90°, or 120° radius, with a few extra degrees to ensure overlap. Additionally, sector antennas are mounted in multiples when wider or all-around coverage is required. In some embodiments, the antenna(s) 110 are rectangular antennas, sometimes referred to as panel antennas or radio antennas, used to transmit and receive radio waves or data between mobile devices or other devices and base stations. In some embodiments, the antenna(s) 110 are circular antennas. In some embodiments, the antenna 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 are MIMO (multiple-input multiple-output) antennas that transmit and receive two or more data signals simultaneously over the same wireless channel by taking advantage of multipath propagation.

[0036] In some embodiments, the UE 112 is a computer or computing system. Additionally or alternatively, the UE 112 has a Liquid Crystal Display (LCD) or Light-Emitting Diode (LED) or Organic Light-Emitting Diode (OLED) screen interface, such as a user interface (UI) 1622 ( FIG. 16 ) that provides a touch screen interface with digital buttons and a keyboard, or with physical buttons along with a physical keyboard. In some embodiments, the UE 112 connects to the Internet and interconnects with other devices. Additionally or alternatively, the UE 112 incorporates a built-in camera, voice and videophone call capabilities, video games, and Global Positioning System (GPS) functionality. Additionally or alternatively, the UE runs an Operating System (OS) that allows for the installation and execution of feature-specific third-party applications.In some embodiments, the UE 112 is a computer (such as a tablet computer, a netbook, a digital media player, a digital assistant, a graphing calculator, a handheld game console, a handheld personal computer (Personal Computer (PC)), a laptop, a Mobile Internet Device (MID), a Personal Digital Assistant (PDA), a pocket calculator, a portable media player, or an ultra-mobile PC), a mobile phone (such as a camera phone, a feature phone, a smartphone, a phablet, or the like), a digital camera (such as a digital camcorder, or a Digital Still Camera (DSC), a Digital Video Camera (DVC), or a front-facing camera), a pager, a Personal Navigation Device (PND)), a wearable computer (such as a calculator watch, a smart watch, a head mounted display, an earpiece, or a biometric device), or a smart card.

[0037] In some embodiments, the geographic coverage cell 114 includes a shape and a size. In some embodiments, the geographic coverage cell 114 is a macro cell (covering 1 Km to 30 Km), a micro cell (covering 200 m to 2 Km), or a pico cell (covering 4 m to 200 m). In some embodiments, the geographic coverage cell is circular, elliptical (FIG. 1), sector-shaped, or lobed, although the geographic coverage cell 114 may be configured in almost any shape or size. The geographic coverage cell 114 represents a geographic area in which the antenna 110 and the UE 112 are configured to communicate. Coverage depends on several factors such as terrain (i.e., mountains) and buildings, technology, radio frequency, and most important for two-way telecommunications, the sensitivity and transmission efficiency of the UE 112. Some frequencies provide better coverage of an area, while other frequencies penetrate obstacles such as city buildings better. The ability of the UE to connect to the base station depends on the strength of the signal.

[0038] A service provider(s) 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, usually its Network Access Point (NAP). A service provider may be called a backbone provider, Internet provider, or vendor. Service providers include telecommunications companies, data carriers, wireless communication providers, Internet service providers, and cable television operators that offer high-speed Internet access.

[0039] The KPI server 118 generates both forecast and live network data. The live network data (KPIs, UE / cell / minimization of drive test (MDT) traces, and crowd-sourced data) enables modeling of network traffic, hotspot identification, and wireless signal propagation. RF drive test is a method of measuring and evaluating the coverage, capacity, and Quality of Service (QoS) of a mobile wireless network, such as the RAN 104. The technique consists of using automobiles that contain mobile wireless 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 what wireless network subscribers experience in an area, wireless carriers make directed changes to the network to provide better coverage and service to their customers. Drive tests typically consist of a moving vehicle equipped with drive test measurement equipment. The equipment is a highly specialized electronic device that typically interfaces with a mobile handset (UE) by an original equipment manufacturer (OEM). This ensures that the measurements are realistic and comparable to real user experience.,In the case of mobile networks, crowdsourcing methodologies leverage a,crowd of participants (e.g., mobile subscribers) to collect,network measurements either manually or automatically via mobile apps,,or directly from the network using call traces.

[0040] The 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, the network slice design is GUI-based. In some embodiments, these operations include a user inputting information such as a network slice name, slice type (eMBB (enhanced mobile broadband) or mIoT (massive internet of things) slice, which provides faster connectivity, higher throughput, and more capacity for high traffic areas such as stadiums, cities, and concert venues), domain (RAN, core, transport, etc.), selection of shared or non-shared slice, public land mobile network (PLMN) ID of the slice, and coverage area of ​​the slice. Other operations include defining service profile parameters (holding original requirements of communication service instances such as latency, data rate, and mobility level) required by the slice's northbound interface (e.g., system internal or manually from a user), and converting the service profile parameters to slice profile parameters (holding slice subnet parameter information of different network domain slice subnet instances (NSSIs) such as RAN, transport network (TN), and CN NSSIs).

[0042] FIG. 2 is a flow diagram of a method 200 for designing a network slice, according to some embodiments.

[0043] 3 to 15 are graphic user interfaces (GUIs) 300 to 1500 for designing network slices according to some embodiments.

[0044] In some embodiments, the NSD method 200 describes the process tasks of network slice design. Although the operations of the NSD method 200 are discussed and illustrated as having a particular order, 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, the NSD method 200 is discussed with reference to Figures 3 through 15.

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

[0046] In operation 204 of the NSD method 200, the NSD module 120 presents a list of slice templates. In FIG. 4, the GUI 400 displays a slice template list 402. In some embodiments, each network slice in the slice template list 402 includes a status (e.g., active or inactive), a name, a slice service type (e.g., eMBB, uRLLC, mIoT, or custom), a service category (e.g., home automation, high-speed train, etc.), a domain (RAN, TN, CN, or E2E), a vendor, a version, shared (or non-shared), a creation date, and a last modification date. The term template refers to a common feature of a software application that defines a unique non-executable file format specifically intended for that 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 a selection of a slice template. In FIG. 4, the user points to a slice template, e.g., slice template 404, and then clicks on the slice template. A user-selected button 406 for creating a new slice pops up, and the user clicks on the user-selected 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] At operation 208 of the NSD method 200, a GUI 500 is presented and a user inputs slice information. In FIG. 5, the user inputs a slice name in user input field 502, selects a slice type (e.g., eMBB or URLLC type of slice) from user selection field 504, selects a 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 a coverage area for 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, a GUI 600 is presented and a user sets network slice information. In FIG. 6, in the slice parameter GUI 600, service profile SLA parameters 602 are presented and configured for the user to change the parameters as needed. In a non-limiting example, the user changes the expected latency in the user selection field 604 to meet the network slice specifications (e.g., set it to 300 ms). Once the user has finalized all the service profile parameters in the parameter field 602 for the complete end-to-end network slice, the user points and clicks on the user selection button 606 of calculate. The slice manager calculates the slice profile parameters (shown in slice profile box 608) for each domain (RAN, CORE, and transport) to meet the service profile SLA. The process proceeds from operation 210 to operation 212.

[0050] At operation 212 of the NSD method 200, a GUI 700 is presented and a user selects a subnet profile, such as an already deployed domain-specific network service (shared network service or dedicated network service). In FIG. 7, a user navigates to the slice subnet profile GUI 700 and the user selects one of the already deployed domain-specific network services (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 on a user selection field 706 of select. In a non-limiting example, in response to a network slice subnet of a RAN domain 708 being shared, an already deployed network slice subnet may be obtained and selected for use. In some embodiments, a network service is selected for the network slice subnet. Continuing with the non-limiting example, a network service for a RAN domain, such as ABC, is an identifier of a network service from a deployed RAN domain. Continuing with the non-limiting example, in a core domain 710, a user may select a template name as a new network service being deployed for the core domain 710 by clicking on a user selection field 706.

[0051] In FIG. 8, GUI 800 is presented after a user clicks on user selection field 706 of Select, and the user is presented with a network service selection pop-up box 802. As shown in box 804, each of the network services, such as User Plane Function (UPF) 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), Network Repository Function (NRF) acts as a central service discovery broker for all Network Functions (NFs) in the 5G Core), or Session Management Function (SMF) is responsible for interacting with the separated data plane, creating, updating, and deleting PDU sessions, and managing session context with UPF). In a non-limiting example, the user selects UPF (highlighted), and within user input field 806 of Share, an indication (e.g., true) is presented to the user that the UPF network service is shared.

[0052] 9, GUI 900 highlights NRF and displays FALSE as presented in Shared user input field 806, indicating that the NRF network service is not shared. Thus, the user fills out Dedicated Network Service template 902. The user selects a network service template in NS Template user selection field 904. In response to selecting a network service template (e.g., UPF NST Sample 2), the user is presented with network features to select from.

[0053] In FIG. 10, a GUI 1000 is presented with a network service included for each domain (RAN, core, and transport). Once each domain includes a network service, the user points and clicks on a feasibility user selection field 1002, and the NSD module 120 determines whether the selected network service is ready to serve the new network slice. In some embodiments, in response to the user clicking on the feasibility user selection field 1002, the NSD module 120 determines whether it is feasible to deploy the selected subnet as part of the new network slice (e.g., in a shared subnet, there is a maximum number of slices that one subnet supports, or whether the new core network service is deployable).

[0054] In FIG. 11, GUI 1100 is presented when a feasibility test fails for one or more domains (e.g., the RAN domain). The user clicks on the network slice subnet name, user selection field 1102 to select a different slice subnet, and clicks on the feasibility, user selection field 1002 to recheck the feasibility. In a non-limiting example, in FIG. 11, the feasibility of RAN domain 708 fails, meaning that the selected network service is not supported in the new network slice, so that the user can click on the user selection field 1102 to select a different RAN subnet from the list 1104, and rerun the feasibility test.

[0055] 12, a GUI 1200 is presented when the feasibility test is successful for each domain. The user clicks on a next user selection button 1202 to deploy the network slice. The process proceeds from operation 212 to operation 214. In a non-limiting example, in response to the viability check being successful, a network slice can be created using each selected domain subnet 1204.

[0056] At operation 214 of method 200, GUI 1300 is presented (FIG. 13) and a user selects SLA parameters, such as those shown in parameter box 1302, to be monitored for the slice. The user searches for the selected domain from the parameters in user input field 1306, Search. In some embodiments, the user drags and drops parameters / KPIs 1308 into parameter box 1302. Furthermore, in response to the slice being deployed and the selection of the parameters or KPIs to be monitored (box 1302), the user selects a policy from user selection field 1304, Policy Name, of the slice auto healing use case. Auto healing is a function that automatically detects disabled access points and restores 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 (FIG. 14) for review by the user. After previewing the network slice 1402 including the service information 1404 and the automation policy 1406, the user clicks on the user selection field 1408 of send after determining that the information is correct. In response to the user selection field 1408 of send being clicked, GUI 1500 (FIG. 15) is displayed with a list of network slices 1502. In some embodiments, in response to the user clicking on the user selection field 1408 of send, the network slice 1402 from GUI 1400 is designed and listed on GUI 1500 (FIG. 15) displayed with a list of network slices 1502. The process proceeds from operation 216 to operation 218.

[0058] At operation 218 of method 200, the user deploys the designed network slice by clicking on the desired network slice in the list of network slices 1502, which displays a pop-up box 1504 of the GUI 1500. The user deploys the designed slice by clicking on a Deploy user selection button 1506. In some embodiments, a slice manager (not shown) makes an API call to an orchestrator (not shown) and the designed slice is deployed. The process proceeds from operation 218 to operation 220.

[0059] At 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, in response to the slice being successfully submitted and listed, the slice is labeled as "designed." GUI 1500 populates 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 suitable slice details within the scope of an embodiment.

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

[0061] 16 is a block diagram of a network slice design (NSD) processing circuitry 1600 according to some embodiments. In some embodiments, the NSD processing circuitry 1600 is a general-purpose computing device including a hardware processor 1602 and a non-transitory computer-readable storage medium 1604. Among other things, the storage medium 1604 is encoded with, i.e., stores, a computer program code 1606, i.e., an algorithm or set of executable instructions, such as the method 200. The execution of the instructions 1606 by the hardware processor 1602 represents (at least in part) a network slice design application that implements a portion or all of the methodology described herein (hereinafter, the process and / or methodology) according to one or more embodiments.

[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 by 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 such 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 such that the NSD processing circuit 1600 can be used to perform a portion or all of the processes and / or methods described. 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 any other suitable processing unit.

[0063] In one or more embodiments, computer readable storage medium 1604 is an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, computer readable storage medium 1604 includes a semiconductor or solid state memory, a magnetic tape, a removable computer diskette, a Random-Access Memory (RAM), a Read-Only Memory (ROM), a rigid magnetic disk, and / or an optical disk. In one or more embodiments that use an optical disk, computer readable storage medium 1604 includes a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk-Read / Write (CD-R / W), and / or a 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 some or all of the described processes and / or methods. In one or more embodiments, the storage medium 1604 also stores information such as mitigation algorithms that facilitate performing some or all of the described processes and / or methods.

[0065] The NSD processing circuit 1600 includes an I / O interface 1610. The I / O interface 1610 is coupled to external circuitry. In one or more embodiments, the I / O interface 1610 includes a keyboard, a keypad, a mouse, a trackball, a trackpad, a touch screen, and / or cursor direction keys for communicating 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 a wireless network interface, such as BLUETOOTH, WIFI, WIMAX, GPRS, or WCDMA, or a wired network interface, such as ETHERNET, USB, IEEE-864, etc. In one or more embodiments, some or all of the described processes and / or methods are performed in two or more NSD processing circuits 1600.

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

[0068] In some embodiments, some or all of the described processes and / or methods are implemented as a stand-alone software application for execution by a processor. In some embodiments, some or all of the described processes and / or methods are implemented as a software application that is part of an additional software application. In some embodiments, some or all of the described processes and / or methods are implemented as a plug-in to a software application.

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

[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; 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.

[0071] In some embodiments, the method further includes causing a user interface (UI) to output, by the processor, a graphical user interface (GUI) including a list of one or more network slice templates configured to design the network slice; updating the GUI with a user input field for creating a new slice; and in response to a selection of the network slice template from the list of the one or more network slice templates, updating the GUI configured to receive input for the network slice template, such as one or more of 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, in response to receiving user input for one or more of the first through fifth user input fields, updating a GUI including one or more user-selected fields configured to be modified to design a network slice service profile, where each user-selected field represents a modifiable domain parameter.

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

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

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

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

[0077] In some embodiments, the method further includes, in response to selection of the domain-specific subnet, updating a GUI including a list of parameters of KPIs configured to be selected by the user, where each parameter or key performance indicator (KPI) is to be monitored as the network slice is deployed.

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

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

[0080] In some embodiments, an apparatus includes a processor and a memory storing instructions that, when executed by the processor, cause the processor to receive a selection of a network slice template from a list of one or more network slice templates, and in response to the selection of the network slice template, receive inputs for the network slice template, 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 create a network slice based on the received inputs for the network slice template.

[0081] In some embodiments, the instructions further cause the processor to output, by a user interface (UI), a graphical user interface (GUI) including a list of one or more network slice templates configured to design the network slice, update the GUI including a user input field of "create a new slice," and in response to the user input field of "create a new slice" being selected by a user, update the GUI 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, and a fifth user input field configured to receive a network slice coverage area.

[0082] In some embodiments, the instructions further cause the processor to update, in response to receiving user input for one or more of the first through fifth user input fields, a GUI including one or more user-selected fields configured to be modified to design a network slice service profile, where each user-selected field represents a modifiable domain parameter.

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

[0084] In some embodiments, the instructions further cause the processor to update a GUI including one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet in response to converting each modifiable domain parameter into a slice profile parameter for each network slice domain identified in the third user input field.

[0085] In some embodiments, a non-transitory computer-readable medium storing 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, and in response to the selection of the network slice template, receive 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 create a network slice based on the received inputs for the network slice template.

[0086] In some embodiments, the instructions further cause the processor to output, by a user interface (UI), a graphical user interface (GUI) including a list of one or more network slice templates configured to design the network slice, update the GUI including a user input field of "create a new slice," and in response to the user input field of "create a new slice" being selected by a user, update the GUI 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, and a fifth user input field configured to receive a network slice coverage area.

[0087] In some embodiments, the instructions further cause the processor to update, in response to receiving user input for one or more of the first through fifth user input fields, a GUI including one or more user-selected fields configured to be modified to design a network slice service profile, where each user-selected field represents a modifiable domain parameter.

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

[0089] In some embodiments, the instructions further cause the processor to update a GUI including one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet in response to converting each modifiable domain parameter into a slice profile parameter for each network slice domain identified in the third user input field.

[0090] The above outlines the features of some embodiments so that those skilled in the art can better understand the aspects of the present disclosure. Those skilled in the art should understand that the present disclosure can be easily used as a basis for designing or modifying other processes and structures for carrying out the same purpose and / or achieving the same advantages of the embodiments introduced herein. Those skilled in the art should also understand that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the present disclosure.

Claims

1. 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, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network Slice Coverage Area receiving inputs for the network slice template, including one or more of: creating, by a processor, a network slice based on the received inputs to the network slice template; A method comprising:

2. causing a user interface (UI) to output, by the processor, a graphical user interface (GUI) including the list of one or more network slice templates configured to design a network slice; updating the GUI with a user input field for creating a new slice; in response to the selection of the network slice template from the list of one or more network slice templates, a first user input field configured to receive a name of the network slice; a second user input field configured to receive the network slice type; a third user input field configured to receive the 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 network slice coverage area. updating the GUI configured to receive inputs for the network slice template, the inputs being one or more of: The method of claim 1 further comprising:

3. in response to receiving user input for one or more of the first through fifth user input fields; 3. The method of 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. 4. The method of claim 3, further comprising converting each modifiable domain parameter for each network slice domain identified in the third user input field into a slice profile parameter.

5. in response to the conversion of each modifiable domain parameter for each network slice domain identified in the third user input field into the slice profile parameters; 5. The method of 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. 6. The method of claim 5, wherein each network slice subnet user selection field includes subnets determined to be available for each domain.

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

8. in response to said selection of said domain-specific subnet; 10. The method of claim 7, further comprising: updating the GUI to include a list of parameters of KPIs configured for selection by a user, where each parameter or key performance indicator (KPI) is to be monitored as the network slice is deployed.

9. The GUI, 10. The method of claim 8, further comprising a sixth user selection field configured to allow the user to select an auto-healing policy for the detected failure.

10. Deploying the network slice. The method of claim 1 further comprising:

11. A processor; a memory, which when executed by the processor, causes the processor to: 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, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network Slice Coverage Area receiving inputs for the network slice template, creating a network slice based on the received inputs to the network slice template. Memory that stores instructions An apparatus comprising:

12. The instructions further cause the processor to: causing a user interface (UI) to output a graphical user interface (GUI) including the list of one or more network slice templates configured to design a network slice; updating the GUI to include a user input field for creating a new slice; In response to a user selecting the user input field for creating a new slice, a first user input field configured to receive the network slice name; a second user input field configured to receive the network slice type; a third user input field configured to receive the network slice domain; and 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 updating the GUI, 12. The apparatus of claim 11.

13. The instructions further cause the processor to: in response to receiving user input for one or more of the first through fifth user input fields; The apparatus of claim 12 , 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.

14. 14. The apparatus of claim 13, wherein the instructions further cause the processor to convert each modifiable domain parameter for each network slice domain identified in the third user input field into a slice profile parameter.

15. 15. The apparatus of claim 14, wherein the instructions further cause the processor to update the GUI to include 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 into the slice profile parameters.

16. When executed by a processor, the processor: 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, Network slice name, Network slice type, Network slice domain, Network slice resource sharing level, or Network Slice Coverage Area receiving inputs for the network slice template, including one or more of: creating a network slice based on the received inputs to the network slice template. A non-transitory computer-readable medium storing instructions.

17. The instructions further cause the processor to: causing a user interface (UI) to output a graphical user interface (GUI) including the list of one or more network slice templates configured to design a network slice; updating the GUI to include a user input field for creating a new slice; In response to a user selecting the user input field for creating a new slice, a first user input field configured to receive the network slice name; a second user input field configured to receive the network slice type; a third user input field configured to receive the 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 updating the GUI, 20. The non-transitory computer-readable medium of claim 16.

18. The instructions further cause the processor to: in response to receiving user input for one or more of the first through fifth user input fields; 20. The non-transitory computer-readable medium of claim 17, 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.

19. The instructions further cause the processor to:

20. The non-transitory computer-readable medium of claim 18, further comprising: converting each modifiable domain parameter for each network slice domain identified in the third user input field into a slice profile parameter.

20. The instructions further cause the processor to: in response to the conversion of each modifiable domain parameter for each network slice domain identified in the third user input field into the slice profile parameters; 20. The non-transitory computer-readable medium of claim 19, causing the GUI to update to include one or more network slice subnet user selection fields configured to allow a user to select a domain-specific subnet.

Images