Abstract: A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.

Abstract: A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.

Abstract: A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.

Abstract: A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.

Abstract: A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.

Abstract: When a virtualized service platform encounters a catastrophic fault, an orchestrator may instantiate new virtual machines instances to deploy additional capacity in other cloud locations to handle failover storms. After the network fault is fixed and service returns to normal condition, these additional VM instances may be removed from the platform and cloud resources may be released. The system may minimize the resource over-provisioning and may continue to support geographical redundancy or dynamic scaling in a large-scale service network.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: A system may assist in moving a communication session in a stable state from a virtual network function serving that communication session to another virtual network function at that same site or another site, such as another cloud data center.

Abstract: Concepts and technologies are disclosed herein for message flow management for virtual networks. A processor can identify a target virtual network function instance that is to be taken offline. The processor can change a status associated with the target virtual network function instance to indicate it being taken offline. The processor can start a graceful shutdown timer to trigger shutdown of the target virtual network function instance. The processor can identify external interfaces and a peer network function that identifies the target virtual network function instance as a next hop. The processor can obtain, for the target virtual network function instance and the peer network function instance, a snapshot that identifies configuration data for the target virtual network function instance and the peer network function instance and can generate a command to trigger a shutdown of the target virtual network function instance.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: Concepts and technologies are disclosed herein for message flow management for virtual networks. A processor can identify a target virtual network function instance that is to be taken offline. The processor can change a status associated with the target virtual network function instance to indicate it being taken offline. The processor can start a graceful shutdown timer to trigger shutdown of the target virtual network function instance. The processor can identify external interfaces and a peer network function that identifies the target virtual network function instance as a next hop. The processor can obtain, for the target virtual network function instance and the peer network function instance, a snapshot that identifies configuration data for the target virtual network function instance and the peer network function instance and can generate a command to trigger a shutdown of the target virtual network function instance.

Abstract: Concepts and technologies are disclosed herein for message flow management for virtual networks. A processor can identify a target virtual network function instance that is to be taken offline. The processor can change a status associated with the target virtual network function instance to indicate it being taken offline. The processor can start a graceful shutdown timer to trigger shutdown of the target virtual network function instance. The processor can identify external interfaces and a peer network function that identifies the target virtual network function instance as a next hop. The processor can obtain, for the target virtual network function instance and the peer network function instance, a snapshot that identifies configuration data for the target virtual network function instance and the peer network function instance and can generate a command to trigger a shutdown of the target virtual network function instance.

Abstract: Virtual machines may have external interfaces (E-VMs) and VMs with internal interfaces (I-VMs). A control system may automatically scale the quantity of I-VMs based on traffic demand, among other things.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: Aspects of the subject disclosure may include, for example, a system that detects a request to reattach to a communication network to update a registration between a wireless communication system and the communication network while the wireless communication system is connected to a session border controller of the communication network. The system delays a release of bearer communications with the communication network responsive to the request to reattach to the communication network not being urgent. Other embodiments are disclosed.

Abstract: Concepts and technologies are disclosed herein for message flow management for virtual networks. A processor can identify a target virtual network function instance that is to be taken offline. The processor can change a status associated with the target virtual network function instance to indicate it being taken offline. The processor can start a graceful shutdown timer to trigger shutdown of the target virtual network function instance. The processor can identify external interfaces and a peer network function that identifies the target virtual network function instance as a next hop. The processor can obtain, for the target virtual network function instance and the peer network function instance, a snapshot that identifies configuration data for the target virtual network function instance and the peer network function instance and can generate a command to trigger a shutdown of the target virtual network function instance.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.

Abstract: A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.