System and method 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] This description relates to a system for the automatic generation and implementation of network slice identifiers and methods of using the same.

Background Art

[0002] A cellular network is a telecommunications system for mobile devices (e.g., mobile phone devices) that communicate via radio waves through one or more local antennas of a cellular base station (e.g., a cell tower). The coverage area in which services are provided is divided into small geographical areas called cells. Each cell is served by an individual low-power multi-channel transceiver and antenna at the cell tower. Mobile devices within a cell communicate via the cell's antenna using a plurality of frequency channels and individual 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 part of a telecommunications system and implements radio access technology. The RAN exists between devices such as mobile phones, computers, or remote control machines and provides a connection to a core network (CN). Depending on the standard, mobile phones and other wireless connection 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 the steps of: creating a network slice by a processor and based on a network slice design submitted by a user; and automatically generating a network slice selection assistance information ID (nSSAI ID) for the network slice by the processor.

[0005] In some embodiments, the device includes a processor and a memory in which instructions are stored. When an instruction is executed by the processor, the processor causes the processor to create a network slice based on a network slice design submitted by a user, and to automatically generate a network slice selection support 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, which, when executed by a processor, cause the processor to create network slices based on a network slice design submitted by a user, and to automatically generate network slice selection support information IDs (nSSAI IDs) for the network slices based on the network slice design.

[0007] The aspects of this disclosure will be understood from the following detailed description by reading with reference to the accompanying drawings. In accordance with the standard practice of the art (industry), various features are not drawn to scale. In some embodiments, the dimensions of various features are arbitrarily increased or decreased for clarity in the description. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a schematic diagram of a system for network slice design (NSD) according to several embodiments.

[0009] [Figure 2] Figure 2 is a flowchart illustrating a method for designing network slices according to several embodiments.

[0010] [Figure 3] Figure 3 shows a graphical user interface (GUI) for designing network slices in several embodiments. [Figure 4] Figure 4 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 5] Figure 5 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 6] Figure 6 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 7] Figure 7 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 8] Figure 8 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 9] Figure 9 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 10] Figure 10 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 11] Figure 11 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 12]Figure 12 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 13] Figure 13 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 14] Figure 14 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments. [Figure 15] Figure 15 shows another diagram of a graphical user interface (GUI) for designing network slices, according to several embodiments.

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

[0012] [Figure 17] Figure 17 shows exemplary nSSAI ID rules according to several embodiments.

[0013] [Figure 18] Figure 18 is a high-level functional block diagram of a processor-based system according to several embodiments. [Modes for carrying out the invention]

[0014] The following disclosure provides many different embodiments or examples for implementing the specific features of the above-described subject matter (technology, overview). In the following, for the purpose of simplifying the present disclosure, examples of components, values, operations, materials, arrangements, etc. are described. Of course, these are examples and are not intended to be limiting. It is possible to use other components, values, operations, materials, arrangements, etc., which fall within the scope of the present invention. For example, in the following description, when forming the first feature portion above or on top of the second feature portion, embodiments in which the first feature portion and the second feature portion are formed in direct contact are included, and further embodiments in which an additional feature portion is formed between the first feature portion and the second feature portion so that the first feature portion and the second feature portion cannot be in direct contact are included. In addition, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for the purpose of brevity and clarity and does not define the relationship between the various embodiments and / or configurations being described.

[0015] Furthermore, spatially relative terms such as "below", "beneath", "lower", "above", "upper", etc. are used herein for ease of explanation to describe the relationship of one element or feature to another as illustrated in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation shown in the figures. The device may be oriented in other directions (rotated 90 degrees or other orientations), and the spatially relative descriptors (expressions, symbols) used herein are to be interpreted accordingly.

[0016] In some embodiments, the automatic generation and implementation of a unique network slice identifier (UNSI) are described in the present disclosure. In some embodiments, a slice identifier is automatically generated, thereby providing ease of network slice management, slice identifier process efficiency, efficient deployment of network slices, and reduction of human errors introduced (occurring) by manual generation of network slice identifiers.

