Systems and methods for automatic generation and implementation of network slice identifiers

Abstract

The method includes creating a network slice by a processor and based on a network slice design submitted by a user, and automatically generating, by the processor, a network slice selection assistance information ID (nSSAI ID) for the network slice.

Description

[Technical field]

[0001] The present description relates to a system for automatic generation and implementation of network slice identifiers and methods of use thereof. [Background technology]

[0002] A cellular network is a telecommunications system in which mobile devices (e.g., mobile phone devices) communicate by radio waves through one or more local antennas at a cellular base station (e.g., a 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 and separate frequency channels assigned by the base station from a common pool of frequencies used by the cellular network.

[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 the 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 creating a network slice by a processor and based on a network slice design submitted by a user, and automatically generating, by the processor, a network slice selection assistance information ID (nSSAI ID) for the network slice.

[0005] In some embodiments, an apparatus includes a processor and a memory having instructions stored thereon that, when executed by the processor, cause the processor to create a network slice based on a network slice design submitted by a user and automatically generate a network slice selection assistance information ID (nSSAI ID) for the network slice based on the network slice design.

[0006] In some embodiments, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to create a network slice based on a network slice design submitted by a user and automatically generate a network slice selection assistance information ID (nSSAI ID) for the network slice based on the network slice design.

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

[0008] [Figure 1] FIG. 1 is a schematic diagram of a system for network slice design (NSD) in accordance with some embodiments.

[0009] [Diagram 2] FIG. 2 is a flow diagram of a method for designing a network slice according to some embodiments.

[0010] [Diagram 3] FIG. 3 is an illustration of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 4] FIG. 4 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Diagram 5] FIG. 5 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 6] FIG. 6 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 7] FIG. 7 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 8] FIG. 8 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 9] FIG. 9 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 10] FIG. 10 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 11] FIG. 11 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 12]FIG. 12 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 13] FIG. 13 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 14] FIG. 14 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments. [Figure 15] FIG. 15 is another diagram of a graphic user interface (GUI) for designing network slices according to some embodiments.

[0011] [Figure 16] FIG. 16 is a data flow diagram of a method for generating and implementing a unique network slice identifier (UNSI) according to some embodiments.

[0012] [Figure 17] FIG. 17 illustrates example nSSAI ID rules, according to some embodiments.

[0013] [Figure 18] FIG. 18 is a high-level functional block diagram of a processor-based system according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The following disclosure provides many different embodiments or examples for implementing the specific features of the subject matter (technology, overview) described above. In the following, examples of components, values, operations, materials, arrangements, etc. are described to simplify the disclosure. Of course, these are examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc. are possible and fall within the scope of the present invention. For example, when a first feature is formed on or above a second feature in the following description, this includes an embodiment in which the first feature and the second feature are formed in direct contact with each other, and further includes an embodiment 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 with each other. In addition, the present disclosure repeats reference numbers and / or letters in various examples. This repetition is for the purpose of brevity and clarity, and does not dictate a relationship between the various embodiments and / or configurations described.

[0015] Additionally, spatially relative terms such as "lower," "below," "lower side," "upper," "upper" and the like are used herein for ease of description to describe the relationship of one element or feature to another element or feature as shown 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 shown in the figures. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors (phrases, symbols) used herein may be interpreted accordingly.

[0016] In some embodiments, automatic generation and implementation of unique network slice identifiers (UNSIs) are described in the present disclosure. In some embodiments, slice identifiers are automatically generated, which provides ease of network slice management, slice identifier process efficiency, efficient deployment of network slices, and reduction of human error introduced by manual generation of network slice identifiers.

[0017] In another approach, the unique network slice identifiers are manually generated. Manually created unique slice identifiers are labor intensive.

[0018] Network slicing is a method of creating multiple unique logical and virtualized networks on a common multi-domain infrastructure. By using software-defined networking, network function virtualization, orchestration, analytics, and automation, network operators manually create network slices that support specific applications, services, sets of users, or networks. Network slices can also be configured to span multiple network domains, such as access networks (user networks, such as RANs, that connect subscribers to service providers and other networks, such as the Internet, via transport networks), CNs (core networks are central conduits designed to forward network traffic at high speeds), and transport networks (public telecommunications infrastructure that enables telecommunications between defined network termination points) deployed across multiple network operators.

[0019] Network slicing supports services with different network requirements, such as connected vehicles to voice calls, which require different throughput, latency, and reliability compared to data communications with Internet of Things (IoT) devices. In network slicing, each slice is configured to have different architecture, management, and security to support specific usage. Functional components and resources are shared across network slices, but capabilities such as data rate, capacity, connectivity, quality, latency, reliability, and service are customized in each slice to comply with a specific service level agreement (SLA) with a vendor. In some embodiments, an example logic for automatically generated unique network slice identifiers is described in the present disclosure.

