Patent classifications
H04L41/5048
Distributed data storage techniques for edge devices
Techniques discussed herein relate to implementing a distributed computing cluster (the “cluster”) including a plurality of edge devices (e.g., devices individually configured to selectively execute within an isolated computing environment). One edge device may be configured to operate as a head node of the cluster at a given time. A request for virtual resources of the cluster may be received from a user device and directed to the first edge device of the cluster. The first edge device may determine it is not operating as a head node of the cluster. The first edge device may determine that a second edge device of the cluster is operating as the head node. In response, the first edge device may forward the request to the second edge device, wherein forwarding the request to the second edge device causes the second request to be processed by the cluster.
Network slice configuration method, apparatus, and system
This application provides a network slice configuration method, apparatus, and system, and pertains to the field of wireless communications technologies. The method includes: after receiving a management request of a network slice, obtaining or determining, by a network slice manager, network resource information corresponding to a subnet included in the network slice, and then sending, in a form of a subnet management request to a subnet manager, the network resource information corresponding to the subnet, so that the subnet manager configures the corresponding subnet based on the network resource information corresponding to the subnet. In this application, network slice configuration efficiency can be improved.
Methods for defining a network service descriptor (NSD) for a network service (NS), and network functions virtualization (NFV) orchestrator (NFVO) using said NSD
There are provided methods for defining a Network Service Descriptor (NSD) for a Network Service (NS), and Network Functions Virtualization (NFV) Orchestrator (NFVO) using said NSD. The NSD comprises zero, one or more of each of: a Virtualized Network Function (VNF) Descriptor (VNFD), a Physical Network Function (PNF) Descriptor (PNFD), a Network Service Descriptor (NSD), a Virtual Link (VL) Descriptor (VLD), and a VNF Forwarding Graph Descriptor (VNFFGD). One method comprising the step of defining at least one Connection Points (CP) Profile, wherein the CP Profile is referenced through a cpProfileId in a Network Forwarding Path Descriptor (NFPD) attribute of the VNFFGD, the CP Profile specifying a Connection Point Descriptor (CPD) or Service Access Point Descriptor (SAPD) for a given VnfProfile, PnfProfile or NsProfile.
Apparatus and method for configuring and enabling virtual applications
A method is implemented by a computing device to configure and monitor a virtual application in a cloud environment. The method includes generating instructions for configuring and monitoring the virtual application based on configuration data for the virtual application, modifying an injection virtual appliance image to include the instructions for configuring and monitoring the virtual application, where the injection virtual appliance image is a template for instantiating an injection virtual appliance (e.g., a software container or unikernel) that is to configure and monitor the virtual application according to the instructions, modifying a virtual application deployment descriptor for the virtual application to indicate that the injection virtual appliance is to be injected into the virtual application, and causing the virtual application, with the injection virtual appliance, to be deployed in the cloud environment using the modified virtual application deployment descriptor.
TECHNIQUES FOR PREVENTING CONCURRENT EXECUTION OF DECLARATIVE INFRASTRUCTURE PROVISIONERS
Techniques for preventing concurrent execution of an infrastructure orchestration service are described. Worker nodes can receive instructions, or tasks, for deploying infrastructure resources and can provide heartbeat notifications to scheduler nodes, also considered a lease. A signing proxy can track the heartbeat notifications sent from the worker nodes to the scheduler node. The signing proxy can receive requests corresponding to a performance of the tasks assigned to the worker nodes. The signing proxy can determine whether the lease between each worker node and the scheduler is valid. If the lease is valid, the signing proxy may make a call to services on behalf of the worker node, and if the lease is not valid, the signing proxy may not make a call to services on behalf of the worker node. Instead, the signing proxy may cut off all outgoing network traffic, blocking access of the worker node to services.
SYSTEM AND METHOD CONFIGURING A SLICE PROFILE IN A FIFTH GENERATION NETWORK
The present disclosure relates to a communication method and system for converging a 5.sup.th-Generation (5G) communication system for supporting higher data rates beyond a 4.sup.th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. Embodiments herein disclose a system and method for configuring slice profile in a Fifth Generation (5G) network. The method comprises determining root slice profile from a Service Profile (101). Further, generating one or more subnet slice profiles (102) associated with corresponding one or more network domains of the 5G network from the root slice profile. Furthermore, classifying one or more attributes (501) in each of the one or more subnet slice profiles (102) as configurable attributes (103) or as non-configurable attributes for the corresponding one or more network entities (105) in the corresponding network domain. Thereafter, providing the one or more attributes (501) categorized as the configurable attributes (103) to the corresponding one or more network entities (105) for enforcing the configurable attributes (103). Finally, providing the one or more attributes (501) categorized as the non-configurable attributes to the corresponding one or more OAM entities for enforcing the non-configurable attributes.
MEMORY WORKFLOW MANAGEMENT IN EDGE DEVICES
Techniques discussed herein relate to providing in-memory workflow management at an edge device (e.g., a computing device distinct from and operating remotely with respect to a data center). The edge device can operate as a computing node in a computing cluster of edge devices and implement a hosting environment (e.g., a distributed data plane). A work request can be obtained by an in-memory workflow manager of the edge device. The work request may include an intended state of a data plane resource (e.g., a computing cluster, a virtual machine, etc.). The in-memory workflow manager can determine the work request has not commenced and initialize an in-memory execution thread to execute orchestration tasks to configure a data plane of the computing cluster according to the intended state. Current state data corresponding to the configured data plane may be provided to the user device and eventually displayed.
Techniques for managing long-running tasks with a declarative provisioner
Techniques for implementing an infrastructure orchestration service are described. In some examples, a declarative provisioner of the infrastructure orchestration service receives instructions for deployment of a resource. The declarative provisioner identifies that the deployment of the resource is a long-running task stores state information corresponding to the deployment of the resource. In certain embodiments, upon identifying that the deployment of the resource is a long-running task, the declarative provisioner pauses its execution of the long-running task. Responsive to a trigger received from the infrastructure orchestration service, the declarative provisioner resumes execution of the deployment of the resource using the state information and transmits deployment information corresponding to the deployment of the resource to the infrastructure orchestration service.
Personalized serverless functions for multitenant cloud computing environment
A system and method are disclosed associated with a multi-tenant cloud computing environment. The system may receive information about a serverless function workload (e.g., a NodeJS, Java function or ABAP workload) to be launched in the cloud computing environment. A tenant associated with the serverless function workload to be launched may be identified and, based at least in part on the identified tenant, an objective function (e.g., throughput, latency, cost, etc.) for the serverless function workload to be launched may be identified. A recommendation service platform may then iteratively configure tuning parameters of the cloud computing environment using Bayesian optimization (e.g., to reach a global optimum using a Gaussian process) and the determined objective function. The system may then arrange for the serverless function workload to be executed in the cloud computing environment in accordance with the configured tuning parameters.
NETWORK SERVICE ACTIVATION SYSTEM
Aspects of the present disclosure involve systems and methods for a service activation system in a telecommunications network that utilizes one or more generic container files for building the configuration file to instantiate the service on the network. A request for service from a network may be received from an order entry system that includes specific information about the requested service. A collection of generic configuration files may be selected based on the information included in the service order and arranged to build a configuration file to be executed on the network. The service activation system may also include a component or group of components to verify a received service order and alter the service order with default information or data where applicable. The configuration file may also be executed on the network through one or more drivers communicating with the affected devices to configure the one or more network devices.