[0017] In other approaches, unique network slice identifiers are generated manually. Manually created unique slice identifiers are labor-intensive.

[0018] Network slicing is a way to create 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 can manually create network slices that support specific applications, services, a set of users, or the network. Network slices can also be configured to span multiple network domains such as an access network (a user network such as a RAN that connects subscribers to a service provider and to other networks such as the Internet via a transport network), a CN (the core network is a central conduit designed to transfer network traffic at high speed), and a transport network (a public telecommunications infrastructure that enables telecommunications between defined network endpoints).

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

[0020] The Single Network Slice Selection Assistance Information (S-NSSAI) identifier (ID) is used to uniquely identify a network slice. The S-NSSAI ID consists of two components: the SST (Slice / Service Type) and, optionally, the SD (Slice Differentiator). In relation to network slicing, the SST is the expected behavior of the network slice with respect to specific functions and services. Standardized SST values ​​include eMBB (enhanced mobile broadband: advanced mobile broadband focused on high-speed end-user data and system capacity), URLLC (ultra-reliable low latency communications: ultra-reliable low latency communications is a subset of 5G network architectures that efficiently schedules data transfers, achieves shorter transmissions over larger subcarriers, and even ensures the scheduling of redundant transmissions), and MIoT (massive internet of things: massive IoT is a category driven by scale rather than speed, where deployments involve tens to billions of connected devices, when the goal of these applications is to efficiently send 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 slices.

[0021] The nSSAI ID typically has a total length of 9 characters, in which case the first 3 characters are SST and the remaining 6 characters are SD. In some embodiments, the naming manager is configured to take business rules and implement them in the form of naming templates, in which case the naming manager is responsible for sequentially creating the nSSAI ID output. In some embodiments, the naming manager is a tool, and the naming templates are created by the user based on business rules. In response to the user calling the naming template using an API, the naming manager provides the user with the necessary inputs for the template, and then the naming manager 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 the nSSAI ID of the newly designed network slice.

[0023] If a network slice is deactivated or terminated, the slice manager makes another API call to the naming manager to request that the nSSAI ID be revoked, 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, the user accesses or creates template rules in which the user enters template parameters. The naming manager is configured to use the rule template to generate nSSAI IDs. Furthermore, 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 this embodiment.

[0025] Network slices are divided into network service (NS) subnets, each dedicated to a domain (e.g., RAN, CN, transport domain, or E2E including each). A transport domain refers to telecommunication transmission facilities, under which voice, data, and video communications are distributed (distributed) between geographically separated locations for shared use.

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

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

[0028] Within the NRF network service are network functions such as MongoDB (an open-source NoSQL database management program), NRF (which provides a single record of network functions available on each public land mobile network (PLMN) along with profiles 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). Furthermore, within the AMF network service are network functions such as Nginx (open-source web server software that runs reverse proxy, load balancing, email proxy, and HTTP cache services), AMF applications, and databases (DBs).

[0029] Transport network services include network functions such as software (SW), SDN (software-defined networking: a network management approach that improves network performance and monitoring by enabling dynamic and programmatically efficient network configurations, similar to cloud computing, rather than traditional network management), and routers (networking devices that transfer data packets between computer networks).

[0030] Figure 1 is a schematic diagram of System 100 for network slice design (NSD) according to several embodiments.

[0031] The NSD system 100 includes a CN 102 that is communicatively connected to the RAN 104 via a transport network 106 that is 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 cell 114). The CN 102 includes one or more service providers 116, a KPI server 118, and a network slice module (NSDM) 120.

[0032] A CN102 (more commonly known as a backbone) is a domain that is part of a computer network interconnecting networks, providing a path for exchanging information between different local area networks (LANs) or subnetworks. In some embodiments, a CN102 connects diverse networks across a wide geographical area, within different buildings in a campus environment, or within the same building.

