Patent classifications
H04L41/5054
Methods and systems of automatic network service initiation
Embodiments of a device and method are disclosed. In an embodiment, a method of automatic network service initiation involves pairing a first network device of a network service block (NSB) with an installer device at a customer site, at the first network device of the NSB, obtaining first network service configuration information from the installer device, performing automatic network service initiation of the first network device of the NSB based on the first network service configuration information, at a second network device of the NSB that is connected with the first network device of the NSB, obtaining address information of a cloud server from the first network device of the NSB, at the second network device of the NSB, obtaining second network service configuration information from the cloud server based on the address information, and performing automatic network service initiation of the second network device of the NSB based on the second network service configuration information.
Systems and methods for configuring and deploying multi-access edge computing applications
A device may include a processor configured to determine a plurality of requirements for a Multi-Access Edge Computing (MEC) application requested by a customer; select a solution blueprint for the MEC application, from a set of solution blueprints, based on the determined plurality of requirements, wherein the solution blueprint includes an application deployment blueprint and a connectivity blueprint; and receive approval of the selected solution blueprint from the customer. The processor may be further configured to configure at least one transport network device based on the connectivity blueprint, in response to receiving the approval of the selected solution blueprint from the customer; and deploy at least one component of the MEC application on a MEC device in a MEC network based on the application deployment blueprint, in response to receiving the approval of the selected solution blueprint from the customer.
Systems and methods for configuring and deploying multi-access edge computing applications
A device may include a processor configured to determine a plurality of requirements for a Multi-Access Edge Computing (MEC) application requested by a customer; select a solution blueprint for the MEC application, from a set of solution blueprints, based on the determined plurality of requirements, wherein the solution blueprint includes an application deployment blueprint and a connectivity blueprint; and receive approval of the selected solution blueprint from the customer. The processor may be further configured to configure at least one transport network device based on the connectivity blueprint, in response to receiving the approval of the selected solution blueprint from the customer; and deploy at least one component of the MEC application on a MEC device in a MEC network based on the application deployment blueprint, in response to receiving the approval of the selected solution blueprint from the customer.
METHOD FOR ACCESSING NETWORK SLICE, ELECTRONIC DEVICE AND STORAGE MEDIUM
The present application discloses a method for accessing a network slice, an electronic device, and a storage medium. The method includes: acquiring access information of a target network slice according to an access request of an application for requesting to access the target network slice; generating a routing policy between the application and the target network slice according to the access information; and accessing the application to the target network slice according to the routing policy, so that the application performs network communication through the target network slice.
End-to-end network slice selection and configuration
A system and associated method for enabling end-to-end (E2E) network slicing in a 5G network are described. A (Radio) Access Network-Network Slice Selection Function ((R)AN-NSSF) can be configured to receive a (R)AN slice selection request and to select, from a pool of (R)AN slice instances, a (R)AN network slice instance including one or more (R)AN slice components. A Core Network-Network Slice Selection Function (CN-NSSF) can be configured to receive a CN slice selection request to select, from a pool of CN slice instances, a CN network slice instance including one or more CN slice components. A Network Slice Policy Control (NSPC) function can be configured to verify that the selected (R)AN slice instance and CN slice instance are consistent with operator policies.
Service chain accomodation apparatus and service chain accommodation method
A service chain accommodation device includes an influence coefficient calculation unit that calculates an influence coefficient indicating that an influence at the time of processing failure of a service chain is greater for a VNF located in a subsequent stage of a service chain and a VNF shared among a plurality of service chains, a residual resource calculation unit that corrects an amount of residual resources that can be accommodated for each of the VNFs through which the service chain passes, and an accommodation design unit that assigns a new service chain on the basis of the amount of the residual resources.
Service chain accomodation apparatus and service chain accommodation method
A service chain accommodation device includes an influence coefficient calculation unit that calculates an influence coefficient indicating that an influence at the time of processing failure of a service chain is greater for a VNF located in a subsequent stage of a service chain and a VNF shared among a plurality of service chains, a residual resource calculation unit that corrects an amount of residual resources that can be accommodated for each of the VNFs through which the service chain passes, and an accommodation design unit that assigns a new service chain on the basis of the amount of the residual resources.
High performance compute infrastructure as a service
A high performance computing environment includes a plurality of computing resources, a plurality of tenant clouds organized from the plurality of computing resources, and an Infrastructure as a Service resource manager. The Infrastructure as a Service resource manager further includes a plurality of Infrastructure as a Service system interfaces and a portal. In operation, a cloud user interacts over a secure link and through the portal with the Infrastructure as a Service system interfaces to perform cloud tasks relative to a particular one of a plurality of tenant clouds of the high performance computing environment.
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.
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.