Systems and methods for network slice subnet distribution

Abstract

1. A method comprising: determining, by a processor, whether a processing load of one or more Network Slice Subnet Management Functions (NSSMFs) exceeds a predetermined processing limit; determining, by the processor, which processing loads of the one or more NSSMFs have exceeded the predetermined processing limit; and implementing, by the processor, an additional NSSMF for each NSSMF that has exceeded the predetermined processing limit based on the processing load that has exceeded the predetermined processing limit.

Description

[Technical Field]

[0001] This description relates to a system for network slice subnet distribution and its method of use. [Background technology]

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

[0003] The Radio Access Network (RAN) is the part of a telecommunications system that implements radio access technology. 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 [Means for solving the problem]

[0004] In some embodiments, the method includes determining, by a processor, whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit; determining, by the processor, which processing loads of the one or more NSSMFs exceed the predetermined processing limit; and implementing, by the processor, an additional NSSMF for each NSSMF that exceeds the predetermined processing limit based on the processing load that exceeds the predetermined processing limit.

[0005] In some embodiments, an apparatus includes a processor and a memory having instructions stored therein that, when executed by the processor, cause the apparatus to determine whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit, determine which services exceed the predetermined processing limit, and implement an additional NSSMF for each NSSMF that exceeds the predetermined processing limit.

[0006] In some embodiments, a non-transitory computer-readable medium has instructions stored therein that, when executed by a processor, cause the apparatus to determine whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit; determine which processing loads of the one or more NSSMFs exceed the predetermined processing limit; and, based on the processing load that exceeds the predetermined processing limit, implement an additional NSSMF for each NSSMF that exceeds the predetermined processing limit.

[0007] Aspects of each embodiment can be understood by reading the following detailed description in conjunction with the accompanying figures. In accordance with standard industry practice, various features have not been drawn to scale. In some embodiments, the dimensions of various features have been arbitrarily increased or decreased for clarity of discussion. [Brief explanation of the drawings]

[0008] [Figure 1]1 is a diagrammatic representation of a system for network slice design (NSD), according to some embodiments.

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

[0010] [Figure 3] FIG. 1 is a block diagram of a Network Slice Subnet Management Function (NSSMF) according to some embodiments.

[0011] [Figure 4] FIG. 1 is a block diagram of an NSSMF, according to some embodiments.

[0012] [Figure 5] FIG. 1 is a block diagram of an edge NSSMF according to some embodiments.

[0013] [Figure 6A] FIG. 1 is a block diagram of a dedicated NSSMF for a radio access network, according to some embodiments.

[0014] [Figure 6B] FIG. 1 is a block diagram of a dedicated NSSMF of a core network and a transport network according to some embodiments.

[0015] [Figure 7] FIG. 1 is a block diagram of NSSMF functionality, according to some embodiments.

[0016] [Figure 8] FIG. 1 is a block diagram of a vendor-specific subnet configurator abstracted from the NSSMF, according to some embodiments.

[0017] [Figure 9A] FIG. 1 is a block diagram of an NSSMF system, according to some embodiments. [Figure 9B] FIG. 1 is a block diagram of an NSSMF system, according to some embodiments.

[0018] [Figure 10] FIG. 1 is a flow diagram of a process for modifying an NSSMF, according to some embodiments.

[0019] [Figure 11] FIG. 1 is a high-level functional block diagram of a processor-based system according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

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

[0021] Additionally, spatially relative terms such as beneath, below, lower, above, upper, etc. are used herein for ease of description to describe the relationship of one element or feature to another, as shown in the figures. 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. In response to a device being otherwise oriented (e.g., rotated 90 degrees or at other orientations), the spatially relative descriptors used herein will be interpreted accordingly.

[0022] Network slicing is a method of creating multiple unique logical and virtualized networks on a common multi-domain infrastructure. Using software-defined networking (SDN), network functions virtualization (NFV), orchestration, analytics, and automation, network operators manually create network slices to support specific applications, services, sets of users, or networks. Network slices can 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, the central conduits designed to forward network traffic at high speeds), and transport networks (TNs), the public telecommunications infrastructure that enables telecommunications between defined network termination points, deployed across multiple network operators.

[0023] Network slicing supports services with different network requirements, such as connected vehicles and voice communications, which require different throughput, latency, and reliability compared to data communications with Internet of Things (IoT) devices. In network slicing, each slice is configured with different architectures, management, and security to support specific uses. 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 specific service level agreements (SLAs) with vendors.

[0024] A network slice is divided into network service subnets (NSS), each dedicated to a domain (e.g., RAN, CN, transport domain (e.g., TN), or end-to-end (E2E) domain). A transport domain refers to the telecommunications transmission facility over which voice, data, and video communications are distributed between remote locations for use on a shared basis.

[0025] Within the NSS, 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 (NR)). Within the 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 service broker for all network functions within the 5G CN) or AMF (Access and Mobility Management Function that receives connection and session-related information from UEs to handle connection and mobility management tasks). Within the transport slice subnet, there are TN services.

[0026] In some embodiments, a distribution manager for NSS is described.In some embodiments, a method for managing NSS distribution is described.

[0027] Regarding other approaches for slice management, other approaches integrate with the NSS in each domain (e.g., RAN, CN, and TN) controlled by a centralized subnet manager. This integration creates problems during subnet scaling (e.g., due to increased load (a measure of the amount of computational work performed by a computer system)) when the entire centralized subnet manager is scaled.

[0028] In software-defined networking (SDN), the southbound interface is an OpenFlow protocol specification that enables communication between controllers, switches, and other network nodes with lower-level components. This also enables routers to identify network topology, determine network flows, and implement requests sent to the router via the northbound interface. The northbound interface includes interfaces that allow a particular component to communicate with higher-level components within the same network.

[0029] Because other approaches are tightly coupled to subnets as a whole, these other approaches cannot scale per subnet and further cannot integrate with multiple southbound services. Other approaches cannot handle subnet-specific loads that vary depending on the region in which the subnet is deployed. Furthermore, these other approaches cannot support multiple subnet configuration service integration for configuration push. Push configuration is a feature that supports enterprise-wide configuration management, where a new configuration is pushed from a running configuration on a source system to a running configuration on one or more target systems.

[0030] In some embodiments, a Network Slice Subnet Management Function (NSSMF) ensures that the behavior of the RAN, CN, and TN domains is abstracted and controlled by the deployment strategy. In some embodiments, the NSSMF operates with any combination of the RAN, CN, and TN, all three together, or individually.

[0031] In some embodiments, the subnet layer and Cloud Management as a Service (CMaaS) / Software Defined Network Controller (SDNC) / Subnet Configuration Services are separated, providing vendors the ability to select which services should be integrated into the NSSMF to configure the subnet.