[0033] In some embodiments, RAN104 is an access network domain. In some embodiments, RAN104 is a Global System for Mobile Communications (GSM) RAN, GSM / EDGE RAN, Universal Mobile Telecommunications System (UMTS) RAN (UTRAN), Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Open RAN (O-RAN), or Cloud RAN (C-RAN). RAN104 resides between UE112 (e.g., a mobile phone, computer, or any remotely controlled machine) and CN102. In some embodiments, RAN104 is C-RAN for the purposes of simplified representation and discussion. In some embodiments, baseband units (BBUs) replace C-RAN.

[0034] In traditional distributed cellular networks, the equipment located at the bottom and top of base stations in cell sites is the BBU (Band Unit). The BBU is a radio unit that links the UE (User Environment) to the CN (Network Center) and processes billions of bits of information per hour. Traditionally, BBUs were located in enclosures or shelters at the bottom of base stations. In contrast, C-RAN (Cellular-Range Network) utilizes the large signal transmission capacity of optical fiber to concentrate a large number of BBUs in dedicated pool locations or base stations. This reduces the number of devices at base stations and offers many other advantages, such as lower latency.

[0035] In a hierarchical telecommunications network, the transport network 106 of the NSD system 100 includes an intermediate link between CN 102 and 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 communications, and point-to-multipoint wireless technologies, are being phased out as capacity and latency requirements increase in 4G and 5G networks. Backhaul refers to the network side that communicates with the internet. The connection between base station 108 and UE 112 begins with the transport network 106 connected to CN 102. In some embodiments, the transport network 106 includes wired, fiber optic, and wireless components. The wireless section includes edge network topologies, mesh, and microwave bandwidths that use high-capacity wireless channels to acquire packets to microwave or fiber links.

[0036] In some embodiments, base station 108 is a grid-like or freestanding tower, guyed tower, monopole tower, and concealed towers (e.g., towers designed to resemble trees, cacti, water towers, signs, optical standards, and other types of structures). In some embodiments, base station 108 is a cellular-enabled mobile device site where antennas and electronic communication equipment are typically placed on a radio mast, tower, or other raised structure to make up a cell (or multiple adjacent cells) in the network. The raised structure typically supports antennas 110, as well as one or more sets of transmitters / receivers (transceivers), digital signal processors, control electronics, remote radio heads (RRHs), primary and backup power supplies, and sheltering. Base stations are also known by other names such as transceiver base stations, cell phone masts, or cell towers. In some embodiments, base stations are replaced by or assisted by other edge devices configured to communicate wirelessly with the UE. Edge devices provide entry points to service provider CNs such as CN102. 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, antenna 110 is a sector antenna. In some embodiments, antenna 110 is a type of directional microwave antenna having a sector-shaped radiation pattern. In some embodiments, the angle of the sector arc is designed to be 60°, 90°, or 120°, with a few extra degrees to ensure overlap. Furthermore, sector antennas are mounted in multiples when wider coverage or omnidirectional coverage is desired. In some embodiments, antenna 110 is a rectangular antenna, sometimes called a panel antenna or radio antenna, used to transmit and receive waves or data between a mobile device or other device and a base station. In some embodiments, antenna 110 is a circular antenna. In some embodiments, antenna 110 operates at microwave or ultra-high frequency (UHF) frequencies (300 MHz to 3 GHz). In other examples, antenna 110 is selected according to their size and directional characteristics. In some embodiments, the antenna 110 is a MIMO (multiple-input, multiple-output) antenna that transmits and receives multiple data signals simultaneously over the same radio channel by utilizing multipath propagation.

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