[0020] A single network slice selection assistance information (S-NSSAI) identification (ID) is used to uniquely identify a network slice. The S-NSSAI ID contains two components: Slice / Service Type (SST) and an optional Slice Differentiator (SD). In the context of network slicing, the SST is the expected behavior of a network slice with respect to specific functions and services. Standardized SST values ​​include eMBB (enhanced mobile broadband, focusing on high speed end-user data and system capacity), URLLC (ultra-reliable low latency communications, a subset of 5G network architecture that ensures efficient scheduling of data transfers, achieving shorter transmissions over larger subcarriers, and even scheduling overlapping transmissions), and MIoT (massive internet of things, a category driven by scale, not speed, where deployments include hundreds to billions of connected devices, where the goal of these applications is to efficiently transmit and consume small amounts of data from a vast number of devices). In network slicing, SD is related to SST and is used as an additional differentiator when multiple network slices carry the same SST value. SD is intended for the implementation of network slicing.

[0021] An nSSAI ID typically has a total length of 9 characters, where the first 3 characters are SST and the remaining 6 characters are SD. In some embodiments, a naming manager is configured to take the business rules and implement the business rules in the form of a naming template, where the naming manager is responsible for creating the nSSAI ID output in turn. In some embodiments, the naming manager is a tool, where the naming template is created by the user based on the business rules. In response to a user invoking the naming template using the API, the naming manager provides the user with the necessary inputs for the template, and the naming manager then returns the desired output.

[0022] In some embodiments, in response to a new network slice being designed, the slice manager automatically makes an application programming interface (API) call to the naming manager to receive an nSSAI ID of the newly designed network slice.

[0023] When a network slice is deactivated or terminated, the slice manager makes another API call to the naming manager requesting that the nSSAI ID be revoked from the naming manager so that the terminated or deactivated nSSAI ID can be reused for another slice.

[0024] In some embodiments, the naming manager generates a unique nSSAI ID each time an API call is made from the slice manager to the naming manager. In some embodiments, the naming manager is a template-based rule engine. Within the rule template, a user accesses or creates a template rule where the user inputs template parameters. The naming manager is configured to use the rule template to generate nSSAI IDs. Additionally, the naming manager is configured to maintain a sequence of generated nSSAI IDs or names. In some embodiments, the naming manager is configured to create rule templates and use them to generate various nSSAI IDs, application names, or other functions within the scope of the present embodiments.

[0025] A network slice is divided into Network Service (NS) subnets, each dedicated to a domain (e.g., RAN, CN, transport domain, or E2E, each of which includes). A transport domain refers to the telecommunication transmission facilities under which voice, data, and video communications are distributed among separate locations for use on a shared basis.

[0026] Within the NS subnet, there are one or more network services. For example, within the RAN slice subnet, there are network services such as gNodeB (gNB is a 3rd Generation Partnership Project (3GPP) 5G next-generation base station that supports 5G new radio). Within the CN slice subnet, there are network services such as NRF (network repository function, which is a function of the 3GPP service-based architecture (SBA) for 5G CN that acts as a central services broker for all network functions in the 5G CN), or AMF (access and mobility management function, which receives connection and session related information from the UE to handle connection and mobility management tasks). Within the transport slice subnet, there are transport network services.

[0027] Within the network service, there are one or more network functions, for example within the gNB network service, there are network functions such as a distributed unit (DU: a distributed unit supports one or more cells, which support radio link control (RLC), medium access control (MAC), and physical layers), a central unit control plane (CUCP: a central unit control plane hosts the control plane part of radio resource control (RRC) and packet data convergence protocol (PDCP)), and a central unit user plane (CUUP: a logical node that hosts the user plane part of the PDCP protocol of the gNB-CU for the gNB and the user plane part of the PDCP protocol of the gNB-CU for the en-gNB or gNB).

[0028] Within the NRF network services are network functions such as MongoDB (an open source NoSQL database management program), NRF (which provides a single record of network capabilities available in each public land mobile network (PLMN) along with a profile of each supported service), and Redis (an in-memory data structure store with optional durability used as a distributed in-memory key-value database, cache, and message broker). Additionally, within the AMF network services are network functions such as Nginx (an open source web server software that performs reverse proxy, load balancing, email proxy, and HTTP cache services), AMF applications, and databases.

[0029] Within the transport network services are software (SW), SDN (software-defined networking: software-defined networking is an approach to network management that enables dynamic, programmatically efficient network configuration to improve network performance and monitoring, much like cloud computing, over traditional network management), and network functions such as routers (networking devices that forward data packets between computer networks).

[0030] FIG. 1 is a schematic diagram of a system 100 for network slice design (NSD) in accordance with some embodiments.

[0031] The NSD system 100 includes a CN 102 communicatively connected to a RAN 104 via a transport network 106 communicatively connected to base stations 108A and 108B (hereinafter referred to as base stations 108), where an antenna 110 is wirelessly connected to a UE 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 a network slice module (NSDM) 120.

[0032] The CN 102 (also known as the backbone) is a domain that is part 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 diverse networks together across a wide geographic area, in different buildings in a campus environment, or within the same building.