[0032] CMaaS is the management of cloud computing products and services. Public clouds are managed by public cloud service providers, including the servers, storage, networking, and data center operations of the public cloud environment. Users choose to manage their own public cloud services using third-party cloud management tools. Managing private clouds involves software tools that help create virtualized pools of compute resources, provide a self-service portal to end users, and handle security, resource allocation, tracking, and billing. Because cloud environments are typically highly virtualized and organized from a portable workload perspective, private cloud management tools tend to be service-driven rather than resource-driven. In hybrid cloud environments, compute, network, and storage resources are managed across multiple domains.

[0033] The SDNC is a logically centralized entity responsible for (i) moving requests from the SDN application layer to the SDN data path and (ii) providing an abstract view of the network (including statistics and events) to SDN applications. The SDNC includes one or more Northbound Interface (NBI) agents, SDN control logic, and Control-Data Plane Interface (CDPI) drivers. The description as a logically centralized entity does not prescribe or preclude implementation details such as federation of multiple controllers, hierarchical connections of controllers, communication interfaces between controllers, or virtualization or slicing of network resources.

[0034] Subnetting is a technique for dividing a network into smaller networks. Subnetting increases routing efficiency, helps increase network security, and reduces the size of broadcast domains. Internet Protocol (IP) subnetting specifies the significant bits from the host as part of the network prefix. This method divides the network into smaller subnets. IP subnetting further reduces the size of the routing tables stored in routers.

[0035] In some embodiments, each deployment of an NSSMF is one or more of the following deployment types: a single NSSMF for a combined CN / RAN / TN, an NSSMF for a combined CN / RAN and a separate NSSMF for the TN, an NSSMF for a combined TN / RAN and a separate NSSMF for the CN, an NSSMF for a combined CN / TN and a separate NSSMF for the RAN, or separate NSSMFs for the RAN, TN, and CN.