[0039] In some embodiments, the geographic coverage cell 114 includes shape and size. In some embodiments, the geographic coverage cell 114 is a macrocell (covering 1 km to 30 km), a microcell (covering 200 m to 2 km), or a picocell (covering 4 m to 200 m). In some embodiments, the geographic coverage cell is circular, elliptical (Figure 1), sector-shaped, or lobe-shaped, but the geographic coverage cell 114 can be substantially any shape or size. The geographic coverage cell 114 represents the geographic area antenna 110, and the UE 112 is configured to communicate.

[0040] A service provider is a company, vendor, customer, or organization that sells bandwidth or network access to subscribers (using a UE) by providing direct internet backbone access to an Internet service provider and, typically, access to a network access point (NAP). Service providers are sometimes also called backbone providers, internet providers, or vendors. Service providers include telecommunications companies, data carriers, wireless communications providers, internet service providers, and cable television operators that provide high-speed internet access.

[0041] The KPI server 118 generates both predictions and live network data. Live network data (KPIs, UE / cell / MDT (Minimized Drive Test) traces, and crowdsourced data) enables modeling of network traffic, hotspot identification, and radio signal propagation. RF drive testing is a method for measuring and evaluating the coverage, capacity, and quality of service (QoS) of mobile radio networks such as RAN104. This technique consists of using a vehicle equipped with mobile radio network air interface (RF) 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 (events) within an area, wireless carriers make changes to their networks to provide better coverage and service to customers. Drive testing generally consists of using a mobile vehicle equipped with drive testing measurement equipment. The equipment is a highly specialized electronic device that typically interfaces with a mobile handset (UE) from an original equipment manufacturer (OEM). This ensures that the measurements are realistic and reflect the actual user experience. In the case of mobile networks, crowdsourcing methodologies leverage a crowd of participants (e.g., mobile subscribers) to collect network measurements manually or automatically via mobile apps, or directly from the network using call traces.

[0042] UE / cell / MDT traces collected in operations support systems (OSS) or via dedicated tools provide user-level information to service provider 116. Geographically, 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 service provider 116 to use UE / cell / MDT traces together with NSDM 120 for network optimization.

[0043] In some embodiments, NSDM120 includes a naming manager (referenced 1610 in Figure 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 (Figure 16). In some embodiments, the naming manager 1610 is a template-based rule engine, where a user 1608 (Figure 16) accesses template rules that store input parameters, 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 embodiment.

[0044] A rule engine is a software system that executes one or more rules in a runtime production environment. Rules can originate from legal regulations, corporate policies, service level agreements (SLAs) with service providers, or other sources. A rule system allows for the definition, testing, execution, and maintenance of corporate policies and other operational decisions independently of application code. Rule engines typically support rules, facts, priorities (scores), mutual exclusion, prerequisites, and other functionalities. Rule engine software is provided as a component of a business rule management system, which, among other functions, provides the ability to register, define, classify, 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 implement one or more of those 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 represented in relation to SLA requirements, using appropriate network functions that can satisfy service constraints. The slice manager provides slice lifecycle management, such as slice performance monitoring, to dynamically reconfigure each slice to accommodate possible changes in SLA requirements.

[0046] Figure 2 is a flowchart illustrating a method for designing a network slice 200 according to one embodiment.

[0047] Figures 3 to 15 show graphical user interfaces (GUIs) 300 to 1500 for designing network slices, according to several 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 specific order, each operation of the NSD method 200 is configured to be executed in any order unless otherwise specified. The NSD method 200 is performed as a set of operations, such as operations 202 to 220. Furthermore, the NSD method 200 is described with reference to Figures 3 to 15 to aid in understanding the NSD method 200.

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

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

[0051] In operation 206 of the NSD method 200, the NSDM 120 receives user input via the GUI 400 indicating the selection of a slice template. In Figure 4, the user points to a slice template, for example, slice template 404, and then clicks on that slice template. A "Create New Slice" user selection button 406 pops up, and the user clicks the user selection button 406 to begin the process of creating a new slice using the selected slice template. The process then moves from operation 206 to operation 208.

[0052] In operation 208 of the NSD method 200, the GUI 500 is presented, and the user inputs basic slice information via the GUI 500. In Figure 5, the user enters the slice name in the user input field 502, selects the slice type from the user selection field 504 (e.g., eMBB, URLLC type slices), selects the domain from the user selection field 506, and selects whether the slice is shared or dedicated from the 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 thereof) and the network slice coverage area in user selection field 510. In user selection field 512, PLMN is selected. In some embodiments, the PLMN selection is based on the coverage area selected in user selection field 510. The process then moves from operation 208 to operation 210.