[0033] In some embodiments, the RAN 104 is an access network domain. In some embodiments, the RAN 104 is a global system for mobile communications (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 remotely controlled machine) and the CN 102. In some embodiments, the RAN 104 is a C-RAN for purposes of simplified representation and discussion. In some embodiments, base band units (BBUs) replace the C-RAN.

[0034] In a traditional distributed cellular network, the equipment at the bottom and top of the base station at the cell site is the BBU. The BBU is a radio device that links the UE to the CN and processes billions of bits of information per hour. The BBU is traditionally placed in an enclosure or shelter located at the bottom of the base station. In contrast, C-RAN uses the large signal transmission capacity of optical fiber to concentrate a large number of BBUs in a dedicated pool location or base station. This reduces the number of equipment at the base station and provides many other benefits such as lower latency.

[0035] In a hierarchical telecommunications network, the transport network 106 of the NSD system 100 includes intermediate links between the CN 102 and the RAN 104. Two main methods in mobile backhaul implementations are fiber-based backhaul and wireless point-to-point backhaul. Other methods such as copper-based wired (wire, cable), satellite communication, and point-to-multipoint wireless technologies are being phased out as capacity and latency requirements become higher in 4G and 5G networks. Backhaul refers to the network side that communicates with the Internet. The connection between the base station 108 and the UE 112 starts from the transport network 106 connected to the CN 102. In some embodiments, the transport network 106 includes wired, optical fiber, and wireless components. The wireless section includes using edge network topologies, mesh and microwave bands that use high capacity wireless channels to get packets onto microwave or fiber links.

[0036] In some embodiments, the base stations 108 are lattice or freestanding towers, guyed towers, monopole towers, and concealed towers (e.g., towers designed to resemble trees, cacti, water towers, signs, light standards, and other types of structures). In some embodiments, the base stations 108 are cellular-enabled mobile device sites where antennas and electronic communication equipment are typically placed on top of a radio mast, tower, or other elevated structure to create a cell (or multiple adjacent cells) in a network. The elevated structure typically supports an antenna 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 sheltering. Base stations are known by other names, such as base transceiver station, cellular phone mast, or cell tower. In some embodiments, the base stations are replaced by or supplemented by other edge devices configured to wirelessly communicate with UEs. An edge device provides an entry point into 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.

[0037] In at least one embodiment, the antenna 110 is a sector antenna. In some embodiments, the antenna 110 is a type of directional microwave antenna with a sector-shaped radiation pattern. In some embodiments, the angle of the sector of the arc is a 60°, 90°, or 120° design with a few extra degrees to ensure overlap. Additionally, sector antennas are mounted in multiples when wider or all-around coverage is desired. In some embodiments, the antenna 110 is a rectangular antenna, sometimes called a panel antenna or radio antenna, used to transmit and receive waves or data between mobile or other devices and base stations. In some embodiments, the antenna 110 is a circular antenna. In some embodiments, the antenna 110 operates at microwave or ultra-high frequency (UHF) frequencies (300 MHz to 3 GHz). In other examples, the antennas 110 are selected for their size and directional characteristics. In some embodiments, antenna 110 is a multiple-input, multiple-output (MIMO) antenna that transmits and receives multiple data signals simultaneously over the same wireless channel by taking advantage of multipath propagation.

[0038] In some embodiments, the UE 112 is a computer or computing system. Additionally or alternatively, the UE 112 has a liquid crystal display (LCD), light emitting diode (LED) or organic light emitting diode (OLED) screen interface (e.g., user interface (UI) 1822 (FIG. 18)) and provides a touch screen interface with digital buttons and a keyboard or 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 an integrated camera, the ability to make and receive voice and video phone calls, video games, and global positioning system (GPS) functions. 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 (PC), a laptop, a mobile Internet device (MID), a personal digital assistant (PDA), a pocket calculator, a portable medial 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 smartwatch, a head mounted display, an earpiece, or a biometric device), or a smart card.

[0039] In some embodiments, the geographic coverage cell 114 includes a 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 (FIG. 1), sector-shaped, or lobed, although the geographic coverage cell 114 may be configured in nearly any shape or size. The geographic coverage cell 114 represents the geographic area antenna 110 over which the UE 112 is configured to communicate.

[0040] A service provider 116 is a business, vendor, customer, or organization that sells bandwidth or network access to subscribers (using UEs) by providing direct Internet backbone access to Internet service providers and typically access to Network Access Points (NAPs). 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.

[0041] The KPI server 118 produces both predictions and live network data. The live network data (KPIs, UE / cell / MDT (minimization of drive test) traces, and crowdsourced data) enable modeling of network traffic, hotspot identification, and radio 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 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 what wireless network subscribers experience in an area, wireless carriers make changes towards the network that provide better coverage and service to their customers. Drive test typically consists of using a moving vehicle equipped with drive test measurement equipment. The equipment is typically a highly specialized electronic device that interfaces to an original equipment manufacturer's (OEM's) mobile handset (UE). This ensures that the measurements are realistic and comparable to real user experiences.,For 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.

