Patent Description:
In today's modern computing world, more and more components are being virtualized in a cloud environment to save capital expenditure for various entities, such as companies, public institutions, government agencies, individuals, and the like. To improve efficiency while conserving resources, entities are gradually allowing third party providers to maintain cloud infrastructure for hosting subscribers' virtual as well as physical components. A cloud or cloud provider, also known as cloud computing or a cluster of servers, becomes viable when entities need to increase their computing capacity or new features without investing in substantial amount of new infrastructure, personnel, hardware and/or software. It should be noted that typical third party or public cloud infrastructure providers includes, but not limited to, Amazon™, Google™, RackSpace™, Predix™, and the like. For example, a cloud provider supplies cloud computing which can be subscription-based or pay-per-use service accessible over the Internet.

While some components or devices can be virtualized, the physical machines with hardware components are still often placed in the vicinity of premise(s), such as user premises, institutional laboratories, developing/testing sites, and/or manufacturing facilities. With voluminous hardware systems, software systems, and virtual systems coupling to various public clouds and private clouds, the typical network communication becomes more sophisticated and difficult to maintain efficiently. A problem associated with a conventional cloud environment is that multiple hops may be required before reaching to a targeted service component(s) or provider(s).

<CIT> describes a process capable of automatically establishing a secure overlay network ("SON") across different clouds. <CIT> describes a network system using a firewall dynamic control method. <CIT> describes a proxy-based two-way web-service router gateway.

The invention is defined by the independent claims; the dependent claims define particular embodiments of the invention. In an aspect, a method for facilitating network communication is provided as defined in claim <NUM>. In another aspect, an apparatus configured to facilitate network communication is provided as defined in claim <NUM>. One example of the present disclosure discloses a process capable of facilitating network communication using forwarders or vforwarders connected through an overlay network. The process, in one aspect, is able to receive a packet stream or network traffic from a customer premise equipment ("CPE") using a first point-to-point ("PTP") connection via the overlay network. After identifying the service component able to provide a network function ("NF") indicated by the packet stream, at least a portion of the packet stream is forwarded to the service component via a second PTP connection through the overlay network according to a set of predefined requirements. Upon receipt of the processed packet stream from the service component, the processed packet stream is forwarded to another forwarder or vforwarder via a hop-to-hop ("HTH") link through the overlay network in accordance with the processed packet stream.

Additional features and benefits of the exemplary embodiment(s) of the present invention will become apparent from the detailed description, figures and claims set forth below.

The exemplary embodiment(s) of the present invention will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the invention, which, however, should not be taken to limit the invention to the specific embodiments, but are for explanation and understanding only.

Exemplary embodiment(s) of the present invention is described herein in the context of a method, device, and apparatus for processing network traffic using forwarders coupled to an overlay network in a cloud environment.

Those of ordinary skills in the art will realize that the following detailed description of the exemplary embodiment(s) is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the exemplary embodiment(s) as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.

In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be understood that in the development of any such actual implementation, numerous implementation-specific decisions may be made in order to achieve the developer's specific goals, such as compliance with application-and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be understood that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skills in the art having the benefit of embodiment(s) of this disclosure.

Various embodiments of the present invention illustrated in the drawings may not be drawn to scale. Thus, the drawings may not depict all of the components of a given apparatus (e.g., device) or method.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skills in the art to which the exemplary embodiment(s) belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and this exemplary embodiment(s) of the disclosure.

The term "system" is used generically herein to describe any number of components, elements, sub-systems, devices, packet switch elements, packet switches, access switches, routers, networks, computer and/or communication devices or mechanisms, or combinations of components thereof. The term "computer" includes a processor, memory, and buses capable of executing instruction wherein the computer refers to one or a cluster of computers, personal computers, workstations, mainframes, or combinations of computers thereof.