[0053] In operation 210 of the NSD method 200, the GUI 600 is presented, and the user configures the network slice parameters. In Figure 6, the slice parameter GUI 600 presents the service profile SLA parameters 602, which are 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 in the user selection field 604 (e.g., set to 300ms) to conform to the network slice specifications. Once the user has reviewed all the service profile parameters in the parameter field 602, for the selected domain, the user points to and clicks the "Calculate" user selection button 606. In some embodiments, this process is repeated for each domain. The slice manager (referenced 1606 in Figure 16) calculates the slice profile parameters (shown in the slice profile box 608) for each domain (RAN, CORE, and transport) to satisfy the service profile SLA. The process then moves from operation 210 to operation 212.

[0054] In operation 212 of NSD method 200, the 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 Figure 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 labels 702 and 704. In response to the network service not existing in or being associated with the network slice subnet, the user can further select a network service template by pointing to and clicking the "Select" user selection field 706.

[0055] In Figure 8, after the user clicks the "Select" user selection field 706, the GUI 800 is presented, and the user is presented with the "Select Network Services" pop-up box 802. As shown in the network services box 804, each of the network services is a user plane function (UPF, which 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 (NRF, which acts as a central service broker for all network functions (NFs) within the 5G core), or a session management function (SMF, which interacts with isolated data planes, creates, updates, and deletes PDU sessions, and manages the session context with the UPF). In a non-specific example, the user selects UPF (highlighted), and the user is presented with an indication (e.g., True) in the Shared user input field 806 that the UPF network service is shared. The network service template name is displayed in user input field 808. The user selects a network service from the network service list 810. Box 812 displays the network functions associated with the network service selected by the user from the network service list 810.

[0056] Alternatively, in Figure 9, GUI 900 displays NRF as highlighted in Network Services Box 804, while False is a display presented in Shared User Input Field 806 indicating that the NRF network service is not shared. The user enters network service information in Template 902 for dedicated network services. The user selects a network service template in the "NS Template" user selection field 904. In response to the selection of a network service template (e.g., UPF NST Sample 2), the user is presented with Network Functions Box 906. In Network Functions Box 906, the user selects network functions (such as UPF App and UPF DB, for which the user selects the distributed unit type, distributed unit code, and cluster ID).

[0057] In Figure 10, the GUI 1000 is presented after each domain (RAN, core, and transport) has included network services. Once each domain has included network services, the user points to and clicks the "Check for Feasibility" user selection field 1002, and the NSDM 120 determines whether the selected network services are ready to serve the new network slice.

[0058] In Figure 11, GUI 1100 is presented in response to a failure in the feasibility test for one or more domains (e.g., a RAN domain). The user selects another slice subnet by clicking the "Network Slice Subnet Name" user selection field 1102 and then rechecks the feasibility by clicking the "Check for Feasibility" user selection field 1002.

[0059] In Figure 12, GUI 1200 is presented if the feasibility test is successful for each domain. In response to the success of the feasibility test, the user clicks the "Next" user selection button 1202 to expand the network slice. In some embodiments, if the feasibility test is unsuccessful, the user cannot proceed with the network slice design. The process then moves from operation 212 to operation 214.

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

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

[0062] In operation 218 of method 200, the user deploys a designed network slice by clicking the desired network slice in the list of network slices 1502, which displays a popup box 1504 of GUI 1500. The user clicks the "Deploy" user selection button 1506 to deploy the designed slice. In some embodiments, the slice manager (reference numeral 1606 in Figure 16) makes an API call to an orchestrator (not shown) and the designed slice is deployed. The process then moves from operation 218 to operation 220.

[0063] In operation 220 of method 200, the status of the designed slice is updated. As seen in the 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] Figure 16 is a data flow diagram of a method for generating and implementing a unique network slice identifier (UNSI) 1600 according to several embodiments.