[0042] The UE / cell / MDT traces collected in operations support systems (OSS) or via dedicated tools provide user-level information to the service provider 116. Once geographically located, the UE / cell / MDT traces are used to enhance path-loss calculations and prediction plots, as well as to identify and locate problem areas and traffic hotspots. The KPI server 118 enables the service provider 116 to use the UE / cell / MDT traces with the NSDM 120 for network optimization.

[0043] In some embodiments, the NSDM 120 includes a naming manager (1610 in FIG. 16) configured to automatically generate and implement unique network slice identifiers (UNSIs). In some embodiments, the naming manager 1610 generates a unique nSSAI ID each time an API call is made to the naming manager 1610 from the slice manager 1606 (FIG. 16). In some embodiments, the naming manager 1610 is a template-based rules engine, where the user 1608 (FIG. 16) accesses template rules where input parameters are stored, and the naming manager 1610 generates and maintains a sequence of generated nSSAI IDs or names. In some embodiments, the naming manager 1610 is configured to create rules and generate various nSSAI IDs, application names, or other functions within the scope of the embodiments.

[0044] A rule engine is a software system that executes one or more rules in a runtime production environment. The rules may come from legal regulations, corporate policies, service level agreements (SLAs) with service providers 116, or other sources. A rule system allows corporate policies and other operational decisions to be defined, tested, executed, and maintained separately from application code. A rule engine typically supports rules, facts, priorities (scores), mutual exclusions, preconditions, and other features. The rule engine software is provided as a component of a business rule management system that provides, among other functions, the ability to register, define, categorize, and manage rules, verify the consistency of rule definitions, define relationships between different rules, and associate some of these rules with IT applications that are affected by or need to enforce one or more of the rules.

[0045] The slice manager 1610 interfaces with various functions performed by each layer (e.g., service layer, network function layer, and infrastructure layer) to coherently manage each slice request. The slice manager 1610 enables reconfigurable, efficient, and flexible slice creation. The slice manager 1610 provides end-to-end service management, including mapping of various service instances expressed in terms of SLA requirements with appropriate network functions that can satisfy the service constraints. The slice manager provides slice lifecycle management, such as slice performance monitoring, to dynamically reconfigure each slice to accommodate possible SLA requirement changes.

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

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

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

[0049] In operation 202 of the NSD method 200, the NSDM 120 receives 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 transitions from operation 202 to operation 204.

[0050] At operation 204 of the NSD method 200, the NSDM 120 presents a list of slice templates 402 via a GUI 400. 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 (home automation, high speed rail, etc.), a domain (RAN, TN, CN, or E2E), a vendor, a version, shared (or not shared), a creation date, and a last modification date. The term template refers to a feature of a software application that defines a unique non-executable file format specifically intended for that application. The process transitions from operation 204 to operation 206.

[0051] In operation 206 of NSD method 200, NSDM 120 receives user input via GUI 400 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 "Create New Slice" user-selected button 406 pops up, and the user clicks on user-selected button 406 to begin the process of creating a new slice using the selected slice template. The process transitions from operation 206 to operation 208.

[0052] In operation 208 of the NSD method 200, a GUI 500 is presented through which a user inputs basic slice information. In FIG. 5, the user inputs a slice name in a user input field 502, selects a slice type from a user selection field 504 (e.g., eMBB, URLLC type slice, etc.), selects a domain from a user selection field 506, and selects whether the slice is shared or dedicated from a 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, Transport in user selection field 508C, or a combination of each) and a coverage area for the network slice in user selection field 510. In user selection field 512, a PLMN is selected. In some embodiments, the PLMN selection is based on the coverage area selected in user selection field 510. The process transitions from operation 208 to operation 210.

[0053] In operation 210 of the NSD method 200, a GUI 600 is presented and a user sets network slice parameters. In FIG. 6, in the slice parameters GUI 600, service profile SLA parameters 602 are presented and configured to allow the user to modify the parameters if applicable (e.g., according to the SLA). In a non-limiting example, the user modifies the expected delay time to meet the network slice specifications in the user selection field 604 (e.g., set to 300 ms). Once the user has confirmed all the service profile parameters in the parameter field 602, for the selected domain, the user points and clicks on the "Calculate" user selection button 606. In some embodiments, this process is repeated for each domain. The slice manager (1606 in FIG. 16) 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 transitions from operation 210 to operation 212.

[0054] In operation 212 of the NSD method 200, a GUI 700 is presented, and the user selects a subnet profile, such as a domain-specific network service (shared network service or dedicated network service) that has already been deployed. In FIG. 7, the user navigates to the slice subnet profile GUI 700, where the user selects a network slice subnet name for each domain from user selection fields 708, 710, and 712. The network services associated with the slice subnet are displayed at 702 and 704. In response to a network service not existing or associated with the network slice subnet, the user can further select a network service template by pointing and clicking on the "Select" user selection field 706.