IP communication network, IP network, or communication network means any type of network having an access network able to transmit data in the form of packets or cells, such as ATM (Asynchronous Transfer Mode) type, on a transport medium, for example, the TCP/IP or UDP/IP type. ATM cells are the result of decomposition (or segmentation) of packets of data, IP type, and those packets (here IP packets) comprise an IP header, a header specific to the transport medium (for example UDP or TCP) and payload data. The IP network may also include a satellite network, a DVB-RCS (Digital Video Broadcasting-Return Channel System) network, providing Internet access via satellite, or an SDMB (Satellite Digital Multimedia Broadcast) network, a terrestrial network, a cable (xDSL) network or a mobile or cellular network (GPRS/EDGE, or UMTS (where applicable of the MBMS (Multimedia Broadcast/Multicast Services) type, or the evolution of the UMTS known as LTE (Long Term Evolution), or DVB-H (Digital Video Broadcasting-Handhelds)), or a hybrid (satellite and terrestrial) network.

One aspect discloses a network process configured to facilitate network communication between various network services and consumers using forwarders or vforwarders coupled to an overlay network. The process, in one aspect, is able to receive a packet stream or network traffic from a customer premise equipment ("CPE") using a first point-to-point ("PTP") connection via the overlay network. After identifying the service component able to provide a network function ("NF") indicated by the packet stream, at least a portion of the packet stream is forwarded to the service component via a second PTP connection through the overlay network according to a set of predefined requirements. Upon receipt of the processed packet stream from the service component, the processed packet stream is forwarded to another forwarder or vforwarder via a hop-to-hop ("HTH") link through the overlay network in accordance with the processed packet stream.

To simplify forgoing discussion, the term "PTP" is used to describe logical connection between a forwarder and a service component, and the term "HTH" is used to describe logical connection between forwarders. The terms "forwarder" and "Vforwarder" are referred to the same or similar apparatus. In one aspect, Vforwarder (or forwarder) is a VM. Alternatively, Vforwarder is a physical machine. A function of Vforwarder is to route network traffic more directly and efficiently. In one embodiment, Vforwarders are connected through the overlay network situated between CPEs and service components using a hop-to-hop mechanism to navigate the traffic more efficiently.

<FIG> is a block diagram <NUM> illustrating an overlay network containing multiple forwarders situated between network components in a cloud environment. Diagram <NUM> includes a network infrastructure or platform layer or network <NUM>, application layer or network <NUM>, and overlay network <NUM>. Network infrastructure or infrastructure layer <NUM> includes hardware and software resources providing network connectivity, communication, and operations/management of a communications network. In one example, network infrastructure <NUM> includes various networking components, such as routers <NUM>, switches <NUM>, satellite hub <NUM>, Internet platform <NUM>, cloud servers <NUM>, and the like. A function of infrastructure layer <NUM> is to provide network traffic communication between users, processes, applications, services, and the Internet. It should be noted that the underlying concept would not change if one or more blocks (or devices) were added to or removed from diagram <NUM>.

Application layer <NUM>, in one embodiment, includes one or more customer premises equipments ("CPEs") <NUM>, servers <NUM>, portable devices <NUM>, wireless devices <NUM>, and/or cloud emulators <NUM>. CPE <NUM>, in one example, can be a network device or user equipment ("UE") located at users' or subscribers' premises and is connected to a communications network. For example, CPE <NUM> can be a telephone, router, switch, residential gateway (RG), set-top box, smartphone, and the like. Application layer <NUM>, in one aspect, employing cloud software such as software as a service ("SaaS") facilitates the cloud environment. To access cloud based various applications, devices in application layer <NUM>, in one embodiment, use application interfaces, web browsers, and/or program interfaces to reach various client or consumer devices via Vforwarders.

Overlay network <NUM>, situated between infrastructure layer <NUM> and application layer <NUM>, is organized to include a group of forwarders or Vforwarders <NUM>-<NUM>. Forwarders or vforwarders <NUM>-<NUM>, hereinafter referred to as vforwarders ("VFds"), are interconnected via HTH east-west ("EW") channels <NUM>-<NUM>. In one embodiment, VFds <NUM>-<NUM> are coupled to various service components and devices <NUM>-<NUM> via PTP south-north ("SN") channels <NUM>-<NUM>. A PTP connection such as channel <NUM> or <NUM> is a network communication link or connection between two nodes such as VFd <NUM> and router <NUM> as a service component via PTP link <NUM>. During an operation, after VFd <NUM>, for example, forwards a packet flow to router <NUM> via PTP link <NUM>, VFd <NUM> subsequently receives the result of routing process from router <NUM> via PTP link <NUM>. Depending on the nature of the packet flow and the result of processing, VFd determines the next hop to reach the next VFd. For example, after receiving the result of packet processing from router <NUM>, VFd <NUM> hops to VFd <NUM> or forwarding the traffic to VFd <NUM> whereby the traffic or packet flow reaches the Internet <NUM> via PTP channel <NUM>.

An overlay network can be considered as a communication network or a computer network which is established on top of another network. For example, a secure overlay network resides on top of another existing network such as the Internet. Nodes in the overlay network are considered as being connected by virtual, physical, and/or logical links. Each link may correspond to a path which facilitates a traffic flow to travel through physical or logical links.

Diagram <NUM> illustrates a network layout containing multiple CPEs <NUM>-<NUM>, service components120-<NUM>, and VFds <NUM>-<NUM> capable of improving network efficiency using PTP VFds. CPEs <NUM>-<NUM> are able to access the communications network via PTP connections. Service components <NUM>-<NUM>, in one example, provide various NFs for routing and processing incoming packet streams. Overlay network <NUM>, in one aspect, is organized with multiple interconnected VFds and is used to link between CPEs <NUM>-<NUM> and service components <NUM>-<NUM>. Every VFd, in one embodiment, includes at least one lookup table containing a set of HTH links used for hoping between VFds <NUM>-<NUM>.

Each VFd, in one embodiment, includes a function definition table indicating various functions associated with various service components such as router <NUM>. For instance, VFd such as VFd <NUM> includes a service directory table indicating addresses associated with various service components. VFd <NUM>, in one example, includes at least one PTP port used to connect to a PTP connection such as PTP connector <NUM> for communicating with service component <NUM>. Note that VFd is operable to forward a packet stream to one of service components point-to-point based on a predefined requirement of load balance.

VFds <NUM>-<NUM>, in an exemplary embodiment, are configured in such a way that each VFd is one hop away from any other VFd. For example, a packet stream at VFd <NUM> can hop to VFd <NUM> via HTH connections <NUM> and <NUM> via a hop connector <NUM>. In one embodiment, VFds <NUM>-<NUM> can be hardware systems, virtual machines ("VMs"), or a combination of hardware systems and VMs. One advantage of using VFds <NUM>-<NUM> organized in overlay network <NUM> is that it can enhance overall performance in a cloud computing environment.

A cloud or cloud environment is cloud computing which includes a cluster of servers residing in one or more clouds. The servers in the cloud are able to support or host multiple VMs running simultaneously. Cloud computing basically uses various resources including hardware, firmware, and software to deliver computing service. A benefit of using a cloud is that it shares resources with other users so that resources can be used more efficiently. Another benefit of using a cloud is that it is able to dynamically reallocate resources on demand.

A cloud can be a private cloud, a public cloud, or a hybrid cloud. A private cloud such as overlay network <NUM> or infrastructure layer <NUM> can be operated for a purpose of an individual corporation, organization, and/or entity. The private cloud, in one example, can provide cloud-computing services over a network. Note that a private cloud can be managed or hosted internally, externally, or both. A public cloud is open to the public providing computing services over a communication network. A public cloud, which is also known as community cloud, can be free or based on a fee schedule in exchange of clouding service. For example, exemplary public cloud services providers can be Amazon web services (AWS)™, Microsoft™, Apple™, and/or Google™ and are able to host services across the Internet. In one example, infrastructure layer <NUM> or a portion of infrastructure layer <NUM> may be operated by a public cloud.

A VM is a software implementation of a particular computer system that processes tasks like a real physical machine. For instance, VM can be configured to execute instructions in a way that follows the emulated computer architecture. A server or a cluster of servers containing specialized hardware and software may be used to provide a VM environment that allows multiple VMs to be operated simultaneously. VM includes system virtual machines and process virtual machines. The system virtual machine includes a set of functions operating based on an operating system. The process virtual machine is able to execute a program based on platform-independent program execution environment. Instance means a VM configured to execute program based on the emulation of a real machine or apparatus.

An advantage of using VFds organized in an overlay network is that while VFds are invisible to the network functions, VFds can also provide load balance between the service components whereby the overall network performance can be improved.

<FIG> is a block diagram <NUM> illustrating an exemplary process using overlay links between input/output ("I/O") components and service components. Diagram <NUM> includes service components <NUM>-<NUM>, input management component <NUM>, output component <NUM>, and eight (<NUM>) overlay links. Diagram <NUM> illustrates a process of Function A and Function B defined and referenced in the tables such as a functional definitions table and services directory table. It should be noted that the underlying concept would not change if one or more blocks (or components) were added to or removed from diagram <NUM>.

In operation, upon receiving a request indicating Function A, a service chain, including service <NUM> component <NUM> followed by service <NUM> component <NUM> followed by service <NUM> component <NUM> followed by service n component <NUM>, is established and managed by a function translation component, not shown in <FIG>. The function translation component, in one example, provides foregoing services to a service translation component, not shown in <FIG>. The service translation component, for instance, looks up corresponding information for each of those services in a services directory table and subsequently passes the information to an overlay component. The overlay component, in one example, uses the information of services to create an operation of service chain. For example, upon a first overlay (or overlay <NUM>) from input management component <NUM> to service <NUM> component <NUM>, a second overlay (or overlay <NUM>) is established from service <NUM> component <NUM> to service <NUM> component <NUM>. After a third overlay (or overlay <NUM>) from service <NUM> component <NUM> to service <NUM> component <NUM>, a fourth overlay (or overlay <NUM>) is connected from service <NUM> component <NUM> to service n component <NUM>. A fifth overlay (or overlay <NUM>) is created from service n component <NUM> to output component <NUM>.

Note that the information obtained from the service translation component provides information, such as keys, directions, et cetera, for making the connections via the overlays. For example, the information may enable the overlay component to create multiple overlays passing through firewalls at one or more service components.

Alternatively, the overlay information relating to Function B, including service <NUM> component <NUM> followed by service <NUM> component <NUM>, is stored in the function definitions table. Upon receipt of a request of Function B, the overlay component creates overlays <NUM>, <NUM>, and <NUM> to produce the processed data as illustrated in diagram <NUM>.

<FIG> is a block diagram <NUM> illustrating an exemplary overlaying operation using VFds. Diagram <NUM> is similar to diagram <NUM> shown in <FIG> except that diagram <NUM> includes VFds <NUM>-<NUM> and links <NUM>-<NUM> wherein links <NUM>-<NUM> includes HTH connections and PTP links. Diagram <NUM> illustrates a process of Function A and Function B which is defined and referenced multiple tables such as functional definitions table and services directory table. It should be noted that the underlying would not change if one or more blocks (or devices) were added to or removed from diagram <NUM>.

In one aspect, diagram <NUM> illustrates an example of creating the overlays utilizing "Vforwarders" or VFds <NUM>-<NUM>. Each VFd can be configured to send received data or packet flows to a particular service component such as service <NUM> component <NUM> and then, upon receiving the processed data back from the service component such as service <NUM> component, VFd such as VFd <NUM> forwards the processed data to another VFd such as VFd <NUM>. The VFds interconnecting information, in one aspect, is included in one or more routing tables. In one example, the overlay component can create VFd(s) based on network application, and becomes part of control plane of a virtual network.

As shown in <FIG>, Function A can be carried out by four VFds <NUM>-<NUM>. For example, VFd <NUM> (or <NUM>st Vforwarder) for performing Function A routes its incoming data to service <NUM> component <NUM>, and routes returned data or processed data from service <NUM> component <NUM> to VFd <NUM> (or 2nd Vforwarder). Note that input management component <NUM> sends incoming data corresponding to Function A to VFd <NUM> (or 1st Vforwarder). Alternatively, VFd <NUM> (or 1st Vforwarder) is configured to intercept incoming data at input management component <NUM> corresponding to Function A. VFd <NUM> (or 2nd Vforwarder) routes received data to service <NUM> component <NUM>, and subsequently routes data returned (or processed data) from service <NUM> component <NUM> to VFd <NUM> (or 3rd Vforwarder). VFd <NUM> (or 3rd Vforwarder) facilitates to route the received data to service <NUM> component <NUM>, and subsequently routes the returned data from service <NUM> component <NUM> to VFd <NUM> (or 4th Vforwarder). VFd <NUM> (or 4th Vforwarder) is configured to route received data to service n component <NUM>, and route data returned from service n component <NUM> to output component <NUM>.

<FIG> is a block diagram <NUM> illustrating an exemplary network operation between components using forwarders and overlay network. Diagram <NUM> includes a CPE <NUM>, SMAC <NUM>, acceleration <NUM>, traffic conditioner <NUM>, classifier <NUM>, border router <NUM>, and Internet <NUM>. In an example, a network controller uses VFd and overlay network to generate a dynamic service chaining based on CPE and/or traffic flow to enhance network performance. It should be noted that the underlying concept would not change if one or more components (or devices) were added to or removed from diagram <NUM>.

In an example, VFds organized by overlay network enables to establish a dynamic service chaining. The dynamic service chaining provides various forwarding decisions based on CPE and/or individual traffic flow (or packet stream). For example, traffic path <NUM> follows a different path than a more traditional path <NUM> through the network when the flow is already classified. Since the flow or traffic flow is not TCP (Transmission Control Protocol), acceleration or acceleration component <NUM> can be skipped. The static service chain, in contrast, creates a path <NUM> allowing the packets flow to pass through every component as such components <NUM>-<NUM>. Dynamic service chaining using VFds, point to point access, hop to hop connection, and overlay network to optimize efficiency of packet flow(s) through a network. An advantage of using the dynamic service chaining is that it can dynamically insert or remove one or more service components along the static service chain path. For service insertion, an NF, for example, can explicitly request traffic to match with certain predefined criteria before redirecting. For service removal, an NF can, for example, explicitly request to skip according to certain criteria.

For example, acceleration <NUM> can request all UDP (User Datagram Protocol) traffic to skip acceleration <NUM>. VFd tables at traffic conditioner <NUM>, in one aspect, can be programmed for packets to be sent to SMAC for FN. Similarly, VForwarder tables at SMAC may be programmed for packets to be sent to traffic conditioner <NUM> for all UDP traffic. Dynamic service chaining, in one example, requires application level integration. A way to implement dynamic service chaining independently from IaaS is to implement the overlay scheme. For example, after a packet is first decapsulated, header fields of packet(s) are looked up.

An advantage of using dynamic service chaining is that it can dynamically add and/or remove services. Another benefit of using dynamic service chaining is that it can locate and remove failed nodes or service components.

<FIG> is a block diagram <NUM> illustrating exemplary forward table identifying next hop. Diagram <NUM> includes a lookup table <NUM> and a next-hop table <NUM>. In one aspect, lookup table <NUM> includes lookup keys <NUM>-<NUM> which point to next hops <NUM>-<NUM>. For example, a forwarding device or VFd uses a key to lookup table <NUM> which will result a next-hop. The key can be a MAC address for L2 devices or an IP address for L3 devices. The next hop can be a MAC address or a VXLAN tunnel. Tables <NUM>-<NUM>, in one example, are programmed by an entity in the control plane such as network orchestrator or network manager.

<FIG> is a block diagram <NUM> illustrating exemplary forwarders or VFds in accordance with an example. Diagram <NUM> includes VFds <NUM>-<NUM>, NFs <NUM>-<NUM>, and links <NUM>-<NUM>. In one aspect, the network functions such as NFs <NUM>-<NUM> are connected together using VFd based dynamic service chain. Depending on the applications, VFd can be implemented as a kernel module as part of the hypervisor. Alternatively, VFd can be an application integrated with a third party forwarding stack (6wind) or resides in a VM in a cloud environment.

Each VFd has two types of interfaces, namely East-West ("EW") path or link and North-South ("NS") path or link. EW path handles or carries traffic that comes from another VFd which is a hop-by-hop encapsulated overlay. Each E-W link or interface can be different. For example, a different overlay tunnel encapsulation can be created in place of VXLAN. NS link or encapsulation facilitates network traffic from a forwarder node to an FN node. The NF node can be a virtual or physical machine.

<FIG> is a block diagram <NUM> illustrating network controller and VFds in accordance with an example. Diagram <NUM> includes an orchestrator <NUM>, network controller <NUM>, NF <NUM>, and VFd <NUM>. Orchestrator <NUM> arranges, coordinates, and manages one or more virtual networks ("VNs") based on users' requests. In addition to virtualization, orchestrator <NUM> is able to provide other network related functions, such as provisioning, workflows, flexible resource allocation, billing, metering, accounting, policies, and user interfaces. To improve network performance, orchestrator <NUM>, in one embodiment, is able to scale up or scale down based on demand based on the performance of VN. The terms "orchestrator," "network orchestrator," and "orchestrator of network," mean the same apparatus and they can be used interchangeably.

Each of NFs <NUM> is assigned to a lookup table so that its load distribution can be managed through the forwarding process. NFs <NUM>, in one example, are in a cluster or group. The traffic for a particular flow needs to get to the right NF Virtual/Physical Entity. VFd lookup table, in one example, may be used to load requests amongst individual members of the NF cluster. Affinity based load balancing has to be facilitated by the NF cluster master via entries at the previous hop.

Diagram <NUM> also includes a network controller protocol <NUM> which is a distribution protocol used for forwarding network traffic. In one aspect, VFd tables are programmed based on forwarding advertisements from NFs. Network controller <NUM> monitors status of corresponding NFs and publishes withdraw messages when an NF(s) becomes unavailable.

<FIG> is a block diagram illustrating an exemplary VFd table <NUM>. Table <NUM> includes a lookup table <NUM>, location ID table <NUM>, nexthop table <NUM>, and incoming port <NUM>. Table or forwarding table <NUM> which resides in VFd is used for traffic forwarding. The following table illustrates exemplary content in a VFd table such as table <NUM>.

<FIG> is a block diagram <NUM> illustrating an exemplary forwarding process using tables. Diagram <NUM> includes a data processing system, definition sub-system <NUM>, and build sub-system <NUM>. Note that the data processing system is similar to the system shown in diagram <NUM> of <FIG>. Definition subsystem <NUM> includes functions update component <NUM>, services update component <NUM>, function definitions table <NUM>, and services directory table <NUM>. Build sub-system <NUM> includes a function translation component <NUM>, service translation component <NUM>, and overlay component <NUM>. It should be noted that the underlying concept would not change if one or more blocks (or tables) were added to or removed from diagram <NUM>.

The data processing system includes an input management component <NUM> for receiving data (e.g., in the form of packets), an output component <NUM> for outputting the processed data, service components <NUM>-<NUM> for providing various functions. Each service component is configured to provide a particular service (e.g., a particular data processing) for data received at input management component <NUM>.

In an example, a function management system includes a definitions sub-system <NUM> and a build sub-system <NUM>. Definitions sub-system <NUM> includes a services directory table <NUM>, a functional definitions table <NUM>. Services directory table <NUM>, in one example, stores information identifying and defining available services (e.g., Service Components deployed in the data processing system). For example, a service identifier identifies a service based on information contained in tables <NUM> or <NUM>. Table <NUM>, for example, contains an address of an input port for a service component within the data processing system. Permissions and/or restrictions on any service(s) (e.g., list(s) of other services with which the service can (or cannot) communicate) can also be listed in table <NUM>. Table <NUM>, in one aspect, contains keys or other information allowing a connection to be made through a service component's firewall for quick access with minimal authentication.

Function definitions table <NUM>, in one aspect, stores information identifying and defining available functions that can be performed by the data processing system for the data received by input management component <NUM>. For example, a function identifier uniquely identifies a function. A dynamic service chain (e.g., a sequence of a sub-set of the services in the services directory table) for performing the function can be included in table <NUM>. It should be noted that definitions sub-system <NUM> also includes a functions update component for adding, deleting, and/or modifying functions.

Build sub-system <NUM> includes function translation component <NUM>, service translation component <NUM>, and overlay component <NUM>. Function translation component <NUM>, in one aspect, receives a function request and retrieves corresponding service chain from function definitions table <NUM> in accordance with the function request. The function request can also identify the data to be processed in accordance with the requested function.

Service translation component <NUM> is configured to receive a service chain from function translation component <NUM> and, for each service, component <NUM> retrieves information corresponding to the service from services directory table <NUM>. Overlay component <NUM>, in one aspect, receives data from service translation component <NUM> for carrying out requested services. Note that multiple connections (e.g., network overlays) may be created from input management component <NUM> through a sequence of services to output component <NUM>.

<FIG> is a block diagram <NUM> illustrating a VFd infrastructure using VFds and network controller in accordance with an example. Diagram <NUM> includes a network controller <NUM>, edge router <NUM>, data center <NUM>, Tor (The Onion Router) <NUM>, and VFds <NUM>. While data center <NUM> manages cloud data storage, Tor is used to manage network traffic through worldwide, private, and/or public networks. To manage virtual entities ("VEs"), an infrastructure overlay or overlay network <NUM> is used to communicate with VEs. Network controller <NUM>, in one aspect, builds a dynamic service chaining overlay <NUM> to manage VFds <NUM>. To communicate with data center <NUM>, VFds <NUM> establish underlay component <NUM> to communicate with Tor <NUM>. It should be noted that the underlying concept would not change if one or more blocks (or devices) were added to or removed from diagram <NUM>.

<FIG> is a block diagram <NUM> illustrating an overlay network to pass through firewalls between clouds in accordance with the claimed invention. Diagram <NUM> includes a service registry <NUM>, public cloud <NUM>, and private cloud <NUM>. While public cloud <NUM> includes service consumer <NUM>, private cloud <NUM> includes service provider <NUM>. To secure network, firewalls <NUM>-<NUM> are created in clouds <NUM>-<NUM>, respectively. To provide an automatic and smooth communication, an overlay component is used to establish an automatic ("auto") overlay channel <NUM>. It should be noted that the underlying concept of the exemplary embodiment(s) of the present invention would not change if one or more blocks (or devices) were added to or removed from diagram <NUM>.

The overlay component, in one example, employs one or more VFds for automatic opening firewalls once auto overlay channel <NUM> is established. A function of auto overlay channel <NUM> is to facilitate network communication efficiently and smoothly between clouds <NUM>-<NUM> with minimal authentication. For example, upon identifying cloud <NUM> containing firewall <NUM> and cloud <NUM> having firewall <NUM>, the overlay component, which can be managed and/or operated by the network controller or network orchestrator, is able to establish an auto overlay channel <NUM> between clouds <NUM>-<NUM> using service discovery as well as registration. According to the claimed invention, auto overlay channel <NUM> generates openings at firewalls <NUM>-<NUM> in response to the service registration for facilitating data passage more freely and quickly between clouds <NUM>-<NUM>. For example, upon initial authentication and registration in service registry <NUM>, an auto overlay channel <NUM> is established. After establishing auto overlay channel <NUM>, subsequent authentication for data transmission and/or transfer between firewall protected clouds <NUM>-<NUM> will be minimized.

The exemplary aspect of the present invention includes various processing steps, which will be described below. The steps of the aspect may be embodied in machine, router, or computer executable instructions. The instructions can be used to create a general purpose or special purpose system, which is programmed with the instructions, to perform the steps of the exemplary aspect of the present invention. Alternatively, the steps of the exemplary aspect of the present invention may be performed by specific hardware components that contain hard-wired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

<FIG> is a flowchart <NUM> illustrating an exemplary process of forwarding traffic using an overlay network in accordance with an example. At block <NUM>, a network forwarding process facilitating network communication including traffic routing and forwarding receives a first packet stream from a CPE via a first PTP connection or link through an overlay network. For example, a packet, packet flow, or traffic flow initiated by a portable device is obtained via a virtual network built on top of a communications network. The virtual network, for example, is able to facilitate direct connection between a network device such as a server in a first cloud and a service component such as VM in a second cloud.

At block <NUM>, the process identifies a first service component able to provide a first NF based on the first packet stream. For example, the process locates a server able to perform a function of packet classification according to the content of the first packet stream. In one aspect, the process is also capable of determining types of NFs required to process the first packet stream in accordance with a predefined content in a lookup table. The lookup table or tables, in one example, can be stored in a VFd or a network controller.

At block <NUM>, the process, in one embodiment, forwards at least a portion of the first packet stream to the first service component via a second PTP connection through the overlay network based on a set of predefined requirements. For example, selecting one of the VMs capable of providing first FN is selected based on a predefined load balancing requirement. Alternatively, one of the VMs capable of providing first FN is selected according to a predefined Internet Protocol ("IP") security requirement.

At block <NUM>, the process receives the first processed packet stream which is the processing result of the first packet stream from the first service component via the second PTP connection. For example, after generating a classification result by the first service component such as a classifier service component based on the first packet stream, the process is able to return the classification result back to a first forwarder or <NUM>st VFd.

At block <NUM>, the process forwards the first processed packet stream to a second forwarder or <NUM>nd VFd via a first HTH link or channel through the overlay network in accordance with the first processed packet stream. For example, after receiving the first processed packet stream from the first forwarder via the first HTH link through the overlay network, the second service component able to provide the second NF in accordance with the first processed packet stream is identified by the <NUM>nd VFd. Upon forwarding at least a portion of the first processed packet stream to the second service component via a third PTP connection through the overlay network, the second processed packet stream in response to the first processed packet stream is received by the <NUM>nd VFd from the second service component via the third PTP connection. The process, in one embodiment, forwards the second processed packet stream to a third forwarder or <NUM>rd VFd via a second HTH link through the overlay network in accordance with the second processed packet stream. In one example, the <NUM>nd VFd can be identified based on the content of the first processed packet stream and the <NUM>rd VFd is determined according to the content of the second processed packet stream. In one example, identifying the next VFd is partially based on a set of predefined requirements such as load balancing, security requirements, and the like.

<FIG> is a flowchart <NUM> illustrating an exemplary process of tunneling through a firewall(s) using an overlay network in accordance with the claimed invention. At block <NUM>, a process for facilitating network communication identifies a first cloud containing a group of service providers secured by a first firewall.

At block <NUM>, a second cloud containing service consumers protected by a second firewall is identified.

At block <NUM>, an automatic overlay channel between the first cloud and the second cloud is established via a service discovery and the authenticated permissions are registered with the service registration.

At block <NUM>, the process permits an auto overlay channel to establish a first opening at the first firewall in response to the service registration. Note that the auto overlay channel facilitates data passage/transmission between the first and second clouds via the automatic overlay channel. The process also permits the automatic overlay channel to establish a second opening at the second firewall in accordance with the service registration for facilitating data passage between the clouds. In operation, after transmitting data from the first cloud through the first opening of first firewall, the data is allowed to travel through the second openings of second firewall to reach the targeted service consumer at the second cloud with no or minimal authentication or delay.

Claim 1:
A method for facilitating network communication, comprising:
identifying a first cloud (<NUM>) containing a plurality of service providers (<NUM>) secured by a first firewall (<NUM>);
identifying a second cloud (<NUM>) containing a plurality of service consumers (<NUM>) protected by a second firewall (<NUM>);
establishing, by an overlay component, an automatic overlay channel (<NUM>) between the first cloud and the second cloud via a service discovery for service registration, the automatic overlay channel being established upon authentication and registration in a service registry (<NUM>);
permitting the automatic overlay channel to establish a first opening at the first firewall in response to the service registration for facilitating data passage between the first cloud and the second cloud via the automatic overlay channel; and
permitting the automatic overlay channel to establish a second opening at the second firewall in accordance with the service registration for facilitating data passage between the first cloud and the second cloud via the automatic overlay channel.