Patent Grant
9672502
Network-as-a-Service (NaaS) is a service model that allows a service provider to provide a virtual network service to a third party. In some cases, NaaS may allow the service provider to provide a network service such as a virtual private network (VPN), bandwidth on demand, custom routing, multicast protocols, a security firewall, intrusion detection and prevention, content monitoring and filtering, and/or antivirus protection.
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
A service provider, associated with a service provider network, may wish to implement a network-as-a-Service (NaaS) service model that allows the service provider to provide agile, on-demand, and/or flexible network services (e.g., virtual network services) to a service location associated with a customer. However, provisioning of network services within the service provider network may be hardware based and the service provider network may be a closed system. As such, the service provider may be forced to manually configure, monitor, update, etc. devices included in the service provider network in order to provide the network service. Moreover, updating, modifying, adjusting, etc. the network service based on a request from the customer may be difficult and time consuming (e.g., since an update would require additional manual configuration). Implementations described herein may allow virtual network functions, associated with providing network services to service locations, to be globally managed (e.g., created, inserted, configured, updated, modified, etc.) such that the network services are provided in an agile, on-demand, and/or flexible manner without the need to manually configure, monitor, and/or update physical devices in the service provider network.
As shown in
As shown by reference number 110, the business logic module may communicate with an information technology (IT) system, associated with the service provider network, to determine context information (e.g., information associated with providing the network service to the service location via the service provider network) based on the customer service order information. As shown by reference number 115, the business logic module may determine (e.g., based on the context information, based on an algorithm, based on the customer service order information, etc.) provisioning details associate with the network service. As shown by reference number 120, the business logic module may generate a service request based on the context information and the provisioning details. As shown, the service request may include information associated with the customer, information associated with configuring a virtual network function (VNF) that is to provide the network service, sizing information associated with the VNF, tuning information associated with the VNF, network insertion information associated with inserting the VNF into the service provider network, and/or other information associated with providing the network service to the service location. As shown by reference number 125, the business logic module may identify a cloud resource (e.g., one or more computing devices included in a cloud computing environment, etc.), cloud resource 1, that is to host the VNF, and may provide the service request to cloud resource 1.
As further shown in
As shown in
As shown by reference number 150, each cloud resource may provide (e.g., in real-time, on a periodic basis, etc.), to the telemetry and analytics module of the product director, the performance information and/or the analytics information determined by the cloud resources. As shown, by reference number 155 the telemetry and analytics module may receive the performance information and/or the local analytics information from each cloud resource, and may determine (e.g., based on performing global analytics based on the performance information and/or the local analytics information), that a group of VNFs (e.g., of the multiple VNFs) are to be modified (e.g., updated, reconfigured, relocated, recreated, adjusted, etc.) to assure that network services, corresponding to the group of VNFs, are adequately provided (e.g., provided in accordance with service level agreements (SLAs) associated with the network services). As shown by reference number 160, the telemetry and analytics module may provide, to the business logic module, VNF modification information associated with the group of VNFs that are to be modified.
As shown in
In this way, virtual network functions, associated with providing network services, may be globally managed (e.g., created, inserted, configured, updated, modified, etc.) such that the network services are provided in an agile, on-demand, and/or flexible manner without the need to manually configure, monitor, and/or update devices in the service provider network.
Customer device 210 may include a device capable of receiving, processing, and/or providing information (e.g., customer service order information). For example, customer device 210 may include a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a computing device (e.g., a laptop computer, a tablet computer, a handheld computer, a gaming device, etc.), a network device (e.g. Customer Premises Equipment (CPE), a router, etc.), or a similar device. In some implementations, customer device 210 may be host an application (e.g., a user input web portal, a cloud services portal, etc.), that may allow the user to provide customer service order information associated with a network service. In some implementations, customer device 210 may include a communication interface that allows customer device 210 to receive (e.g., based on user input) customer service order information associated with providing a network service to a service location. Additionally, or alternatively, customer device 210 may be capable of providing the customer service order information to another device in environment 200 (e.g., order manager 220).
Order manager 220 may include one or more devices capable of receiving, storing, processing, generating, and/or providing customer service order information. For example, order manager 220 may include a server device or a collection of server devices. In some implementations, order manager 220 may include a communication interface that allows order manager 220 to receive customer service order information from customer device 210 and/or forward the customer service order information to other devices in environment 200 (e.g., product director 230). In some implementations, order manager 220 may include a device capable of receiving the customer service order information, verifying the customer service order information, and/or authenticating a customer associated with the customer service order information.
Product director 230 may include one or more devices capable of receiving, storing, processing, generating, and/or providing customer service order information, context information associated with the customer service order information, and/or another type of information. For example, order manager 220 may include a server device or a collection of server devices. In some implementations, product director 230 may be capable of communicating with order manager 220 to receive customer service order information. Additionally, or alternatively, product director 230 may be capable of communicating with IT system 240 to determine context information associated with the customer service order information received from order manager 220. Additionally, or alternatively, product director 230 may be capable of generating a service request based on the context information received from IT system 240, and providing the service request to cloud resource 260.
In some implementations, product director 230 may include software associated with determining context information and/or provisioning details associated with customer service order information, generating a service request, determining and/or providing billing information, receiving performance information associated with a VNF, performing global analytics based on the performance information, and/or another function. For example, product director 230 may host one or more software modules, such as a business logic module, a financial logic module, a telemetry module, and/or an analytics module. In some implementations, these modules may cooperate in order to globally manage multiple VNFs operating on multiple cloud resources 260.
In some implementations, product director 230 may be associated with multiple cloud resources 260. For example, product director 230 may be configured to manage network services provided via a group of cloud resources 260. In some implementations, each product director 230 could be associated with a respective geographic region and cloud resources 260 also associated with that respective geographic region. Additionally, or alternatively, each product director 230 could be associated with a respective logical group of cloud resources 260 (e.g., a group of cloud resources 260 associated with providing network services at a particular time, a group of cloud resources 260 associated with a particular customer type, a group of cloud resources associated with providing network services within a particular price band, etc.). Additionally, or alternatively, product director 230 may be capable of identifying a particular cloud resource 260 that is to create and insert a network service associated with customer service order information received from order manager 220. In some implementations, product director 230 may be capable of receiving performance information and/or local analytics information from the multiple cloud resources 260, and performing global service assurance associated with the multiple cloud resources 260.
IT system 240 may include one or more devices capable of receiving, storing, processing, generating, and/or providing context information and/or another type of information. For example, IT system 240 may include a server device or a collection of server devices. In some implementations, IT system 240 may be capable of communicating with product director 230 to provide context information associated with customer service order information. In some implementations, IT system 240 may include one or more devices (e.g., server devices) that are configured to store context information and/or to provide the context information to product director 230.
Cloud computing environment 250 may include an environment that delivers computing as a service, whereby shared resources, services, etc. may be provided to customer device 210. Cloud computing environment 250 may provide computation, software, data access, storage, etc. services that do not require end-user (e.g., customer device 210) knowledge of a physical location and configuration of system(s) and/or device(s) that deliver the services.
As shown, cloud computing environment 250 may include a group of cloud resources 260 (referred to collectively as “cloud resources 260” and individually as “cloud resource 260”).
Cloud resource 260 may include one or more computing devices. In some implementations, cloud resource 260 may provide network services to customer device 210. The network services may use compute instances executing in cloud resource 260, storage devices provided in cloud resource 260, data transfer operations executed by cloud resource 260, etc. In some implementations, cloud resource 260 may communicate with other cloud resources 260 via wired connections, wireless connections, or a combination of wired and wireless connections. In some implementations, one or more cloud resources 260 may be assigned (e.g., by a device associated with a service provider, etc.) to receive, process, store and/or provide traffic, associated with a customer, in accordance with an agreement (e.g., a service level agreement (“SLA”)).
In some implementations, cloud resource 260 may be capable of receiving a service request associated with providing a network service, creating a VNF associated with the network service (e.g., within cloud resource 260), and inserting the VNF into service provider network 270 (e.g., such that the network service is provided via the VNF). In some implementations, cloud resource 260 may be capable of determining performance information associated with network services provided via VNFs running on cloud resource 260, and performing local service assurance based on the performance information and/or local analytics information determined by cloud resource 260.
As further shown in
VNF 262 may include one or more network functions that may be provided to or accessed by customer device 210. VNF 262 may eliminate a need to install and execute the network functions on customer device 210 and/or another device associated with customer device 210. For example, VNF 262 may include a network function associated with a firewall, a load balancer, malware detection, and/or any other network function capable of being provided via cloud computing environment 250. In some implementations, one VNF 262 may send/receive information to/from one or more other VNF 262, via virtual machine 264.
Virtual machine 264 may include a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 264 may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by virtual machine 264. A system virtual machine may provide a complete system platform that supports execution of a complete operating system (“OS”). A process virtual machine may execute a single program, and may support a single process. In some implementations, virtual machine 264 may execute on behalf of a customer (e.g., customer device 210) to provide a network service to a service location associated with the customer. In some implementations, a VNF may correspond to one or more VNFs 262, virtual machines 264, virtualized storages 266, and/or hypervisors 268.
Virtualized storage 266 may include one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of cloud resource 260. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.
Hypervisor 268 may provide hardware virtualization techniques that allow multiple virtual machines 264 to execute concurrently on a host computer, such as computing resource 260. Hypervisor 268 may present a virtual operating platform to virtual machines 264, and may manage the execution of the virtual machines 264. Multiple instances of a variety of virtual machines 264 may share virtualized hardware resources. Hypervisor 268 may provide an interface to infrastructure as a service provided by cloud computing environment 250.
Service provider network 270 may include one or more wired and/or wireless networks associated with a service provider. For example, service provider network 270 may include a cellular network, a public land mobile network (PLMN), a second generation (2G) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a long term evolution (LTE) network, and/or a similar type of network. Additionally, or alternatively, service provider network 270 may include a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), an ad hoc network, an intranet, the Internet, a fiber optic-based network, a satellite network, a cloud computing network, and/or a combination of these or other types of networks. In some implementations, service provider network 270 may include network devices (e.g., base stations, gateways, routers, modems, switches, network interface cards (“NIC”), hubs, bridges, servers, etc.) that may be configured to provide a network service to a service location associated with a customer.
The number and arrangement of devices and networks shown in
Bus 310 may include a component that permits communication among the components of device 300. Processor 320 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that interprets and/or executes instructions. Memory 330 may include a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by processor 320.
Storage component 340 may store information and/or software related to the operation and use of device 300. For example, storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive.
Input component 350 may include a component that permits device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively, input component 350 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 360 may include a component that provides output information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).
Communication interface 370 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 370 may permit device 300 to receive information from another device and/or provide information to another device. For example, communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
Device 300 may perform one or more processes described herein. Device 300 may perform these processes in response to processor 320 executing software instructions stored by a computer-readable medium, such as memory 330 and/or storage component 340. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into memory 330 and/or storage component 340 from another computer-readable medium or from another device via communication interface 370. When executed, software instructions stored in memory 330 and/or storage component 340 may cause processor 320 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number and arrangement of components shown in
As shown in
Customer service order information may include information associated with a network service to be provided to a service location via a service provider network. For example, the customer service order information may include information that identifies a customer associated with the network service (e.g., a customer name, a customer identification (ID) number, a customer username, a customer password, SLA information associated with the customer, etc.), information that identifies the network service (e.g., a name of the service, a service type of the service, etc.), information that identifies the service location (e.g., a service location name, a service location address, a service location ID number, etc.), timing information associated with the network service (e.g., a date that provisioning of the network service is to begin, a date that provisioning of the network service is to end, a time of day that the network service is to be provided, a day of the week that the network service is to be provided, etc.), and/or other information associated with network service. Additionally, or alternatively, the customer service order information may include information that identifies desired configuration information associated with the network service (e.g., a desired amount of bandwidth, a desired amount of random access memory (RAM), a desired amount of computing resources, a desired amount of memory storage, etc.). In some implementations, configuration information may be determined, by product director 230, based on the desired configuration information, as discussed below. In some implementations, the customer service order information may be associated with initiating a network service, modifying a network service, adding a network service, and/or terminating a network service.
In some implementations, the customer service order information may be based on input provided (e.g., via a user interface associated with the service provider) by the customer (e.g., a user of customer device 210). For example, the customer may wish for the service provider to initiate provisioning of the network service to the service location, and may navigate to a service provider web site (e.g., associated with order manager 220) that may be used to order the network service from the service provider. In this example, the service provider web site may include a user interface that allows the customer to provide input associated with the customer service order information. Here, the customer may provide, to customer device 210, input associated with the customer service order information, and customer device 210 may forward the customer service order information to order manager 220. Order manager 220 may verify the customer service order information and/or authenticate the customer, and may forward the customer service order information to product director 230.
As further shown in
Context information may include information associated with creating a VNF (e.g., a service virtual machine (VM) configured to run on a hypervisor) that is to provide the network service, and inserting the VNF into the service provider network. For example, the context information may include information associated with the customer (e.g., a customer name, a customer ID, a customer account number, a username, a password, etc.), information associated with the network service (e.g., a service type of the network service, a quantity of devices to be provided with the network service, etc.), network insertion information associated with inserting the VNF into the service provider network (e.g., a port identifier, routing information, virtual routing and forwarding information, etc.), or another type of information.
In some implementations, product director 230 may determine the context information based on information stored by IT system 240. For example, product director 230 may receive the customer service order information, and may send, to IT system 240, one or more requests for IT system 240 to provide the context information. IT system 240 may receive the one or more requests, may determine (e.g., based on information stored by IT system 240), the context information, and may provide the context information to product director 230. In some implementations, IT system 240 may include one or more databases that store the context information. In some implementations, product director 230 may store the context information (e.g., such that the context information may be retrieved by product director 230 at a later time). In some implementations, product director 230 may determine whether the service is available to the service location before determining the context information. For example, product director 230 may receive the customer service order information and may send, to IT system 240, a request associated with determining whether the network service is available to the service location. In this example, IT system 240 may provide, to product director 230, information indicating whether the network service is available to the service location, and product director 230 may determine (e.g., based on information provided by IT system 240) whether the network service is available to the service location, accordingly. If the network service is available at the service location, product director 230 may provide, to the customer, (e.g., via order manager 220 and/or customer device 210) an indication that the network service is available, and an estimated time (e.g., 2 hours, 3 days, etc.) associated with initiating the network service. If the network service is not available at the service location, product director 230 may provide, to the customer, an indication that the network service is not currently available, and/or may provide an estimated time (e.g., 6 months, 1 year, etc.) that the network service may be available.
As further shown in
Provisioning details, associated with the network service, may include location information associated with the network service (e.g., a geographic location of cloud resource 260 that is to provide the network service, a logical location of cloud resource 260 that is to provide the network service, etc.), timing information associated with the network service (e.g., a time of day when provisioning of the service is to be initiated, a period of time during the network service is to be provided, etc.), quality of service (QoS) information associated with the network service (e.g., a QoS level at which the network service may be provided, etc.), pricing information associated with the network service (e.g., a cost associated with provisioning of the network service), and/or another type of information.
Additionally, or alternatively, the provisioning details may include configuration information associated with the VNF that is to provide the network service, such as sizing information (e.g., an amount of computing resources, an amount of RAM, an amount of storage, etc.), tuning information (e.g., when the network service requires a non-default VNF), and/or another type of configuration information. In some implementations, product director 230 may determine the configuration information based on the desired configuration information included in the customer service order (e.g., product director 230 may determine whether or not the VNF may be configured based on the desired configuration information).
In some implementations, product director 230 may determine the provisioning details based on information associated with product director 230. For example, product director 230 may store information associated with a heuristic algorithm associated with determining the provisioning details. In this example, product director 230 may determine (e.g., based on information received from one or more cloud resources 260) real-time information associated with network services being provided by the one or more cloud resources 260. Here, product director 230 may use the customer service order information, the real-time information, the context information, and/or the heuristic algorithm to determine the provisioning details associated with the network service.
In some implementations, product director may perform blocks 420 and 430 multiple times and/or in reverse order. In other words, determining the context information and/or the provisioning details may require product director 230 to determine context information and/or provision details multiple times before a service request may be generated and provided to cloud resource 260.
In some implementations, the business logic module of product director 230 may determine the provisioning details based on information received from the financial logic module of product director 230. For example, product director 230 may receive customer service order information that identifies a maximum price that the customer is willing to pay for the network service. In this example, the business logic module may provide the customer service order information to the financial logic module. The financial logic module may determine (e.g., based on a rules engine associated with financial logic module) whether the network service may be provided at, or below, the maximum price, and/or may determine provisioning details associated with providing the network service at, or below, the maximum price, and may notify the business logic module, accordingly.
In some implementations, product director 230 may modify an existing VNF based on additional provisioning details determined by product director 230. For example, product director 230 may cause a VNF to be created on a first cloud resource 260 based on the context information and the provisioning details, and may receive (e.g., from IT system 240) additional context information (e.g., information associated with a pricing change, information associated with a planned outage, etc.) at a later time. In this example, product director 230 may receive the additional context information and may determine additional provisioning details based on the context information. Product director 230 may then determine that the VNF is to be modified (e.g., relocated, adjusted, updated, etc.) based on the additional context information and/or the additional provisioning details, and may generate an additional service request to cause the VNF to be modified accordingly.
As further shown in
A service request may include context information and/or provisioning details prepared in a format that may be used by cloud resource 260 to create and insert the VNF such that the network service is provided to the service location. In some implementations, the service request may be generated in a manner (e.g., using a particular protocol, in a particular format, etc.) such that product director 230 need only provide a single service request to cloud resource 260 (e.g., rather than providing multiple service requests) to cause cloud resource 260 to create and insert the VNF. In some implementations, the service request may include the context information and/or the provisioning details associated with the network service. Additionally, or alternatively, the service request may include the customer service order information. Additionally, or alternatively, product director 230 may generate multiple copies of a service request to allow the service request to be provided to multiple cloud resources 260.
As further shown in
In some implementations, product director 230 may provide the service request based on timing information associated with the network service. For example, the provisioning details, associated with the network service, may include timing information that identifies a time (e.g., a date that the network service is to be initiated, a period of time during which the network service is to be provided, etc.) associated with providing the network service, and product director 230 may provide the service request to cloud resource 260 based on the timing information.
In some implementations, product director 230 may identify cloud resource 260 that is to receive the service request before product director 230 provides the service request. In other words, product director 230 may identify (e.g., based on the provisioning details, based on the context information) a particular cloud resource 260, of a group of cloud resources 260 managed by product director 230, to create and insert the VNF associated with the service request. In some implementations, product director 230 may identify cloud resource 260 based on a geographic area associated with cloud resource 260. For example, product director 230 may be associated with multiple cloud resources 260, and each cloud resource 260 may be configured to provide network services for a corresponding geographic area. In this example, the service request may be associated with a network service to be provided to a service location located within a particular geographic area. As such, product director 230 may provide the service request to a particular cloud resource 260 that is configured to provide network services for the particular geographic area. Additionally, or alternatively, each product director 230 could be associated with a respective logical group of cloud resources 260 (e.g., a group of cloud resources 260 associated with providing network services at a particular time, a group of cloud resources 260 associated with a particular customer type, a group of cloud resources associated with providing network services within a particular price band, etc.) Additionally, or alternatively, product director 230 may identify cloud resource 260 in another manner (e.g., based on a quantity of remaining computing capacity of cloud resource 260, based on a speed at which cloud resource 260 is able to create and insert the VNF, based on a predicted workload growth associated with cloud resource 260, based on a planned cloud resource 260 outage, based on a semi-planned cloud resource 260 outage, etc.).
In some implementations, product director 230 may determine whether cloud resource 260, identified by product director 230, is available to provide the network service. For example, product director 230 may identify cloud resource 260 and may determine (e.g., based on performance information and/or local analytics information previously received from cloud resource 260, based on a request provided to cloud resource 260, etc.) whether cloud resource 260 has sufficient resources (e.g., processing power, RAM, memory storage space, etc.) available to provide the network service. If cloud resource 260 has sufficient computing resources available, then product director 230 may provide the service request to cloud resource 260. Alternatively, if cloud resource 260 does not have sufficient computing resources available, then product director 230 may identify another cloud resource 260 to provide the network service, and may provide the service request to the other cloud resource 260.
As further shown in
In some implementations, the indication may indicate that cloud resource 260 has successfully created and inserted the VNF associated with the service request. For example, product director 230 may provide, to cloud resource 260, a service request associated with creating and inserting a VNF. Cloud resource 260 may create the VNF and insert the VNF based on the service request (e.g., such that the network service may be provided to the service location), and may provide, to product director 230, an indication that the VNF was successfully created and inserted.
Alternatively, the indication may indicate that cloud resource 260 did not successfully create and/or insert the VNF associated with the service request. For example, product director 230 may provide, to cloud resource 260, a service request associated with creating and inserting a VNF. Cloud resource 260 may attempt to create the VNF and/or insert the VNF based on the service request, but cloud resource 260 may be unsuccessful (e.g., when cloud resource 260 experiences an error, when cloud resource 260 is unable to create and/or insert the VNF, etc.). In this example, cloud resource 260 may provide, to product director 230, an indication that the VNF was not successfully created and inserted. Product director 230 may then send another (e.g., duplicate) service request, associated with the VNF, to cloud resource 260, or may identify another cloud resource 260 to which the service request may be provided, and may provide the service request, accordingly.
In some implementations, cloud resource 260 may insert the VNF into service provider network 270 by configuring the VNF created by cloud resource 260. For example, cloud resource 260 may configure the VNF to communicate with an edge router (e.g., associated with cloud resource 260) that is configured to receive and/or provide traffic to and/or from service provider network 270. Additionally, or alternatively, cloud resource 260 may insert the VNF into service provider network 270 by configuring physical devices included in service provider network 270. For example, cloud resource 260 may insert the network service into service provider network 270 by providing information included in the service request to a router, associated with routing traffic to and/or from the service location, included in service provider network 270 (e.g., such that the router is configured to route traffic to and/or receive traffic from the VNF included in cloud resource 260, rather than receiving and/or providing the traffic directly from and/or to the service location). In other words, the VNF may be inserted into service provider network 270 such that the VNF interacts with physical devices included in service provider network 270 in order to provide the network service to the service location.
As further shown in
In some implementations, the billing notification may include information associated with initiating billing for the network service. For example, the billing information may include an indication that IT system 240 (e.g., a billing device associated with IT system 240) is to initiate billing for the network service. Additionally, or alternatively, the billing notification may include the customer service order information, the context information associated with the network service, and/or other information associated with billing for the network service.
In some implementations, the billing notification may be provided based on the indication received from cloud resource 260. For example, cloud resource 260 may provide, to the business logic module of product director 230, the indication that the VNF has been successfully created and inserted into service provider network 270. In this example, the business logic module may provide an indication that the network service has been initiated (e.g., since the VNF has been successfully created and inserted), the customer service order information, and/or the context information to the financial logic module. The financial logic module may generate a billing notification, associated with billing for the network service, and may provide the billing notification to IT system 240 (e.g., and IT system 240 may initiate billing for the network service, accordingly).
In some implementations, product director 230 may receive, from cloud resource 260, performance information and/or local analytics information, and the financial logic module of product director 230 may determine billing information associated with the network service provided by the VNF. For example, the financial logic module may receive performance information associated with the VNF, and may implement a financial rules engine that includes a billing model associated with the network service, a billing interval associated with the network service, a pricing structure associated with the network service, etc. to determine the billing information. In this example, the financial logic module may provide the billing information to IT system 240 to cause the customer to be billed for the network service. In some implementations, the financial logic module may implement customer and/or network service specific billing rules when determining the billing information.
In this way, product director 230 may generate a service request, associated with creating and inserting a VNF configured to provide a network service, determine that the VNF has been created and inserted, and provide a billing notification such that billing for the network service may be initiated.
Although
As shown in
As shown by reference number 510, the business logic module may send, to IT system 240, one or more requests for context information based on the customer service order information. As shown by reference number 515, IT system 240 may determine (e.g., based on information stored by IT system 240) the context information, and may provide, to the business logic module, responses to the one or more requests that include the context information.
As shown by reference number 520, the business logic module may receive the context information, and may determine (e.g., based on the context information, based on an algorithm, based on a geographic location of the service location, etc.) provisioning details associated with providing Firewall X to the service location. In some implementations, the order of steps between reference numbers 510 and 520 may be reversed and/or may be performed multiple times to allow the business logic module to determine the context information and/or the provisioning details associated with providing the Firewall X network service to the service location.
As shown by reference number 525, the business logic module may also generate, based on the context information and the provisioning details, a Firewall X service request associated with creating and inserting a VNF configured to provide Firewall X to the service location. As shown by reference number 530, the Firewall X service request may contain (e.g., based on the context information and the provisioning details) information associated with the customer (e.g., Username: jsmith, Account No.: A13847), configuration information associated with the VNF (e.g., Service Type: Firewall X, Edge Router: R23A), VNF sizing information (e.g., Processors: 1 CPU, RAM: 4Gb, Storage: 8 Gb), information indicating that the VNF does not require tuning (e.g., Required: NO), network insertion information (e.g., Insert @ Router: R64G, Port No. 80), and/or additional information associated with creating and/or inserting the VNF. As shown by reference number 535, the business logic module may provide the Firewall X service request to the cloud resource 260 identified by the business logic module.
For the purposes of
As indicated above,
As shown in
Performance information, associated with a VNF, may include information associated with one or more performance metrics associated with the VNF. For example, the performance information may include an amount of computing resources consumed by the VNF, an amount of RAM used by the VNF, an amount of memory storage used by the VNF, an amount of bandwidth used by the VNF, and/or another type of performance metric. In some implementations, cloud resource 260 may determine the performance information (e.g., in-real time, on a periodic basis, etc.). Local analytics information, associated with a VNF, may include information associated with analyzing the performance information associated with the VNF. For example, cloud resource 260 may determine performance information associated with the VNF, and may perform (e.g., based on an algorithm, a model, etc. stored by cloud resource 260) local analytics based on the performance information to determine local analytics information associated with the VNF. In some implementations, the performance information and/or the local analytics information may be determined at different time granularities (e.g., first performance information, associated with a first VNF, may be determined every 1 second, while second performance information, associated with a second VNF, may be determined every 5 seconds, etc.).
In some implementations, product director 230 may receive the performance information and/or the local analytics information as cloud resource 260 determines the performance information and/or the local analytics information (e.g., in real-time), on a periodic basis (e.g., every 5 seconds, every 30 seconds, etc.), or in another manner. In some implementations, product director 230 may receive performance information and/or local analytics information from multiple cloud resources 260 (e.g., when product director 230 is configured to manage the multiple cloud resources 260). Additionally, or alternatively, product director 230 may receive performance information and/or local analytics information associated with multiple VNFs.
As further shown in
In some implementations, product director 230 may determine that the VNF is to be modified based on the performance information and/or the local analytics information received from cloud resource 260. For example, product director 230 may receive, from multiple cloud resources 260, performance information and local analytics information associated with multiple VNFs. Product director 230 may perform (e.g., using a global analytics algorithm, a global analytics model, etc.) global analytics based on the performance information and the local analytics information to determine global analytics information (e.g., predictive workload balancing, usage trends, predictive billing information, dynamic pricing information, etc.). In this example, the global analytics information may indicate a manner in which one or more of the multiple VNFs are to be modified in order to assure that the multiple VNFs are adequately providing their respective network services. In some implementations, product director 230 may perform global analytics based on the performance information, the local analytics information, environmental information, geo-political information, and/or information associated with one or more physical devices included in service provider network 270. In some implementations, product director 230 may determine modification information (e.g., information indicating a manner in which a VNF is to be modified) based on the global analytics information. Additionally, or alternatively, the global analytics information may be provided to another device associated with service provider network 270.
As further shown in
In some implementations, product director 230 may cause cloud resource 260 to modify the VNF. For example, product director 230 may cause cloud resource 260 to modify a configuration of the VNF, relocate the VNF (e.g., to another computing resource associated with cloud resource 260), recreate the VNF (e.g., on another cloud resource 260), or otherwise change, adjust, or alter the VNF.
In some implementations, product director 230 may cause the VNF to be modified by sending a service request to cloud resource 260 associated with the VNF. For example, the telemetry and analytics module of product director 230 may determine (e.g., based on performing global analytics) modification information associated with the VNF, and may provide the modification information to the business logic model module of product director 230. The business logic module may receive the modification information, may determine stored context information and/or provisioning details associated with the VNF (e.g., when the business logic model is configured to store context information and/or the provisioning details when initially causing the VNF to be created and inserted), and may generate a new service request, associated with the VNF, based on the modification information and the stored context information. The business logic module may then provide the new service request to cloud resource 260 associated with the VNF (e.g., or to another cloud resource 260 when the telemetry and analytics module determines that the VNF is to be recreated on another cloud resource 260). Cloud resource 260 may receive the new service request and may act, accordingly.
In this way, product director 230 may determine whether network services, provided by VNFs running on cloud resources 260 managed by product director 230, are being adequately provided, and may cause the VNFs to be modified accordingly. In other words, product director 230 may globally manage network services being provided across multiple cloud resources 260.
Although
As shown in
As shown by reference number 720, the telemetry and analytics module may receive the performance information from each cloud resource, and may determine that none of the VNFs require modification (e.g., since each cloud resource is operating below 100% capacity).
For the purposes of
As shown by reference number 740, the telemetry and analytics module may determine that cloud resource X and cloud resource Z are still operating below 100% capacity, and may determine (e.g., since no cloud resource Y performance information was received), that cloud resource Y has failed and that VNF D and VNF E are no long running on cloud resource Y. As further shown, the telemetry and analytics module may determine that VNF D and VNF E are to be recreated (e.g., since the network services associated with VNF D and VNF E are not being provided). As shown by reference number 745, the telemetry and analytics module may determine (e.g., by performing global analytics based on the cloud resource X and cloud resource Z performance information) that VNF D is to be recreated on cloud resource Z and that VNF E is to be recreated on cloud resource X, and may provide modification information, associated with recreating VNF D and VNF E, to the business logic module of product director 230.
As shown in
As indicated above,
Implementations described herein may allow virtual network functions, associated with providing network services, to be globally managed (e.g., created, inserted, configured, updated, modified, etc.) such that the network services are provided in an agile, on-demand, and/or flexible manner without the need to manually configure, monitor, and/or update devices in the service provider network.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. For example, product director 230 may be capable of simulating the creation and/or insertion of a VNF into the service provider network to determine where a network service will be provisioned without causing the VNF to be created or inserted (e.g., in order to determine pricing information associated with the network service). Similarly, product director 230 may provided with performance information associated with simulated, planned, and/or semi-planned outages associated with one or more cloud resources 260 in order to predict re-distribution of network services among the one or more cloud resources 260.
As used herein, the term component is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software.
To the extent the aforementioned embodiments collect, store or employ personal information provided by individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage and use of such information may be subject to consent of the individual to such activity, for example, through well known “opt-in” or “opt-out” processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.
It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based on the description herein.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20040210895 | Esfahany | Oct 2004 | A1 |
| 20120178414 | Fiatal | Jul 2012 | A1 |
| 20130210464 | Mittal | Aug 2013 | A1 |
| 20130346465 | Maltz | Dec 2013 | A1 |
| Entry |
|---|
| Wikipedia, “Network as a service” http://en.wikipedia.org/wiki/Network—as—a —service, Sep. 16, 2013, 3 pages. |
| Harish Vadada, “Network as a Service (NaaS)”, http://www.telecom-cloud.net/network-as-a-service/, Jul. 16, 2011, 15 pages. |
| Wikipedia, “Network Functions Virtualization”, http://en.wikipedia.org/wiki/Network—Functions—Virtualization, Apr. 24, 2014, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150326448 A1 | Nov 2015 | US |