[0055] In FIG. 8, after the user clicks on the "Select" user selection field 706, the GUI 800 is presented and the user is presented with a "Select Network Services" pop-up box 802. As shown in the network services box 804, there are each of the network services such as a user plane function (the UPF (user plane function) is responsible for packet routing and forwarding, packet inspection, quality of service (QoS) handling, and external protocol data unit (PDU) sessions for interconnecting data networks (DNs) in the 5G architecture), a network repository function (the NRF (network repository function) acts as a central service broker for all network functions (NFs) in the 5G core), or a session management function (the SMF (session management function) is responsible for interacting with the separated data plane, creating, updating and deleting PDU sessions, and managing session context with the UPF). In a non-limiting example, the user selects UPF (shown highlighted) and the user is presented with an indication that the UPF network service is shared (e.g., True) in Shared user input field 806. The network service template name is displayed in user input field 808. The user selects a network service from network services list 810. Box 812 displays network features associated with the network service selected by the user from network services list 810.

[0056] Alternatively, in FIG. 9, GUI 900 displays NRF as highlighted in network service box 804, with False being an indication presented in shared user input field 806 indicating that the NRF network service is not shared. A user enters network service information in template 902 for a dedicated network service. A 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), a user is presented with network function box 906. In network function box 906, a user selects a network function (such as UPF App and UPF DB where the user selects a distributed unit type, distributed unit code, and cluster ID).

[0057] 10, the GUI 1000 is presented after each of the domains (RAN, Core, and Transport) includes a network service. Once each domain includes a network service, the user points and clicks on the "Check for Feasibility" user selection field 1002, and the NSDM 120 determines whether the selected network service is ready to provide service to the new network slice.

[0058] 11, GUI 1100 is presented in response to a feasibility test failing for one or more domains (e.g., the RAN domain). The user selects another slice subnet by clicking on the “Network Slice Subnet Name” user-selected field 1102 and rechecks feasibility by clicking on the “Check for Feasibility” user-selected field 1002.

[0059] 12, GUI 1200 is presented if the feasibility testing is successful for each domain. In response to the feasibility testing being successful, the user clicks on a "Next" user-selected button 1202 to deploy the network slice. In some embodiments, if the feasibility testing is not successful, the user is not allowed to proceed with the network slice design. The process transitions from operation 212 to operation 214.

[0060] At operation 214 of method 200, GUI 1300 is presented (FIG. 13) and a user selects SLA parameters (e.g., parameters and KPIs shown in parameters box 1302) to be monitored for a network slice based on one or more SLA agreements. The user searches for a parameter or KPI in a "Search" user input field 1306 for a selected domain shown in user selection field 1310. In some embodiments, the user drags a parameter / KPI from box 1308 and drops it into parameter / KPI box 1302. Further, the slice is expanded and in response to the selection of the parameter / KPI to be monitored (e.g., shown in box 1302), the user selects a policy from a "Policy Name" user selection field 1304 for slice automated healing use-cases. Auto-healing is a feature that automatically detects disabled access points and restores the wireless network. The process transitions from operation 214 to operation 216.

[0061] At operation 216 of method 200, the designed network slice 1402 is displayed on a GUI 1400 (FIG. 14) for review by a user. After previewing the network slice 1402 including the service information 1404 and the automation policies 1406, the user clicks on a "Submit" user selection field 1408 after determining that the information is correct. In response to the "Submit" user selection field 1408 being clicked, a GUI 1500 (FIG. 15) is displayed with a list of network slices 1502. The process transitions from operation 216 to operation 218.

[0062] 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 in GUI 1500. The user clicks on a "Deploy" user-selected button 1506 to deploy the designed slice. In some embodiments, the slice manager (1606 in FIG. 16) makes an API call to an orchestrator (not shown) to deploy the designed slice. The process transitions from operation 218 to operation 220.

[0063] In operation 220 of method 200, the status of the designed slice is updated. As seen in Status box 1508, the status of the network slice is updated from designed to deployed. Other statuses include running, Activation Failed, and Deployment Failed.

[0064] FIG. 16 is a data flow diagram of a method for generating and implementing a unique network slice identifier (UNSI) 1600 according to some embodiments.

[0065] The method for generating and implementing UNSI 1600 includes operations 1652-1668, although the operations are not necessarily performed in the order shown. Operations are added, substituted, reordered, and / or removed as appropriate in accordance with the spirit and scope of the disclosed embodiments. In some embodiments, one or more of the operations of the method for generating and implementing UNSI 1600 are repeated. In some embodiments, the operations of the method for generating and implementing UNSI 1600 are performed in sequence, unless otherwise specified. In some embodiments, the operations of the method for generating and implementing UNSI 1600 are performed by NSDM 120.

[0066] 2-15, in operation 1652 of the method for generating and implementing a UNSI 1600, a user 1608 designs a network slice via a GUI 300-1500. The process transitions from operation 1652 to operation 1654.

