Patent Grant
10833943
This technology generally relates to methods and systems for service chaining in a network environment.
With prior technologies, service chaining in a communication network has been utilized to perform various functions including applying various services to data traffic requested by a client device. In particular, one of these applied services on data traffic has been a virus removal service where the data traffic is passed through antivirus scanner devices to detect, prevent, and remove viruses and other malicious threats. Unfortunately, these antivirus scanner devices are very expensive so this prior practice of routing all data traffic through antivirus scanner devices can be cost prohibitive and is not efficient.
A method for service chaining, implemented in cooperation with a network traffic management system comprising one or more network traffic management modules, server modules, additional service modules, security service chaining modules or client modules, includes sending a server response to a client request from a requesting client device to a service chaining device. A modified server response from the service chaining device is received based on a correlation of the server response to one or more service policies. A determination is made on whether the modified server response requires additional processing by one or more additional service chaining devices based on the modified server response. The processed server response is received from the one or more additional service chaining devices when the determination indicated processing was required. The processed server response is transmitted to the requesting client device.
A network traffic management apparatus including memory including programmed instructions stored thereon and one or more processors configured to be capable of executing the stored programmed instructions to send a server response to a client request from a requesting client device to a service chaining device. A modified server response from the service chaining device is received based on a correlation of the server response to one or more service policies. A determination is made on whether the modified server response requires additional processing by one or more additional service chaining devices based on the modified server response. The processed server response is received from the one or more additional service chaining devices when the determination indicated processing was required. The processed server response is transmitted to the requesting client device.
A non-transitory computer readable medium having stored thereon instructions for including executable code that, when executed by one or more processors, causes the processors to send a server response to a client request from a requesting client device to a service chaining device. A modified server response from the service chaining device is received based on a correlation of the server response to one or more service policies. A determination is made on whether the modified server response requires additional processing by one or more additional service chaining devices based on the modified server response. The processed server response is received from the one or more additional service chaining devices when the determination indicated processing was required. The processed server response is transmitted to the requesting client device.
A network traffic management system includes one or more network traffic management modules, server modules, additional service modules, security service chaining modules or client modules, memory comprising programmed instructions stored thereon, and one or more processors configured to be capable of executing the stored programmed instructions to send a server response to a client request from a requesting client device to a service chaining device. A modified server response from the service chaining device is received based on a correlation of the server response to one or more service policies. A determination is made on whether the modified server response requires additional processing by one or more additional service chaining devices based on the modified server response. The processed server response is received from the one or more additional service chaining devices when the determination indicated processing was required. The processed server response is transmitted to the requesting client device.
This technology has a number of advantages including providing methods, non-transitory computer readable media, network traffic management apparatuses, and network traffic management systems that dynamically provide service chaining of devices where services are enabled as needed based on analysis of the response prior to final transmission of the modified response to the requesting client. With this technology, the requests are transmitted between the network traffic management apparatus and the service chaining devices in a manners so that only the responses are modified. As a result, any number of services can be seamlessly chained together with no externally visible side effects, such as redirects or duplicate requests.
An exemplary network environment which incorporates an exemplary network traffic management system 10 is illustrated in
In this particular example, the network traffic management apparatus 12, the service chaining device 13, the server devices 14(1)-14(n), the additional service chaining devices 15(1)-15(n), and the client devices 16(1)-16(n) are disclosed in
As one example, the network traffic management apparatus 12, as well as any of its components, models, or applications, can be a module implemented as software executing on one of the server devices 14(1)-14(n), and many other permutations and types of implementations can also be used in other examples. Moreover, any or all of the network traffic management apparatus 12, the service chaining device 13, the server devices 14(1)-14(n), the additional service chaining devices 15(1)-15(n), and the client devices 16(1)-16(n), can be implemented, and may be referred to herein, as a module.
Referring to
The processor(s) 20 of the network traffic management apparatus 12 may execute programmed instructions stored in the memory 22 of the network traffic management apparatus 12 for the any number of the functions identified above. The processor(s) 20 of the network traffic management apparatus 12 may include one or more CPUs or general purpose processors with one or more processing cores, for example, although other types of processor(s) can also be used.
The memory 22 of the network traffic management apparatus 12 stores these programmed instructions for one or more aspects of the present technology as described and illustrated herein, although some or all of the programmed instructions could be stored elsewhere. A variety of different types of memory storage devices, such as random access memory (RAM), read only memory (ROM), hard disk, solid state drives, flash memory, or other computer readable medium which is read from and written to by a magnetic, optical, or other reading and writing system that is coupled to the processor(s) 20, can be used for the memory 22.
Accordingly, the memory 22 of the network traffic management apparatus 12 can store one or more applications that can include computer executable instructions that, when executed by the network traffic management apparatus 12, cause the network traffic management apparatus 12 to perform actions, such as to transmit, receive, or otherwise process messages, for example, and to perform other actions described and illustrated below with reference to
Even further, the application(s) may be operative in a cloud-based computing environment. The application(s) can be executed within or as virtual machine(s) or virtual server(s) that may be managed in a cloud-based computing environment. Also, the application(s), and even the network traffic management apparatus 12 itself, may be located in virtual server(s) running in a cloud-based computing environment rather than being tied to one or more specific physical network computing devices. Also, the application(s) may be running in one or more virtual machines (VMs) executing on the network traffic management apparatus 12. Additionally, in one or more examples of this technology, virtual machine(s) running on the network traffic management apparatus 12 may be managed or supervised by a hypervisor.
In this particular example, the memory of the network traffic management apparatus 12 includes a response storage 28 and content policy module 30, although the memory 22 can include other policies, modules, databases, or applications, for example. The response storage 28 is a data store, which stores copies of server responses sent by client devices 16(1)-16(n). The server responses may include modified server responses. The content policy module 30 stores policies associated with file types included in a client requested by the client devices 16(1)-16(n).
The response storage 28 stores server responses received from client devices 16(1)-16(n). The network traffic management apparatus 12 receives client requests from client devices 16(1)-16(n), requesting content at one or more server devices 14(1)-14(n). When the network traffic management apparatus 12 receives the server responses, the network traffic management apparatus 12 stores copies of the original server responses in response storage 28. These copies of the server responses are then utilized later by the network traffic management apparatus 12 as explained in detail below in
The content policy module 30 stores policies associated with file types included in a client requested by the client devices 16(1)-16(n). The file types may include, for example, video files, image files, Microsoft word files, Microsoft excel files, Microsoft PowerPoint presentation files, PDF documents, .ISO image files, text files, any presentation files, although other numbers and/or types of file types could be used. The policies associated with these file types may include, for example, to forward client requests to the additional service chaining devices 15(1)-15(n) that request word document files, excel files, PowerPoint presentation files, PDF documents and not to forward client requests to additional service chaining device that request ISO image files and video files, although any other numbers and/or types of policies could be used.
Referring back to
By way of example only, the communication network(s) 18 can include local area network(s) (LAN(s)) or wide area network(s) (WAN(s)), and can use TCP/IP over Ethernet and industry-standard protocols, although other types and/or numbers of protocols and/or communication networks can be used. The communication network(s) 18 in this example can employ any suitable interface mechanisms and network communication technologies including, for example, teletraffic in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Ethernet-based Packet Data Networks (PDNs), combinations thereof, and the like.
While the network traffic management apparatus 12 is illustrated in this example as including a single device, the network traffic management apparatus 12 in other examples can include a plurality of devices or blades each having one or more processors (each processor with one or more processing cores) that implement one or more steps of this technology. In these examples, one or more of the devices can have a dedicated communication interface or memory. Alternatively, one or more of the devices can utilize the memory, communication interface, or other hardware or software components of one or more other devices included in the network traffic management apparatus 12.
Additionally, one or more of the devices that together comprise the network traffic management apparatus 12 in other examples can be standalone devices or integrated with one or more other devices or apparatuses, such as one or more of the service chaining device 13, the server devices 14(1)-14(n), or the additional service chaining devices 15(1)-15(n), for example. Moreover, one or more of the devices of the network traffic management apparatus 12 in these examples can be in a same or a different communication network including one or more public, private, or cloud networks, for example.
The service chaining device 13 of the network traffic management system 10 in this example includes one or more processors, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and/or types of network devices could be used. The service chaining device 13 in this example process requests received from the client devices 16(1)-16(n) via the network traffic management apparatus 12. Further the service chaining device 13 utilizes policies stored in the memory to evaluate which additional services, such as security services by way of example, should be applied to the service chain flow during the processing of client request by adding additional devices into the service chain flow. The service chaining device 13 evaluates the client request received from the client devices 16(1)-16(n) via the network traffic management apparatus 12 and evaluates and modifies the server response. Based on the determined file type the service chaining device 13 may add additional service chaining devices to service the client request based on the requirement associated with the file type. The service chaining device 13 may be hardware or software or may represent a system with multiple servers in a pool, which may include internal or external networks.
Although the service chaining device 13 of the network traffic management system 10 is illustrated as a single device, a plurality of service chaining devices, such as additional service chaining devices 15(1)-15(n) may be included and each of the plurality of service chaining devices maybe coupled by a bus or other communication link to each other and to the network traffic management apparatus. One or more actions of each of the service chaining devices may be distributed across one or more distinct network computing devices that together comprise one or more of the service chaining devices. Moreover, the service chaining devices are not limited to a particular configuration. Thus, the service chaining devices may contain a plurality of network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the service chaining devices operate to manage and/or otherwise coordinate operations of the other network computing devices. The service chaining devices may operate as a plurality of network computing devices within a cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture, for example.
Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged. For example, one or more of the service chaining devices can operate within the network traffic management apparatus 12 itself rather than as a stand-alone server device communicating with the network traffic management apparatus 12 via the communication network(s) 18. In this example, the service chaining device 13 operate within the memory of the network traffic management apparatus 12.
Each of the server devices 14(1)-14(n) of the network traffic management system 10 in this example includes one or more processors, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and/or types of network devices could be used. The server devices 14(1)-14(n) in this example can include application servers, database servers, access control servers, or encryption servers, for example, that exchange communications along communication paths expected based on application logic in order to facilitate interactions with an application by users of the client devices 16(1)-16(n).
Accordingly, in some examples, one or more of the server devices 14(1)-14(n) process login and other requests received from the client devices 16(1)-16(n) via the communication network(s) 18(1) and 18(2) according to the HTTP-based application RFC protocol, for example. A web application may be operating on one or more of the server devices 14(1)-14(n) and transmitting data (e.g., files or web pages) to one or more of the client devices 16(1)-16(n) (e.g., via the network traffic management apparatus 12) in response to one or more requests from the client devices 16(1)-16(n). The server devices 14(1)-14(n) may be hardware or software or may represent a system with multiple servers in a pool, which may include internal or external networks.
Although the server devices 14(1)-14(n) are illustrated as single devices, one or more actions of each of the server devices 14(1)-14(n) may be distributed across one or more distinct network computing devices that together comprise one or more of the server devices 14(1)-14(n). Moreover, the server devices 14(1)-14(n) are not limited to a particular configuration. Thus, the server devices 14(1)-14(n) may contain network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the server devices 14(1)-14(n) operate to manage or otherwise coordinate operations of the other network computing devices. The server devices 14(1)-14(n) may operate as a plurality of network computing devices within a cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture, for example.
Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged. For example, one or more of the server devices 14(1)-14(n) can operate within the network traffic management apparatus 12 itself rather than as a stand-alone server device communicating with the network traffic management apparatus 12 via communication network(s) 18. In this example, the one or more of the server devices 14(1)-14(n) operate within the memory 22 of the network traffic management apparatus 12.
The additional service chaining devices 15(1)-15(n) of the network traffic management system 10 in this example include one or more processors, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and/or types of network devices with other elements could be used. Additionally, in some examples the additional service chaining devices 15(1)-15(n) may be hardware or software or may represent a system with multiple servers in a pool, which may include internal or external networks. Further, the additional service chaining devices 15(1)-15(n) may act as additional service chaining devices to provide additional servicing of the server response to the client request. The additional service chaining devices 15(1)-15(n) may provide further processing of the client request received from the network traffic management apparatus 12 and the associated response from one of the server devices 14(1)-14(n). By way of example, one of the additional service chaining devices 15(1)-15(n) may receive a copy of the client request or another version of the client request, such as a generated or dummy request based on the original client request by way of example, as well as the server response with any modifications by prior servicing chaining from the network traffic management apparatus 12. In response to receiving the copy of the client request or another version of the client request, the one of the additional the service chaining devices 15(1)-15(n) opens up a connection and then sends the copy of the client request or another version of the client request and information about a connection back to the network traffic management apparatus 12. Next, the network traffic management apparatus 12 then forwards the server response to the one of the additional service chaining devices 15(1)-15(n). The one of the additional service chaining devices 15(1)-15(n) may perform additional servicing on the server response, such as an antivirus scanner device or a threat protection service device that performs detection, prevention and removal of malicious threats to the network by way of example only. By way of further example, the one of the additional service chaining devices 15(1)-15(n) may perform a scan on the content included in the server response to detect, prevent and remove threats, from viruses or malicious threats like, for example, malicious browser helper objects (BHOs), browser hijackers, ransomware, keyloggers, backdoors, rootkits, trojan horses, worms, malicious LSPs, dialers, fraud tools, adware and spyware although any other numbers and/or types of viruses or malicious threats are included. After the server response is serviced the one of the additional service chaining devices 15(1)-15(n) forwards the additionally serviced server response back to network traffic management apparatus 12.
Although the plurality of additional service chaining devices 15(1)-15(n) may be coupled by a bus or other communication link to each other and to the network traffic management apparatus 12. One or more actions of each of the additional service chaining devices 15(1)-15(n) may be distributed across one or more distinct network computing devices that together comprise one or more of the additional service chaining devices 15(1)-15(n). Moreover, the additional service chaining devices 15(1)-15(n) are not limited to a particular configuration. Thus, the additional service chaining devices 15(1)-15(n) may contain a plurality of network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the additional service chaining devices 15(1)-15(n) operate to manage and/or otherwise coordinate operations of the other network computing devices. The additional service chaining devices 15(1)-15(n) may operate as a plurality of network computing devices within a cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture, for example. Further, the additional service chaining devices 15(1)-15(n) and the service chaining device 13 can be included within the network traffic management apparatus 12 as one single apparatus and all the functions of these devices can be performed as one single apparatus.
Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged. For example, one or more of the additional service chaining devices 15(1)-15(n) can operate within the network traffic management apparatus 12 itself rather than as a stand-alone server device communicating with the network traffic management apparatus 12 via the communication network(s) 18. In this example, the one or more service chaining device 13 operates within the memory of the network traffic management apparatus 12.
The client devices 16(1)-16(n) of the network traffic management system 10 in this example include any type of computing device that can exchange network data, such as mobile, desktop, laptop, or tablet computing devices, virtual machines (including cloud-based computers), or the like. Each of the client devices 16(1)-16(n) in this example includes a processor, a memory, and a communication interface, which are coupled together by a bus or other communication link (not illustrated), although other numbers or types of components could also be used.
The client devices 16(1)-16(n) may run interface applications, such as standard web browsers or standalone client applications, which may provide an interface to make requests for, and receive content stored on, one or more of the server devices 14(1)-14(n) via the communication network(s) 18(1) and 18(2). The client devices 16(1)-16(n) may further include a display device, such as a display screen or touchscreen, or an input device, such as a keyboard for example (not illustrated). Additionally, one or more of the client devices 16(1)-16(n) can be configured to execute software code (e.g., JavaScript code within a web browser) in order to log client-side data and provide the logged data to the network traffic management apparatus 12, as described and illustrated in more detail later.
Although the exemplary network traffic management system 10 with the network traffic management apparatus 12, the service chaining device 13, the additional service chaining devices 15(1)-15(n), server devices 14(1)-14(n), client devices 16(1)-16(n), and communication network(s) 18 are described and illustrated herein, other types or numbers of systems, devices, components, or elements in other topologies can be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).
One or more of the components depicted in the network security system 10, such as the network traffic management apparatus 12, the service chaining device 13, server devices 14(1)-14(n), the additional service chaining devices 15(1)-15(n) or client devices 16(1)-16(n), for example, may be configured to operate as virtual instances on the same physical machine. In other words, one or more of the network traffic management apparatus 12, the service chaining device 13, server devices 14(1)-14(n), the additional service chaining devices 15(1)-15(n), or client devices 16(1)-16(n) may operate on the same physical device rather than as separate devices communicating through communication network(s) 18. Additionally, there may be more or fewer network traffic management apparatuses, client devices, or server devices than illustrated in
In addition, two or more computing systems or devices can be substituted for any one of the systems or devices in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also can be implemented, as desired, to increase the robustness and performance of the devices and systems of the examples. The examples may also be implemented on computer system(s) that extend across any suitable network using any suitable interface mechanisms and traffic technologies, including by way of example only teletraffic in any suitable form (e.g., voice and modem), wireless traffic networks, cellular traffic networks, Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.
The examples may also be embodied as one or more non-transitory computer readable media having instructions stored thereon, such as in the memory 22, for one or more aspects of the present technology, as described and illustrated by way of the examples herein. The instructions in some examples include executable code that, when executed by one or more processors, such as the processor(s) 20, cause the processors to carry out steps necessary to implement the methods of the examples of this technology that are described and illustrated herein.
An exemplary method of service chaining through Just-In-Time (JIT) virtual hosting will now be described with reference to
In step 305, the network traffic management apparatus 12 transmits the client request to a service chaining device 13 which acts as a proxy device, although other configurations may be used. The service chaining device 13 may store the client request and then transmit the client request back to the network traffic management apparatus 12, although the service chaining device 13 may execute other operations on the client request and the client request that is returned may include other information, such as information about a connection between network traffic management apparatus 12 and the service chaining device 13.
In step 310, the network traffic management apparatus 12 receives the client request back from the service chaining device 13 along with any information on the connection that may have been provided.
In step 315, the network traffic management apparatus 12 re-encrypts the client request and transmits the encrypted client request to one of the server devices 14(1)-14(n) associated with servicing the client request, although the content may be transmitted in other formats, such as unencrypted.
In step 320, the network traffic management apparatus 12 receives an encrypted server response to the client request from the one of the server devices 14(1)-14(n). Next, if encrypted, the network traffic management apparatus 12 decrypts the encrypted server response to provide access to the content. By way of example, the content in the server response may comprise one or more applications, services, files and/or other data, although other types of content may be included. The network traffic management apparatus 12 may store a copy of this server response in the response storage 28 of the memory 22, although the response may be stored or managed in other manners.
In step 325, the network traffic management apparatus 12 transmits the decrypted server response to a service chaining device 13 to perform an inspection of and possible modify the server response based on one or more service chaining policies at the service chaining device 13. By way of example only, the service chaining device 13 may be a data loss prevention device (DLP) that monitors for potential data breaches and prevents these breaches by inspecting and modifying a header of the server response with content covered by one of the stored service chaining policies relating to security, such as by providing a designation in the header that signifies the security level of the content and that the network traffic management apparatus 12 needs to check the authorization associated with the client request to determine if access to the content is permitted. In other examples, the service chaining device 13 may execute one or more services on the server response, such as running a virus scan and removing any threats in the response to generate a modified server response.
In step 330, the network traffic management apparatus 12 receives the modified server response from the service chaining device 13. Upon receiving the modified server response, the network traffic management apparatus 10 may again store a copy of the modified server response in the response storage 28 of the memory 22, although this response may be stored or managed in other manners.
In step 335, the network traffic management apparatus 12 analyzes the modified server response to determine one of a plurality of classifications that may have been applied to the server response which may then be correlated against stored traffic management policies at the network traffic management apparatus 12 to execute one or more operations, although in some example additional operations on the modified server response may not be performed. By way of example, the network traffic management apparatus 12 may analyze the modified server response to determine based on the modification in the header data that the classification of the server response comprises an excel file or a presentation file. In another example, the network traffic management apparatus 12 may analyze the modified server response to determine based on payload data in data packets in the server response that the classification of the server response comprises an MPEG file, although again other types and manners of analyzing and classifying the content may be used. Additionally, the network traffic management apparatus 12 may further process the modified server response based on the determined classification correlated to one or more network traffic management policies stored in the network traffic management apparatus 12, although other types of operations may be performed or no further action may be executed by the network traffic management apparatus 12 on the modified server response.
In step 340, the network traffic management apparatus 12 determines when one or more additional service chaining devices 15(1)-15(n) need to be included in the service chain to further process the modified server response based on the content in the modified server response. If in step 340 the network traffic management apparatus 12 determines that one or more additional service chaining devices 15(1)-15(n) do not need to be included in the service chain to further process the modified server response, then the No branch is taken to step 370. In step 370, the network traffic management apparatus 12 re-encrypts the final modified server response and sends the encrypted final modified server response to the requesting one of the client devices 16(1)-16(n) and then this example of the method may end here.
If back in step 340 the network traffic management apparatus 12 determines that one or more additional service chaining devices 15(1)-15(n) need to be included in the service chain to further process the modified server response, then the Yes branch is taken to step 345. In step 345, the network traffic management apparatus 12 sends a version of the client request to one of the additional service chaining devices 15(1)-15(n), such as a copy of the original client request to the one of the additional service chaining devices 15(1)-15(n) or a newly generated or dummy request based on the on the original client request, although other types and/or versions of the client request may be obtained and sent.
In step 350, the network traffic management apparatus 12 receives back the copy or other version of the client request back from the one of the additional service chaining devices 15(1)-15(n) and may also receive information about a connection between the network traffic management apparatus 12 and the one of the additional service chaining devices 15(1)-15(n), although other types of information may be provided.
In step 355, the network traffic management apparatus 12 forwards the modified server response to the one of the additional service chaining devices 15(1)-15(n). The one of the additional service chaining devices 15(1)-15(n) may perform additional servicing on the server response, such as an antivirus scanner device or a threat protection service device that performs detection, prevention and removal of malicious threats to the network by way of example only, although other types of processing or modification of the server response may be executed. The one of the additional service chaining devices 15(1)-15(n) forwards the an additionally modified server response back to the network traffic management apparatus 12.
In step 360, the network traffic management apparatus 12 receives an additionally modified server response from the one of the additional service chaining devices 15(1)-15(n). Upon receiving the modified server response, the network traffic management apparatus 10 may again store a copy of the modified server response in the response storage 28 of the memory 22, although this response may be stored or managed in other manners.
In step 365, the network traffic management apparatus 12 analyzes the additionally modified server response to determine one of a plurality of classifications that may have been applied to the server response which may again be correlated against stored traffic management policies at the network traffic management apparatus 12 to execute one or more operations, although in some example additional operations on the modified server response may not be performed. Next, this example of the method returns to step 340 as described earlier.
Accordingly, as illustrated and described by way of the examples herein, this technology is able to dynamically provide service chaining of devices where services are enabled as needed based on analysis prior to transmission of the modified response to the requesting client. With this technology, the requests are transmitted between the network traffic management apparatus and the service chaining devices in a manners so that only the responses are modified. As a result, any number of services can be seamlessly chained together with no externally visible side effects, such as redirects or duplicate requests.
Having thus described the basic concept of the invention, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the invention. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the invention is limited only by the following claims and equivalents thereto.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/636,929, filed Mar. 1, 2018, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4993030 | Krakauer et al. | Feb 1991 | A |
| 5218695 | Noveck et al. | Jun 1993 | A |
| 5303368 | Kotaki | Apr 1994 | A |
| 5473362 | Fitzgerald et al. | Dec 1995 | A |
| 5511177 | Kagimasa et al. | Apr 1996 | A |
| 5537585 | Blickenstaff et al. | Jul 1996 | A |
| 5548724 | Akizawa et al. | Aug 1996 | A |
| 5550965 | Gabbe et al. | Aug 1996 | A |
| 5583995 | Gardner et al. | Dec 1996 | A |
| 5586260 | Hu | Dec 1996 | A |
| 5590320 | Maxey | Dec 1996 | A |
| 5623490 | Richter et al. | Apr 1997 | A |
| 5649194 | Miller et al. | Jul 1997 | A |
| 5649200 | Leblang et al. | Jul 1997 | A |
| 5668943 | Attanasio et al. | Sep 1997 | A |
| 5692180 | Lee | Nov 1997 | A |
| 5721779 | Funk | Feb 1998 | A |
| 5724512 | Winterbottom | Mar 1998 | A |
| 5806061 | Chaudhuri et al. | Sep 1998 | A |
| 5832496 | Anand et al. | Nov 1998 | A |
| 5832522 | Blickenstaff et al. | Nov 1998 | A |
| 5838970 | Thomas | Nov 1998 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5884303 | Brown | Mar 1999 | A |
| 5893086 | Schmuck et al. | Apr 1999 | A |
| 5897638 | Lasser et al. | Apr 1999 | A |
| 5905990 | Inglett | May 1999 | A |
| 5917998 | Cabrera et al. | Jun 1999 | A |
| 5920873 | Van Huben et al. | Jul 1999 | A |
| 5926816 | Bauer et al. | Jul 1999 | A |
| 5937406 | Balabine et al. | Aug 1999 | A |
| 5991302 | Berl et al. | Nov 1999 | A |
| 5995491 | Richter et al. | Nov 1999 | A |
| 5999664 | Mahoney et al. | Dec 1999 | A |
| 6012083 | Savitzky et al. | Jan 2000 | A |
| 6029168 | Frey | Feb 2000 | A |
| 6044367 | Wolff | Mar 2000 | A |
| 6047129 | Frye | Apr 2000 | A |
| 6072942 | Stockwell et al. | Jun 2000 | A |
| 6078929 | Rao | Jun 2000 | A |
| 6085234 | Pitts et al. | Jul 2000 | A |
| 6088694 | Bums et al. | Jul 2000 | A |
| 6104706 | Richter et al. | Aug 2000 | A |
| 6128627 | Mattis et al. | Oct 2000 | A |
| 6128717 | Harrison et al. | Oct 2000 | A |
| 6161145 | Bainbridge et al. | Dec 2000 | A |
| 6161185 | Guthrie et al. | Dec 2000 | A |
| 6181336 | Chiu et al. | Jan 2001 | B1 |
| 6202156 | Kalajan | Mar 2001 | B1 |
| 6223206 | Dan et al. | Apr 2001 | B1 |
| 6233648 | Tomita | May 2001 | B1 |
| 6237008 | Beal et al. | May 2001 | B1 |
| 6256031 | Meijer et al. | Jul 2001 | B1 |
| 6282610 | Bergsten | Aug 2001 | B1 |
| 6289345 | Yasue | Sep 2001 | B1 |
| 6308162 | Ouimet et al. | Oct 2001 | B1 |
| 6324581 | Xu et al. | Nov 2001 | B1 |
| 6329985 | Tamer et al. | Dec 2001 | B1 |
| 6339785 | Feigenbaum | Jan 2002 | B1 |
| 6349343 | Foody et al. | Feb 2002 | B1 |
| 6374263 | Bunger et al. | Apr 2002 | B1 |
| 6389433 | Bolosky et al. | May 2002 | B1 |
| 6393581 | Friedman et al. | May 2002 | B1 |
| 6397246 | Wolfe | May 2002 | B1 |
| 6412004 | Chen et al. | Jun 2002 | B1 |
| 6438595 | Blumenau et al. | Aug 2002 | B1 |
| 6466580 | Leung | Oct 2002 | B1 |
| 6469983 | Narayana et al. | Oct 2002 | B2 |
| 6477544 | Bolosky et al. | Nov 2002 | B1 |
| 6487561 | Ofek et al. | Nov 2002 | B1 |
| 6493804 | Soltis et al. | Dec 2002 | B1 |
| 6516350 | Lumelsky et al. | Feb 2003 | B1 |
| 6516351 | Borr | Feb 2003 | B2 |
| 6542909 | Tamer et al. | Apr 2003 | B1 |
| 6549916 | Sedlar | Apr 2003 | B1 |
| 6553352 | Delurgio et al. | Apr 2003 | B2 |
| 6556997 | Levy | Apr 2003 | B1 |
| 6556998 | Mukherjee et al. | Apr 2003 | B1 |
| 6560230 | Li et al. | May 2003 | B1 |
| 6601101 | Lee et al. | Jul 2003 | B1 |
| 6606663 | Liao et al. | Aug 2003 | B1 |
| 6612490 | Herrendoerfer et al. | Sep 2003 | B1 |
| 6654346 | Mahalingaiah et al. | Nov 2003 | B1 |
| 6721794 | Taylor et al. | Apr 2004 | B2 |
| 6728265 | Yavatkar et al. | Apr 2004 | B1 |
| 6738357 | Richter et al. | May 2004 | B1 |
| 6738790 | Klein et al. | May 2004 | B1 |
| 6742035 | Zayas et al. | May 2004 | B1 |
| 6744776 | Kalkunte et al. | Jun 2004 | B1 |
| 6748420 | Quatrano et al. | Jun 2004 | B1 |
| 6754215 | Arikawa et al. | Jun 2004 | B1 |
| 6757706 | Dong et al. | Jun 2004 | B1 |
| 6775672 | Mahalingam et al. | Aug 2004 | B2 |
| 6775673 | Mahalingam et al. | Aug 2004 | B2 |
| 6775679 | Gupta | Aug 2004 | B2 |
| 6782450 | Amott et al. | Aug 2004 | B2 |
| 6801960 | Ericson et al. | Oct 2004 | B1 |
| 6826613 | Wang et al. | Nov 2004 | B1 |
| 6839761 | Kadyk et al. | Jan 2005 | B2 |
| 6847959 | Arrouye et al. | Jan 2005 | B1 |
| 6847970 | Keller et al. | Jan 2005 | B2 |
| 6850997 | Rooney et al. | Feb 2005 | B1 |
| 6871245 | Bradley | Mar 2005 | B2 |
| 6880017 | Marce et al. | Apr 2005 | B1 |
| 6889249 | Miloushev et al. | May 2005 | B2 |
| 6914881 | Mansfield et al. | Jul 2005 | B1 |
| 6922688 | Frey, Jr. | Jul 2005 | B1 |
| 6934706 | Mancuso et al. | Aug 2005 | B1 |
| 6938039 | Bober et al. | Aug 2005 | B1 |
| 6938059 | Tamer et al. | Aug 2005 | B2 |
| 6959373 | Testardi | Oct 2005 | B2 |
| 6961815 | Kistler et al. | Nov 2005 | B2 |
| 6973455 | Vahalia et al. | Dec 2005 | B1 |
| 6973549 | Testardi | Dec 2005 | B1 |
| 6975592 | Seddigh et al. | Dec 2005 | B1 |
| 6985936 | Agarwalla et al. | Jan 2006 | B2 |
| 6985956 | Luke et al. | Jan 2006 | B2 |
| 6986015 | Testardi | Jan 2006 | B2 |
| 6990114 | Erimli et al. | Jan 2006 | B1 |
| 6990547 | Ulrich et al. | Jan 2006 | B2 |
| 6990667 | Ulrich et al. | Jan 2006 | B2 |
| 6996841 | Kadyk et al. | Feb 2006 | B2 |
| 7003533 | Noguchi et al. | Feb 2006 | B2 |
| 7006981 | Rose et al. | Feb 2006 | B2 |
| 7010553 | Chen et al. | Mar 2006 | B2 |
| 7013379 | Testardi | Mar 2006 | B1 |
| 7020644 | Jameson | Mar 2006 | B2 |
| 7020669 | McCann et al. | Mar 2006 | B2 |
| 7024427 | Bobbitt et al. | Apr 2006 | B2 |
| 7039061 | Connor et al. | May 2006 | B2 |
| 7051112 | Dawson | May 2006 | B2 |
| 7054998 | Amott et al. | May 2006 | B2 |
| 7072917 | Wong et al. | Jul 2006 | B2 |
| 7075924 | Richter et al. | Jul 2006 | B2 |
| 7089286 | Malik | Aug 2006 | B1 |
| 7111115 | Peters et al. | Sep 2006 | B2 |
| 7113962 | Kee et al. | Sep 2006 | B1 |
| 7120728 | Krakirian et al. | Oct 2006 | B2 |
| 7120746 | Campbell et al. | Oct 2006 | B2 |
| 7127556 | Blumenau et al. | Oct 2006 | B2 |
| 7133967 | Fujie et al. | Nov 2006 | B2 |
| 7143146 | Nakatani et al. | Nov 2006 | B2 |
| 7146524 | Patel et al. | Dec 2006 | B2 |
| 7152184 | Maeda et al. | Dec 2006 | B2 |
| 7155466 | Rodriguez et al. | Dec 2006 | B2 |
| 7165095 | Sim | Jan 2007 | B2 |
| 7167821 | Hardwick et al. | Jan 2007 | B2 |
| 7171469 | Ackaouy et al. | Jan 2007 | B2 |
| 7173929 | Testardi | Feb 2007 | B1 |
| 7194579 | Robinson et al. | Mar 2007 | B2 |
| 7234074 | Cohn et al. | Jun 2007 | B2 |
| 7236491 | Tsao et al. | Jun 2007 | B2 |
| 7280536 | Testardi | Oct 2007 | B2 |
| 7284150 | Ma et al. | Oct 2007 | B2 |
| 7293097 | Borr | Nov 2007 | B2 |
| 7293099 | Kalajan | Nov 2007 | B1 |
| 7293133 | Colgrove et al. | Nov 2007 | B1 |
| 7343351 | Bishop et al. | Mar 2008 | B1 |
| 7343398 | Lownsbrough | Mar 2008 | B1 |
| 7346664 | Wong et al. | Mar 2008 | B2 |
| 7383288 | Miloushev et al. | Jun 2008 | B2 |
| 7401220 | Bolosky et al. | Jul 2008 | B2 |
| 7406484 | Srinivasan et al. | Jul 2008 | B1 |
| 7415488 | Muth et al. | Aug 2008 | B1 |
| 7415608 | Bolosky et al. | Aug 2008 | B2 |
| 7440982 | Lu et al. | Oct 2008 | B2 |
| 7457982 | Rajan | Nov 2008 | B2 |
| 7467158 | Marinescu | Dec 2008 | B2 |
| 7475146 | Bazot et al. | Jan 2009 | B2 |
| 7475241 | Patel et al. | Jan 2009 | B2 |
| 7477796 | Sasaki et al. | Jan 2009 | B2 |
| 7509322 | Miloushev et al. | Mar 2009 | B2 |
| 7512673 | Miloushev et al. | Mar 2009 | B2 |
| 7519813 | Cox et al. | Apr 2009 | B1 |
| 7562110 | Miloushev et al. | Jul 2009 | B2 |
| 7571168 | Bahar et al. | Aug 2009 | B2 |
| 7574433 | Engel | Aug 2009 | B2 |
| 7587471 | Yasuda et al. | Sep 2009 | B2 |
| 7590747 | Coates et al. | Sep 2009 | B2 |
| 7599941 | Bahar et al. | Oct 2009 | B2 |
| 7610307 | Havewala et al. | Oct 2009 | B2 |
| 7610390 | Yared et al. | Oct 2009 | B2 |
| 7624109 | Testardi | Nov 2009 | B2 |
| 7639883 | Gill | Dec 2009 | B2 |
| 7644109 | Manley et al. | Jan 2010 | B2 |
| 7653699 | Colgrove et al. | Jan 2010 | B1 |
| 7685177 | Hagerstrom et al. | Mar 2010 | B1 |
| 7689596 | Tsunoda | Mar 2010 | B2 |
| 7694082 | Golding et al. | Apr 2010 | B2 |
| 7711771 | Kimos | May 2010 | B2 |
| 7734603 | McManis | Jun 2010 | B1 |
| 7743035 | Chen et al. | Jun 2010 | B2 |
| 7752294 | Meyer et al. | Jul 2010 | B2 |
| 7769711 | Srinivasan et al. | Aug 2010 | B2 |
| 7788335 | Miloushev et al. | Aug 2010 | B2 |
| 7793342 | Ebrahimi et al. | Sep 2010 | B1 |
| 7809691 | Karmarkar et al. | Oct 2010 | B1 |
| 7818299 | Federwisch et al. | Oct 2010 | B1 |
| 7822939 | Veprinsky et al. | Oct 2010 | B1 |
| 7831639 | Panchbudhe et al. | Nov 2010 | B1 |
| 7836493 | Xia et al. | Nov 2010 | B2 |
| 7849112 | Mane et al. | Dec 2010 | B2 |
| 7870154 | Shitomi et al. | Jan 2011 | B2 |
| 7877511 | Berger et al. | Jan 2011 | B1 |
| 7885970 | Lacapra | Feb 2011 | B2 |
| 7904466 | Valencia et al. | Mar 2011 | B1 |
| 7913053 | Newland | Mar 2011 | B1 |
| 7953701 | Okitsu et al. | May 2011 | B2 |
| 7958347 | Ferguson | Jun 2011 | B1 |
| 8005953 | Miloushev et al. | Aug 2011 | B2 |
| 8046547 | Chatterjee et al. | Oct 2011 | B1 |
| 8103622 | Karinta | Jan 2012 | B1 |
| 8112392 | Bunnell et al. | Feb 2012 | B1 |
| 8271751 | Hinrichs, Jr. | Sep 2012 | B2 |
| 8326798 | Driscoll et al. | Dec 2012 | B1 |
| 8351600 | Resch | Jan 2013 | B2 |
| 20010007560 | Masuda et al. | Jul 2001 | A1 |
| 20010014891 | Hoffert et al. | Aug 2001 | A1 |
| 20010047293 | Waller et al. | Nov 2001 | A1 |
| 20010051955 | Wong | Dec 2001 | A1 |
| 20020035537 | Waller et al. | Mar 2002 | A1 |
| 20020059263 | Shima et al. | May 2002 | A1 |
| 20020065810 | Bradley | May 2002 | A1 |
| 20020073105 | Noguchi et al. | Jun 2002 | A1 |
| 20020083118 | Sim | Jun 2002 | A1 |
| 20020087887 | Busam et al. | Jul 2002 | A1 |
| 20020106263 | Winker | Aug 2002 | A1 |
| 20020120763 | Miloushev et al. | Aug 2002 | A1 |
| 20020133330 | Loisey et al. | Sep 2002 | A1 |
| 20020133491 | Sim et al. | Sep 2002 | A1 |
| 20020138502 | Gupta | Sep 2002 | A1 |
| 20020143909 | Botz et al. | Oct 2002 | A1 |
| 20020147630 | Rose et al. | Oct 2002 | A1 |
| 20020150253 | Brezak et al. | Oct 2002 | A1 |
| 20020156905 | Weissman | Oct 2002 | A1 |
| 20020161911 | Pinckney et al. | Oct 2002 | A1 |
| 20020188667 | Kimos | Dec 2002 | A1 |
| 20020194342 | Lu et al. | Dec 2002 | A1 |
| 20030005280 | Bobde et al. | Jan 2003 | A1 |
| 20030009429 | Jameson | Jan 2003 | A1 |
| 20030012382 | Ferchichi et al. | Jan 2003 | A1 |
| 20030028514 | Lord et al. | Feb 2003 | A1 |
| 20030033308 | Patel et al. | Feb 2003 | A1 |
| 20030033535 | Fisher et al. | Feb 2003 | A1 |
| 20030061240 | McCann et al. | Mar 2003 | A1 |
| 20030065956 | Belapurkar et al. | Apr 2003 | A1 |
| 20030115218 | Bobbitt et al. | Jun 2003 | A1 |
| 20030115439 | Mahalingam et al. | Jun 2003 | A1 |
| 20030128708 | Inoue et al. | Jul 2003 | A1 |
| 20030135514 | Patel et al. | Jul 2003 | A1 |
| 20030149781 | Yared et al. | Aug 2003 | A1 |
| 20030156586 | Lee et al. | Aug 2003 | A1 |
| 20030159072 | Bellinger et al. | Aug 2003 | A1 |
| 20030171978 | Jenkins et al. | Sep 2003 | A1 |
| 20030177364 | Walsh et al. | Sep 2003 | A1 |
| 20030177388 | Botz et al. | Sep 2003 | A1 |
| 20030179755 | Fraser | Sep 2003 | A1 |
| 20030200207 | Dickinson | Oct 2003 | A1 |
| 20030204635 | Ko et al. | Oct 2003 | A1 |
| 20040003266 | Moshir et al. | Jan 2004 | A1 |
| 20040006575 | Visharam et al. | Jan 2004 | A1 |
| 20040010654 | Yasuda et al. | Jan 2004 | A1 |
| 20040017825 | Stanwood et al. | Jan 2004 | A1 |
| 20040025013 | Parker et al. | Feb 2004 | A1 |
| 20040028043 | Maveli et al. | Feb 2004 | A1 |
| 20040028063 | Roy et al. | Feb 2004 | A1 |
| 20040030857 | Krakirian et al. | Feb 2004 | A1 |
| 20040044705 | Stager et al. | Mar 2004 | A1 |
| 20040054748 | Ackaouy et al. | Mar 2004 | A1 |
| 20040054777 | Ackaouy et al. | Mar 2004 | A1 |
| 20040093474 | Lin et al. | May 2004 | A1 |
| 20040098383 | Tabellion et al. | May 2004 | A1 |
| 20040098595 | Aupperle et al. | May 2004 | A1 |
| 20040133573 | Miloushev et al. | Jul 2004 | A1 |
| 20040133577 | Miloushev et al. | Jul 2004 | A1 |
| 20040133606 | Miloushev et al. | Jul 2004 | A1 |
| 20040133607 | Miloushev et al. | Jul 2004 | A1 |
| 20040133650 | Miloushev et al. | Jul 2004 | A1 |
| 20040133652 | Miloushev et al. | Jul 2004 | A1 |
| 20040139355 | Axel et al. | Jul 2004 | A1 |
| 20040148380 | Meyer et al. | Jul 2004 | A1 |
| 20040153479 | Mikesell et al. | Aug 2004 | A1 |
| 20040181605 | Nakatani et al. | Sep 2004 | A1 |
| 20040199547 | Winter et al. | Oct 2004 | A1 |
| 20040213156 | Smallwood et al. | Oct 2004 | A1 |
| 20040236798 | Srinivasan et al. | Nov 2004 | A1 |
| 20040267830 | Wong et al. | Dec 2004 | A1 |
| 20050021615 | Amott et al. | Jan 2005 | A1 |
| 20050050107 | Mane et al. | Mar 2005 | A1 |
| 20050091214 | Probert et al. | Apr 2005 | A1 |
| 20050108575 | Yung | May 2005 | A1 |
| 20050114291 | Becker-Szendy et al. | May 2005 | A1 |
| 20050114701 | Atkins et al. | May 2005 | A1 |
| 20050117589 | Douady et al. | Jun 2005 | A1 |
| 20050160161 | Barrett et al. | Jul 2005 | A1 |
| 20050175013 | Le Pennec et al. | Aug 2005 | A1 |
| 20050187866 | Lee | Aug 2005 | A1 |
| 20050198501 | Andreev et al. | Sep 2005 | A1 |
| 20050213587 | Cho et al. | Sep 2005 | A1 |
| 20050246393 | Coates et al. | Nov 2005 | A1 |
| 20050289109 | Arrouye et al. | Dec 2005 | A1 |
| 20050289111 | Tribble et al. | Dec 2005 | A1 |
| 20060010502 | Mimatsu et al. | Jan 2006 | A1 |
| 20060045096 | Farmer et al. | Mar 2006 | A1 |
| 20060074922 | Nishimura | Apr 2006 | A1 |
| 20060075475 | Boulos et al. | Apr 2006 | A1 |
| 20060080353 | Miloushev et al. | Apr 2006 | A1 |
| 20060106882 | Douceur et al. | May 2006 | A1 |
| 20060112151 | Manley et al. | May 2006 | A1 |
| 20060123062 | Bobbitt et al. | Jun 2006 | A1 |
| 20060140193 | Kakani et al. | Jun 2006 | A1 |
| 20060153201 | Hepper et al. | Jul 2006 | A1 |
| 20060161518 | Lacapra | Jul 2006 | A1 |
| 20060167838 | Lacapra | Jul 2006 | A1 |
| 20060179261 | Rajan | Aug 2006 | A1 |
| 20060184589 | Lees et al. | Aug 2006 | A1 |
| 20060190496 | Tsunoda | Aug 2006 | A1 |
| 20060200470 | Lacapra et al. | Sep 2006 | A1 |
| 20060206547 | Kulkarni et al. | Sep 2006 | A1 |
| 20060212746 | Amegadzie et al. | Sep 2006 | A1 |
| 20060218135 | Bisson et al. | Sep 2006 | A1 |
| 20060224636 | Kathuria et al. | Oct 2006 | A1 |
| 20060224687 | Popkin et al. | Oct 2006 | A1 |
| 20060230265 | Krishna | Oct 2006 | A1 |
| 20060242179 | Chen et al. | Oct 2006 | A1 |
| 20060259949 | Schaefer et al. | Nov 2006 | A1 |
| 20060268692 | Wright et al. | Nov 2006 | A1 |
| 20060271598 | Wong et al. | Nov 2006 | A1 |
| 20060277225 | Mark et al. | Dec 2006 | A1 |
| 20060282461 | Marinescu | Dec 2006 | A1 |
| 20060282471 | Mark et al. | Dec 2006 | A1 |
| 20070022121 | Bahar et al. | Jan 2007 | A1 |
| 20070024919 | Wong et al. | Feb 2007 | A1 |
| 20070027929 | Whelan | Feb 2007 | A1 |
| 20070027935 | Haselton et al. | Feb 2007 | A1 |
| 20070028068 | Golding et al. | Feb 2007 | A1 |
| 20070053297 | Wu et al. | Mar 2007 | A1 |
| 20070088702 | Fridella et al. | Apr 2007 | A1 |
| 20070098284 | Sasaki et al. | May 2007 | A1 |
| 20070136308 | Tsirigotis et al. | Jun 2007 | A1 |
| 20070139227 | Speirs et al. | Jun 2007 | A1 |
| 20070180314 | Kawashima et al. | Aug 2007 | A1 |
| 20070208748 | Li | Sep 2007 | A1 |
| 20070209075 | Coffman | Sep 2007 | A1 |
| 20070226331 | Srinivasan et al. | Sep 2007 | A1 |
| 20080046432 | Anderson et al. | Feb 2008 | A1 |
| 20080070575 | Claussen et al. | Mar 2008 | A1 |
| 20080091807 | Strub | Apr 2008 | A1 |
| 20080104443 | Akutsu et al. | May 2008 | A1 |
| 20080114718 | Anderson et al. | May 2008 | A1 |
| 20080189468 | Schmidt et al. | Aug 2008 | A1 |
| 20080200207 | Donahue et al. | Aug 2008 | A1 |
| 20080208933 | Lyon | Aug 2008 | A1 |
| 20080209073 | Tang | Aug 2008 | A1 |
| 20080215836 | Sutoh et al. | Sep 2008 | A1 |
| 20080222223 | Srinivasan et al. | Sep 2008 | A1 |
| 20080243769 | Arbour et al. | Oct 2008 | A1 |
| 20080282047 | Arakawa et al. | Nov 2008 | A1 |
| 20080294446 | Guo et al. | Nov 2008 | A1 |
| 20090007162 | Sheehan | Jan 2009 | A1 |
| 20090013138 | Sudhakar | Jan 2009 | A1 |
| 20090037975 | Ishikawa et al. | Feb 2009 | A1 |
| 20090041230 | Williams | Feb 2009 | A1 |
| 20090055507 | Oeda | Feb 2009 | A1 |
| 20090077097 | Lacapra et al. | Mar 2009 | A1 |
| 20090089344 | Brown | Apr 2009 | A1 |
| 20090094252 | Wong et al. | Apr 2009 | A1 |
| 20090106255 | Lacapra et al. | Apr 2009 | A1 |
| 20090106263 | Khalid et al. | Apr 2009 | A1 |
| 20090132616 | Winter et al. | May 2009 | A1 |
| 20090204649 | Wong et al. | Aug 2009 | A1 |
| 20090204650 | Wong et al. | Aug 2009 | A1 |
| 20090204705 | Marinov et al. | Aug 2009 | A1 |
| 20090210431 | Marinkovic et al. | Aug 2009 | A1 |
| 20090210875 | Bolles et al. | Aug 2009 | A1 |
| 20090240705 | Miloushev et al. | Sep 2009 | A1 |
| 20090240899 | Akagawa et al. | Sep 2009 | A1 |
| 20090254592 | Marinov et al. | Oct 2009 | A1 |
| 20090265396 | Ram et al. | Oct 2009 | A1 |
| 20100017643 | Baba et al. | Jan 2010 | A1 |
| 20100077294 | Watson | Mar 2010 | A1 |
| 20100082542 | Feng et al. | Apr 2010 | A1 |
| 20100205206 | Rabines et al. | Aug 2010 | A1 |
| 20100211547 | Kamei et al. | Aug 2010 | A1 |
| 20100325634 | Ichikawa et al. | Dec 2010 | A1 |
| 20110083185 | Sheleheda et al. | Apr 2011 | A1 |
| 20110087696 | Lacapra | Apr 2011 | A1 |
| 20110093471 | Brockway et al. | Apr 2011 | A1 |
| 20110107112 | Resch | May 2011 | A1 |
| 20110119234 | Schack et al. | May 2011 | A1 |
| 20110320882 | Beaty et al. | Dec 2011 | A1 |
| 20120144229 | Nadolski | Jun 2012 | A1 |
| 20120150699 | Trapp et al. | Jun 2012 | A1 |
| 20150207695 | Varney | Jul 2015 | A1 |
| 20170302470 | Clark | Oct 2017 | A1 |
| 20170332421 | Sternberg | Nov 2017 | A1 |
| 20170359252 | Kumar | Dec 2017 | A1 |
| 20180115468 | Bildhauer | Apr 2018 | A1 |
| 20180227185 | Turner | Aug 2018 | A1 |
| 20190018760 | Webb | Jan 2019 | A1 |
| 20190268232 | Garcia Azorero | Aug 2019 | A1 |
| 20190268384 | Hu | Aug 2019 | A1 |
| 20190349426 | Smith | Nov 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003300350 | Jul 2004 | AU |
| 2080530 | Apr 1994 | CA |
| 2512312 | Jul 2004 | CA |
| 0605088 | Feb 1996 | EP |
| 0738970 | Oct 1996 | EP |
| 63-10250 | Jan 1988 | JP |
| 06-205006 | Jul 1994 | JP |
| 06-332782 | Dec 1994 | JP |
| 08-021924 | Mar 1996 | JP |
| 08-328760 | Dec 1996 | JP |
| 08-339335 | Dec 1996 | JP |
| 09-16510 | Jan 1997 | JP |
| 11-282741 | Oct 1999 | JP |
| 2000-183935 | Jun 2000 | JP |
| 566291 | Dec 2008 | NZ |
| 2002039696 | May 2002 | WO |
| 2002056181 | Jul 2002 | WO |
| 2004061605 | Jul 2004 | WO |
| 2006091040 | Aug 2006 | WO |
| 20080130983 | Oct 2008 | WO |
| 20080147973 | Dec 2008 | WO |
| 2009064720 | May 2009 | WO |
| Entry |
|---|
| Ott et al., “A Mechanism for TCP-Friendly Transport-level Protocol Coordination,” USENIX Annual Technical Conference, University of North Carolina at Chapel Hill, pp. 1-12, Jun. 10, 2002. |
| Padmanabhan et al., “Using Predictive Prefetching to Improve World Wide Web Latency”, ACM SIGCOMM Computer Communication Review, vol. 26, No. 3, pp. 22-36, Jul. 1996. |
| Pashalidis et al., “A Taxonomy of Single Sign-On Systems,” Australasian Conference on Informatiion Security and Privacy, pp. 249-264, Springer, Berlin, Heidelberg, Jul. 9, 2003. |
| Pashalidis et al., “Impostor: A Single Sign-On System for Use From Untrusted Devices,” 5 pp, IEEE Global Telecommunications Conference, 2004, GLOBECOM '04, Nov. 29-Dec. 3, 2004. |
| Patterson et al., “A Case for Redundant Arrays of Inexpensive Disks (RAID),” SIGMOD '88 Proceedings of ACM SIGMOD International Conference on Management of Data, pp. 109-116, Jun. 1-3, 1988. |
| Pearson, Peter K, “Fast Hashing of Variable-Length Text Strings,” Communications of the ACM, pp. 677-680, vol. 33, No. 6, Jun. 1990. |
| Peterson, Michael, “Introducing Storage Area Networks,” Infostor, InfoStor, 6 pp, Feb. 1998. |
| Preslan et al., “Scalability and Failure Recovery in a Linux Cluster File System,” in Proceedings of the 4th Annual Linux Showcase & Conference, 17 pp, Atlanta, Georgia, Oct. 10-14, 2000. |
| Rodriguez et al., “Parallel-Access for Mirror Sites in the Internet,” Proceedings IEEE Infocom 2000, pp. 864-873, Conference on Computer Communications, Nineteenth Annual Joint Conference of the IEEE Computer and Communications Societies, Mar. 26, 2000. |
| Rosen et al., “MPLS Label Stack Encoding,” Network Working Group, Request for Comments 3032, Standards Track, 23 pp, Jan. 2001. |
| “Welcome to the RSYNC Web Pages,” RSYNC, http://samba.anu.edu.au/rsync/, Retrieved on Dec. 18, 2009. |
| Savage et al., “AFRAID—A Frequently Redundant Array of Independent Disks,” Proceedings of the USENIX 1996 Annual Technical Conference, San Diego, California, Jan. 1996. |
| Soltis et al., “The Design and Performance of Shared Disk File System for IRIX,” 6th NASA Goddard Space Flight Center Conference on Mass Storage & Technologies, 15th IEEE Symposium on Mass Storage Systems, 17 pp, Mar. 23-26, 1998. |
| Soltis et al., “The Global File System,” 24 pages, Fifth NASA Goddard Conference on Mass Storage Systems and Technologies, NASA Conference Publication 3340, vol. II, Sep. 17-19, 1996. |
| Sorenson, K.M., “Installation and Administration” Kimberlite Cluster Version 1.1.0, Revision D, 136 pp, Mission Critical Linux, Dec. 2000. |
| Stakutis, Chris, “Benefits of SAN-Based File System Sharing,” InfoStor, Jul. 2000. |
| Thekkath et al., “Frangipani: A Scalable Distributed File System,” Proceedings of the 16th ACM Symposium on Operating Systems Principles, Oct. 1997. |
| “Microsoft Encyclopedia of Security,” pp. 218, 300-301, Mitch Tulloch, Microsoft Press, Redmond, Washington, 2003. |
| Wang Bing, “Priority and Realtime Data Transfer Over the Best-Effort Internet,” A Dissertation, UMI No. 3193954, Sep. 2005. |
| “Content-Centric Networking”, Wikipedia, pp. 1-4, en.wikipedia.org/wiki/Content-centric_networking, Oct. 31, 2012. |
| Wilkes, J et al., “The HP AutoRAID Hierarchical Storage System,” pp. 1-29, ACM Transactions on Computer Systems, vol. 14, No. 1, Feb. 1996. |
| Woo Thomas Y.C., “A Modular Approach to Packet Classification: Algorithms and Results,” Proceedings IEEE Infocom 2000, Conference on Computer Communications, Nineteenth Annual Joint Conference of the IEEE Computer and Communications Societies, Cat. No. 00CH37064, vol. 3, Mar. 26-30, 2000. |
| Zayas, Edward R., “AFS-3 Programmer's Reference: Architectural Overview,” AFS-3 Design Goals, Transarc Corporation, Version 1.0, Sep. 2, 1991. |
| “Ankeena is now part of Juniper Networks,” AMDS-Ankeena, Obtained from http://www.ankeena.com/technology, 1 pp, last accessed Jun. 2, 2010. |
| “A Storage Architecture Guide,” Second Edition, Auspex Systems, Inc., 71 pp, 2001. |
| “CSA Persistent File System Technology,” Colorado Software Architecture, Inc., A White Paper, pp. 1-3, Jan. 1, 1999. |
| “Deploying the BIG-IP LTM With Multiple Big-IP AAM and ASM Devices,” Deployment Guide, F5 Networks, Inc., pp. 1-14, Feb. 4, 2015. |
| “Distributed File System: Logical View of Physical Storage,” White Paper, Microsoft Corp., pp. 1-26, last accessed on Dec. 20, 2002. |
| “How DFS Works: Remote File Systems,” Distributed File System (DFS) Technical Reference, retrieved from the Internet on Feb. 13, 2009: URL:http://technetmicrosoft.com/en-us/library/cc782417.aspx>(2003). |
| “Disk Striping,” NERSC Tutorials: I/O on the Cray T3E, Chapter 8, pp. 1-9, Feb. 21, 2002. |
| “Scaling Next Generation Web Infrastructure with Content-Intelligent Switching,” White Paper, Alteon WebSystems, Inc., 10 pp, Apr. 2000. |
| “The AFS File System in Distributed Computing Environments,” IBM, http://www_transarcibm_com/Library/whitepapers/AFS/afsoverview.html, 6 pp, last accessed Dec. 20, 2002. |
| “New VERITAS Volume Management and File System Technology for Cluster Environments,” VERITAS SANPoint Foundation Suite™and SANPoint Foundation Suite™ HA, VERITAS White Paper, VERITAS Software Corporation, 27 pp, Sep. 2001. |
| “Welcome to the RSYNC Web Pages,” http://samba.anu.edu.au/rsync/, 5 pp, last accessed Dec. 18, 2009. |
| “Windows Clustering Technologies—An Overview,” Microsoft® Windows® 2000 Server Technical Aid, 31 pp, Nov. 2001. |
| Aguilera et al., “Improving Recoverability in Multi-Tier Storage Systems,” International Conference on Dependable Systems and Networks (DSN-2007), Edinburgh, Scotland, 10 pages, Jun. 2007. |
| Anderson et al., “Serverless Network File System, The 15th Symposium on Operating Systems Principles,” Computer Science Division, University of California at Berkeley, pp. 1-18, Dec. 1995. |
| Anderson et al., “Interposed Request Routing for Scalable Network Storage,” ACM Transactions on Computer Systems 20(1):25-48 (Feb. 2002). |
| “Tiger Developer Overview Series: Working with Spotlight,” Apple Computer, Inc., <http://web.archive.org/web/20041123005335/developerapple.com/macosx/tiger/spotlight_html>, pp. 1-11, Nov. 2, 2004. |
| Transcription of “Mac Os X Keynote Intro. Part 2,” Apple Computers, Inc., http://youtube.com/watch?v=zSBJwEmRJbY, pp. 1-6, Jun. 2004. |
| Basney et al., “Credential Wallets: A Classification of Credential Repositories Highlighting MyProxy,” 31st Research Conference on Communication, Information and Internet Policy (TPRC 2003), pp. 1-20, Sep. 19-21, 2003. |
| Botzum, Keys, “Single Sign On—A Contrarian View,” IBM Software Services for WebSphere, SSO—A Contrarian View, pp. 1-8, Aug. 6, 2001. |
| Cabrera et al., “Swift: A Storage Architecture for Large Objects,” Digest of Papers Eleventh IEEE Symposium on Mass Storage Systems, Conference Paper, 7 pp, Oct. 7-10, 1991. |
| Cabrera et al., “Swift: Using Distributed Disk Striping to Provide High I/O Data Rates,” Computing Systems, 4(1):405-436, Fall 1991. |
| Cabrera et al., “Using Data Striping in a Local Area Network,” Technical Report UCSC-CRL-92-09, University of Califomia at Santa Cruz, Mar. 1, 1992. |
| Callaghan et al., “NFS Version 3 Protocol Specification” Network Working Group, Request for Comments 1813, Category Informal, Sun Microsystems, Inc., 126 pp., Jun. 1995. |
| Carns et al., “PVFS: A Parallel File System for Linux Clusters,” Proceedings of the Extreme Linux Track: 4th Annual Linux Showcase and Conference, 11 pp, Atlanta, Georgia, Oct. 10-14, 2000. |
| Cavale, Mohan., “Introducing Microsoft Cluster Service (MSCS) in the Windows Server 2003 Family,” Microsoft Corporation, 10 pp, Nov. 2002. |
| English Translation of Notification of Reason(s) for Refusal for JP 2002-556371, Dispatch Date: Jan. 22, 2007. |
| Fan et al., “Summary Cache: A Scalable Wide-Area Protocol,” CM SIGCOMM Computer Communications Review, 28(4), pp. 254-265. |
| Farley, Marc, “Building Storage Networks,” Second Edition, Book Review, Osborne McGraw Hill, ISBN 0072120725, Aug. 6, 2002. |
| Gibson et al., “File Server Scaling with Network-Attached Secure Disks,” Proceedings of the ACM International Conference on Measurement and Modeling of Computer Systems, 13 pages, (Sigmetrics '97), Seattle, Washington, Jun. 15-18, 1997. |
| Gibson et al., “NASD Scalable Storage Systems,” Proceedings of USENIX 1999, Linux Workshop, Monterey, Califonia, pp. 1-6, Jun. 9-11, 1999. |
| Gupta et al., “Algorithms for Packet Classification,” Stanford University, IEEE Network, pp. 24-32, Mar./Apr. 2001. |
| EP Response filed May 19, 2008 to Official EP Communication dated Nov. 9, 2007 in corresponding European Patent Application No. 02718824.2, 3 pp. |
| Hartman, John Henry, “The Zebra Striped Network File System,” A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate Division of the University of California at Berkeley, 160 pp, 1994. |
| Haskin et al., “The Tiger Shark File System,” COMPCON '96, Technologies for the Information Superhighway Digest of Papers, Santa Clara, CA, Feb. 25-28, 1996. |
| Heinz II Gerald J, “Priorities in Stream Transmission Control Protocol (SCTP) Multistreaming,” 35 pp, University of Delaware, Department of Computer and Information Sciences, Spring 2003. |
| Hwang et al., “Designing SSI Clusters with Hierarchical Checkpointing and Single I/O Space,” IEEE Concurrency, 7(11):60-69, Jan.-Mar. 1999. |
| Ilvesmaki et al., “On the Capabilities of Application Level Traffic Measurements to Differentiate and Classify Internet Traffic,” SPIE Proceedings Series, Denver, Colorado, 11 pp, Aug. 19-21, 2001. |
| Internet Protocol,“DARPA Internet Program Protocol Specification”, (RFC: 791), prepared for Defense Advanced Research Projects Agency, Information Processing Techniques Office, Information Sciences Institute, University of Southern California, pp. 1-49, Sep. 1981. |
| Jacobson, Van, “A New Way to look at Networking,” Google Tech Talks, (http://www.youtube.com/watch?r=oCZMoY3q2uM), 2 pp, Aug. 30, 2006. |
| Jacobson, Van, “Introduction to Content Centric Networking,” FISS 09, Presentation, Bremen, Germany, 96 pp, Jun. 22, 2009. |
| Karamanolis et al., “An Architecture for Scalable and Manageable File Services,” Internet Systems and Storage Laboratory, HP Laboratories, HPL-2001-173, 16 pp, Jul. 26, 2001. |
| Katsurashima. et al., “NAS Switch: A Novel CIFS Server Virtualization,” Proceedings, 20th IEEE/11th NASA Goddard Conference on Mass Storage Systems and Technologies, (MSST 2003), 5 pp, 2003. |
| Kimball et al., “Automated Client-Side Integration of Distributed Application Servers,” Proceedings of LISA '99: 13th Systems Administration Conference, pp. 275-282 of the Proceedings, Nov. 7-12, 1999. |
| Kohl et al., “The Kerberos Network Authentication Service (V5),” Network Working Group, Request for Comments 1510, pp. 1-112, Sep. 1993. |
| Lelil, S, “Storage Technology News: AutoVirt adds tool to help data migration projects,” pp. 1-3 <http://searchstorage.techtarget.com/news/article/0,289142,sid5_gci1527986,00_html>, Feb. 25, 2011. |
| Long et al., “Swift/RAID: A Distributed RAID System,” the Usenix Association, Computing Systems, vol. 7, No. 3, pp. 333-359, Summer 1994. |
| Modiano Eytan, “Scheduling Algorithms for Message Transmission Over a Satellite Broadcast System,” MIT Lincoln Laboratory Advanced Network Group, pp. 1-7, Nov. 1997. |
| Noghani et al., “A Novel Approach to Reduce Latency on the Internet: Component-Based Download,” Department of Electrical and Computer Engineering, Univesity of Manitoba, Winnipeg, Jun. 2000. |
| “Common Internet File System (CIFS) Version CIFS-Spec 0.9,” Storage Networking Industry Association, Work Group In Progress, Revision Date: Mar. 26, 2001. |
| Novotny et al., “An Online Credential Repository for the Grid: MyProxy,” Proceedings 10th IEEE International Symosium on High Performance Distributed Computing, 8 pp, Aug. 7-9, 2001. |
| Number | Date | Country | |
|---|---|---|---|
| 62636929 | Mar 2018 | US |