[0065] The method for generating and implementing UNSI1600 includes operations 1652–1668, but the operations are not necessarily performed in the order shown. The operations may be added, replaced, reordered, and / or deleted as appropriate in accordance with the spirit and scope of the disclosed embodiments. In some embodiments, one or more operations of the method for generating and implementing UNSI1600 are repeated. In some embodiments, the operations of the method for generating and implementing UNSI1600 are performed sequentially unless otherwise specified. In some embodiments, the operations of the method for generating and implementing UNSI1600 are performed by NSDM120.

[0066] As illustrated in Figures 2 to 15, in operation 1652 of the method for generating and implementing UNSI1600, user 1608 designs network slices via GUIs 300 to 1500. The process then transitions from operation 1652 to operation 1654.

[0067] In operation 1654 of the method for generating and implementing UNSI1600, the network slice is submitted to the slice manager 1606 by user 1608, as described in operation 216 of the method for designing network slice 200. The process then transitions from operation 1604 to operation 1608.

[0068] In operation 1656 of the method for generating and implementing UNSI1600, 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 a business rule and implement the business rule in the form of a naming template, in which case the naming manager 1610 is responsible for sequentially creating the nSSAI ID output. The process then moves from operation 1656 to operation 1658.

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

[0070] If we discuss the naming manager in more detail in this invention, we believe there is a possibility of overlap with the invention of the naming manager itself.

[0071] Furthermore, the naming manager 1610 is configured to maintain the sequence of generated nSSAI IDs or names. In some embodiments, the naming manager 1610 is configured to create rule templates and use them to create various nSSAI IDs, application names, or other functions within the scope of this embodiment. The process then moves from operation 1658 to operation 1660.

[0072] In operation 1660 of the method for generating and implementing UNSI1600, the slice manager 1606 stores the nSSAI IDs in inventory 1612. Inventory 1612 tracks the nSSAI IDs distributed to network slices. As illustrated in Figure 17, the assigned nSSAI IDs describe the general configuration settings for each network slice. The process then moves from operation 1660 to operation 1662.

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

[0074] In operation 1664 of the method for generating and implementing UNSI1600, the slice manager receives a request from user 1608 to deactivate a network slice. The process transitions from operation 1664 to operation 1666. In a non-limiting example, a user may deactivate a slice in response to an unwanted slice from the customer, 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 operation 1666 of the method for generating and implementing UNSI1600, the slice manager requests that the network slice be deactivated from inventory 1612. The process then proceeds from operation 1666 to operation 1668.

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

[0077] Figure 17 shows exemplary nSSAI ID rule 1700 in several embodiments.