[0067] At operation 1654 of the method for generating and implementing a UNSI 1600, the network slice is submitted by a user 1608 to the slice manager 1606, as described at operation 216 of the method for designing a network slice 200. The process transitions from operation 1604 to operation 1608.

[0068] At operation 1656 of the method for generating and implementing a UNSI 1600, in response to the designed network slice being designed and submitted, the slice manager 1606 automatically makes an API call requesting the naming manager 1610 to generate an nSSAI ID. In some embodiments, the naming manager 1610 is configured to take business rules and implement the business rules in the form of a naming template, where the naming manager 1610 is responsible for, in turn, creating the nSSAI ID output. The process transitions from operation 1656 to operation 1658.

[0069] At operation 1658 of the method for generating and implementing UNSI 1600, naming manager 1610 returns the generated nSSAI ID to slice manager 1606. In some embodiments, in response to a new network slice being designed at operation 1652, slice manager 1606 automatically makes an application programming interface (API) call to naming manager 1610 to receive an nSSAI ID of the newly designed network slice. In some embodiments, naming manager 1610 generates a unique nSSAI ID for each API call made from slice manager 1606. In some embodiments, naming manager 1610 is a template-based rule engine. Within a rule template, user 1608 accesses or creates a template rule where user 1608 enters template parameters. Naming manager 1610 is configured to use the rule template to generate an nSSAI ID. In some embodiments, the rule template is a tool associated with the Naming Manager UI, where in response to a user clicking on a "Create Naming Rule Template" user input field via the UI, the user determines the number of bits of the nSSAI ID, the number of bits entered by the user, and the remaining bits entered by the Naming Manager to maintain a numbering sequence starting at 0 and incrementing in positive integers.

[0070] It is believed that a more detailed discussion of the naming manager in this invention may overlap with the invention of the naming manager itself.

[0071] Additionally, the naming manager 1610 is configured to maintain a sequence of generated nSSAI IDs or names. In some embodiments, the naming manager 1610 is configured to create rule templates that are used to create various nSSAI IDs, application names, or other functionality within the scope of the present embodiments. The process transitions from operation 1658 to operation 1660.

[0072] At operation 1660 of the method for generating and implementing UNSI 1600, slice manager 1606 stores the NSSAI ID in inventory 1612. Inventory 1612 tracks nSSAI IDs that are distributed to network slices. As described in FIG. 17, the assigned nSSAI IDs describe the general configuration settings of each network slice. The process transitions from operation 1660 to operation 1662.

[0073] At operation 1662 of the method for generating and implementing UNSI 1600, slice manager 1606 displays the new nSSAI on a UI, such as UI 1822 (FIG. 18), to user 1608. The process optionally transitions from operation 1662 to operation 1664.

[0074] At operation 1664 of the method for generating and implementing UNSI 1600, the slice manager receives a request from the user 1608 to deactivate a network slice. The process transitions from operation 1664 to operation 1666. In non-limiting examples, a user may deactivate a slice in response to a customer not wanting a slice, deactivating a current slice, in response to a customer attempting to order a new slice of new capacity, or in response to a slice causing problems in the network.

[0075] In an operation 1666 of the method for generating and implementing a UNSI 1600, the slice manager requests to deactivate the network slice from the inventory 1612. The process transitions from operation 1666 to operation 1668.

[0076] In operation 1666 of the method for generating and implementing UNSI 1600, slice manager 1606 makes an API call to naming manager 1610 to request that the nSSAI ID be revoked from naming manager 1610 so that the deactivated nSSAI ID can be reused for a new slice. If a network slice is deactivated or terminated, slice manager 1606 makes another API call to naming manager 1610 to request that the nSSAI ID be revoked from naming manager 1610 so that the terminated or deactivated nSSAI ID can be reused for another slice.

[0077] FIG. 17 is an example nSSAI ID rule 1700 according to some embodiments.

[0078] The S-NSSAI ID 1702 is used to uniquely identify a network slice. In the example of FIG. 17, it is an ultra reliable low latency communications (URLCC) service type with rural macro network services (e.g., base stations such as base station 108 in rural areas). The S-NSSAI ID 1702 includes two components: SST (slice / service type) 1704 and an optional SD (slice differentiator) 1706. In the context of network slicing, the SST 1704 is the expected behavior of the network slice with respect to specific functions and services. Standardized SST values ​​include eMBB (enhanced mobile broadband, focusing on high speed end-user data and system capacity), URLLC (ultra-reliable low latency communication, a subset of 5G network architecture that ensures efficient scheduling of data transfers, achieving shorter transmissions over larger subcarriers, and even scheduling overlapping transmissions), and MIoT (massive IoT, a category driven by scale, not speed, where deployments include hundreds to billions of connected devices, where the goal of these applications is to efficiently transmit and consume small amounts of data from a vast number of devices). In network slicing, SD1706 is related to SST1716 and is used as an additional differentiator when multiple network slices carry the same SST value. SD1706 is intended for the implementation of network slicing.

