Embodiments of the present invention relate generally to packet capturing. More particularly, embodiments of the invention relate to streaming packet captures from network access devices to a cloud server over HTTP.
Packet capture (PCAP) is the act of capturing data packets crossing a computer network. Deep packet capture (DPC) is the act of capturing, at full network speed, complete network packets (e.g., header and payload) crossing a network with a high traffic rate. Once captured and stored, either in short-term memory or long-term storage, software tools can perform deep packet inspection (DPI) to review network packet data, perform forensics analysis to uncover the root cause of network problems, identify security threats, and ensure data communications and network usage complies with outlined policy. Some DPCs can be coupled with DPI and can as a result manage, inspect, and analyze all network traffic in real-time at wire speeds while keeping a historical archive of all network traffic for further analysis.
Typically, in order to configure a network device to perform PCAPs, one has to set up certain PCAP rules. Traditionally, setting up a remote packet capture is a manually intensive process that can only be run on the network devices with enough resources (e.g., CPU, memory, and storage) to do all the filtering and store the results on the machine where the PCAP is taking place. For example, an administrator must log into the device; the device must have a program to execute the packet capture; it must run the capture and store the results locally; and then, via a separate process, one must transfer the results (which may be large) from the remote device to a local device for additional analysis.
This may be difficult or impossible if the device does not have enough disk space to store the capture or the device is not remotely accessible. If one wants to run this process across multiple devices, for instance capturing across multiple access points (APs), she must repeat every step and then try to merge the results together. Finally, this process does not take place over a standard service, so accessing from remote devices may be difficult.
Embodiments of the invention are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
Various embodiments and aspects of the inventions will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the invention and are not to be construed as limiting the invention. Numerous specific details are described to provide a thorough understanding of various embodiments of the present invention. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present inventions.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.
According to some embodiments, a centralized backend server (e.g., Web-based or cloud-based management server) maintains a persistent network connection such as a hypertext transport protocol (HTTP) connection with each of packet capturing devices. A network access device can be one of a gateway device, an access point (AP), and a network switch, which provides network access to one or more client devices over a local area network (LAN). In one embodiment, a management server presents a Web interface that has the same inputs as traditional packet captures, allowing a user to select which remote devices to run the capture on and start a packet capture session. In one embodiment, the management server receives one or more expressions, such as a TCPDUMP expression, from the Web interface for packet captures in one or more of the network access devices. The management server compiles the expressions into bytecode that is platform independent and allows the capture devices themselves to do filtering without having them to be capable of translating expressions into bytecode. Alternatively, the expressions or information representing filtering rules can be transmitted from the management server to at least some of the network access devices. The network access devices can then compile the received information into a set of one or more filtering rules for packet capturing. Each of the network access devices maintains a management tunnel (mTunnel) with the management server so that a management server can connect to the network access devices, for example, for distributing packet capturing information and/or reporting captured packets.
In one embodiment, each of the network access devices that perform packet capture includes a HTTP server component running therein that uses HTTP-chunking to stream captured information of packets to a HTTP client component running within the management server. The management server creates a process that initiates an HTTP connection to each capture device which streams results back and merges multiple PCAP streams together to a merged stream, including reordering and/or deduplicating the PCAP packets. The server component of a network access device streams the results of the process over a HTTP-chunked connection that will work over a standard Web server. In one embodiment, the management server parses the output and streams an output such as a TCPDUMP text output to the user over a Web service.
According to one embodiment, network access devices 102-103 may represent “capture devices” that a network operator (e.g., administrator 107) wishes to capture packets from. Each of network access devices 102-103 is connected to management server 101 (e.g., backend system) via an Internet protocol (IP) tunnel referred to herein as an “mTunnel.” Each capture device runs a Web service that a program can connect to over an mTunnel. A user connects to a “Web service” which can run programs that can access devices over the mTunnel. When the user selects to run a packet capture, the Web service connects to a program that streams from multiple capture devices (e.g., network access devices 102-103) to aggregate multiple streams into one that it itself streams back to the end user, either via an update to a Web interface or via a download.
Referring back to
A conventional system requires user 107 to individually log into each of the network access devices that perform the packet captures to specify the PCAP configuration. Such a manual process is tedious and error prone. In one embodiment, by compiling the PCAP configuration information into bytecode representing the PCAP filtering rules, the network access devices do not need the processing resources that are required to compile the same filtering rules. Since the typical bytecode is much smaller in size (e.g., around 20 bytes) compared to a typical HTTP expression that sets up the filtering rules, it takes much less resource or bandwidth to transmit from management server 101 to network access devices 102-103 and it takes less processing resource in the network access devices to execute the bytecode.
According to another embodiment, a network access device may have enough processing power or bandwidth to maintain a rule generator such as rule generator 112 to compile the packet capturing information to generate capture filtering rules 124. In such an embodiment, management server 101 receives packet capturing information from user 107 via Web interface 111. User 107 can specify via Web interface 111 which of the network access devices 105-106 would receive the packet capturing information. The capturing information representing filtering rules can be transmitted from the management server 101 to at least some of the network access devices 105-106. The network access devices 105-106 can then compile the received information into a set of one or more filtering rules, such as rules 124, for packet capturing.
According to one embodiment, each of network access devices 102-103 maintains a persistent mTunnel with management server 101. The bytecode representing capture filtering rules 113 is downloaded over the mTunnels to the specified network access devices, in this example, as part of capture filtering rules 124 of network access device 102. The capture filtering rules may be carried by a user datagram protocol (UDP) packet that is encapsulated in another packet and tunneled to network access device 102 such as UDP over IP (UDP/IP) encapsulation or UDP over HTTP (UDP/HTTP) encapsulation. Network access device 102 includes a router 121 to route packets exchanged between its client devices 108 and the Internet 104 via path 133. In addition, network access device 102 includes a capture program 122 (also referred to as a packet analyzer) coupled to router 121 to capture packets or packet information (e.g., parameters) that satisfy capture filtering rules 124. Note that the network access devices 105-106 can capture packets even if those packets are not being routed to or from the Internet via any kind of Layer 3 (i.e., IP layer) routing; the packet capturing can be done at Layer 2 (i.e., media access control or MAC layer). Thus, even when the network access devices 105-106 are operating in a “bridge mode” and not themselves performing any routing at Layer 3, they can still perform packet capturing at Layer 2. Of course, the network access device must themselves have layer 3 connectivity (i.e. an IP address) in order to communicate with the management server 101.
Capture program 122 may be implemented as part of router 121 or a network stack of an operating system of network access device 102. Alternatively, capture program 122 may be a third-party packet capture utility such as TCPDUMP utility. TCPDUMP is a packet analyzer that runs under the command line. It allows the user to intercept and display TCP/IP and other packets being transmitted or received over a network to which the computer is attached. TCPDUMP works on most LINUX operating systems.
According to one embodiment, network access device 102 includes an HTTP server component 123 that is communicatively coupled to HTTP client component 115 of management server 101 to maintain a persistent HTTP connection. The persistent HTTP connection may be part of an mTunnel between management server 101 and network access device 102. HTTP client 115 and HTTP server 123 work with each other to maintain an open HTTP connection. In one embodiment, when network access device 102 powers up and contacts management server 101, HTTP client 115 sends an HTTP request to HTTP server 123. Instead of immediately responding to the HTTP request, HTTP server 123 may withhold the HTTP response until there is data to be sent to management server 101. Alternatively, the initial HTTP request from client 115 to server 123 happens when the administer requests a new PCAP to start, rather than when NAD 102 boots up. The HTTP server 123 receives configuration parameters about the new PCAP (e.g., the byte code for the filtering rules, the duration of the PCAP, maximum number of packets to capture, etc) as HTTP parameters that are part of that initial HTTP fetch. HTTP client 115 would start a new fetch for each PCAP that is requested, rather than immediately starting one once NAD 102 boots up. In one embodiment, when capture program 122 captures the PCAP information based on capture filtering rules 124, the PCAP information is handed over to HTTP server 123. In response, HTTP server 123 transmits the PCAP information as part of a pending HTTP response to HTTP client 115. In one embodiment, once HTTP client 115 receives an HTTP response from HTTP server 123, HTTP client 115 immediately sends another HTTP request to HTTP server 123, which will be withheld to maintain the HTTP connection open.
According to one embodiment, the PCAP information is streamed by HTTP server 123 to HTTP client 115 using HTTP streaming protocols, such as HTTP streaming or HTTP live streaming protocol. HTTP streaming (also referred to as HTTP server push) is a mechanism for sending data from a Web server (e.g., HTTP server) to a Web browser (e.g., HTTP client). Generally the Web server does not terminate a connection after response data has been served to a client. The Web server leaves the connection open so that if an event is received, it can immediately be sent to one or more clients. Otherwise, the data would have to be queued until the client's next request is received. HTTP live streaming (HLS) is an HTTP-based media streaming communications protocol. It works by breaking the overall stream into a sequence of small HTTP-based file downloads, each download loading one short chunk of an overall potentially unbounded transport stream. Since its requests use only standard HTTP transactions, HTTP live streaming is capable of traversing any firewall or proxy server that lets through standard HTTP traffic, unlike UDP-based protocols.
According to one embodiment, HTTP server 123 of network access device 102 listens for an incoming HTTP connection (e.g., HTTP request) from HTTP client 115 of management server. Once the HTTP connection has been established, capture program 122 starts capturing packet information based on capture filtering rules 124 and streams back via path 134 the capture result to management server 101 via HTTP server 123. In one embodiment, packet capture program 122 selects an interface, a time or packet limit, and loads the byte code 124 into the kernel memory so that capture program 122 will filter and unwanted packets. Alternatively, capture filtering rules 124 and the interface and time/packet limits information used by capture program 122 are provided as part of HTTP parameters in the HTTP fetch from client 115 to server 123. For any packets it reads back it streams to its output, and once the stream ends (or times out) it closes the connection and the stream ends. Similarly, network access device 103 streams the respective capture result to management server 101 via path 135.
When HTTP client 115 collects the HTTP streams from network access devices 102-103, the HTTP streams are handed over to merger 114. The HTTP streams may be temporarily stored in buffer 116 for reordering and/or deduplication purposes. Merger 114 merges, with optional reordering and deduplication, the received HTTP streams into merged PCAP stream 117 to allow user 107 to download it through Web interface 111 via path 132.
In one embodiment, capture program 122 communicates with router 121 to monitor certain LAN interfaces such as LAN interfaces 305-307 and capture packets or at least the parameters of the packets exchanged via the selected LAN interfaces based on bytecode 124. Router 121 is responsible for routing packets as part of normal network traffic 302 between client devices associated with LAN interfaces 305-307 and external network node(s) 301 over Internet 104. Any of the LAN interfaces 305-307 may represent physical interfaces such as ports, logical interfaces such as virtual LANs (VLANs), or a combination thereof. Capture program 122 may be implemented as part of router 121, or vice versa. Network access device 102 may be located behind another network access device (e.g., gateway device). According to one embodiment, capture program 122 provides the PCAP information to HTTP server 123. HTTP server 123 then streams the PCAP information 303 to management server 101 via mTunnel 304 using an HTTP streaming protocol. As described above, the packet capturing can be performed at other network layers such as Layer 2.
In addition, according to one embodiment, merger 114 includes a deduplication module 405 to remove any deduplicated stream and/or packets or segments within a stream. In one embodiment, for each packet/segment or stream in merged stream 117, a hash of the content is generated using a predetermined hash function (e.g., SHA-1, MD5) and maintained as part of hashes 406. For a new packet or segment, a new hash is generated and compared with the hashes 406 to determine whether the packet or segment has already been stored in merged stream 117. If the new hash matches one of the hashes 406, it means more likely than not that the corresponding packet/segment exists in merged stream 117. Thus, instead of storing the duplicated packet/segment in merged stream 117 again, the duplicated packet/segment may be dropped or ignored. According to one embodiment, merger 114 further includes a decoder (not shown) that, rather than streaming back the actual packet contents, the decoder interprets and decodes the content and streams back a human-readable text summary of each packet.
According to one embodiment, a network access device may represent a gateway device interfacing a LAN to WAN 1004 and performs network address translation (NAT) for its clients, which may be client devices 1008-1009 or other network access devices. A network access device may be configured behind another network access device. For example, an uplink of an access point may be coupled to a downlink of a gateway device. Alternatively, an uplink of a network switch may be coupled to a downlink of a gateway device or an access point, etc. A network access device may be an integrated device integrating two or more of these functionalities (e.g., router/gateway, access point, and/or network switch), wired and/or wireless.
Referring back to
According to one embodiment, management server 1001 includes a management module 1010 and a configuration module 1011 to manage and to configure network access devices 1002-1003 and to generate management server configuration information for each of network access devices 1002-1003, which may be stored in configuration information database 1013. In one embodiment, management server 1001 provides a user interface 1014 such as a Web interface to allow a network administrator such as administrators 1007A and 1007B to create and log into an account associated with an organization to which the network access devices 1002 or network access devices 1003 belong.
The management server 1001 further includes a NAD information database 1012, including information regarding the network access devices 1002-1003. In one embodiment, the NAD information database 1012 includes a serial number and a mechanism to authenticate the network access device's identity (e.g., the public key of a private public key pair, the private key of which was embedded or stored in the network access device during the manufacturing). NAD information database 1012 may be populated different ways in different embodiments (e.g., populated by the seller of the network access devices, populated by the network administrator). In embodiments in which this information is populated by the seller, different ones of these embodiments may associate the information regarding network access devices 1002-1003 in the router information database with the user account in different ways (example, network administrators 1007A and 1007B may provide an order number (or invoice number) associated with a purchase of network access devices 1002 or 1003).
According to one embodiment, when a network access device is powered up and attempts entering network 1004, the network access device attempts to contact management server 1001. In one embodiment, certain device information such as an IP address and domain name service (DNS) name of management server 1001 is stored in the network access device when it is manufactured. In one embodiment, when the network access device is powered up, the network access device performs any self-configuration processes including obtaining an IP address for itself from a dynamic host configuration protocol (DHCP) facility (which address may be a public IP address, or may be a private IP address if there is a device performing NAT between the router and the WAN (that is to say, the network access device is behind a device performing NAT)). The network access device then accesses management server 1001 based on the server's IP address and authenticates itself (e.g., signing a message (e.g., including the serial number of the network access device) using a private key associated (and/or stored) with the network access device, such that management server 1001 can authenticate the network access device using the associated public key (stored in NAD information database 1012) maintained by management server 1001).
In one embodiment, each of network access devices 102-103 creates one or more secure communication channels (e.g., a control tunnel) with server 1001 using the keys downloaded from management server 101 to exchange control traffic such as management messages or notification, operating statuses of the network access device, etc. Such a tunnel for network management purposes is referred to herein as an mTunnel. In this example, network access devices 1002 maintain at least one mTunnel 1021 with management server 1001 and network access devices 1003 maintain at least one mTunnel 1022 with management server 1001. In one embodiment, each of network access devices 1002 may maintain a persistent mTunnel with management server 1001. Alternatively, only the network access device operating as a gateway device maintains an mTunnel with management server 1001, while other network access devices behind the gateway device communicate with the gateway device to share the same mTunnel. In one embodiment, a network access device operating as a gateway performs network address translation (NAT) for its clients, which may be a network client device or another network access device.
In one embodiment, once a network access device has been successfully authenticated by server 1001, the network access device downloads configuration information and stores it in a storage device within the network access device. This download may take place over a secure session layer (SSL)-encrypted session and/or the management server may encrypt the data using the public key corresponding to the private key. This secure channel may also be used to receive subsequent configuration updates from management server 1001. According to one embodiment, subsequently, when there is a change in the configuration, such as adding or removing a network access device, changing of subnet settings (for example, by an administrator such as administrators 1007A and 1007B via a Web interface of management server 1001), management server 1001 is to generate updated configuration information and communicate the updates to the network access devices via their corresponding mTunnels (such communication can be done with different mechanisms depending on the embodiment of type of information, including a push mechanism, a pull mechanism, etc.).
A variety of tunneling protocols can be utilized over an mTunnel between a network access device and management server 1001, such as, for example, Internet protocol (IP) over user datagram protocol (UDP) (IP/UDP) encapsulation. UDP is one of the core members of the Internet Protocol Suite, the set of network protocols used for the Internet. With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an IP protocol network without requiring prior communications to set up special transmission channels or data paths. UDP uses a simple transmission model without handshaking dialogues for providing reliability, ordering, or data integrity. Thus, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. UDP assumes that error checking and correction is either not necessary or performed in the application, avoiding the overhead of such processing at the network interface level. Time-sensitive applications often use UDP because dropping packets is preferable to waiting for delayed packets, which may not be an option in a real-time system. If error correction facilities are needed at the network interface level, an application may use the Transmission Control Protocol (TCP), which is designed for this purpose. UDP applications use datagram sockets to establish host-to-host communications. An application binds a UDP socket to its endpoint of data transmission, which is a combination of an IP address and a UDP port.
For example, a network management message may be carried as an IP packet and the IP packet may be encapsulated within a UDP packet exchanged between a network access device and management server 1001 over a respective mTunnel. In one embodiment, an IP packet having one or more network management messages embedded therein may be wrapped with a predetermined mTunnel header and is transmitted within a UDP packet between management server 1001 and a network access device, even if the network access device is behind a NAT device.
In some configurations, if a network access device is behind a firewall that does not allow any UDP packet going through, a UDP packet carrying a network management message may be encapsulated within a hypertext transport protocol (HTTP), referred to herein as UDP over HTTP (UDP/HTTP). Since most of the firewalls allow Internet traffic using HTTP protocol with a transport control protocol (TCP) port of 80, it is likely a UDP packet embedded within an HTTP packet having a destination TCP port of 80 or port 443 can reach management server 1001. In such a configuration, when management server 1001 receives the HTTP packet, it may remove any HTTP header to reveal a UDP packet encapsulated therein. Thereafter, an IP packet encapsulated within the UDP packet may be extracted and the network management message within the IP packet can be obtained.
According to one embodiment, management server 1001 and network access devices associated with an organization such as network access devices 1002 may utilize an internal set of IP addresses (also referred to as mTunnel or management IP addresses) to exchange network management messages via the respective mTunnel or mTunnels. That is, the internal IP addresses used by management server 1001 and network access devices 1002 via the respective mTunnel or mTunnels may be in a separate IP address space (e.g., 6.x.x.x) that is different from an IP address space used between network access devices 1002 and their network client devices 1008 over LAN(s) 1005 (e.g., 10.x.x.x). The internal IP addresses described herein are only used between management server 1001 and network access devices 1002 to exchange network management messages over the respective mTunnel(s). In one embodiment, for a network access device that performs NAT for its LAN devices, it may have at least three IP addresses: 1) an uplink IP address for regular network traffic to an external network (e.g., external IP address used in the external network, or a public IP address if the uplink interface of the network access device is directly coupled to the Internet; 2) a downlink IP address (e.g., a private IP address used between the network access device and its LAN devices); and 3) an internal IP address (e.g., a management IP address or mTunnel IP address) solely used between a management server and the network access device via an mTunnel over the Internet for the purpose of exchanging network management messages. In this example, management server 1001 and network access devices 1002 using the internal IP addresses to exchange network management messages over mTunnel(s) 1021 forms a logical network 1023 (e.g., a logical management network).
Similarly, management server 1001 and network access devices 1003 of another organization in this example may utilize a different set of internal IP addresses to exchange network management messages through the respective mTunnel or mTunnels, where the internal IP addresses may be in a different IP address space than the one of IP addresses used between network access devices 1003 and their client devices 1009. Similarly, in this example, management server 1001 and network access devices 1003 using internal IP addresses to exchange network management messages over mTunnel(s) 1022 forms a logical network 1024 (e.g., a logical management network). The internal IP addresses (referred to herein as a first set of internal IP addresses) used between management server 1001 and network access devices 1002 may be different than the internal IP addresses (referred to herein as a second set of internal IP addresses). The first and second sets of internal IP addresses may be in different IP address spaces or in the same IP address space dependent upon the specific configuration.
According to one embodiment, when a network access device is powered up and initialized, the network access device performs certain self-configuration operations to determine whether the network access device should operate as a gateway or as an access point behind a gateway. In one embodiment, when a network access device boots up, it initializes its Ethernet interface and attempts to request an IP address (e.g., a publicly accessible IP address over the Internet, also referred to as an uplink IP address) by broadcasting its media access control (MAC) address within a dynamic host configuration protocol (DHCP) request via its Ethernet interface. If the Ethernet interface of this network access device is connected to the Internet, a DHCP server, which may be a separate server or part of management server 1001, will respond with a valid IP address assignment, and the network access device will operates as a gateway device. If there is no DHCP response received within a predetermined period of time, the network access device assumes that it is operating behind another gateway device that performs NAT, and the network access device then joins an existing network and operates as an access point.
According to one embodiment, when operating behind a gateway, each of the network access devices derives its own IP address and assigns IP addresses to its client devices using a predetermined method in a consistent manner. In one embodiment, a network access device performs a hash operation on at least a portion of its hardware identifier such as a MAC address to generate an IP address. In a particular embodiment, a network access device hashes its 6-byte MAC address using a predetermined hash function (e.g., CRC-32 hash function) to generate lower three bytes of its IP address. Note that each of the network access devices may generate two IP addresses for itself: 1) an internal IP address in a first IP address space (e.g., 6.x.x.x) solely for communicating network management messages with management server 1001 via an mTunnel; and 2) a private IP address in a second IP address space (e.g., 10.x.x.x) for normal network traffic with its client devices.
Similarly, when a network client device, such as client devices 1008, requests an IP address, the associated network access device hashes a MAC address of the client device to derive an IP address for the client device. Since each of the network access devices performs the same hash operation using the same hash function on a MAC address of a client device, the client device can consistently obtain the same IP address from different network access devices. As result, the client device can roam across different network access devices without having to change its IP address or to perform any address resolution protocol (ARP) related operations.
Referring back to
Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices. Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer-readable media, such as non-transitory computer-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer-readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals).
The processes or methods depicted in the preceding figures may be performed by processing logic that comprises hardware (e.g. circuitry, dedicated logic, etc.), firmware, software (e.g., embodied on a non-transitory computer readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described may be performed in a different order. Moreover, some operations may be performed in parallel rather than sequentially.
In the foregoing specification, embodiments of the invention have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
This application is a continuation of U.S. patent application Ser. No. 14/704,417, entitled “METHOD FOR STREAMING PACKET CAPTURES FROM NETWORK ACCESS DEVICES TO A CLOUD SERVER OVER HTTP,” filed on May 5, 2015 which in turn, is a continuation of U.S. patent application Ser. No. 13/829,839, entitled “METHOD FOR STREAMING PACKET CAPTURES FROM NETWORK ACCESS DEVICES TO A CLOUD SERVER OVER HTTP,” filed on Mar. 14, 2013, all of which are incorporated by reference herein in their entireties for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
5812773 | Norin | Sep 1998 | A |
5889896 | Meshinsky et al. | Mar 1999 | A |
6108782 | Fletcher | Aug 2000 | A |
6178453 | Mattaway et al. | Jan 2001 | B1 |
6298153 | Oishi | Oct 2001 | B1 |
6343290 | Cossins et al. | Jan 2002 | B1 |
6490617 | Hemphill | Dec 2002 | B1 |
6643260 | Kloth et al. | Nov 2003 | B1 |
6683873 | Kwok et al. | Jan 2004 | B1 |
6721804 | Rubin | Apr 2004 | B1 |
6733449 | Krishnamurthy et al. | May 2004 | B1 |
6735631 | Oehrke et al. | May 2004 | B1 |
6996615 | McGuire | Feb 2006 | B1 |
7054930 | Cheriton | May 2006 | B1 |
7058706 | Lyer et al. | Jun 2006 | B1 |
7062571 | Dale et al. | Jun 2006 | B1 |
7111177 | Chauvel et al. | Sep 2006 | B1 |
7203173 | Bonney | Apr 2007 | B2 |
7212490 | Kao et al. | May 2007 | B1 |
7277948 | Igarashi et al. | Oct 2007 | B2 |
7313667 | Pullela et al. | Dec 2007 | B1 |
7379846 | Williams et al. | May 2008 | B1 |
7480672 | Hahn et al. | Jan 2009 | B2 |
7496043 | Leong et al. | Feb 2009 | B1 |
7536476 | Alleyne | May 2009 | B1 |
7567504 | Darling et al. | Jul 2009 | B2 |
7606147 | Luft et al. | Oct 2009 | B2 |
7647594 | Togawa | Jan 2010 | B2 |
7773510 | Back et al. | Aug 2010 | B2 |
7808897 | Mehta et al. | Oct 2010 | B1 |
7881957 | Cohen et al. | Feb 2011 | B1 |
7917647 | Cooper et al. | Mar 2011 | B2 |
8010598 | Tanimoto | Aug 2011 | B2 |
8028071 | Mahalingam et al. | Sep 2011 | B1 |
8041714 | Aymeloglu et al. | Oct 2011 | B2 |
8121117 | Amdahl et al. | Feb 2012 | B1 |
8171415 | Appleyard et al. | May 2012 | B2 |
8234377 | Cohn | Jul 2012 | B2 |
8244559 | Horvitz et al. | Aug 2012 | B2 |
8250215 | Stienhans et al. | Aug 2012 | B2 |
8280880 | Aymeloglu et al. | Oct 2012 | B1 |
8284664 | Aybay et al. | Oct 2012 | B1 |
8301746 | Head et al. | Oct 2012 | B2 |
8345692 | Smith | Jan 2013 | B2 |
8406141 | Couturier | Mar 2013 | B1 |
8407413 | Yucel et al. | Mar 2013 | B1 |
8448171 | Donnellan et al. | May 2013 | B2 |
8477610 | Zuo et al. | Jul 2013 | B2 |
8495356 | Ashok et al. | Jul 2013 | B2 |
8510469 | Portolani | Aug 2013 | B2 |
8514868 | Hill | Aug 2013 | B2 |
8532108 | Li et al. | Sep 2013 | B2 |
8533687 | Greifeneder | Sep 2013 | B1 |
8547974 | Guruswamy | Oct 2013 | B1 |
8560639 | Murphy et al. | Oct 2013 | B2 |
8560663 | Baucke et al. | Oct 2013 | B2 |
8589543 | Dutta et al. | Nov 2013 | B2 |
8590050 | Nagpal et al. | Nov 2013 | B2 |
8611356 | Yu et al. | Dec 2013 | B2 |
8612625 | Andries et al. | Dec 2013 | B2 |
8630291 | Shaffer et al. | Jan 2014 | B2 |
8639787 | Lagergren et al. | Jan 2014 | B2 |
8656024 | Krishnan et al. | Feb 2014 | B2 |
8660129 | Brendel et al. | Feb 2014 | B1 |
8719804 | Jain | May 2014 | B2 |
8775576 | Hebert et al. | Jul 2014 | B2 |
8797867 | Chen et al. | Aug 2014 | B1 |
8805951 | Faibish et al. | Aug 2014 | B1 |
8850182 | Fritz et al. | Sep 2014 | B1 |
8856339 | Mestery et al. | Oct 2014 | B2 |
8909928 | Ahmad et al. | Dec 2014 | B2 |
8918510 | Gmach et al. | Dec 2014 | B2 |
8924720 | Raghuram et al. | Dec 2014 | B2 |
8930747 | Levijarvi et al. | Jan 2015 | B2 |
8938775 | Roth et al. | Jan 2015 | B1 |
8959526 | Kansal et al. | Feb 2015 | B2 |
8977754 | Curry, Jr. et al. | Mar 2015 | B2 |
9009697 | Breiter et al. | Apr 2015 | B2 |
9015324 | Jackson | Apr 2015 | B2 |
9043439 | Bicket et al. | May 2015 | B2 |
9049115 | Rajendran et al. | Jun 2015 | B2 |
9063789 | Beaty et al. | Jun 2015 | B2 |
9065727 | Liu et al. | Jun 2015 | B1 |
9075649 | Bushman et al. | Jul 2015 | B1 |
9164795 | Vincent | Oct 2015 | B1 |
9167050 | Durazzo et al. | Oct 2015 | B2 |
9201701 | Boldyrev et al. | Dec 2015 | B2 |
9201704 | Chang et al. | Dec 2015 | B2 |
9203784 | Chang et al. | Dec 2015 | B2 |
9223634 | Chang et al. | Dec 2015 | B2 |
9244776 | Koza et al. | Jan 2016 | B2 |
9251114 | Ancin et al. | Feb 2016 | B1 |
9264478 | Hon et al. | Feb 2016 | B2 |
9313048 | Chang et al. | Apr 2016 | B2 |
9361192 | Smith et al. | Jun 2016 | B2 |
9380075 | He et al. | Jun 2016 | B2 |
9432294 | Sharma et al. | Aug 2016 | B1 |
9444744 | Sharma et al. | Sep 2016 | B1 |
9473365 | Melander et al. | Oct 2016 | B2 |
9503530 | Niedzielski | Nov 2016 | B1 |
9558078 | Farlee et al. | Jan 2017 | B2 |
9613078 | Vermeulen et al. | Apr 2017 | B2 |
9628471 | Sundaram et al. | Apr 2017 | B1 |
9658876 | Chang et al. | May 2017 | B2 |
9692802 | Bicket et al. | Jun 2017 | B2 |
9755858 | Bagepalli et al. | Sep 2017 | B2 |
20010039579 | Trcka | Nov 2001 | A1 |
20020073337 | Ioele et al. | Jun 2002 | A1 |
20020143928 | Maltz | Oct 2002 | A1 |
20020166117 | Abrams et al. | Nov 2002 | A1 |
20020174216 | Shorey et al. | Nov 2002 | A1 |
20030018591 | Komisky | Jan 2003 | A1 |
20030056001 | Mate et al. | Mar 2003 | A1 |
20030228585 | Inoko et al. | Dec 2003 | A1 |
20040004941 | Malan et al. | Jan 2004 | A1 |
20040095237 | Chen et al. | May 2004 | A1 |
20040131059 | Ayyakad et al. | Jul 2004 | A1 |
20040264481 | Darling et al. | Dec 2004 | A1 |
20050060418 | Sorokopud | Mar 2005 | A1 |
20050125424 | Herriott et al. | Jun 2005 | A1 |
20060104286 | Cheriton | May 2006 | A1 |
20060126665 | Ward | Jun 2006 | A1 |
20060146825 | Hofstaedter et al. | Jul 2006 | A1 |
20060155875 | Cheriton | Jul 2006 | A1 |
20060168338 | Bruegl et al. | Jul 2006 | A1 |
20070174663 | Crawford et al. | Jul 2007 | A1 |
20070223487 | Kajekar et al. | Sep 2007 | A1 |
20070242830 | Conrado et al. | Oct 2007 | A1 |
20080005293 | Bhargava et al. | Jan 2008 | A1 |
20080084880 | Dharwadkar | Apr 2008 | A1 |
20080165778 | Ertemalp | Jul 2008 | A1 |
20080198752 | Fan et al. | Aug 2008 | A1 |
20080201711 | Amir Husain | Aug 2008 | A1 |
20080235755 | Blaisdell | Sep 2008 | A1 |
20090006527 | Gingell, Jr. et al. | Jan 2009 | A1 |
20090019367 | Cavagnari et al. | Jan 2009 | A1 |
20090031312 | Mausolf et al. | Jan 2009 | A1 |
20090083183 | Rao et al. | Mar 2009 | A1 |
20090138763 | Arnold | May 2009 | A1 |
20090177775 | Radia et al. | Jul 2009 | A1 |
20090178058 | Stillwell, III et al. | Jul 2009 | A1 |
20090182874 | Morford et al. | Jul 2009 | A1 |
20090265468 | Annambhotla et al. | Oct 2009 | A1 |
20090265753 | Anderson et al. | Oct 2009 | A1 |
20090293056 | Ferris | Nov 2009 | A1 |
20090300608 | Ferris et al. | Dec 2009 | A1 |
20090313562 | Appleyard et al. | Dec 2009 | A1 |
20090323706 | Germain et al. | Dec 2009 | A1 |
20090328031 | Pouyadou et al. | Dec 2009 | A1 |
20100042720 | Stienhans et al. | Feb 2010 | A1 |
20100061250 | Nugent | Mar 2010 | A1 |
20100115341 | Baker et al. | May 2010 | A1 |
20100131765 | Bromley et al. | May 2010 | A1 |
20100191783 | Mason et al. | Jul 2010 | A1 |
20100192157 | Jackson et al. | Jul 2010 | A1 |
20100205601 | Abbas et al. | Aug 2010 | A1 |
20100211782 | Auradkar et al. | Aug 2010 | A1 |
20100293270 | Augenstein et al. | Nov 2010 | A1 |
20100318609 | Lahiri et al. | Dec 2010 | A1 |
20100325199 | Park et al. | Dec 2010 | A1 |
20100325441 | Laurie et al. | Dec 2010 | A1 |
20100333116 | Prahlad et al. | Dec 2010 | A1 |
20110016214 | Jackson | Jan 2011 | A1 |
20110035754 | Srinivasan | Feb 2011 | A1 |
20110055396 | Dehaan | Mar 2011 | A1 |
20110055398 | Dehaan et al. | Mar 2011 | A1 |
20110055470 | Portolani | Mar 2011 | A1 |
20110072489 | Parann-Nissany | Mar 2011 | A1 |
20110075667 | Li et al. | Mar 2011 | A1 |
20110110382 | Jabr et al. | May 2011 | A1 |
20110116443 | Yu et al. | May 2011 | A1 |
20110126099 | Anderson et al. | May 2011 | A1 |
20110138055 | Daly et al. | Jun 2011 | A1 |
20110145413 | Dawson et al. | Jun 2011 | A1 |
20110145657 | Bishop et al. | Jun 2011 | A1 |
20110173303 | Rider | Jul 2011 | A1 |
20110185063 | Head et al. | Jul 2011 | A1 |
20110213966 | Fu et al. | Sep 2011 | A1 |
20110219434 | Betz et al. | Sep 2011 | A1 |
20110231715 | Kunii et al. | Sep 2011 | A1 |
20110231899 | Pulier et al. | Sep 2011 | A1 |
20110239039 | Dieffenbach et al. | Sep 2011 | A1 |
20110252327 | Awasthi et al. | Oct 2011 | A1 |
20110261811 | Battestilli et al. | Oct 2011 | A1 |
20110261828 | Smith | Oct 2011 | A1 |
20110276675 | Singh et al. | Nov 2011 | A1 |
20110276951 | Jain | Nov 2011 | A1 |
20110295998 | Ferris et al. | Dec 2011 | A1 |
20110305149 | Scott | Dec 2011 | A1 |
20110307531 | Gaponenko et al. | Dec 2011 | A1 |
20110320870 | Kenigsberg | Dec 2011 | A1 |
20120005724 | Lee | Jan 2012 | A1 |
20120054367 | Ramakrishnan et al. | Mar 2012 | A1 |
20120072318 | Akiyama et al. | Mar 2012 | A1 |
20120072578 | Alam | Mar 2012 | A1 |
20120072581 | Tung et al. | Mar 2012 | A1 |
20120072985 | Davne et al. | Mar 2012 | A1 |
20120072992 | Arasaratnam et al. | Mar 2012 | A1 |
20120084445 | Brock et al. | Apr 2012 | A1 |
20120084782 | Chou et al. | Apr 2012 | A1 |
20120096134 | Suit | Apr 2012 | A1 |
20120102193 | Rathore et al. | Apr 2012 | A1 |
20120102199 | Hopmann et al. | Apr 2012 | A1 |
20120131174 | Ferris et al. | May 2012 | A1 |
20120137215 | Kawara | May 2012 | A1 |
20120158967 | Sedayao et al. | Jun 2012 | A1 |
20120159097 | Jennas, II et al. | Jun 2012 | A1 |
20120167094 | Suit | Jun 2012 | A1 |
20120173710 | Rodriguez | Jul 2012 | A1 |
20120179909 | Sagi et al. | Jul 2012 | A1 |
20120180044 | Donnellan et al. | Jul 2012 | A1 |
20120182891 | Lee | Jul 2012 | A1 |
20120185913 | Martinez et al. | Jul 2012 | A1 |
20120192016 | Gotesdyner et al. | Jul 2012 | A1 |
20120192075 | Ebtekar et al. | Jul 2012 | A1 |
20120201135 | Ding et al. | Aug 2012 | A1 |
20120214506 | Skaaksrud et al. | Aug 2012 | A1 |
20120222106 | Kuehl | Aug 2012 | A1 |
20120236716 | Anbazhagan et al. | Sep 2012 | A1 |
20120240113 | Hur | Sep 2012 | A1 |
20120265976 | Spiers et al. | Oct 2012 | A1 |
20120272025 | Park et al. | Oct 2012 | A1 |
20120281706 | Agarwal et al. | Nov 2012 | A1 |
20120281708 | Chauhan et al. | Nov 2012 | A1 |
20120290647 | Ellison et al. | Nov 2012 | A1 |
20120297238 | Watson et al. | Nov 2012 | A1 |
20120311106 | Morgan | Dec 2012 | A1 |
20120311568 | Jansen | Dec 2012 | A1 |
20120324092 | Brown et al. | Dec 2012 | A1 |
20120324114 | Dutta et al. | Dec 2012 | A1 |
20130003567 | Gallant | Jan 2013 | A1 |
20130013248 | Brugler et al. | Jan 2013 | A1 |
20130036213 | Hasan et al. | Feb 2013 | A1 |
20130044636 | Koponen et al. | Feb 2013 | A1 |
20130066940 | Shao | Mar 2013 | A1 |
20130080509 | Wang | Mar 2013 | A1 |
20130080624 | Nagai et al. | Mar 2013 | A1 |
20130091557 | Gurrapu | Apr 2013 | A1 |
20130097601 | Podvratnik et al. | Apr 2013 | A1 |
20130104140 | Meng et al. | Apr 2013 | A1 |
20130111540 | Sabin | May 2013 | A1 |
20130117337 | Dunham | May 2013 | A1 |
20130124712 | Parker | May 2013 | A1 |
20130125124 | Kempf et al. | May 2013 | A1 |
20130138816 | Kuo et al. | May 2013 | A1 |
20130144978 | Jain et al. | Jun 2013 | A1 |
20130152076 | Patel | Jun 2013 | A1 |
20130152175 | Hromoko et al. | Jun 2013 | A1 |
20130159097 | Schory et al. | Jun 2013 | A1 |
20130159496 | Hamilton et al. | Jun 2013 | A1 |
20130160008 | Cawlfield et al. | Jun 2013 | A1 |
20130162753 | Hendrickson et al. | Jun 2013 | A1 |
20130169666 | Pacheco et al. | Jul 2013 | A1 |
20130179941 | McGloin et al. | Jul 2013 | A1 |
20130182712 | Aguayo et al. | Jul 2013 | A1 |
20130185433 | Zhu et al. | Jul 2013 | A1 |
20130191106 | Kephart et al. | Jul 2013 | A1 |
20130198374 | Zalmanovitch et al. | Aug 2013 | A1 |
20130204849 | Chacko | Aug 2013 | A1 |
20130232491 | Radhakrishnan et al. | Sep 2013 | A1 |
20130246588 | Borowicz et al. | Sep 2013 | A1 |
20130250770 | Zou et al. | Sep 2013 | A1 |
20130254415 | Fullen et al. | Sep 2013 | A1 |
20130262347 | Dodson | Oct 2013 | A1 |
20130283364 | Chang et al. | Oct 2013 | A1 |
20130297769 | Chang et al. | Nov 2013 | A1 |
20130318240 | Hebert et al. | Nov 2013 | A1 |
20130318546 | Kothuri et al. | Nov 2013 | A1 |
20130339949 | Spiers et al. | Dec 2013 | A1 |
20140006481 | Frey | Jan 2014 | A1 |
20140006535 | Reddy | Jan 2014 | A1 |
20140006585 | Dunbar et al. | Jan 2014 | A1 |
20140040473 | Ho et al. | Feb 2014 | A1 |
20140040883 | Tompkins | Feb 2014 | A1 |
20140052877 | Mao | Feb 2014 | A1 |
20140059310 | Du et al. | Feb 2014 | A1 |
20140074850 | Noel et al. | Mar 2014 | A1 |
20140075048 | Yuksel et al. | Mar 2014 | A1 |
20140075108 | Dong et al. | Mar 2014 | A1 |
20140075357 | Flores et al. | Mar 2014 | A1 |
20140075501 | Srinivasan et al. | Mar 2014 | A1 |
20140089727 | Cherkasova et al. | Mar 2014 | A1 |
20140098762 | Ghai et al. | Apr 2014 | A1 |
20140108985 | Scott et al. | Apr 2014 | A1 |
20140119428 | Catchpole | May 2014 | A1 |
20140122560 | Ramey et al. | May 2014 | A1 |
20140136779 | Guha et al. | May 2014 | A1 |
20140140211 | Chandrasekaran et al. | May 2014 | A1 |
20140141720 | Princen et al. | May 2014 | A1 |
20140156557 | Zeng et al. | Jun 2014 | A1 |
20140164486 | Ravichandran et al. | Jun 2014 | A1 |
20140188825 | Muthukkaruppan et al. | Jul 2014 | A1 |
20140189095 | Lindberg et al. | Jul 2014 | A1 |
20140189125 | Amies et al. | Jul 2014 | A1 |
20140215471 | Cherkasova | Jul 2014 | A1 |
20140222953 | Karve et al. | Aug 2014 | A1 |
20140244851 | Lee | Aug 2014 | A1 |
20140245298 | Zhou et al. | Aug 2014 | A1 |
20140282536 | Dave et al. | Sep 2014 | A1 |
20140282611 | Campbell et al. | Sep 2014 | A1 |
20140282889 | Ishaya et al. | Sep 2014 | A1 |
20140289200 | Kato | Sep 2014 | A1 |
20140297569 | Clark et al. | Oct 2014 | A1 |
20140297835 | Buys | Oct 2014 | A1 |
20140314078 | Jilani | Oct 2014 | A1 |
20140317261 | Shatzkamer et al. | Oct 2014 | A1 |
20140366155 | Chang et al. | Dec 2014 | A1 |
20140372567 | Ganesh et al. | Dec 2014 | A1 |
20150033086 | Sasturkar et al. | Jan 2015 | A1 |
20150043576 | Dixon et al. | Feb 2015 | A1 |
20150052247 | Threefoot et al. | Feb 2015 | A1 |
20150052517 | Raghu et al. | Feb 2015 | A1 |
20150058382 | St. Laurent et al. | Feb 2015 | A1 |
20150058459 | Amendjian et al. | Feb 2015 | A1 |
20150071285 | Kumar et al. | Mar 2015 | A1 |
20150100471 | Curry, Jr. et al. | Apr 2015 | A1 |
20150106802 | Ivanov et al. | Apr 2015 | A1 |
20150106805 | Melander et al. | Apr 2015 | A1 |
20150117199 | Chinnaiah Sankaran et al. | Apr 2015 | A1 |
20150117458 | Gurkan et al. | Apr 2015 | A1 |
20150120914 | Wada | Apr 2015 | A1 |
20150178133 | Phelan et al. | Jun 2015 | A1 |
20150215819 | Bosch et al. | Jul 2015 | A1 |
20150227405 | Jan et al. | Aug 2015 | A1 |
20150242204 | Hassine et al. | Aug 2015 | A1 |
20150249709 | Teng et al. | Sep 2015 | A1 |
20150280980 | Bitar | Oct 2015 | A1 |
20150281067 | Wu | Oct 2015 | A1 |
20150281113 | Siciliano et al. | Oct 2015 | A1 |
20150309908 | Pearson et al. | Oct 2015 | A1 |
20150319063 | Zourzouvillys et al. | Nov 2015 | A1 |
20150326524 | Tankala et al. | Nov 2015 | A1 |
20150339210 | Kopp et al. | Nov 2015 | A1 |
20150373108 | Fleming et al. | Dec 2015 | A1 |
20160011925 | Kulkarni et al. | Jan 2016 | A1 |
20160013990 | Kulkarni et al. | Jan 2016 | A1 |
20160062786 | Meng et al. | Mar 2016 | A1 |
20160094398 | Choudhury et al. | Mar 2016 | A1 |
20160094480 | Kulkarni et al. | Mar 2016 | A1 |
20160094643 | Jain et al. | Mar 2016 | A1 |
20160099847 | Melander et al. | Apr 2016 | A1 |
20160105393 | Thakkar et al. | Apr 2016 | A1 |
20160127184 | Bursell | May 2016 | A1 |
20160134557 | Steinder et al. | May 2016 | A1 |
20160164914 | Madhav et al. | Jun 2016 | A1 |
20160188527 | Cherian et al. | Jun 2016 | A1 |
20160234071 | Nambiar et al. | Aug 2016 | A1 |
20160239399 | Babu et al. | Aug 2016 | A1 |
20160253078 | Ebtekar et al. | Sep 2016 | A1 |
20160254968 | Ebtekar et al. | Sep 2016 | A1 |
20160261564 | Foxhoven et al. | Sep 2016 | A1 |
20160277368 | Narayanaswamy et al. | Sep 2016 | A1 |
20170005948 | Melander et al. | Jan 2017 | A1 |
20170024260 | Chandrasekaran et al. | Jan 2017 | A1 |
20170026470 | Bhargava et al. | Jan 2017 | A1 |
20170041342 | Efremov et al. | Feb 2017 | A1 |
20170054659 | Ergin et al. | Feb 2017 | A1 |
20170097841 | Chang et al. | Apr 2017 | A1 |
20170099188 | Chang et al. | Apr 2017 | A1 |
20170104755 | Arregoces et al. | Apr 2017 | A1 |
20170147297 | Krishnamurthy et al. | May 2017 | A1 |
20170171158 | Hoy et al. | Jun 2017 | A1 |
20170339070 | Chang et al. | Nov 2017 | A1 |
Number | Date | Country |
---|---|---|
101719930 | Jun 2010 | CN |
101394360 | Jul 2011 | CN |
102164091 | Aug 2011 | CN |
104320342 | Jan 2015 | CN |
105740084 | Jul 2016 | CN |
2228719 | Sep 2010 | EP |
2439637 | Apr 2012 | EP |
2645253 | Nov 2014 | EP |
10-2015-0070676 | May 2015 | KR |
M394537 | Dec 2010 | TW |
WO 2009155574 | Dec 2009 | WO |
WO 2010030915 | Mar 2010 | WO |
WO 2013158707 | Oct 2013 | WO |
Entry |
---|
Amedro, Brian, et al., “An Efficient Framework for Running Applications on Clusters, Grids and Cloud,” 2010, 17 pages. |
Author Unknown, “A Look at DeltaCloud: The Multi-Cloud API,” Feb. 17, 2012, 4 pages. |
Author Unknown, “About Deltacloud,” Apache Software Foundation, Aug. 18, 2013, 1 page. |
Author Unknown, “Architecture for Managing Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-IS0102, Jun. 18, 2010, 57 pages. |
Author Unknown, “Cloud Infrastructure Management Interface—Common Information Model (CIMI-CIM),” Document No. DSP0264, Version 1.0.0, Dec. 14, 2012, 21 pages. |
Author Unknown, “Cloud Infrastructure Management Interface (CIMI) Primer,” Document No. DSP2027, Version 1.0.1, Sep. 12, 2012, 30 pages. |
Author Unknown, “cloudControl Documentation,” Aug. 25, 2013, 14 pages. |
Author Unknown, “Interoperable Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-IS0101, Nov. 11, 2009, 21 pages. |
Author Unknown, “Microsoft Cloud Edge Gateway (MCE) Series Appliance,” Iron Networks, Inc., 2014, 4 pages. |
Author Unknown, “Use Cases and Interactions for Managing Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-ISO0103, Jun. 16, 2010, 75 pages. |
Author Unknown, “Apache Ambari Meetup What's New,” Hortonworks Inc., Sep. 2013, 28 pages. |
Author Unknown, “Introduction,” Apache Ambari project, Apache Software Foundation, 2014, 1 page. |
Citrix, “Citrix StoreFront 2.0” White Paper, Proof of Concept Implementation Guide, Citrix Systems, Inc., 2013, 48 pages. |
Citrix, “CloudBridge for Microsoft Azure Deployment Guide,” 30 pages. |
Citrix, “Deployment Practices and Guidelines for NetScaler 10.5 on Amazon Web Services,” White Paper, citrix.com, 2014, 14 pages. |
Gedymin, Adam, “Cloud Computing with an emphasis on Google App Engine,” Sep. 2011, 146 pages. |
Good, Nathan A., “Use Apache Deltacloud to administer multiple instances with a single API,” Dec. 17, 2012, 7 pages. |
Kunz, Thomas, et al., “OmniCloud—The Secure and Flexible Use of Cloud Storage Services,” 2014, 30 pages. |
Logan, Marcus, “Hybrid Cloud Application Architecture for Elastic Java-Based Web Applications,” F5 Deployment Guide Version 1.1, 2016, 65 pages. |
Lynch, Sean, “Monitoring cache with Claspin” Facebook Engineering, Sep. 19, 2012, 5 pages. |
Meireles, Fernando Miguel Dias, “Integrated Management of Cloud Computing Resources,” 2013-2014, 286 pages. |
Mu, Shuai, et al., “uLibCloud: Providing High Available and Uniform Accessing to Multiple Cloud Storages,” 2012 IEEE, 8 pages. |
Sun, Aobing, et al., “laaS Public Cloud Computing Platform Scheduling Model and Optimization Analysis,” Int. J. Communications, Network and System Sciences, 2011, 4, 803-811, 9 pages. |
Szymaniak, Michal, et al., “Latency-Driven Replica Placement”, vol. 47 No. 8, IPSJ Journal, Aug. 2006, 12 pages. |
Toews, Everett, “Introduction to Apache jclouds,” Apr. 7, 2014, 23 pages. |
Von Laszewski, Gregor, et al., “Design of a Dynamic Provisioning System for a Federated Cloud and Bare-metal Environment,” 2012, 8 pages. |
Ye, Xianglong, et al., “A Novel Blocks Placement Strategy for Hadoop,” 2012 IEEE/ACTS 11th International Conference on Computer and Information Science, 2012 IEEE, 5 pages. |
Author Unknown, “5 Benefits of a Storage Gateway in the Cloud,” Blog, TwinStrata, Inc., Jul. 25, 2012, XP055141645, 4 pages, https://web.archive.org/web/20120725092619/http://blog.twinstrata.com/2012/07/10//5-benefits-of-a-storage-gateway-in-the-cloud. |
Author Unknown, “Joint Cisco and VMWare Solution for Optimizing Virtual Desktop Delivery: Data Center 3.0: Solutions to Accelerate Data Center Virtualization,” Cisco Systems, Inc. and VMware, Inc., Sep. 2008, 10 pages. |
Author Unknown, “Open Data Center Alliance Usage: Virtual Machine (VM) Interoperability in a Hybrid Cloud Environment Rev. 1.2,” Open Data Center Alliance, Inc., 2013, 18 pages. |
Author Unknown, “Real-Time Performance Monitoring on Juniper Networks Devices, Tips and Tools for Assessing and Analyzing Network Efficiency,” Juniper Networks, Inc., May 2010, 35 pages. |
Beyer, Steffen, “Module “Data::Locations?!”,” YAPC::Europe, London, UK,ICA, Sep. 22-24, 2000, XP002742700, 15 pages. |
Borovick, Lucinda, et al., “Architecting the Network for the Cloud,” IDC White Paper, Jan. 2011, 8 pages. |
Bosch, Greg, “Virtualization,” last modified Apr. 2012 by B. Davison, 33 pages. |
Broadcasters Audience Research Board, “What's Next,” http://lwww.barb.co.uk/whats-next, accessed Jul. 22, 2015, 2 pages. |
Cisco Systems, Inc. “Best Practices in Deploying Cisco Nexus 1000V Series Switches on Cisco UCS B and C Series Cisco UCS Manager Servers,” Cisco White Paper, Apr. 2011, 36 pages, http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.pdf. |
Cisco Systems, Inc., “Cisco Unified Network Services: Overcome Obstacles to Cloud-Ready Deployments,” Cisco White Paper, Jan. 2011, 6 pages. |
Cisco Systems, Inc., “Cisco Intercloud Fabric: Hybrid Cloud with Choice, Consistency, Control and Compliance,” Dec. 10, 2014, 22 pages. |
Cisco Technology, Inc., “Cisco Expands Videoscape TV Platform Into the Cloud,” Jan. 6, 2014, Las Vegas, Nevada, Press Release, 3 pages. |
CSS Corp, “Enterprise Cloud Gateway (ECG)—Policy driven framework for managing multi-cloud environments,” original published on or about Feb. 11, 2012; 1 page; http://www.css-cloud.com/platform/enterprise-cloud-gateway.php. |
Fang K., “LISP MAC-EID-TO-RLOC Mapping (LISP based L2VPN),” Network Working Group, Internet Draft, CISCO Systems, Jan. 2012, 12 pages. |
Herry, William, “Keep It Simple, Stupid: OpenStack nova-scheduler and its algorithm”, May 12, 2012, IBM, 12 pages. |
Hewlett-Packard Company, “Virtual context management on network devices”, Research Disclosure, vol. 564, No. 60, Apr. 1, 2011, Mason Publications, Hampshire, GB, Apr. 1, 2011, 524. |
Juniper Networks, Inc., “Recreating Real Application Traffic in Junosphere Lab,” Solution Brief, Dec. 2011, 3 pages. |
Kenhui, “Musings on Cloud Computing and IT-as-a-Service: [Updated for Havana] Openstack Computer for VSphere Admins, Part 2: Nova-Scheduler and DRS”, Jun. 26, 2013, Cloud Architect Musings, 12 pages. |
Kolyshkin, Kirill, “Virtualization in Linux,” Sep. 1, 2006, XP055141648, 5 pages, https://web.archive.org/web/20070120205111/http://download.openvz.org/doc/openvz-intro.pdf. |
Lerach, S.R.O., “Golem,” http://www.lerach.cz/en/products/golem, accessed Jul. 22, 2015, 2 pages. |
Linthicum, David, “VM Import could be a game changer for hybrid clouds”, InfoWorld, Dec. 23, 2010, 4 pages. |
Naik, Vijay K., et al., “Harmony: A Desktop Grid for Delivering Enterprise Computations,” Grid Computing, 2003, Fourth International Workshop on Proceedings, Nov. 17, 2003, pp. 1-11. |
Nair, Srijith K. et al., “Towards Secure Cloud Bursting, Brokerage and Aggregation,” 2012, 8 pages, www.flexiant.com. |
Nielsen, “SimMetry Audience Measurement—Technology,” http://www.nielsen-admosphere.eu/products-and-services/simmetry-audience-measurement-technology/, accessed Jul. 22, 2015, 6 pages. |
Nielsen, “Television,” http://www.nielsen.com/us/en/solutions/measurement/television.html, accessed Jul. 22, 2015, 4 pages. |
Open Stack, “Filter Scheduler,” updated Dec. 17, 2017, 5 pages, accessed on Dec. 18, 2017, https://docs.openstack.org/nova/latest/user/filter-scheduler.html. |
Rabadan, J., et al., “Operational Aspects of Proxy-ARP/ND in EVPN Networks,” BESS Worksgroup Internet Draft, draft-snr-bess-evpn-proxy-arp-nd-02, Oct. 6, 2015, 22 pages. |
Saidi, Ali, et al., “Performance Validation of Network-Intensive Workloads on a Full-System Simulator,” Interaction between Operating System and Computer Architecture Workshop, (IOSCA 2005), Austin, Texas, Oct. 2005, 10 pages. |
Shunra, “Shunra for HP Software; Enabling Confidence in Application Performance Before Deployment,” 2010, 2 pages. |
Son, Jungmin, “Automatic decision system for efficient resource selection and allocation in inter-clouds,” Jun. 2013, 35 pages. |
Wikipedia, “Filter (software)”, Wikipedia, Feb. 8, 2014, 2 pages, https://en.wikipedia.org/w/index.php?title=Filter_%28software%29&oldid=594544359. |
Wikipedia; “Pipeline (Unix)”, Wikipedia, May 4, 2014, 4 pages, https://en.wikipedia.org/w/index.php?title=Pipeline2/028Unix%29&oldid=606980114. |
Number | Date | Country | |
---|---|---|---|
20170264663 A1 | Sep 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14704417 | May 2015 | US |
Child | 15607089 | US | |
Parent | 13829839 | Mar 2013 | US |
Child | 14704417 | US |