[0078] The S-NSSAI ID 1702 is used to uniquely identify a network slice. In the example in Figure 17, it is an ultra-reliable low-latency communications (URLCC) service type with a rural macro network service (e.g., base stations such as base station 108 in a rural area). The S-NSSAI ID 1702 includes two components: the SST (Slice / Service Type) 1704 and the optional SD (Slice Differentiating Factor) 1706. In relation to network slicing, the SST 1704 is the expected behavior of the network slice with respect to a particular function and service. Standardized SST values ​​include eMBB (enhanced mobile broadband: advanced mobile broadband focused on high-speed end-user data and system capacity), URLLC (ultra-high reliability low latency communication, a subset of 5G network architectures that efficiently schedules data transfers, achieves shorter transmissions over larger subcarriers, and even ensures the scheduling of overlapping transmissions), and MIoT (Mega-IoT, a category driven by scale rather than speed, where deployments involve tens to billions of connected devices, when the goal of these applications is to efficiently send 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 9 characters, in which case the first 3 characters are SST1704 and the remaining 6 characters are SD1706. In some embodiments, the naming manager 1610 is configured to take a business rule and implement the business rule in the form of a naming template, in which case 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, the nSSAI ID in the second slice becomes 00002, and in the third slice, the nSSAI ID becomes 00003.

[0080] In some embodiments, eMBB includes SST 000, URLLC includes SST 001, and MIoT includes SST 002. In the example nSSAI ID 1702, the SST is shown as URLLC. Thus, the exemplary nSSAI ID is designed to efficiently schedule data transfers, achieve shorter transmissions over larger subcarriers, and schedule duplicate transmissions. Service Builder List 1708 presents several options for URLLC, including 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 of SD 1706 (e.g., sd1 and sd2) indicate that the SD of nSSAI ID 1702 is set to a 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, for each service in service builder 1708, there are 0001-FFFE (65,535) possible network capabilities.

[0082] Figure 18 is a block diagram of a network slice design (NSD) processing circuit 1800 according to several embodiments. In some embodiments, the NSD processing circuit 1800 is a general-purpose computing device including a hardware processor 1802 and a non-temporary computer-readable storage medium 1804. The storage medium 1804 stores, among other things, computer program code 1806, i.e., a set of executable instructions such as algorithms, or encoded in methods 200 and 1600 (i.e., storing computer program code 1806). The execution of 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 above 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 the bus 1808. The processor 1802 is further electrically coupled to the I / O interface 1810 via the bus 1808. The network interface 1812 is further electrically connected to the processor 1802 via the bus 1808. The network interface 1812 is connected to the network 1814 so 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 in order to make the NSD processing circuit 1800 available to perform some or all of the above processes and / or methods. 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 a suitable processing unit.

[0084] In one or more embodiments, the computer-readable storage medium 1804 is an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, the computer-readable storage medium 1804 includes semiconductor or solid-state memory, magnetic tape, removable computer diskette, random access memory (RAM), read-only memory (ROM), rigid magnetic disk, and / or optical disk. In one or more embodiments using an optical disk, the computer-readable storage medium 1804 includes compact disc read-only memory (CD-ROM), compact disc read / write (CD-R / W), and / or digital video disc (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 above process and / or method. 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 above process and / or method.

[0086] The NSD processing circuit 1800 includes an I / O interface 1810. The I / O interface 1810 is connected to an external circuit. In one or more embodiments, the I / O interface 1810 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor directional keys for communicating information and commands to the processor 1802.

[0087] The NSD processing circuit 1800 further includes a network interface 1812 connected to a 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 wireless network interfaces such as BLUETOOTH®, WIFI, WiMAX, GPRS, or WCDMA®, or wired network interfaces such as ETHERNET, USB, or IEEE-864. In one or more embodiments, 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 the I / O interface 1810. The information received via the I / O interface 1810 includes one or more 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 the UI 1822 via the I / O interface 1810. The information is stored in the computer-readable medium 1804 as the user interface (UI) 1822.

[0089] In some embodiments, some or all of the above processes and / or methods are implemented as standalone software applications for execution by a processor. In some embodiments, some or all of the above processes and / or methods are implemented as software applications that are part of an additional software application. In some embodiments, some or all of the above processes and / or methods are implemented as plug-ins to a software application.

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

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

[0092] In some embodiments, the method further includes the step of storing the nSSAI ID by a processor.

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

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

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

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

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

[0098] In some embodiments, the device includes a processor and a memory in which instructions are stored. When an instruction is executed by the processor, the processor causes the processor to create a network slice based on a network slice design submitted by the user, and to automatically generate a network slice selection support information ID (nSSAI ID) for the network slice based on the network slice design.

[0099] In some embodiments, before creating a network slice, the instruction further causes the processor to receive a network slice design submitted by the user.

[0100] In some embodiments, the instruction further causes the processor to store the nSSAI ID.

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

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

[0103] In some embodiments, the instruction further causes the processor to retrieve a network slice from the storage device.

[0104] In some embodiments, the instruction further causes the processor to deactivate the network slice.

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

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

[0107] In some embodiments, before creating a network slice, the instruction further causes the processor to receive a network slice design submitted by the user.

[0108] In some embodiments, the instruction further causes the processor to store the nSSAI ID.

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

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

Claims

1. The process involves creating a network slice using a processor and based on a network slice design submitted by the user. The processor automatically generates a network slice selection support information ID (nSSAI ID) for the network slice, A method including, The step of generating the aforementioned nSSAI ID is: Steps to access the naming template, The steps include generating a first part of the nSSAI ID based on the behavior of the network slice created using the naming template, The step includes generating a second part of the nSSAI ID based on the implementation of the network slice created using the naming template, A method wherein the first portion has a first predetermined length, and the second portion has a second predetermined length different from the first predetermined length.

2. The method according to claim 1, further comprising the step of receiving the network slice design submitted by the user before the step of creating the network slice.

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

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

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

6. The method according to claim 5, further comprising the step of obtaining the network slice from a storage device using the processor.

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

8. The method according to claim 7, further comprising the step of reusing the network slice as another network slice using the processor.

9. Processor and A device comprising a memory in which instructions are stored, When the aforementioned instruction is executed by the processor, the processor will: Create network slices based on the network slice design submitted by the user. Based on the aforementioned network slice design, the network slice selection support information ID (nSSAI ID) for the network slice is automatically generated. The aforementioned processor, Accessing naming templates, Based on the behavior of the network slice created using the naming template, the first part of the nSSAI ID is generated. Using the naming template, the second part of the nSSAI ID is generated based on the implementation of the network slice created. The nSSAI ID is generated by the following: An apparatus in which the first part has a first predetermined length, and the second part has a second predetermined length different from the first predetermined length.

10. The apparatus according to claim 9, wherein, before creating the network slice, the instruction further causes the processor to receive the network slice design submitted by the user.

11. The apparatus according to claim 9, further causing the processor to store the nSSAI ID.

12. The apparatus according to claim 9, wherein the instruction further causes the processor to display the nSSAI ID in the graphical user interface (GUI) included in the user interface (UI).

13. The apparatus according to claim 9, wherein the instruction further causes the processor to receive a request to deactivate the network slice.

14. The apparatus according to claim 13, further causing the processor to obtain the network slice from the storage device.

15. The apparatus according to claim 14, further causing the instruction to cause the processor to deactivate the network slice.

16. The apparatus according to claim 15, wherein the instruction further causes the processor to reuse the network slice as another network slice.

17. A non-temporary computer-readable medium on which instructions are stored, When the aforementioned instruction is executed by the processor, the processor will: Create network slices based on the network slice design submitted by the user. Based on the aforementioned network slice design, the network slice selection support information ID (nSSAI ID) for the network slice is automatically generated. The aforementioned instruction is, Accessing naming templates, Based on the behavior of the network slice created using the naming template, the first part of the nSSAI ID is generated. Using the naming template, the second part of the nSSAI ID is generated based on the implementation of the network slice created. This causes the processor to generate the nSSAI ID, The first portion has a first predetermined length, and the second portion has a second predetermined length that is different from the first predetermined length. Non-temporary computer-readable media.

18. The non-temporary computer-readable medium according to claim 17, wherein, before creating the network slice, the instruction further causes the processor to receive the network slice design submitted by the user.

19. The instruction further causes the processor to store the nSSAI ID in the non-temporary computer-readable medium according to claim 17.

20. The non-temporary computer-readable medium according to claim 17, further comprising the instruction causing the processor to display the nSSAI ID in a graphical user interface (GUI) included in the user interface (UI).

Images