[0079] The nSSAI ID typically has a total length of nine characters, where the first three characters are SST 1704 and the remaining six characters are SD 1706. In some embodiments, the Naming Manager 1610 is configured to take business rules and implement the business rules in the form of a naming template, where the Naming Manager 1610 is responsible for sequentially creating the nSSAI ID output. In a non-limiting example, in response to a first slice containing the nSSAI ID as 00001, in a second slice the nSSAI ID will be 00002, and in a third slice the nSSAI ID will be 00003.

[0080] In some embodiments, eMBB includes an SST of 000, URLLC includes an SST of 001, and MIoT includes an SST of 002. In the example nSSAI ID 1702, the SST is shown as URLLC. Thus, the example nSSAI ID is designed to efficiently schedule data transfers, achieve shorter transmissions over larger subcarriers, and schedule overlapping transmissions. A Service Builder list 1708 presents several options for URLLC, such as Urban Macro services, Rural Macro services, Indoor Hotspot services, Broadband Access in a Crowd services, Dense Urban services, Broadcast-like Services, High-speed Train services, High-speed Vehicle services, and Airplanes Connectivity services.

[0081] From the example nSSAI ID 1702, the first two digits (e.g., sd1 and sd2) of the SD 1706 indicate that the SD of the nSSAI ID 1702 is set to Rural Macro Service. The remaining SD digits (e.g., sd3, sd4, sd5, and sd6) are configured to be used to specify network capabilities. In this example, there are 0001-FFFE (65,535) possible network capabilities for each service in the service builder 1708.

[0082] 18 is a block diagram of a network slice design (NSD) processing circuit 1800 according to some embodiments. In some embodiments, the NSD processing circuit 1800 is a general-purpose computing device including a hardware processor 1802 and a non-transitory computer-readable storage medium 1804. The storage medium 1804 is encoded with (i.e., stores) computer program code 1806, i.e., a set of executable instructions such as algorithms or methods 200 and 1600, among others. The execution of the instructions 1806 by the hardware processor 1802 represents (at least in part) a network slice design application that implements some or all of the methods described herein (hereinafter referred to as the processes and / or methods) according to one or more embodiments.

[0083] The processor 1802 is electrically coupled to the computer readable storage medium 1804 via a bus 1808. The processor 1802 is further electrically coupled to an I / O interface 1810 by the bus 1808. A network interface 1812 is further electrically connected to the processor 1802 via the bus 1808. The network interface 1812 is connected to a network 1814 such that the processor 1802 and the computer readable storage medium 1804 connect to external elements via the network 1814. The processor 1802 is configured to execute computer program code 1806 encoded in the computer readable storage medium 1804 to enable the NSD processing circuit 1800 to perform some or all of the processes and / or methods described above. In one or more embodiments, the processor 1802 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application specific integrated circuit (ASIC), and / or other suitable processing unit.

[0084] In one or more embodiments, computer readable storage medium 1804 is an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, computer readable storage medium 1804 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 1804 includes a compact disk read only memory (CD-ROM), a compact disk read / write (CD-R / W), and / or a digital video disk (DVD).

[0085] In one or more embodiments, the storage medium 1804 stores computer program code 1806 configured to enable the NSD processing circuit 1800 to perform some or all of the processes and / or methods described above. In one or more embodiments, the storage medium 1804 further stores information such as algorithms that facilitate the execution of some or all of the processes and / or methods described above.

[0086] The NSD processing circuit 1800 includes an I / O interface 1810. The I / O interface 1810 is connected to external circuitry. In one or more embodiments, the I / O interface 1810 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 1802.

[0087] The NSD processing circuit 1800 further includes a network interface 1812 coupled to the processor 1802. The network interface 1812 enables the NSD processing circuit 1800 to communicate with a network 1814 to which one or more other computer systems are connected. The network interface 1812 includes a wireless network interface, such as BLUETOOTH, WIFI, WIMAX, GPRS, or WCDMA, or a wired network interface, such as ETHERNET, USB, or IEEE-864. In one or more embodiments, some or all of the above processes and / or methods are implemented in two or more processors 1802.

[0088] The NSD processing circuit 1800 is configured to receive information via an I / O interface 1810. The information received via the I / O interface 1810 includes one or more of instructions, data, rules, and / or other parameters for processing by the processor 1802. The information is transferred to the processor 1802 via the bus 1808. The NSD processing circuit 1800 is configured to receive information related to a UI 1822 via the I / O interface 1810. The information is stored in the computer-readable medium 1804 as a user interface (UI) 1822.

[0089] In some embodiments, some or all of the above 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 above 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 above processes and / or methods are implemented as a plug-in to a software application.

[0090] In some embodiments, the method includes creating a network slice by the processor and based on a network slice design submitted by a user, and automatically generating, by the processor, a network slice selection assistance information ID (nSSAI ID) for the network slice.

[0091] In some embodiments, prior to the step of creating the network slice, the method further includes receiving a network slice design submitted from a user.

[0092] In some embodiments, the method further comprises storing, by the processor, the nSSAI ID.