[0036] In some embodiments, the user switches between deployments based on network load. In some embodiments, the NSSMF is configured with a multi-vendor subnet configuration SPI. (SPI is generally an acronym for three cloud service delivery models: Software-as-a-Service (SaaS is the ability offered to users to use a provider's applications that run on cloud infrastructure and are accessible from a variety of client devices, either through thin-client interfaces such as web browsers (e.g., web-based email) or programmatic interfaces); Platform-as-a-Service (PaaS is the ability offered to users to deploy user-written or user-acquired applications, created using programming languages, libraries, services, and tools supported by the provider, onto cloud infrastructure; the user does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but does control the deployed applications and, in some cases, the configuration settings of the application-hosting environment); and Infrastructure-as-a-Service (IaaS is the ability for users to deploy and run any software, including operating systems and applications; the user does not manage or control the underlying cloud infrastructure, but does have control over the operating systems, storage, and deployed applications, and, in some cases, limited control over selected networking components).

[0037] In some embodiments, the technical solution is based on scaling in or out the load of individual subnets, thus making the maintenance and operation of the subnets more efficient.

[0038] In some embodiments, the NSSMF includes several components, such as subnet adapters (e.g., CN, RAN, and TN) and a configuration manager that connects to a configuration service to push configurations to network functions.

[0039] In some embodiments, individual NSSMF subnet adapters are switched on based on deployment and depending on the slice subnet load they are managing (e.g., CN-RAN-TN, CN-RAN, TN-RAN, CN-TN, or solely RAN, TN, CN). In some embodiments, users switch on any combination (e.g., CN-RAN-TN, CN-RAN, TN-RAN, CN-TN, or solely RAN, TN, CN), thus handling a larger load with greater efficiency.

[0040] In some embodiments, the configuration manager generates a configuration file that pushes the configuration and connectivity structure to a configuration service, which then pushes the configuration to the network function. In some embodiments, multiple configuration options are supported. In some embodiments, a user switches on specific services of the configuration push mechanism. Thus, because there are multiple protocols supported by the network function (NF) and configuration service, such as Network Configuration Protocol (Netconf), Representational State Transfer (REST), and gRemote Procedure Call (GRPC), more options are available to the user for configuring the network function. Thus, providing flexibility for the user to select from a number of supported configuration services.

[0041] NETCONF is a network management protocol developed and standardized by the Internet Engineering Task Force (IETF). NETCONF provides mechanisms for installing, manipulating, and deleting the configuration of network devices. NETCONF operates on top of a simple remote procedure call (RPC) layer. The NETCONF protocol uses an Extensible Markup Language (XML)-based data encoding for configuration data and protocol messages. Protocol messages are exchanged over a secure transport protocol. The NETCONF protocol is implemented by equipment vendors in network devices such as routers and switches. NETCONF supports robust configuration changes using transactions that involve several devices.

[0042] REST is a software architectural style that describes a uniform interface between physically separate components, often over the Internet in a client-server architecture. REST defines four interface constraints: (1) resource identification, (2) resource operations, (3) self-describing messages, and (4) hypermedia as the engine of application state. Generally, REST describes machine-to-machine interfaces. In web development, REST enables content to be rendered when requested, often referred to as dynamic content.

[0043] GRPC (recursive acronym) is a cross-platform, open-source, high-performance RPC framework. GRPC is used to drive use cases from microservices to the "last mile" of computing (mobile, web, and Internet of Things). GRPC uses HTTP / 2 for transport and Protocol Buffers as the interface description language, and provides features such as authentication, bidirectional streaming and flow control, blocking or non-blocking bindings, and cancellation and timeouts. The most common usage scenarios include connecting services in a microservices-style architecture or connecting mobile device clients to backend services.

[0044] In some embodiments, a use case deployment strategy includes moving the NSSMF closer to the CMaaS deployment location of the RAN and CN to maintain sessions. In some embodiments, the NSSMF is adaptive and plug-and-play capable. In some embodiments, the NSSMF can be deployed closer to the CMaaS, which handles higher loads and is closer to network functions, while the CMaaS primarily handles the CN and RAN. Yet another deployment strategy includes a separate NSSMF handling TN layer traffic.

[0045] Plug and Play (PnP) is a feature of a computer system that allows a device, feature, or software to be used by the computer system as soon as the device, feature, or software is connected to the computer system.

[0046] In some embodiments, the NSSMF supports multiple CMaaS software development kit (SDK) integrations with northbound CMAAS. Thus, with the help of a workflow engine, the NSSMF also provides flexibility at the protocol level (e.g., REST, NETCONF, GRPC, etc., as well as vendor-specific protocols such as Mavenir and NEC). In some embodiments, configuration templates support editing of static values ​​and updating of dynamic parameters.

[0047] An SDK is a collection of software development tools in a single installable package. SDKs facilitate the creation of applications by including compilers, debuggers, and sometimes software frameworks. To create applications with advanced features such as push notifications, most application software developers use specific software development kits.

[0048] A workflow engine is a software application that manages business processes. Workflow engines are a component of workflow technology and typically utilize a database server. A workflow engine manages and monitors the state of activities in a workflow, such as processing and approving a loan application form, and determines which new activities to transition to according to a defined process (e.g., workflow). Actions can be anything from saving the application form in a document management system to sending a reminder email to a user or reporting a past-due item to management. A workflow engine facilitates the flow of information, tasks, and events.

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

[0050] 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, base stations 108), where antennas 110 are wirelessly connected to UEs 112 located within geographic coverage cells 114A and 114B (hereinafter, geographic coverage cells 114). The CN 102 includes one or more service providers 116, a KPI server 118, and a network slicing module (NSDM) 120.

[0051] The CN 102 (also known as a 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 subnetworks. In some embodiments, the CN 102 ties diverse networks together across a wide geographic area, within different buildings in a campus environment, or within the same building.

[0052] 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 remote control machine) and the CN 102. In some embodiments, the RAN 104 is a C-RAN for simplified representation and explanation. In some embodiments, a baseband unit (BBU) replaces the C-RAN.

[0053] In traditional distributed cellular networks, BBUs are the pieces of equipment located at the bottom and top of base stations at cell sites. BBUs are radio equipment that link UEs to the CN and process billions of bits of information per hour. BBUs are traditionally located in enclosures or shelters located at the bottom of base stations. In contrast, C-RAN uses the large signal-carrying capacity of optical fiber to centralize many BBUs in dedicated pool locations or base stations. This reduces the amount of equipment at base stations and offers many other benefits, including lower latency.

[0054] 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. The two main methods in mobile backhaul implementations are fiber-based backhaul and wireless point-to-point backhaul. Other methods, such as copper-based wired, satellite communications, 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 begins with 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 microwave bands, mesh, and edge network topologies, which use high-capacity wireless channels to send packets to microwave or fiber links.

[0055] In some embodiments, the base station 108 is a lattice or freestanding tower, a guy tower, a monopole tower, and a hidden tower (e.g., a tower designed to resemble a tree, a cactus, a water tower, a sign, a light pole, and other types of structures). In some embodiments, the base station 108 is a cellular-enabled mobile device site where antennas and electronic communications equipment are typically located on a radio mast, tower, or other elevated structure to create a cell (or adjacent cells) in the network. The elevated structure typically supports antenna(s) 110 and one or more sets of transmitters / receivers (transceivers), digital signal processors, control electronics, remote radio heads (RRHs), primary and backup power sources, and shelters. Base stations are known by other names, such as base transceiver station, mobile phone mast, or cell tower. In some embodiments, the base station is replaced or supplemented by other edge devices configured to communicate wirelessly with UEs. The edge devices provide an entry point to a service provider CN, such as the CN 102. Examples include routers, routing switches, integrated access devices (IADs), multiplexers, and various metropolitan area network (MAN) and wide area network (WAN) access devices.

[0056] In at least one embodiment, antenna 110 is a sector antenna. In some embodiments, antenna 110 is a type of directional microwave antenna with a fan-shaped radiation pattern. In some embodiments, the arc angle of the fan is a 60°, 90°, or 120° design, with a few extra degrees to ensure overlap. Additionally, sector antennas are mounted in multiples if wider or full-circle coverage is desired. In some embodiments, antenna 110 is a rectangular antenna, sometimes called a panel antenna or wireless antenna, used to transmit and receive waves or data between mobile devices or other devices and base stations. 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, antennas 110 are chosen for their size and directionality. In some embodiments, antenna 110 is a multiple-input, multiple-output (MIMO) antenna that simultaneously transmits and receives two or more data signals over the same wireless channel by taking advantage of multipath propagation.

[0057] 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, such as user interface (UI) 922 ( FIG. 9 ), and provides a touchscreen 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, functionality for making and receiving voice and video phone calls, video games, and global positioning system (GPS) capabilities. Additionally or alternatively, the UE operates an operating system (OS) that enables the installation and operation of capability-specific third-party apps. In some embodiments, the UE 112 is a computer (such as a tablet computer, netbook, digital media player, digital assistant, graphing calculator, handheld game console, handheld personal computer (PC), laptop, mobile internet device (MID), personal digital assistant (PDA), pocket calculator, portable media player, or ultra-mobile PC), a mobile phone (such as a camera phone, feature phone, smartphone, or phablet), a digital camera (such as a digital camcorder, or digital still camera (DSC), digital video camera (DVC), or front-facing camera), a pager, a personal navigation device (PND), a wearable computer (such as a calculator watch, smartwatch, head-mounted display, earphones, or biometric device), or a smart card.

[0058] In some embodiments, the geographic coverage cell 114 includes a shape and a 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 lobe-shaped, although the geographic coverage cell 114 may be configured in almost any shape or size. The geographic coverage cell 114 represents the geographic area in which the antennas 110 and the UEs 112 are configured to communicate.

[0059] Service provider(s) 116 are companies, vendors, customers, or organizations that provide Internet backbone access directly to Internet service providers and sell bandwidth or network access to subscribers (using UEs), typically through access to network access points (NAPs). Service providers are sometimes referred to as backbone providers, Internet providers, or vendors. Service providers include telecommunications companies, data carriers, wireless communication providers, Internet service providers, and cable television operators that offer high-speed Internet access.

[0060] The KPI server 118 generates both forecasts and live network data. The live network data (KPIs, UE / cell / MDT (drive test minimization) traces, and crowd-sourced 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 wireless networks, such as the RAN 104. This technique involves using moving vehicles containing mobile wireless network air interface measurement equipment to detect and record a wide variety of physical and virtual parameters of mobile cellular service in each geographic area. By measuring what wireless network subscribers experience in an area, wireless carriers can make targeted changes to their networks that provide better coverage and service to their customers. Drive testing typically consists of a moving vehicle equipped with drive test measurement equipment. This equipment is typically a highly specialized electronic device that interfaces with mobile handsets (UEs) from the original equipment manufacturer (OEM). This ensures that measurements are realistic and comparable to actual user experiences. In the case of mobile networks, crowdsourcing methodologies leverage a population of participants (e.g., mobile subscribers) to collect network measurements manually or automatically via mobile apps, or directly from the network using call traces.

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

[0062] In some embodiments, the NSD module 120 is configured to allow a user to design one or more network slices. In some embodiments, the network slice design is GUI-based. In some embodiments, operations include a user entering basic information such as a network slice name, slice type, domain, and shared or non-shared slice selection. Other operations include defining a slice, such as service profile parameters (including the original request for a communication service instance, such as latency, data rate, and mobility level) requested by a northbound interface (e.g., internal to the system or manually from a user), and translating the service profile parameters into slice profile parameters (including slice subnet parameter information for different network domain slice subnet instances (NSSIs), such as RAN, transport network (TN), and CN NSSIs).

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

[0064] In some embodiments, NSD method 200 describes the process tasks of network slice design. Although the operations of NSD method 200 are discussed and illustrated as having a particular order, the operations of NSD method 200 are configured to be performed in any order unless otherwise specified. NSD method 200 is implemented as a set of operations, such as operation 202 through operation 220.

[0065] At operation 202 of NSD method 200, NSDM 120 receives input from a user to initiate network slice design. In some embodiments, the user is presented with a graphical user interface (GUI) that indicates that a network slice design application is starting. The process proceeds from operation 202 to operation 204.

[0066] A GUI is a form of user interface (UI) that allows users to interact with electronic devices through graphical icons and audio indicators, such as primary notation, instead of text-based UIs, typed command labels, or text navigation. Actions in a GUI are typically performed by direct manipulation of graphical elements.

[0067] At operation 204 of NSD method 200, NSDM 120 presents a list of slice templates via a GUI. In some embodiments, each network slice in the slice template list 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 non-shared), a creation date, and a last modification date. The term template refers to a software application's ability to define a unique, non-executable file format specifically intended for that application. The process proceeds from operation 204 to operation 206.

[0068] At operation 206 of NSD method 200, NSDM 120 receives user input via the GUI indicating a selection of a slice template. In some embodiments, the user points to and then clicks on the slice template. In some embodiments, the user clicks on a user selection button to begin the process of creating a new slice with the selected slice template. The process proceeds from operation 206 to operation 208.

[0069] At operation 208 of NSD method 200, a GUI is presented and a user enters basic slice information via the GUI. In some embodiments, the user enters a slice name, selects a slice type (e.g., eMBB, URLLC slice type, etc.), selects a domain, and selects whether the slice is shared or dedicated. For example, the user selects a shared or dedicated slice subnet for each domain (RAN, CN, TN, or a combination thereof) and coverage area of ​​the network slice. In some embodiments, the selection of a public land mobile network (PLMN) is based on the selected coverage area. The process proceeds from operation 208 to operation 210.

[0070] At operation 210 of NSD method 200, a GUI is presented for a user to set network slice parameters. In some embodiments, the slice parameter GUI presents service profile SLA parameters and, if applicable (e.g., depending on the SLA), configures the user to change the parameters. In a non-limiting example, the user changes the expected latency to meet the network slice specification (e.g., set to 300 ms). In some embodiments, the slice manager calculates slice profile parameters for each domain (RAN, CN, and TN) to meet the service profile SLA. In some embodiments, this process is repeated for each domain. The process proceeds from operation 210 to operation 212.

[0071] At operation 212 of NSD method 200, a GUI is presented in which 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 some embodiments, the user navigates to a slice subnet profile GUI in which the user selects a network slice subnet name for each domain. In some embodiments, the network services associated with the slice subnet are displayed. In some embodiments, in response to a network service not existing or associated with the network slice subnet, the user may further select a network service template.

[0072] In some embodiments, a GUI is presented, and a user is presented with a network service selection pop-up box. In some embodiments, the network service box includes each of the network services, such as a user plane function (the UPF is responsible for packet routing and forwarding, packet inspection, quality of service (QoS) processing, and external protocol data unit (PDU) sessions for interconnecting data networks (DNs) in a 5G architecture), a network repository function (the NRF acts as a central service broker for all network functions (NFs) in the 5G core), or a session management function (the SMF is responsible for interacting with the separated data plane, creating, updating, and deleting PDU sessions, and managing session contexts with the UPF). In a non-limiting example, the user selects the UPF (highlighted), and an indication that the UPF network service is shared (e.g., true) is presented to the user. The user selects a network service from the network service list, and the box displays the network functions associated with the selected network service selected by the user from the network service list.

[0073] Alternatively, the GUI displays the NRF highlighted in the network service box, with false being presented in the shared user input field indicating that the NRF network service is not shared. The user enters network service information into a dedicated network service template. The user selects a network service template in the NS template user selection field. In response to selecting a network service template (e.g., UPF NST), the user is presented with a network function box. In the network function box, the user selects a network function (e.g., UPF app, UPF DB, etc., in which the user selects a distributed unit type, distributed unit code, and cluster ID).

[0074] The GUI is presented after each domain (RAN, Core, and Transport) includes a network service. Once each domain includes a network service, NSDM 120 determines whether the selected network service is ready to serve the new network slice.

[0075] In some embodiments, the GUI is presented in response to a feasibility test failing for one or more domains (e.g., the RAN domain). In some embodiments, the user selects a different slice subnet and rechecks the feasibility.

[0076] In some embodiments, the GUI is presented upon successful feasibility testing for each domain. In response to a successful feasibility testing, the user deploys the network slice. In some embodiments, if the feasibility testing is not successful, the user cannot proceed with the network slice design. The process proceeds from operation 212 to operation 214.

[0077] At operation 214 of method 200, a GUI is presented in which a user selects SLA parameters, such as parameters and KPIs, to be monitored for the network slice based on one or more SLA agreements. In some embodiments, the user searches for parameters or KPIs for the selected domain. In some embodiments, the user drags and drops parameters / KPIs. Further, in response to the selection of parameters / KPIs for which the slice will be deployed and monitored, the user selects a policy for a slice auto-repair use case. Auto-repair is a function that automatically detects disabled access points and restores the wireless network. The process proceeds from operation 214 to operation 216.

[0078] At operation 216 of method 200, the designed network slices are displayed in a GUI for user review. In some embodiments, the GUI is displayed with a list of network slices. The process proceeds from operation 216 to operation 218.

[0079] At operation 218 of method 200, a user deploys the designed network slice by clicking a desired network slice in a list of network slices, which displays a pop-up box. In some embodiments, the slice manager makes an API call to an orchestrator (not shown) to deploy the designed slice. The process proceeds from operation 218 to operation 220.

[0080] At operation 220 of method 200, the status of the designed slice is updated. In some embodiments, the state of the network slice is updated from designed to deployed. Other statuses include "in operation," "activation failed," and "deployment failed."

[0081] FIG. 3 is a block diagram of a network slice subnet management function (NSSMF) 322, according to some embodiments.

[0082] FIG. 4 is a block diagram of an NSSMF 400 according to some embodiments.

[0083] 3 and 4 are described together to provide a better understanding of the NSSMF 322 and the NSSMF system 400.

[0084] In FIG. 3, NSSMF 322 includes a core subnet 324, a RAN subnet 326, a transport subnet 328, and a subnet configurator 330, which connects to a configuration service, such as NSSMF management service 432 in FIG. 4, to push configurations to network services, such as RAN 434, CN 436, and TN 438 in FIG. 4.

[0085] In some embodiments, the NSSMF 322 ensures that the behavior of the RAN, such as the RAN 104, the CN, such as the CN 102, and the TN, such as the TN 106, is abstracted and controlled by the NSSMF deployment strategy. In some embodiments, the NSSMF 322 operates in some combination of the RAN subnet adapter 304, the CN subnet adapter 302, or the TN subnet adapter 306, all three together (FIG. 3) or individually (FIGS. 9A and 9B).

[0086] The NSSMF 322 includes the subnet configurator 308, the CN subnet 302, the RAN subnet 304, and the TN subnet 306, and maintains lifecycle management for each individual subnet. In Figure 3, a single NSSMF deployment, such as the NSSMF 322, manages the CN subnet 302, the RAN subnet 304, and the TN subnet 306, and thus the NSSMF 322 is the lifecycle manager for the CN subnet 302, the RAN subnet 304, and the TN subnet 306 contained in the NSSMF 322.

[0087] The subnet configurator 308 helps generate configuration files and pushes the configuration and connection files to the configuration service, which pushes the configuration services and files to the network features. In some embodiments, multiple configuration options are supported depending on the vendor, and the vendor turns on or off specific NSSMF features based on the load of each network service. In some embodiments, this provides users / vendors with more options for configuring network features because there are multiple protocols, such as Netconf, REST, and GRPC, supported by the network features and different configuration services. In some embodiments, this provides users / vendors with the flexibility to choose from a number of supported configuration services.

[0088] In some embodiments, a configuration service such as the subnet configurator 308 (e.g., a service that configures the hardware and software details of network elements to ensure interoperability and communication) pushes network slice subnet configurations to network services (NSs such as the CN 102, RAN 104, and TN 106). A configuration push is when hardware and / or software configuration changes are pushed to the southbound layer, which implements the desired changes until a new configuration push is received.

[0089] In FIG. 4, the NSSMF management service 432 receives subnet configurations, for example, from the NSSMF 322 (i.e., the subnet configurator 308 ), and distributes the respective subnet configurations to each of the RAN 434 , the core 436 , and the transport 438 .

[0090] Each of the RAN 434, Core 436, and Transport 438 is operatively coupled to a RAN configuration manager, a Core configuration manager 442, and a Transport layer configuration manager 444, which generate configuration files and push the configuration files to the network functions. In some embodiments, multiple vendor configuration options are supported, and the user / vendor switches on specific services of a particular configuration push mechanism. Thus, there can be multiple protocols, such as Netconf, REST, and GRPC, supported by the network function, providing the user / vendor with more options for configuring the network function. As a result, providing flexibility for the user to select from a number of supported configuration services.

[0091] FIG. 5 is a block diagram of an edge NSSMF 500 according to some embodiments.

[0092] In some embodiments, when one or more edge RANs 550 are present, each edge RAN 550 is configured with an NSSMF 522 in proximity to the edge RAN 550 to reduce latency. In this manner, the latency of this configuration is lower the closer each NSSMF 522 is to the edge RAN 550. The NSSMF 522 is deployed closer to RAN deployments in EDGE to handle the configuration of those network functions and provide an advance in latency, as opposed to an NSSMF deployed further away from the RAN deployment, such as the edge RAN 550.

[0093] In some embodiments, the NSSMF 522 is moved from the main data center to a data center closer to one or more edge RANs 550. Because the NSSMF 522 has plug-and-play capabilities, each NSSMF 522 can be deployed as a single or multi-domain subnet configurator.

[0094] FIG. 6A is a block diagram of a dedicated NSSMF for a radio access network according to some embodiments.

[0095] FIG. 6B is a block diagram of a dedicated NSSMF for core and transport networks according to some embodiments.

[0096] In some embodiments, a cascaded deployment is possible, with each subnet including a dedicated NSSMF. In some embodiments, an NSSMF is assigned to a subnet based on subnet load. Referring to FIGS. 5 and 6A , in a non-limiting example, in response to the RAN subnet 660 experiencing increased load over time, a user deploys an NSSMF 622B for the RAN subnet 660 to manage the RAN subnet 660. Continuing in a non-limiting example, the CN subnet 662 and the TN subnet 664 remain with the original NSSMF 662A, which originally handled the three subnets together (e.g., the RAN subnet 660, the core subnet 662, and the transport subnet 664). In response, the processing of the CN subnet 662 and the TN subnet 664 is improved by moving the RAN subnet processing to the NSSMF 622B, and load handling capacity is increased by adding a dedicated NSSMF 662B to the RAN subnet 660. In a scenario where the dedicated RAN subnet 662B was not added as the RAN subnet 660 was increasing its load over time, the increased load on the RAN subnet 660 would in turn slow down overall processing for each of the RAN subnet 660, the CN subnet 662, and the TN subnet 664. In some embodiments, the subnet manager NSSMF 622B is deployed and scaled separately, so that resource utilization depends on the load of that particular subnet.

[0097] In some embodiments, the more distributed the network, the more load (e.g., bandwidth) the network can handle. This deployment strategy of the NSSMF, supporting each of the three subnets (e.g., RAN subnet 660, core subnet 662, and transport subnet 664), or specific subnets, or groupings of two types of subnets, allows the network to handle a greater processing load on each subnet. Thus, subnet handling and per-subnet configuration push are substantially improved.

[0098] In some embodiments, each deployment of NSSMF 622B or 622A is one or more of the following deployment types: CN / RAN / TN (shown in FIG. 3), CN / RAN, TN / RAN, CN / TN (FIG. 6B), or one NSSMF for each of RAN (FIGS. 5, 6A, 9A, 9B), TN (FIGS. 9A and 9B), and CN (FIGS. 9A and 9B) alone. In some embodiments, a user / vendor switches between deployments based on network load.

[0099] In some embodiments, NSSMF subnet adapters 622B and / or 622A are switched on based on the deployment and depending on the slice subnet load of subnet adapters 660, 662, and / or 664 (e.g., CN-RAN-TN, CN-RAN, TN-RAN, CN-TN, or singly RAN, TN, CN). In some embodiments, the user / vendor can switch between any of the combinations supported for their deployment and thus handle larger bandwidth loads more efficiently (described in more detail with respect to Figures 9A and 9B).

[0100] FIG. 7 is a block diagram of an NSSMF function 700 according to some embodiments.

[0101] In some embodiments, network slicing includes a network slice manager function (NSMF) 722 that maps services and oversees functionality between layers, and an NSSMF, e.g., an NSSMF RAN 724, an NSSMF core 726, and an NSSMF transport 728. The NSSMF function 700 includes a network slice management function (NSMF) 722 that is responsible for subnet design, deployment, activation, deactivation, and decommissioning of subnet implementations. The NSMF sends subnet information to the NSSMF RAN 724 via a RAN API 740, to the NSSMF core 726 via a core API 742, and to the NSSMF transport 728 via a transport API 744, respectively.

[0102] Each of the NSSMF RAN 724, NSSMF Core 726, and NSSMF Transport 728 forwards subnet information to the Subnet Configurator 708. The Subnet Configurator 708 supports multiple CMAAS SDK integrations with northbound CMAAS. Thus, it provides flexibility at the protocol level (i.e., REST, NETCONF, GRPC) as well as vendor-specific (e.g., Mavenir and NEC) protocol levels. This provides vendors with greater flexibility in handling the processing load at the RAN, Core, and Transport levels. In some embodiments, this aspect is improved by the workflow engine described in detail above.

[0103] In some embodiments, the use case deployment strategy involves placing the NSSMF 722 close to the CMaaS deployment locations of the RAN 704 and CN 702 to maintain sessions and reduce latency. In some embodiments, as described above, the NSSMF 700 is flexible and plug-and-play capable.

[0104] In some embodiments, the NSSMF function 700 includes several components, such as subnet adapters (e.g., CN 724, RAN 726, and TN 728) and a configuration manager 708 that connects to a configuration service to push network configurations.

[0105] In some embodiments, the NSSMF function 700 may be deployed closer to the CMaaS 730, handling a higher load and closer to the network functions primarily handling the CN 702 and the RAN 704. In some embodiments, another deployment strategy includes a separate NSSMF handling TN layer traffic (FIGS. 9A and 9B).

[0106] In some embodiments, NSSMF 700 is highly compatible with third-party vendors for configuration management SDNC integration (FIG. 8). In some embodiments, the deployment strategy, such as how the vendor allocates network slice subnets, is managed. In some embodiments, subnet configurator 708 includes template configurator 750 and CMaaS SDK integrator 752. Subnet configurator 708 includes template configurator 750 and CMaaS SDK integrator 752. In some embodiments, another embodiment of the subnet configurator is a template configurator. In some embodiments, a configuration template is inserted and a configuration payload is created based on the configuration template.

[0107] FIG. 8 is a block diagram of a vendor-specific subnet configurator 800 abstracted from the NSSMF, according to some embodiments.

[0108] In some embodiments, the subnet layer, Vendor 1 CMAAS 802, Vendor 2 CMAAS 804 / SDNC 806 / Subnet Configuration Service 808, is separated out to provide vendors, such as Vendor 1 Core 808, Vendor 2 Core 810, the ability to select the services that are integrated into the NSSMF to configure the subnet.

[0109] In some embodiments, the NSSMF is configured with a multi-vendor subnet configuration SPI. (SPI is an acronym for three common cloud service delivery models: Software-as-a-Service (SaaS is the ability offered to users to use a provider's applications that run on cloud infrastructure and are accessible from a variety of client devices, either through a thin-client interface such as a web browser (e.g., web-based email) or through a programmatic interface); Platform-as-a-Service (PaaS is the ability offered to users to deploy user-written or user-acquired applications, created using programming languages, libraries, services, and tools supported by the provider, onto cloud infrastructure; the user does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but controls the deployed applications and, in some cases, the configuration settings of the application-hosting environment); and Infrastructure-as-a-Service (IaaS is the ability for users to deploy and run any software, including operating systems and applications; the user does not manage or control the underlying cloud infrastructure, but has control over the operating systems, storage, and deployed applications, and, in some cases, limited control over selected networking components).

[0110] In some embodiments, the NSSMF supports multiple CMaaS software development kit (SDK) integrations with northbound CMAAS. Thus, with the help of a workflow engine, the NSSMF also provides flexibility at the protocol level (e.g., REST, NETCONF, GRPC, etc.), as well as vendor-specific protocols (e.g., Mavenir, NEC, etc.). In some embodiments, configuration templates support editing of static values ​​and updating of dynamic parameters.

[0111] In some embodiments, the technical solution is based on scaling in or out the load of individual subnets, thus making the maintenance and operation of the subnets more efficient.

[0112] In some embodiments, the subnet configurator provides at least three types of integrations: (1) CMaaS, (2) SDNC, and (3) CMaaS SDK. In some embodiments, the CMaaS configurator is configured to support multiple CMaaS SDKs that provide integrations with northbound systems. This means that in some embodiments, there are multiple CMaaSs, such as a CMaaS from a first vendor and a second CMaaS from a second vendor. Both the first and second vendors have different CMaaS integrations that communicate with their network services. Thus, in the CMaaS SDK integration in the subnet configuration element, the user inserts scripts that communicate with each of the two separate CMaaSs through a single NSSMF module. Thus, the subnet configurator supports multi-vendor integrations.

[0113] In some embodiments, the subnet configurator provides three types of integration: (1) CMaaS, (2) SDNC, and (3) CMaaS SDK. In some embodiments, the CMaaS configurator is configured to support multiple CMaaS SDKs that provide integration with northbound systems. This means that in some embodiments, there are multiple CMaaSs, such as a CMaaS from a first vendor and a second CMaaS from a second vendor. Both the first and second vendors have different CMaaS integrations that communicate with network services. Thus, in the CMaaS SDK integration in the subnet configuration element, the user inserts scripts that communicate with each of the two separate CMaaSs through a single NSSMF module. Thus, the subnet configurator supports multi-vendor integration.

[0114] In some embodiments, the network distribution strategy includes a subnet configuration for CMaaS. In some embodiments, the NSSMF provides a more vendor-friendly network distribution.

[0115] Multi-vendor integration further supports different protocols, or protocols specific to a particular vendor. In a non-limiting example, if a single subnet configurator is used with a CMaaS that runs one protocol for a first vendor CN, a CMaaS that runs another protocol for a second vendor CN, and an SDNC for the TN, the single subnet configurator supports multi-vendor multi-CMaaS client integration, which is achieved by different volume engines (e.g., CMaaSs modified via SDKs) and users insert scripts to integrate call flows (e.g., volumes) to the CMaaSs.

[0116] In some embodiments, configuration templates provide flexibility to edit static values ​​and also update dynamic parameter formulas. In some embodiments, static values ​​are changed and dynamic formulas created from the objects are further manipulated. In some embodiments, this provides user flexibility to push different types of configurations, aids in network scaling, and makes the subnet manager user-friendly. [Table 1]

[0117] In some embodiments, a dynamic formula is a mathematical description. In a non-limiting example, in response to having slice profile objects (e.g., P1 and P2), an engineer modifies the loaded profile object values ​​and creates new dynamic parameters in a configuration template. In some embodiments, a configuration template includes formulas that are objects used internally. In a non-limiting example of a formula, formula (1) is the Jinja formula 1 = (P1 · P2) 100 + P'1 + C.

[0118] In some embodiments, using the objects (P1, P2, P'1, and C1), engineers update formulas that use those objects to scale the network. In some embodiments, the formulas are dynamic, and based on the vendor's API, engineers manipulate the formulas to scale. In some embodiments, the formulas cannot be changed while the configuration template is being pushed. In some embodiments, application vendors or engineers cannot change dynamic parameters on the backend using configuration templates. In some embodiments, in response to an engineer initially loading a configuration template, as part of creating a network slice, users have the flexibility to update dynamic formulas as needed.

[0119] Thus, in some embodiments, network distribution is based on load and configuration parameters, thus allowing user flexibility to change configuration parameters, test all, and integrate multiple CMaaS SDK client integrations or SDNC integrations.

[0120] In some embodiments, these are two parts (eg, a CMaaS Subnet Configurator contained in the NSSMF, and a Lifecycle Manager contained in the NSSMF), with the entire NSSMF deployed in multiple locations.

[0121] 9A and 9B are block diagrams of NSSMF systems 900A and 900B according to some embodiments.

[0122] In FIGS. 9A and 9B, a single NSFM 902 is responsible for NSSFM RAN 904, NSSFM 906, and NSSFM 908, which are fed into a configuration manager 910.

[0123] FIG. 10 is a flow diagram of a method for modifying the NSSMF 1000 according to some embodiments.

[0124] 9A, 9B, and 10 are described together to provide a better understanding of the NSSMF through a method for modifying the NSSMF 1000. Although the method of operations for modifying the NSSMF 1000 is described and illustrated as having a particular order, the operations in the method for modifying the NSSMF 1000 are configured to be performed in any order unless otherwise specified. The method for modifying the NSSMF 1000 is implemented as a set of operations, such as operations 1002 through 1008.

[0125] An operation 1002 of the method for modifying the NSSMF 1000 determines an increase in processing load on one or more subnet services above a predetermined amount. In response to the processing load being below the predetermined amount, the operation proceeds to operation 1004, where no action is taken to install one or more NSSMFs. The process ends with this operation.

[0126] At operation 1004 of the method for modifying the NSSMF 1000, if no additional processing is required in either or each of the NSSFM RAN subnet 904, the NSSFM core subnet 908, or the NSSFM transmit subnet 906, then no action is taken. The operation ends at operation 1004.

[0127] At operation 1006 of the method for modifying the NSSMF 1000, in response to determining that the increased processing load exceeds a predetermined amount, a determination is made as to which subnets are experiencing a heavier than normal processing load. The process proceeds from operation 1006 to operation 1008.

[0128] At operation 1008 of the method for modifying the NSSMF 1000, additional NSSFMs, such as NSSFM RANs 904A and 904B and / or NSSFM core 908A, are added in response to a greater than normal processing load on one or more subnets (e.g., the NSSFM RAN subnet 904, the NSSFM core subnet 908, or the NSSFM transmit subnet 906). The process proceeds from operation 1008 to operation.

[0129] In operation 1010 of the method for modifying the NSSMF 1000, an additional configuration manager 910B is added to the core 964.

[0130] 11 is a block diagram of a processing circuit 1100 according to some embodiments. In some embodiments, the processing circuit 1100 is a general-purpose computing device including a hardware processor 1102 and a non-transitory computer-readable storage medium 1104. Among other things, the storage medium 1104 is encoded with, i.e., stores, computer program code 1106, i.e., a set of executable instructions such as an algorithm, or according to methods 200 and 1000. Execution of the instructions 1106 by the hardware processor 1102 represents (at least in part) a network slice design application that implements a portion or all of a method described herein (hereinafter, a process and / or method) according to one or more embodiments.

[0131] The processor 1102 is electrically coupled to a computer-readable storage medium 1104 via a bus 1108. The processor 1102 is further electrically coupled to an I / O interface 1110 by the bus 1108. A network interface 1112 is further electrically connected to the processor 1102 via the bus 1108. The network interface 1112 is connected to a network 1114 such that the processor 1102 and the computer-readable storage medium 1104 connect to external elements via the network 1114. The processor 1102 is configured to execute computer program code 1106 encoded on the computer-readable storage medium 1104 to enable the processing circuit 1100 to perform some or all of the described processes and / or methods. In one or more embodiments, the processor 1102 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or other suitable processing unit.

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

[0133] In one or more embodiments, the storage medium 1104 stores computer program code 1106 configured to enable the processing circuit 1100 to perform some or all of the described processes and / or methods. In one or more embodiments, the storage medium 1104 further stores information such as algorithms that facilitate the execution of some or all of the described processes and / or methods.

[0134] The NSD processing circuit 1100 includes an I / O interface 1110. The I / O interface 1110 is coupled to external circuitry. In one or more embodiments, the I / O interface 1110 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor direction keys for communicating information and commands to the processor 1102.

[0135] The processing circuit 1100 further includes a network interface 1112 coupled to the processor 1102. The network interface 1112 enables the processing circuit 1100 to communicate with a network 1114 to which one or more other computer systems are connected. The network interface 1112 includes a wireless network interface, such as BLUETOOTH, WIFI, WIMAX, GPRS, or WCDMA, or a wired network interface, such as ETHERNET, USB, IEEE-864, etc. In one or more embodiments, some or all of the described processes and / or methods are implemented in two or more processors 1102.

[0136] The processing circuit 1100 is configured to receive information via an I / O interface 1110. The information received via the I / O interface 1110 includes one or more of instructions, data, rules, and / or other parameters for processing by the processor 1102. The information is transferred to the processor 1102 via the bus 1108. The processing circuit 1100 is configured to receive information related to a UI 1122 via the I / O interface 1110. The information is stored on the computer-readable medium 1104 as a user interface (UI) 1122.

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

[0138] In some embodiments, the method includes determining, by a processor, whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit; determining, by the processor, which processing loads of the one or more NSSMFs exceed the predetermined processing limit; and implementing, by the processor, an additional NSSMF for each NSSMF that exceeds the predetermined processing limit based on the processing load that exceeds the predetermined processing limit.

[0139] In some embodiments, the method further includes taking no action by the processor in response to determining that none of the one or more NSSMFs has exceeded a predetermined processing limit.

[0140] In some embodiments, two or more additional NSSMFs are implemented by the processor to meet processing requirements.

[0141] In some embodiments, any one of the following combinations is satisfied by one or more NSSMFs: a first NSSMF for a radio access network (RAN), a core network (CN), and a transport network (TN), or a second NSSMF for the RAN and CN and a third NSSMF for the TN, or a third NSSMF for the RAN and TN and a fourth NSSMF for the CN, or a sixth NSSMF for a fifth CN and TN and the RAN, or a seventh NSSMF for the RAN and an eighth NSSMF for the CN and a ninth NSSMF for the TN.

[0142] In some embodiments, the method further includes implementing, by the processor, a configuration manager that receives communications from the core subnet, the RAN subnet, and the transport subnet.

[0143] In some embodiments, the method further includes distributing, by the processor, the subnet communication to one or more of a RAN, a core network, or a transport network.

[0144] In some embodiments, the method further includes pushing, by the processor, the configuration to a configuration service that pushes the configuration to the network function.

[0145] In some embodiments, the method further includes positioning, by the processor, the NSSMF near the edge RAN to reduce latency.

[0146] In some embodiments, an apparatus includes a processor and a memory, the memory having instructions stored therein that, when executed by the processor, cause the apparatus to determine whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit, determine which services exceed the predetermined processing limit, and implement an additional NSSMF for each NSSMF that exceeds the predetermined processing limit.

[0147] In some embodiments, the apparatus further prevents action by the processor in response to determining that none of the one or more NSSMFs has exceeded a predetermined processing limit.

[0148] In some embodiments, the device further implements two or more additional NSSMFs to meet processing requirements.

[0149] In some embodiments, a non-transitory computer-readable medium has instructions stored therein that, when executed by a processor, cause the apparatus to determine whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit; determine which processing loads of the one or more NSSMFs exceed the predetermined processing limit; and, based on the processing load that exceeds the predetermined processing limit, implement an additional NSSMF for each NSSMF that exceeds the predetermined processing limit.

[0150] In some embodiments, the apparatus is further adapted to implement configuration management for receiving communications from the core subnet, the RAN subnet, and the transport subnet.

[0151] In some embodiments, the apparatus further distributes the subnet communications to one or more of a RAN, a core network, or a transport network.

[0152] In some embodiments, the device further pushes the configuration to a pushing configuration service that pushes the configuration to the network function.

[0153] In some embodiments, the apparatus further comprises locating the NSSMF close to the edge RAN to reduce latency.

[0154] In some embodiments, a non-transitory computer-readable medium has instructions stored therein that, when executed by a processor, cause the apparatus to determine whether a processing load of one or more network slice subnet management functions (NSSMFs) exceeds a predetermined processing limit, determine which services exceed the predetermined processing limit, and implement an additional NSSMF for each NSSMF that exceeds the predetermined processing limit.

[0155] In some embodiments, the apparatus further prevents action by the processor in response to determining that none of the one or more NSSMFs has exceeded a predetermined processing limit.

[0156] In some embodiments, the device further implements two or more additional NSSMFs to meet processing requirements.

[0157] In some embodiments, the apparatus further satisfies any one of the following combinations with one or more NSSMFs: a first NSSMF for a radio access network (RAN), a core network (CN), and a transport network (TN), or a second NSSMF for the RAN and CN and a third NSSMF for the TN, or a third NSSMF for the RAN and TN and a fourth NSSMF for the CN, or a fifth NSSMF for the CN and TN and a sixth NSSMF, or a seventh NSSMF for the RAN and an eighth NSSMF for the CN, and a ninth NSSMF for the TN.

[0158] The foregoing outlines features of some embodiments so that those skilled in the art may better understand aspects of the present disclosure. Those skilled in the art will readily appreciate that this disclosure may be used as a basis for designing or modifying other processes and structures to carry out the same purposes and / or achieve the same advantages as the embodiments introduced herein. Those skilled in the art should further recognize that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations may be made herein without departing from the spirit and scope of the present disclosure.

Claims

1. 1. A method comprising: determining, by a processor, whether the processing load of one or more Network Slice Subnet Management Functions (NSSMFs) exceeds a predetermined processing limit; determining, by the processor, which of the one or more NSSMFs has a processing load that exceeds the predetermined processing limit; implementing, by the processor, an additional NSSMF for each NSSMF that exceeds the predetermined processing limit based on the processing load that exceeds the predetermined processing limit; A method comprising:

2. The method further comprises: taking no action in response to the determination, by the processor, that none of the one or more NSSMFs has exceeded the predetermined processing limit. The method of claim 1.

3. and in response to the service exceeding the predetermined processing limit, implementing, by the processor, two or more additional NSSMFs to meet processing requirements. The method of claim 1.

4. Each combination of the following: a first NSSMF for the Radio Access Network (RAN), the Core Network (CN), and the Transport Network (TN); or a second NSSMF for the RAN and the CN and a third NSSMF for the TN; or the third NSSMF for the RAN and the TN and a fourth NSSMF for the CN; or a fifth CN and a sixth NSSMF for the TN and the RAN; or a seventh NSSMF for the RAN; and an eighth NSSMF for the CN; and a ninth NSSMF for the TN; is satisfied by one or more NSSMFs; The method of claim 1.

5. The method further comprises: and implementing, by the processor, configuration management for receiving communications from a core subnet, a RAN subnet, or a transport subnet. The method of claim 1.

6. The method further comprises: by the processor RAN, the core network, or Transport networks, distributing subnet communications to one or more of The method of claim 5.

7. The method further comprises: and pushing, by the processor, the configuration to a configuration service that pushes the configuration to the network function. The method of claim 6.

8. The method further comprises: and placing, by the processor, an NSSMF near an edge RAN to reduce latency. The method of claim 7.

9. 1. An apparatus comprising: a processor and a memory having instructions stored therein; The instructions, when executed by the processor, cause the device to: Determining whether the processing load of one or more Network Slice Subnet Management Functions (NSSMFs) exceeds a predetermined processing limit; determining which services have exceeded the predetermined processing limit based on the processing load exceeding the predetermined processing limit; installing an additional NSSMF for each NSSMF that exceeds the predetermined processing limit; A device that performs the following.

10. in response to determining that none of the one or more NSSMFs has exceeded the predetermined processing limit, causing no action to be taken by the processor; 10. The apparatus of claim 9.

11. The device further comprises: and in response to the service exceeding the predetermined processing limit, implementing two or more additional NSSMFs to meet processing requirements.

10. The apparatus of claim 9.

12. Each combination of the following: a first NSSMF for the Radio Access Network (RAN), the Core Network (CN), and the Transport Network (TN); or a second NSSMF for the RAN and the CN and a third NSSMF for the TN; or the third NSSMF for the RAN and the TN and a fourth NSSMF for the CN; or a fifth CN and a sixth NSSMF for the TN and the RAN; or a seventh NSSMF for the RAN; and an eighth NSSMF for the CN; and a ninth NSSMF for the TN; is satisfied by one or more NSSMFs.

10. The apparatus of claim 9.

13. The device further comprises: and implementing configuration management to receive communications from a core subnet, a RAN subnet, or a transport subnet.

10. The apparatus of claim 9.

14. The device further comprises: RAN, the core network, or Transport networks, and further performing the steps of:

14. The apparatus of claim 13.

15. The device further comprises: and further performing a configuration push to push configuration service that pushes the configuration to the network function.

15. The apparatus of claim 14.

16. The device further comprises: and further placing the NSSMF close to the edge RAN to reduce latency.

16. The apparatus of claim 15.

17. A non-transitory computer-readable medium having instructions stored therein that, when executed by a processor, cause an apparatus to: Determining whether the processing load of one or more Network Slice Subnet Management Functions (NSSMFs) exceeds a predetermined processing limit; determining which processing load of the one or more NSSMFs has exceeded the predetermined processing limit; Based on the processing load exceeding the predetermined processing limit, deploying an additional NSSMF for each NSSMF that exceeds the predetermined processing limit; A non-transitory computer-readable medium for causing the execution of

18. the apparatus further causing no action to be taken by the processor in response to determining that none of the one or more NSSMFs has exceeded the predetermined processing limit.

20. The non-transitory computer-readable medium of claim 17.

19. the device further performing, in response to the service exceeding the predetermined processing limit, implementing two or more additional NSSMFs to meet processing requirements.

20. The non-transitory computer-readable medium of claim 17.

20. The apparatus further comprising: Each combination of the following: a first NSSMF for the Radio Access Network (RAN), the Core Network (CN), and the Transport Network (TN); or a second NSSMF for the RAN and the CN and a third NSSMF for the TN; or the third NSSMF for the RAN and the TN and a fourth NSSMF for the CN; or a fifth CN and a sixth NSSMF for the TN and the RAN; or a seventh NSSMF for the RAN; and an eighth NSSMF for the CN; and a ninth NSSMF for the TN; is satisfied by one or more NSSMFs; 20. The non-transitory computer-readable medium of claim 17.

Images