[0093] In some embodiments, the method further includes displaying, by the processor, the nSSAI ID on a graphical user interface (GUI) included in a user interface (UI).

[0094] In some embodiments, the method further includes receiving, by the processor, a request to deactivate the network slice.

[0095] In some embodiments, the method further includes obtaining, by the processor, the network slice from storage.

[0096] In some embodiments, the method further includes deactivating, by the processor, the network slice.

[0097] In some embodiments, the method further includes reusing, by the processor, the network slice as another network slice.

[0098] In some embodiments, an apparatus includes a processor and a memory having instructions stored thereon that, when executed by the processor, cause the processor to create a network slice based on a network slice design submitted by a user and automatically generate a network slice selection assistance information ID (nSSAI ID) for the network slice based on the network slice design.

[0099] In some embodiments, prior to creating the network slice, the instructions further cause the processor to receive a network slice design submitted by a user.

[0100] In some embodiments, the instructions further cause the processor to store the nSSAI ID.

[0101] In some embodiments, the instructions further cause the processor to display the nSSAI ID on a graphical user interface (GUI) included in a user interface (UI).

[0102] In some embodiments, the instructions further cause the processor to receive a request to deactivate the network slice.

[0103] In some embodiments, the instructions further cause the processor to obtain the network slice from a storage device.

[0104] In some embodiments, the instructions further cause the processor to deactivate the network slice.

[0105] In some embodiments, the instructions further cause the processor to reuse the network slice as another network slice.

[0106] In some embodiments, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to create a network slice based on a network slice design submitted by a user and automatically generate a network slice selection assistance information ID (nSSAI ID) for the network slice based on the network slice design.

[0107] In some embodiments, prior to creating the network slice, the instructions further cause the processor to receive a network slice design submitted by a user.

[0108] In some embodiments, the instructions further cause the processor to store the nSSAI ID.

[0109] In some embodiments, the instructions further cause the processor to display the nSSAI ID on a graphical user interface (GUI) included in a user interface (UI).

[0110] The above description outlines features of some embodiments so that those skilled in the art may better understand the aspects of the present disclosure. Those skilled in the art will appreciate that they may readily use this disclosure as a basis for designing or modifying other processes and structures for carrying out the same purposes and / or achieving the same advantages as the embodiments described herein. Those skilled in the art should further appreciate that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and improvements may be made herein without departing from the spirit and scope of the present disclosure.

Claims

1. creating a network slice by a processor and based on a network slice design submitted by a user; Automatically generating, by the processor, a network slice selection assistance information ID (nSSAI ID) for the network slice; The method includes:

2. 2. The method of claim 1, prior to creating the network slice, the method further comprising receiving the network slice design submitted from a user.

3. The method of claim 1 , further comprising storing, by the processor, the nSSAI ID.

4. The method of claim 1 , further comprising displaying, by the processor, the nSSAI ID in a graphical user interface (GUI) included in a user interface (UI).

5. 10. The method of claim 1, further comprising receiving, by the processor, a request to deactivate the network slice.

6. The method of claim 5 , further comprising obtaining, by the processor, the network slice from a storage device.

7. The method of claim 6 , further comprising deactivating, by the processor, the network slice.

8. The method of claim 7 , further comprising reusing, by the processor, the network slice as another network slice.

9. A processor; a memory having instructions stored thereon, The instructions, when executed by the processor, cause the processor to: Creating a network slice based on a network slice design submitted by a user; An apparatus for automatically generating a network slice selection assistance information ID (nSSAI ID) of the network slice based on the network slice design.

10. 10. The apparatus of claim 9, prior to creating the network slice, the instructions further cause the processor to receive the network slice design submitted by a user.

11. 10. The apparatus of claim 9, wherein the instructions further cause the processor to store the nSSAI ID.

12. 10. The apparatus of claim 9, wherein the instructions further cause the processor to display the nSSAI ID in a graphical user interface (GUI) included in a user interface (UI).

13. 10. The apparatus of claim 9, wherein the instructions further cause the processor to receive a request to deactivate the network slice.

14. The apparatus of claim 13 , wherein the instructions further cause the processor to obtain the network slice from a storage device.

15. 15. The apparatus of claim 14, wherein the instructions further cause the processor to deactivate the network slice.

16. The apparatus of claim 15 , wherein the instructions further cause the processor to reuse the network slice as another network slice.

17. A non-transitory computer readable medium having instructions stored thereon, comprising: The instructions, when executed by a processor, cause the processor to: Creating a network slice based on a network slice design submitted by a user; Automatically generating a network slice selection support information ID (nSSAI ID) of the network slice based on the network slice design; Non-transitory computer-readable medium.

18. 20. The non-transitory computer-readable medium of claim 17, prior to creating the network slice, the instructions further cause the processor to receive the network slice design submitted by a user.

19. 20. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the processor to store the nSSAI ID.

20. 20. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the processor to display the nSSAI ID in a graphical user interface (GUI) included in a user interface (UI).

Images