Managing request routing information utilizing client identifiers

Information

  • Patent Grant
  • 11108729
  • Patent Number
    11,108,729
  • Date Filed
    Wednesday, May 24, 2017
    7 years ago
  • Date Issued
    Tuesday, August 31, 2021
    3 years ago
Abstract
Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. The request routing functionality can correspond to the processing of domain name service (“DNS”) requests for resources by computing devices and the resolution of the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Based on the processing of DNS queries initiated by a client computing device, a CDN service provider can correlate client computing device identifiers, such as an Internet Protocol (“IP”) address, with identifiers (e.g., IP addresses) associated with other components in a content delivery environment, such as DNS resolvers associated with the client computing device.
Description
BACKGROUND

Generally described, computing devices and communication networks can be utilized to exchange information. In a common application, a computing device can request content from another computing device via the communication network. For example, a user at a personal computing device can utilize a software browser application to request a Web page from a server computing device via the Internet. In such embodiments, the user computing device can be referred to as a client computing device and the server computing device can be referred to as a content provider.


Content providers are generally motivated to provide requested content to client computing devices often with consideration of efficient transmission of the requested content to the client computing device and/or consideration of a cost associated with the transmission of the content. For larger scale implementations, a content provider may receive content requests from a high volume of client computing devices which can place a strain on the content provider's computing resources. Additionally, the content requested by the client computing devices may have a number of components, which can further place additional strain on the content provider's computing resources.


With reference to an illustrative example, a requested Web page, or original content, may be associated with a number of additional resources, such as images or videos, which are to be displayed with the Web page. In one specific embodiment, the additional resources of the Web page are identified by a number of embedded resource identifiers, such as uniform resource locators (“URLs”). In turn, software on the client computing devices typically processes embedded resource identifiers to generate requests for the content. Often, the resource identifiers associated with the embedded resources reference a computing device associated with the content provider such that the client computing device would transmit the request for the additional resources to the referenced content provider computing device. Accordingly, in order to satisfy a content request, the content provider would provide client computing devices data associated with the Web page as well as the data associated with the embedded resources.


Some content providers attempt to facilitate the delivery of requested content, such as Web pages and/or resources identified in Web pages, through the utilization of a content delivery network (“CDN”) service provider. A CDN service provider typically maintains a number of computing devices in a communication network that can maintain content from various content providers. In turn, content providers can instruct, or otherwise suggest to, client computing devices to request some, or all, of the content provider's content from the CDN service provider's computing devices.


As with content providers, CDN service providers are also generally motivated to provide requested content to client computing devices often with consideration of efficient transmission of the requested content to the client computing device and/or consideration of a cost associated with the transmission of the content. Accordingly, CDN service providers often consider factors such as latency of delivery of requested content in order to meet service level agreements or to generally improve the quality of delivery service. Additionally, in embodiments in which computing devices utilize an Internet service provider (“ISP”) to provide connectivity, the CDN service provider can consider additional factors associated with the interaction between the CDN service provider, client computing and ISP devices, such as a DNS resolver component.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:



FIG. 1 is a block diagram illustrative of a content delivery environment including a number of client computing devices, a content provider, and a content delivery network service provider;



FIG. 2 is a block diagram of the content delivery environment of FIG. 1 illustrating the registration of a content provider with a CDN service provider;



FIG. 3 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation of resource requests by a client computing device;



FIG. 4 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation of embedded resource requests by a client computing device;



FIG. 5 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation of DNS queries by a client computing device to a CDN service provider;



FIG. 6 is a block diagram of the content delivery environment of FIG. 1 illustrating the generation of resource requests by a client computing device;



FIG. 7 is a flow diagram illustrative of a client computing device IP address mapping routine implemented by a CDN service provider; and



FIG. 8 is a flow diagram illustrative of a request routing processing routine implemented by a service provider.





DETAILED DESCRIPTION

Generally described, the present disclosure is directed to managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider. Specifically, aspects of the disclosure will be described with regard to the management and processing request routing functionality by a service provider, such as a content delivery network (“CDN”) service provider, on behalf of a content provider. Illustratively, the request routing functionality can correspond to the processing of domain name service (“DNS”) requests for resources by computing devices and the resolution of the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Based on the processing of DNS queries initiated by a client computing device, the CDN service provider can correlate client computing device identifiers, such as an Internet Protocol (“IP”) address, with identifiers (e.g., IP addresses) associated with other components in a content delivery environment. Examples of the other components can include DNS resolvers associated with the client computing device. In a further embodiment, the CDN service provider can utilize the correlated information to optimize client computing device resource requests received from a DNS resolver component based, at least in part, on correlated information.


Although various aspects of the disclosure will be described with regard to illustrative examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting. For example, the present disclosure may be described with regard to request routing services provided by a service provider, such as a CDN service provider, that may provide additional services and functionality including network-based storage services, caching services, application hosting, or other services. However, one skilled in the relevant art will appreciate that a service provider need not provide all, or any, of the additional services or functionality that may be associated with some service providers, such as a CDN service provider.



FIG. 1 is a block diagram illustrative of a content delivery environment 100 for the managing registration of a content provider with a service provider, such as a CDN service provider, and subsequent processing of at least a portion of content requests on behalf of the content provider. As illustrated in FIG. 1, the content delivery environment 100 includes a number of client computing devices 102 (generally referred to as clients) for requesting content from a content provider, a network storage provider 110, and/or a CDN service provider 106. In an illustrative embodiment, the client computing devices 102 can correspond to a wide variety of computing devices including personal computing devices, laptop computing devices, hand-held computing devices, terminal computing devices, mobile devices, wireless devices, various electronic devices and appliances and the like. In an illustrative embodiment, the client computing devices 102 include necessary hardware and software components for establishing communications over a communication network 110, such as a wide area network or local area network. For example, the client computing devices 102 may be equipped with networking equipment and browser software applications that facilitate communications via the Internet or an intranet.


Illustratively, at least some of the client computing devices 102 utilize a DNS resolver component 108, such as a DNS Name server, that receives DNS queries from a client computing device 102 and then generates the DNS queries attributed to the client computing device, or on behalf of the client computing device. In one embodiment, the DNS resolver component 108 may be a local DNS component provided by an enterprise network to which the client computing device 102 belongs. In another embodiment, the local DNS resolver component 108 may be provided by an Internet Service Provider (“ISP”) that provides the communication network connection to the client computing device 102. In embodiments in which the client computing devices 102 utilize a DNS resolver component 108, one skilled in the relevant art will appreciate that the DNS queries generated on behalf of the client computing devices would be associated with the IP address of the DNS resolver component 108 in accordance with a traditional networking protocols.


The content delivery environment 100 can also include a content provider 104 in communication with the one or more client computing devices 102 via the communication network 110. The content provider 104 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a content provider. Specifically, the content provider 104 can include a web server component 112 corresponding to one or more server computing devices for obtaining and processing requests for content (such as Web pages) from the client computing devices 102. The content provider 104 can further include an origin server component 114 and associated storage component 116 corresponding to one or more computing devices for obtaining and processing requests for network resources. One skilled in the relevant art will appreciate that the content provider 104 can be associated with various additional computing resources, such additional computing devices for administration of content and resources and the like. Additionally, although the origin server component 114 and associated storage component 116 are logically associated with the content provider 104, the origin server component 114 and associated storage components 116 may be geographically distributed throughout the communication network 110 in a manner to best serve various demographics of client computing devices 102.


Although not illustrated in FIG. 1, the content provider 104 can be associated with a number of additional or supplement components to facilitate interaction with client computing devices 102 or service providers. For example, a content provider 104 may maintain one or more DNS name server components that are operative to receive DNS queries related to registered domain names associated with the content provider 104. The one or more DNS name servers can be authoritative to resolve client computing device DNS queries corresponding to the registered domain names of the content provider 104. The content provider 104 can also maintain additional storage components, such as proxy servers, or utilize network storage service providers to maintain at least a portion of the content/resources provided to the client computing devices 102.


With continued reference to FIG. 1, the content delivery environment 100 can further include a service provider, generally referred to as the CDN service provider 106, in communication with the one or more client computing devices 102 and the content provider 104 via the communication network 110. The CDN service provider 106 illustrated in FIG. 1 corresponds to a logical association of one or more computing devices associated with a service provider. Specifically, the CDN service provider 106 can include a number of Point of Presence (“POP”) locations 118, 124 that correspond to nodes on the communication network 110. Each POP 118, 124 includes a DNS component 120, 126 made up of a number of DNS server computing devices for resolving DNS queries from the client computing devices 102. Each POP 118, 124 also optionally includes a resource cache component 122, 128 made up of a number of cache server computing devices for storing resources from content providers or network storage providers and transmitting various requested resources to various client computing devices 102. The DNS components 120, 126 and the resource cache components 122, 128 may further include additional software and/or hardware components that facilitate communications including, but not limited, load balancing or load sharing software/hardware components.


Still further, the CDN service provider 106 can include additional data stores for managing request routing information. Specifically, in an illustrative embodiment, the CDN service provider 106 can include a client ID mapping data store 130 for maintaining information correlating client computing device 102 identifiers, such as a client computing device IP address, with other identifiers, such as a DNS resolver 108 IP address. The CDN service provider 106 can further include a DNS request log data store 132 for maintaining information regarding DNS queries provided by the DNS resolvers 108 on behalf of client computing devices 102. Although the client ID mapping data store 130 and DNS request log data store 132 are illustrated as single, centrally located data stores, one skilled in the relevant art will appreciate that the data stores may be distributed among several data stores or be maintained, at least in part, among the POPs 118, 124.


In an illustrative embodiment, the DNS component 120, 126 and resource cache component 122, 128 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the POPs 118, 124 are illustrated in FIG. 1 as logically associated with the CDN service provider 106, the POPs will be geographically distributed throughout the communication network 110 in a manner to best serve various demographics of client computing devices 102. Additionally, one skilled in the relevant art will appreciate that the CDN service provider 106 can be associated with various additional computing resources, such additional computing devices for administration of content and resources, and the like. Even further, the components of the CDN service provider 106 can be managed by the same or different entities. One skilled in the relevant art will also appreciate that the components and configurations provided in FIG. 1 are illustrative in nature. Accordingly, additional or alternative components and/or configurations, especially regarding the additional components, systems and subsystems for facilitating communications may be utilized.


With reference now to FIGS. 2-6, the interaction between various components of the content delivery environment 100 of FIG. 1 will be illustrated. For purposes of the example, however, the illustration has been simplified such that many of the components utilized to facilitate communications are not shown. One skilled in the relevant art will appreciate that such components can be utilized and that additional interactions would accordingly occur without departing from the spirit and scope of the present disclosure.


With reference to FIG. 2, an illustrative interaction for the optional registration of a content provider 104 with the CDN service provider 106 for hosting content on behalf of the content provider 104 will be described. As illustrated in FIG. 2, the CDN service provider content registration process begins with registration of the content provider 104 with the CDN service provider 106. In an illustrative embodiment, the content provider 104 utilizes a registration application program interface (“API”) to register with the CDN service provider 106 such that the CDN service provider 106 can provide content on behalf of the content provider 104, or at least perform the processes described herein. Illustratively, the registration API can include the identification of the origin server 114 of the content provider 104 that may provide requested resources to the CDN service provider 106. In addition or alternatively, the registration API can include the content to be stored by the CDN service provider 106 on behalf of the content provider 104. Additionally, the content provider 104 can specify one or more network storage providers (not illustrated) that may act as an origin server for the content provider 104.


With continued reference to FIG. 2, upon receiving the registration API, the CDN service provider 106 obtains the registration information and generates, or otherwise obtains, embedded resource identifiers that will be utilized in the mapping of client identifiers. In an illustrative embodiment, and as will be explained in greater detail below, the embedded resource identifiers correspond to data or instructions that are processed by the client computing devices 102 to cause the client computing devices 102 to request specific resources from the CDN service provider 106. The request for specific resources from the CDN service provider 106 will result in the collection of client computing devices identifiers, e.g., IP addresses, associated with the resource request. As will be explained in greater detail below, the collected identifiers will be correlated with identifiers in a subsequent DNS query. Illustratively, the requesting of content corresponding to the embedded resource identifier provided by the CDN service provider 106 may not result in the transmittal of actual content by the CDN service provider 106.


The CDN service provider 106 returns the embedded resource identifiers to the content provider 104 along with any additional information. In turn, the content provider 104 can then store for the embedded resource identifiers for embedding in requested content or otherwise embed (or associate) the embedded resource identifiers with requested content (such as Web page markup language). In an illustrative embodiment, the embedded resource identifiers can be applicable to multiple content providers 104. Alternatively, the embedded resource identifiers can be unique to each particular content provider 104. Still further, the CDN service provider 106 may provide additional logic to the content providers 104 that controls the circumstances and/or methodologies for embedding the embedded resource identifiers into content. For example, the embedded resource identifiers can include instructions (or executable code) that defines that the type of content (e.g., specific Web pages) for which the embedded resource identifiers will apply.


With reference now to FIG. 3, after completion of the registration and embedding processes illustrated in FIG. 2, a client computing device 102 generates a content request that is received and processed by the content provider 104, such as through the Web server 110. In accordance with an illustrative embodiment, the request for content can be in accordance with common network protocols, such as the hypertext transfer protocol (“HTTP”). Upon receipt of the content request, the content provider identifies the appropriate responsive content. In an illustrative embodiment, the requested content can correspond to a Web page that is displayed on the client computing device 102 via the processing of information, such as hypertext markup language (“HTML”), extensible markup language (“XML”), and the like. The requested content can also include a number of embedded resource identifiers that corresponds to resource objects that should be obtained by the client computing device 102 as part of the processing of the requested content. The embedded resources can correspond to multi-media content, such as images, videos, text, etc. that will be processed by the client computing devices 102 and rendered on output device. Additionally, the requested content will also include the additional embedded resource identifiers, instructions, executable code or logic previously provided by the CDN service provider 106 (FIG. 2). In an illustrative embodiment, the embedded resource identifiers, instructions, executable code or logic previously provided by the CDN service provider 106 can be arranged in a manner such that it is processed prior to processing any other of the content in the requested content or processed in the earlier stages of the processing of the requested content, as allowed. Alternatively, the embedded resource embedded resource identifiers, instructions, executable code or logic previously provided by the CDN service provider 106 can also be arranged such that it is processed after all any other embedded resources are process so as to mitigate any type of interference or delay in the processing of other embedded resources/identifiers.


Generally, the identification of the embedded resources provided by the content provider 104 will be in the form of embedded resource identifiers that can be processed by the client computing device 102, such as through a browser software application. In an illustrative embodiment, the resource identifiers can be in the form of a uniform resource locator (“URL”). For purposes of an illustrative example, the URL can identify a domain of the content provider 104 (e.g., contentprovider.com) or CDN service provider 106 (e.g., CDNserviceprovider), a name of the resource to be requested (e.g., “resource.xxx”) and a path where the resource will be found (e.g., “path”). One skilled in the relevant art will appreciate that the identified domain could correspond to third parties as well. By way of an illustrative example, the URLs of the embedded resource have the form of:


http://www.contentprovider.com/path/resource.xxx or


http://www.CDNserviceprovider.com/path/resource.xxx


Additionally, in an illustrative embodiment, the embedded resource previously provided by the CDN service provider 106 will also be in the form of a resource identifier (e.g., URLs) that can be processed by the client computing device 102, such as through a browser software application. For purposes of an illustrative example, the URL can identify a domain of the CDN service provider 106 (e.g., CDNserviceprovider.com), a name of a resource to be requested (e.g., “resource.xxx”) and a path where the resource will be found (e.g., “path”). As will be explained in greater detail, the embedded resource previously provided by the CDN service provider 106 will identify a special resource such that a request for the special resource may not result in the delivery of an actual resource to the requesting client computing device 102. In this illustrative example, the URLs of the embedded resource have the form of:


http://www.CDNserviceprovider.com/path/resource.xxx


With reference now to FIG. 4, upon receipt of the requested content, including the embedded resource identifiers, instructions, executable code or logic previously provided by the CDN service provider 106, the client computing device 102 processes the received information in a manner that causes the client computing device 102 to request embedded resource previously provided by the CDN service provider 106 from the CDN service provider 106. In accordance with an embodiment utilizing the hypertext transfer protocol (“HTTP”), the request of a resource can correspond to a GET request transmitted by the client computing device 102 to an IP address associated with CDN service provider 106. Although not illustrated in FIG. 4, the client computing device 102 would first issue a DNS query for the embedded resource previously provided by the CDN service provider 106, which if properly resolved, would include the identification of the above mentioned IP address associated with the CDN service provider 106. One skilled in the relevant art will appreciate that the resolution of the DNS query may involve multiple DNS queries to either the content provider 104 or CDN service provider 106.


With continued reference to FIG. 4, upon receipt of the request for the embedded resource previously provided by the CDN service provider 106, the receiving POP, illustratively, POP 118, generates a unique identifier for utilization in tracking an identifier associated with the requesting client computing device, such as an IP address, in subsequent requests to the CDN service provider 106. Specifically, the unique identifier includes at least a portion of the identifier associated with the requesting client computing device 102. In an illustrative embodiment, the unique identifier generated by the CDN service provider 106 will be in the form of a URL that will be returned to the requesting client computing device 102. For purposes of an illustrative example, the URL can identify a domain of the CDN service provider 106 (e.g., “CDNserviceprovider.com”), an identification of the POP generating the unique identifier (e.g., “POP1”), and at least a portion of the identifier associated with the requesting client computing device. The URL can also include timestamp information associated with a time corresponding to the request (relative or absolute) and additional processing information. In this illustrative example, the URLs of the embedded resource have the form of:


http://uniqueID.additional_information.pop_identification.CDNserviceprovider.com


In this illustrative example, the label “uniqueID” can include the portion of the identifier associated with the requesting client computing device and the timestamp information. Responsive to the client computing device request, the CDN service provider 106 (via the receiving POP, POP 118) returns the requested content. In an illustrative embodiment, the CDN service provider 106 generates a response for the requested content that includes a command indicative of another location for the requested content. For example, the CDN service provider 106 can generate a LOCATION command in accordance with HTTP that identifies an alternate location for the requested content. Accordingly, the location included in the response sent by the CDN service provider 106 is the unique identifier in the form of the URL previously generated by the CDN service provider 106 and discussed above.


With reference now to FIG. 5, upon receipt of the response from the CDN service provider 106, the client computing device 102 processes the command that will cause the client computing device 102 to request the content from the identified alternative location. As illustrated in FIG. 5, in accordance with traditional communication protocols, the client computing device 102 would first transmit a DNS query through its DNS resolver 108 to request an IP address of a computing device corresponding to the unique identifier provided by the CDN service provider 106. In accordance with traditional request routing principles, the DNS query would be received by the DNS resolver 108 and then transmitted on behalf of the requesting client computing device 102.


By way of example, in accordance with traditional DNS request routing principles, a DNS query for the URL http://uniqueID.additional_information.pop_identification.CDNserviceprovider.com would first include the identification of a DNS server authoritative to the “.” and the “com” portions of the URL to the DNS resolver 108. The issuance of DNS queries corresponding to the “.” and the “com” portions of a URL are well known and have not been illustrated. After partially resolving the modified URL according to the “.” and “com” portions of the URL, the DNS resolver 108 then issues another DNS query for the resource URL that results in the identification of the DNS server corresponding to the “.CDNserviceprovider” portion of the URL, as illustrated in FIG. 5, illustrative as the DNS server component 120 of POP 118.


The receiving DNS server component 120 obtains the DNS query from the DNS resolver component 108 and processes the query. In an illustrative embodiment, the DNS server component 120 identifies the identifier associated with the DNS resolver 108 based on the received DNS query. The DNS server component 120 also extracts the at least a portion of the client computing device 102 identifier that was included in the URL, such as by parsing portions of the URL included in the DNS queries. The DNS server component 120 can also parse additional information included in the URL. Thereafter, the DNS server component 120 correlates and stores the collected information, such as in the client ID mapping data store 130 (either locally or centrally). Additionally, in accordance with traditional networking principles, because the DNS server component 120 is authoritative for the URL, the DNS server component 120 provides the DNS resolver 108 with the identification of an IP address that can provide the requested content, such as a resource cache component 122 of the POP 118.


Turning now to FIG. 6, upon receipt of the resolved DNS query, the client computing device 102 transmits a request for the content to the IP address corresponding to a resource cache component or storage component. The content request is received and processed by the corresponding resource cache component 122 (FIG. 1) and storage component. In one aspect, the resource cache component 122 can conduct measurements or record data that will be used by the CDN service provider 106 to measure request routing performance for client computing devices 102 or groups of client computing device 102 associated with particular DNS resolver components 108 or ISPs. In another aspect, the resource cache component 122 can return some type of confirmation to the client computing device 102. As previously described, in an illustrative embodiment, the client computing device 102 may not receive any type of content, so the confirmation may include no additional content or some type of null content.


With reference now to FIG. 7, one embodiment of a routine 700 implemented by the CDN service provider 106 for correlating client identifiers with other information will be described. One skilled in the relevant art will appreciate that actions/steps outlined for routine 700 may be implemented by one or many computing devices/components that are associated with the CDN service provider 106. Accordingly, routine 700 has been logically associated as being generally performed by the CDN service provider 106, and thus the following illustrative embodiments should not be construed as limiting.


At block 702, the CDN service provider 106 obtains a request for an embedded resource. As previously described, in an illustrative embodiment, the embedded resource may correspond to one of several embedded resources provided by a content provider 104 (FIG. 1) in response to an initial content request from a client computing device. The embedded resource can be in the form of a URL that results in the generation of the request by the client computing device 102 to the CDN service provider 106. At block 704, the CDN service provider 106 generates a unique client identifier in response to the content request. As previously described, in an illustrative embodiment, the unique client identifier can include at least a portion of a client identifier that is used by the client computing device 102, such as a client IP address. In an alternative embodiment, the unique client identifier can correspond to lookup code or other information that will be used by CDN service provider 106 to subsequently recall the client identifier. The unique client identifier can also include additional information identifying the client computing device 102, such as other networking address information, information associated with the request, time stamps, location information, etc., and information identifying a user associated with the client computing device 102, such as user identifiers, account identifiers, etc. In an illustrative example, the URLs of the embedded resource have the form of:


http://uniqueID.additional_information.pop_identification.CDNserviceprovider.com


At block 706, the CDN service provider 106 transmits the unique client identifier to the requesting client computing device 102. In an illustrative embodiment, the unique client identifier may be encrypted, encoded, or otherwise processed. At block 708, the CDN service provider 106 obtains a DNS query corresponding to the unique client identifier. As previously described, the DNS query can be submitted by a DNS resolver 108, or other component, on behalf of the client computing device 102 and received at a DNS name server component associated with the CDN service provider 106.


At block 710, the CDN service provider 106 obtains the client identifier information included in the DNS query and identifier information associated with the DNS query. Illustratively, the client identifier information includes at least a portion of the IP address associated with the client computing device 102. In such embodiment, the CDN service provider 106 can parse the DNS query to obtain the IP address information included in the unique identifier. In embodiments in which the unique identifier includes lookup information, the CDN service provider 106 would parse the lookup information and then obtain the relevant IP address information from a local or remote data store. With continued reference to block 710, the CDN service provider 106 can also obtain an IP address associated with the DNS resolver component 108 transmitted the DNS query on behalf of the client computing device. Still further, the CDN service provider 106 can parse and obtain any additional information included in the unique identifier or identified by additional lookup information included in the unique identifier.


At block 712, the CDN service provider 106 processes the client identifier and DNS resolver IP address information. Specifically, the CDN service provider 106 correlates the client identifier IP address information to resolver IP address information. The correlated information can be stored in the client ID mapping data store 130. The CDN service provider 106 can also record a timestamp corresponding to the received DNS query that can used to compare with the time stamp information included in the unique identifier. Still further, the CDN service provider 106 can process additional information, such as location information, user identifiers, etc. and associate the information with the DNS resolver IP address information. In still a further embodiment, the CDN service provider 106 can establish criteria that must be satisfied prior in order to begin utilizing the correlated information. For example, the CDN service provider 106 may establish a minimum number of correlated client computing identifiers that must be processed. In another example, a defined period of time must be expired prior to utilizing the correlated data. In such embodiments, the CDN service provider 106 may track the additional criteria as part of the processing of the client identifier and DNS resolver IP address information. At block 714, the CDN service provider 106 processes the DNS query by returning an IP address (or other responsive information) to the client computing device 102 via the DNS resolver 108. At block 716, the routine 700 terminates.


With reference now to FIG. 8, one embodiment of a request routing routine 800 for routing information based on mapped client computing device 102 identifiers and DNS resolver 108 identifiers will be described. Specifically, a service provider, such as the CDN service provider 106, can utilized correlated client computing device identifier information, such as correlated IP address information, to optimize request routing processing. One skilled in the relevant art will appreciate that actions/steps outlined for routine 800 may be implemented by one or many computing devices/components that are associated with the CDN service provider 106. Accordingly, routine 800 has been logically associated as being performed by the CDN service provider 106.


At a block 802, a receiving DNS server of the CDN service provider 106 receives a DNS query corresponding to a requested resource from a client computing device 102, which may be transmitted via a DNS resolver 108. As previously described, in the event the DNS query is transmitted via a DNS resolver 108, the receiving DNS server of the CDN service provider 106 cannot obtain an IP address, or other client identifier, directly from the DNS query. At block 804, the receiving DNS server of the CDN service provider 106 obtains correlated client identifier information based on processing the IP address associated with the DNS resolver 108.


At block 806, the CDN service provider 106 determines a class corresponding to the DNS resolver identifiers based on previously correlated information, as illustrated and discussed above. In an illustrative embodiment, classes can correspond to a specific geographic region to which client computing devices 102 belong. In another embodiment, classes can correspond to an ISP associated with the client computing devices 102 or the DNS resolver 108. In an illustrative embodiment, the determination of one or more classes can specifically include the association of requesting client computing devices 102 to a cluster of other client computing devices based on a variety of criteria. Such criteria can include geographic region and internet service provider data, as mentioned above, in addition to routing path information, networking equipment, client sponsored service level agreements, content provider service level agreements, and the like.


Also at block 808, the DNS server attempts to resolve the DNS query by identifying cache routing information based on the determined class of the DNS resolver component 108. In an illustrative embodiment, a receiving DNS server of the CDN service provider 106 can determine whether it is authoritative to resolve the DNS query from the DNS resolver 108 there are no canonical name (“CNAME”) records corresponding to the received resource identifier, as is known in the general art. If no CNAME records correspond to the received resource identifier, the receiving DNS server selects an appropriate resource cache component for providing content associated with the resource request based on routing information for the above determined class. The receiving DNS server then resolves the DNS query by providing IP address information associated with the selected resource cache component to the requesting DNS resolver 108.


In an illustrative embodiment, each receiving DNS server of the CDN server provider 106 may have the same or different request routing information that is used to process the DNS query according to class. For example, DNS server components may have different request routing information based on the physical or logical location of its associated POP within a communication network. In another example, DNS server components may have different request routing information based on contractual agreements, such as service level agreements. Accordingly, DNS queries received at two different DNS server components of the CDN service provider 106 may be processed differently.


In an illustrative embodiment, the resolution of the DNS query can correspond to a selection of one or more resource cache components from a list of resource cache components capable of servicing the content request for a particular class of client computing devices 102 or DNS resolvers 102. Accordingly, the receiving DNS server can use a variety of logic to select a resource cache component from the list. In one embodiment, a probabilistic based distribution of resource cache components can be defined such that a receiving DNS server selects a resource cache component based on the determined distributions. For example, a receiving DNS server will most frequently select the resource cache component with the highest probability of selection/distribution (e.g., a resource cache component associated with 75% of all DNS queries for a particular client computing device 102 or DNS resolver component 108), but can also, at times, select a resource cache component with a lower probability of selection. In this case, the probabilities correspond to anticipated performance of the selected computing device 102 or DNS resolver component 108. As will be described further below, the CDN service provider 106 can monitor performance of delivering requested resources to clients in a particular class and thereafter update the routing information (e.g., probabilities) accordingly. In other embodiments, the probabilities can correspond to load shedding or other network traffic mitigation. By periodically selecting a non-preferred resource cache component and monitoring its performance for the class, the CDN service provider 106 can thus determine if changes to the routing information for the class are desirable.


In another embodiment, the receiving DNS server can utilize alternative or additional criteria, in selecting one or more resource cache components capable of servicing the content request for a particular class of client computing devices 102 or DNS resolvers 102. For example, the receiving DNS server can utilize geographic information or logical network information associated with specific client computing device IP address correlated to the DNS resolver 108. In another example, the receiving DNS server can utilize network conditions, often referred to as “Internet weather”, in determining which resource cache components may be capable of servicing the content request. In this example, the receiving DNS server may utilize criteria such as a minimum or threshold performance level for the class of computing devices, such as latency, that must be delivered by the selected resource cache components. Other criteria can include selecting an average performance level for the class of computing devices, such as latency, that must be delivered by the selected resource cache components. In a further example, the receiving DNS server can utilize contractual criteria, such as service level agreements, associated with client computing devices 102, enterprises or ISPs to process DNS queries for a class of client computing device 102 or DNS resolvers 108.


At block 810, the CDN service provider 106 monitors network performance criteria associated with delivery of the requested resource is monitored. The network performance criteria can correspond to measurements of network performance for transmitting data from the CDN service provider POPs to the client computing device 102. In one embodiment, network data transfer latencies associated with the delivery of the requested resource is measured by the client computing device 102. Alternatively, the CDN service provider 106, such as through the resource cache component, can measure the performance as part of providing content to a client computing device 102. Such network performance data can be managed and maintained globally by the CDN service provider and shared with the DNS servers of the CDN or individually by the DNS servers of the CDN service provider. Moreover, network performance criteria can be provided as a batch process from POPs or sent in response to a request from one POP to another.


At decision block 812, a determination is made as to whether an update to the routing information for the identified class is needed based on the performance data. In one embodiment, the update determination can be made by the CDN service provider 106 globally or by the individual DNS service components or DNS servers. In an illustrative embodiment where individual DNS servers determine whether to update routing information for a class, each DNS server can manage and maintain routing information for the identified class unique to the particular DNS server. In this illustrative embodiment, the performance data can be maintained globally by the CDN service provider 106 and shared with the DNS components and/or DNS servers, with each DNS component and/or DNS server managing how the performance data is used. Accordingly, routing information for a class may vary from one DNS component/server to another.


If an update is needed at decision block 812, the routing information for the identified class is modified at block 814. In one embodiment, the CDN service provider 106 modifies a list of computing devices (e.g. DNS components/servers and/or resource cache components) for servicing a resource request from a particular class of client computing devices 102 or DNS resolver component 108. In another embodiment, the CDN service provider 106 and/or specific DNS components/servers can maintain and modify probabilities of selection of particular computing devices for servicing a resource request for a class of client computing devices. For example, if performance data indicates that a DNS server and/or a resource cache component which has a lower probability of selection has performed well, the probability of selection may be increased so that the particular DNS server and/or resource cache component will be selected more frequently for servicing a resource request from a client computing device. After a modification has been made at block 814, or if an update is not needed at decision block 812, the routine 800 returns to block 802 for further processing as described above.


It will be appreciated by one skilled in the relevant art that there are a number of ways to modify the routing information associated with requests from a class of client computing devices. It will further be appreciated by one skilled in the relevant art that the timing at which performance is monitored and updates to routing information are made can vary.


It will be appreciated by those skilled in the art and others that all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.


Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.


Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above.


It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims
  • 1. A computer-implemented method comprising: obtaining, by a service provider, a first request for content from a first client computing device;determining, by the service provider, a first address associated with the first client computing device;generating, by the service provider, an alternative identifier responsive to the first request for content from the first client computing device, the alternative identifier comprising a uniform resource locator (URL), the alternative identifier including information related to the first address associated with the first client computing device and additional information not included in the first request for content in a domain name service (DNS) portion of the URL, the additional information associated with routing or processing the request for content, and the additional information comprising timestamp information associated with a first time corresponding to the first request for content from the first client computing device;transmitting, by the service provider, at least one instruction causing the first client computing device to generate a second request for content based on the alternative identifier; wherein the second request is associated with a second address corresponding to a DNS resolver component;receiving, by the service provider at a DNS server component, the second request for content based on the alternative identifier, the second request comprising a first DNS query;correlating, by the service provider at the DNS server component, the at least a portion of the first address associated with the first client computing device and the additional information included in the DNS portion of the URL with the second address and a second time corresponding to the second request for content for comparison with the first time corresponding to the first request for content to form correlated information;obtaining, by the service provider, a second DNS query from a second client computing device; andresponsive to the second DNS query, at the service provider: determining a class associated with the second client computing device based at least in part on the correlated information; andresolving the second DNS query based on the determined class.
  • 2. The method as recited in claim 1, wherein the at least one instruction causing the first client computing device to generate the subsequent request for content comprises a URL of the service provider.
  • 3. The method as recited in claim 1, wherein the at least one instruction causing the first client computing device to generate the subsequent request for content comprises a URL of a content provider.
  • 4. The method as recited in claim 1, wherein the additional information in the DNS portion of the alternative identifier comprises additional information identifying the first client computing device.
  • 5. The method as recited in claim 1, wherein generating the alternative identifier responsive to the request for content from the first client computing device includes encrypting the at least a portion of the obtained first address associated with the first client computing device.
  • 6. The method as recited in claim 1, wherein the alternative identifier comprises a label representative of the at least a portion of the first address.
  • 7. The method as recited in claim 6, wherein the label representative of the at least a portion of the first address comprises a label representative of the timestamp information.
  • 8. The method as recited in claim 1 further comprising determining, by the service provider, a minimum number of correlated client computing identifiers that must be processed before utilizing the correlated information.
  • 9. A computer-implemented system comprising: one or more computing devices comprising a processor configured with specific computer executable instructions to: obtain, by a service provider, a first request for content from a first client computing device;determine, by the service provider, a first address associated with the first client computing device;generate, by the service provider, an alternative identifier responsive to the first request for content from the first client computing device, the alternative identifier comprising a uniform resource locator (URL), the alternative identifier including information related to the first address associated with the first client computing device and additional information not included in the first request for content in a domain name service (DNS) portion of the URL, the additional information associated with routing or processing the request for content, and the additional information comprising timestamp information associated with a first time corresponding to the first request for content from the first client computing device;transmit, by the service provider, at least one instruction causing the first client computing device to generate a second request for content based on the alternative identifier; wherein the second request is associated with a second address corresponding to a DNS resolver component;receive, by the service provider at a DNS server component, the second request for content based on the alternative identifier, the second request comprising a DNS query;correlate, by the service provider at the DNS server component, the at least a portion of the first address associated with the first client computing device and the additional information included in the DNS portion of the URL with the second address and a second time corresponding to the second request for content for comparison with the first time corresponding to the first request for content to form correlated information;obtain, by the service provider, a second DNS query from a second client computing device; andresponsive to the second DNS query, at the service provider: determine a class associated with the second client computing device based at least in part on the correlated information; andresolve the second DNS query based on the determined class.
  • 10. The system as recited in claim 9, wherein the at least one instruction causing the first client computing device to generate the subsequent request for content comprises a URL of the service provider.
  • 11. The system as recited in claim 9, wherein the at least one instruction causing the first client computing device to generate the subsequent request for content comprises a URL of a content provider.
  • 12. The system as recited in claim 9, wherein the additional information in the DNS portion of the alternative identifier comprises additional information identifying the first client computing device.
  • 13. The system as recited in claim 9, wherein generating the alternative identifier responsive to the request for content from the first client computing device includes encrypting the at least a portion of the obtained first address associated with the first client computing device.
  • 14. The system as recited in claim 9, wherein the alternative identifier comprises a label representative of the at least a portion of the first address.
  • 15. The system as recited in claim 14, wherein the label representative of the at least a portion of the first address comprises a label representative of the timestamp information.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/892,777, now U.S. Pat. No. 9,712,484, entitled “MANAGING REQUEST ROUTING INFORMATION UTILIZING CLIENT IDENTIFIERS” and filed Sep. 28, 2010, the disclosure of which is incorporated herein by reference.

US Referenced Citations (1744)
Number Name Date Kind
1075551 D'Amours Oct 1913 A
5063500 Shorter Nov 1991 A
5341477 Pitkin et al. Aug 1994 A
5459837 Caccavale Oct 1995 A
5611049 Pitts Mar 1997 A
5627889 Eslambolchi May 1997 A
5701467 Freeston Dec 1997 A
5764910 Shachar Jun 1998 A
5774660 Brendel et al. Jun 1998 A
5815649 Utter et al. Sep 1998 A
5852717 Bhide et al. Dec 1998 A
5892914 Pitts Apr 1999 A
5893116 Simmonds et al. Apr 1999 A
5895462 Toki Apr 1999 A
5905248 Russell et al. May 1999 A
5933811 Angles et al. Aug 1999 A
5937427 Shinagawa et al. Aug 1999 A
5974454 Apfel et al. Oct 1999 A
5991306 Burns et al. Nov 1999 A
5999274 Lee et al. Dec 1999 A
6006264 Colby et al. Dec 1999 A
6016512 Huitema Jan 2000 A
6018619 Allard et al. Jan 2000 A
6026452 Pitts Feb 2000 A
6038601 Lambert et al. Mar 2000 A
6108703 Leighton et al. Mar 2000 A
6052718 Gifford Apr 2000 A
6078960 Ballard Jun 2000 A
6085234 Pitts et al. Jul 2000 A
6092100 Berstis et al. Jul 2000 A
6098096 Tsirigotis et al. Aug 2000 A
6128279 O'Neil et al. Oct 2000 A
6151631 Ansell et al. Nov 2000 A
6157942 Chu et al. Dec 2000 A
6167438 Yates et al. Dec 2000 A
6167446 Lister et al. Dec 2000 A
6173316 De Boor et al. Jan 2001 B1
6182111 Inohara et al. Jan 2001 B1
6182125 Borella et al. Jan 2001 B1
6185598 Farber et al. Feb 2001 B1
6192051 Lipman et al. Feb 2001 B1
6205475 Pitts Mar 2001 B1
6223209 Watson et al. Apr 2001 B1
6223288 Byrne Apr 2001 B1
6243761 Mogul et al. Jun 2001 B1
6256671 Strentzsch et al. Jul 2001 B1
6275496 Burns et al. Aug 2001 B1
6286043 Cuomo et al. Sep 2001 B1
6286084 Wexler et al. Sep 2001 B1
6304913 Rune Oct 2001 B1
6324580 Jindal et al. Nov 2001 B1
6330602 Law et al. Dec 2001 B1
6338082 Schneider Jan 2002 B1
6345308 Abe Feb 2002 B1
6351743 DeArdo et al. Feb 2002 B1
6351775 Yu Feb 2002 B1
6363411 Dugan et al. Mar 2002 B1
6366952 Pitts Apr 2002 B2
6374290 Scharber et al. Apr 2002 B1
6377257 Borrel et al. Apr 2002 B1
6386043 Millins May 2002 B1
6389532 Gupta et al. May 2002 B1
6405252 Gupta et al. Jun 2002 B1
6408360 Chamberlain et al. Jun 2002 B1
6411967 Van Renesse Jun 2002 B1
6415280 Farber et al. Jul 2002 B1
6430607 Kavner Aug 2002 B1
6438592 Killian Aug 2002 B1
6442165 Sitaraman et al. Aug 2002 B1
6452925 Sistanizadeh et al. Sep 2002 B1
6457047 Chandra et al. Sep 2002 B1
6459909 Bilcliff et al. Oct 2002 B1
6473804 Kaiser et al. Oct 2002 B1
6484143 Swildens et al. Nov 2002 B1
6484161 Chipalkatti et al. Nov 2002 B1
6493765 Cunningham et al. Dec 2002 B1
6505241 Pitts Jan 2003 B2
6513112 Craig et al. Jan 2003 B1
6523036 Hickman et al. Feb 2003 B1
6529910 Fleskes Mar 2003 B1
6529953 Van Renesse Mar 2003 B1
6553413 Leighton et al. Apr 2003 B1
6560610 Eatherton et al. May 2003 B1
6564380 Murphy May 2003 B1
6611873 Kanehara Aug 2003 B1
6622168 Datta Sep 2003 B1
6643357 Lumsden Nov 2003 B2
6643707 Booth Nov 2003 B1
6654807 Farber et al. Nov 2003 B2
6658462 Dutta Dec 2003 B1
6665706 Kenner et al. Dec 2003 B2
6678717 Schneider Jan 2004 B1
6678791 Jacobs et al. Jan 2004 B1
6681282 Golden et al. Jan 2004 B1
6687846 Adrangi et al. Feb 2004 B1
6694358 Swildens et al. Feb 2004 B1
6697805 Choquier et al. Feb 2004 B1
6718324 Edlund et al. Apr 2004 B2
6724770 Van Renesse Apr 2004 B1
6732237 Jacobs et al. May 2004 B1
6754699 Swildens et al. Jun 2004 B2
6754706 Swildens et al. Jun 2004 B1
6760721 Chasen et al. Jul 2004 B1
6769031 Bero Jul 2004 B1
6782398 Bahl Aug 2004 B1
6785704 McCanne Aug 2004 B1
6795434 Kumar et al. Sep 2004 B1
6799214 Li Sep 2004 B1
6804706 Pitts Oct 2004 B2
6810291 Card et al. Oct 2004 B2
6810411 Coughlin et al. Oct 2004 B1
6829654 Jungck Dec 2004 B1
6862607 Vermeulen Mar 2005 B1
6868439 Basu et al. Mar 2005 B2
6874017 Inoue et al. Mar 2005 B1
6917951 Orbits et al. Jul 2005 B2
6925499 Chen et al. Aug 2005 B1
6928467 Peng et al. Aug 2005 B2
6928485 Krishnamurthy et al. Aug 2005 B1
6941562 Gao et al. Sep 2005 B2
6944167 McPherson Sep 2005 B1
6950848 Yousefi'zadeh et al. Sep 2005 B1
6961783 Cook et al. Nov 2005 B1
6963850 Bezos et al. Nov 2005 B1
6968389 Menditto et al. Nov 2005 B1
6976090 Ben-Shaul et al. Dec 2005 B2
6981017 Kasriel et al. Dec 2005 B1
6981025 Frazier et al. Dec 2005 B1
6985945 Farhat et al. Jan 2006 B2
6986018 O'Rourke et al. Jan 2006 B2
6990526 Zhu Jan 2006 B1
6996616 Leighton et al. Feb 2006 B1
7003555 Jungck Feb 2006 B1
7006099 Gut et al. Feb 2006 B2
7007089 Freedman Feb 2006 B2
7010578 Lewin et al. Mar 2006 B1
7010598 Sitaraman et al. Mar 2006 B2
7024466 Outten et al. Apr 2006 B2
7027582 Khello et al. Apr 2006 B2
7031445 Lumsden Apr 2006 B2
7032010 Swildens et al. Apr 2006 B1
7058633 Gnagy et al. Jun 2006 B1
7058706 Iyer et al. Jun 2006 B1
7058953 Willard et al. Jun 2006 B2
7062158 Ayaki Jun 2006 B1
7065587 Huitema et al. Jun 2006 B2
7072982 Teodosiu et al. Jul 2006 B2
7076633 Tormasov et al. Jul 2006 B2
7082476 Cohen et al. Jul 2006 B1
7086061 Joshi et al. Aug 2006 B1
7092505 Allison et al. Aug 2006 B2
7092997 Kasriel et al. Aug 2006 B1
7095715 Buckman et al. Aug 2006 B2
7096266 Lewin et al. Aug 2006 B2
7099936 Chase et al. Aug 2006 B2
7103645 Leighton et al. Sep 2006 B2
7114160 Suryanarayana et al. Sep 2006 B2
7117262 Bai et al. Oct 2006 B2
7133905 Dilley et al. Nov 2006 B2
7136922 Sundaram et al. Nov 2006 B2
7139808 Anderson et al. Nov 2006 B2
7139821 Shah et al. Nov 2006 B1
7143169 Champagne et al. Nov 2006 B1
7143170 Swildens et al. Nov 2006 B2
7146560 Dang et al. Dec 2006 B2
7149747 Cheng et al. Dec 2006 B1
7149809 Barde et al. Dec 2006 B2
7152118 Anderson, IV et al. Dec 2006 B2
7162539 Garcie-Luna-Aceves Jan 2007 B2
7165117 Sitaraman et al. Jan 2007 B1
7171469 Ackaouy et al. Jan 2007 B2
7174382 Ramanathan et al. Feb 2007 B2
7185046 Ferstl et al. Feb 2007 B2
7185063 Kasriel et al. Feb 2007 B1
7185084 Sirivara et al. Feb 2007 B2
7188214 Kasriel et al. Mar 2007 B1
7194522 Swildens et al. Mar 2007 B1
7194552 Schneider Mar 2007 B1
7200667 Teodosiu et al. Apr 2007 B2
7200673 Augart Apr 2007 B1
7216170 Ludvig et al. May 2007 B2
7225254 Swildens et al. May 2007 B1
7228350 Hong et al. Jun 2007 B2
7228359 Monteiro Jun 2007 B1
7233978 Overton et al. Jun 2007 B2
7240100 Wein et al. Jul 2007 B1
7249196 Peiffer et al. Jul 2007 B1
7251675 Kamakura et al. Jul 2007 B1
7254626 Kommula et al. Aug 2007 B1
7254634 Davis et al. Aug 2007 B1
7254636 O'Toole, Jr. et al. Aug 2007 B1
7257581 Steele et al. Aug 2007 B1
7260598 Liskov et al. Aug 2007 B1
7260639 Afergan et al. Aug 2007 B2
7269784 Kasriel et al. Sep 2007 B1
7272227 Beran Sep 2007 B1
7274658 Bornstein et al. Sep 2007 B2
7284056 Ramig Oct 2007 B2
7289519 Liskov Oct 2007 B1
7293093 Leighton Nov 2007 B2
7308499 Chavez Dec 2007 B2
7310686 Uysal Dec 2007 B2
7316648 Kelly et al. Jan 2008 B2
7318074 Iyengar et al. Jan 2008 B2
7320131 O'Toole, Jr. Jan 2008 B1
7321918 Burd et al. Jan 2008 B2
7337968 Wilz, Sr. et al. Mar 2008 B2
7339937 Mitra et al. Mar 2008 B2
7340505 Lisiecki et al. Mar 2008 B2
7343397 Kochanski Mar 2008 B2
7350075 Eastham et al. Mar 2008 B1
7362703 Taft et al. Apr 2008 B1
7363291 Page Apr 2008 B1
7363626 Koutharapu et al. Apr 2008 B2
7370089 Boyd et al. May 2008 B2
7372809 Chen May 2008 B2
7373416 Kagan et al. May 2008 B2
7376716 Dilley et al. May 2008 B2
7376736 Sundaram et al. May 2008 B2
7380078 Ikegaya et al. May 2008 B2
7389354 Sitaraman et al. Jun 2008 B1
7392236 Rusch et al. Jun 2008 B2
7398301 Hennessey et al. Jul 2008 B2
7406512 Swildens et al. Jul 2008 B2
7406522 Riddle Jul 2008 B2
7409712 Brooks et al. Aug 2008 B1
7430610 Pace et al. Sep 2008 B2
7441045 Skene et al. Oct 2008 B2
7441261 Slater et al. Oct 2008 B2
7451230 Corrado et al. Nov 2008 B2
7454457 Lowery et al. Nov 2008 B1
7454500 Hsu et al. Nov 2008 B1
7461170 Taylor et al. Dec 2008 B1
7464142 Flurry et al. Dec 2008 B2
7472201 Aitken Dec 2008 B1
7478148 Neerdaels Jan 2009 B2
7492720 Pruthi et al. Feb 2009 B2
7496651 Joshi Feb 2009 B1
7499998 Toebes et al. Mar 2009 B2
7502836 Menditto et al. Mar 2009 B1
7505464 Okmianski et al. Mar 2009 B2
7506034 Coates et al. Mar 2009 B2
7519705 Papagiannaki et al. Apr 2009 B1
7519720 Fishman et al. Apr 2009 B2
7519726 Palliyil et al. Apr 2009 B2
7523181 Swildens et al. Apr 2009 B2
7543024 Holstege Jun 2009 B2
7548947 Kasriel et al. Jun 2009 B2
7552235 Chase et al. Jun 2009 B2
7555542 Ayers et al. Jun 2009 B1
7561571 Lovett et al. Jul 2009 B1
7565407 Hayball Jul 2009 B1
7568032 Feng et al. Jul 2009 B2
7531009 Hsu et al. Aug 2009 B2
7573916 Bechtolsheim et al. Aug 2009 B1
7574499 Swildens et al. Aug 2009 B1
7584507 Nucci Sep 2009 B1
7593935 Sullivan Sep 2009 B2
7594189 Walker Sep 2009 B1
7596619 Leighton et al. Sep 2009 B2
7603439 Dilley et al. Oct 2009 B2
7613815 Prakash et al. Nov 2009 B1
7617222 Coulthard et al. Nov 2009 B2
7623460 Miyazaki Nov 2009 B2
7624169 Lisiecki et al. Nov 2009 B2
7624264 Aura et al. Nov 2009 B2
7540296 Fuchs et al. Dec 2009 B2
7626940 Jain Dec 2009 B2
7631101 Sullivan et al. Dec 2009 B2
7650376 Blumenau Jan 2010 B1
7653700 Bahl et al. Jan 2010 B1
7653725 Yahiro et al. Jan 2010 B2
7657613 Hanson et al. Feb 2010 B1
7657622 Douglis et al. Feb 2010 B1
7661027 Langen et al. Feb 2010 B2
7664831 Cartmell et al. Feb 2010 B2
7664879 Chan et al. Feb 2010 B2
7676570 Levy et al. Mar 2010 B2
7680897 Carter et al. Mar 2010 B1
7684394 Cutbill et al. Mar 2010 B1
7685109 Ransil et al. Mar 2010 B1
7685251 Houlihan et al. Mar 2010 B2
7685270 Vermeulen et al. Mar 2010 B1
7685273 Anastas et al. Mar 2010 B1
7693813 Cao et al. Apr 2010 B1
7693959 Leighton et al. Apr 2010 B2
7698418 Shimada et al. Apr 2010 B2
7702724 Brydon et al. Apr 2010 B1
7706740 Collins et al. Apr 2010 B2
7707071 Rigole Apr 2010 B2
7707314 McCarthy et al. Apr 2010 B2
7711647 Gunaseelan et al. May 2010 B2
7711788 Lev Ran et al. May 2010 B2
7716367 Leighton et al. May 2010 B1
7725602 Liu et al. May 2010 B2
7725658 Lang et al. May 2010 B2
7730187 Racihorski et al. Jun 2010 B2
7739400 Lindbo et al. Jun 2010 B2
7747720 Toebes et al. Jun 2010 B2
7748005 Romero et al. Jun 2010 B2
7756017 Goyal et al. Jul 2010 B2
7756032 Feick et al. Jul 2010 B2
7756913 Day Jul 2010 B1
7756965 Joshi Jul 2010 B2
7757202 Dahisted et al. Jul 2010 B2
7761572 Auerbach Jul 2010 B1
7765295 Anastas et al. Jul 2010 B2
7765304 Davis et al. Jul 2010 B2
7769823 Jenny et al. Aug 2010 B2
7773596 Marques Aug 2010 B1
7774342 Virdy Aug 2010 B1
7783727 Foley et al. Aug 2010 B1
7787380 Aggarwal et al. Aug 2010 B1
7792989 Toebes et al. Sep 2010 B2
7805516 Kettler et al. Sep 2010 B2
7809597 Das et al. Oct 2010 B2
7813308 Reddy et al. Oct 2010 B2
7814229 Cabrera et al. Oct 2010 B1
7818454 Kim et al. Oct 2010 B2
7827256 Phillips et al. Nov 2010 B2
7836177 Kasriel et al. Nov 2010 B2
7853680 Phatak Dec 2010 B2
7853719 Cao et al. Dec 2010 B1
7860735 Evanitsky Dec 2010 B2
7865594 Baumback et al. Jan 2011 B1
7865953 Hsieh et al. Jan 2011 B1
7873065 Mukerji et al. Jan 2011 B1
7890612 Todd et al. Feb 2011 B2
7890989 Hofrichter et al. Feb 2011 B1
7899899 Joshi Mar 2011 B2
7904875 Hegyi Mar 2011 B2
7912921 O'Rourke et al. Mar 2011 B2
7925713 Day et al. Apr 2011 B1
7925782 Sivasubramanian et al. Apr 2011 B2
7930393 Baumback et al. Apr 2011 B1
7930402 Swildens et al. Apr 2011 B2
7930427 Josefsberg et al. Apr 2011 B2
7933988 Nasuto et al. Apr 2011 B2
7937456 McGrath Apr 2011 B2
7937477 Day et al. May 2011 B1
7945693 Farber et al. May 2011 B2
7949779 Farber et al. May 2011 B2
7958222 Pruitt et al. Jun 2011 B1
7958258 Yeung et al. Jun 2011 B2
7961736 Ayyagari Jun 2011 B2
7962597 Richardson et al. Jun 2011 B2
7966404 Hedin et al. Jun 2011 B2
7970816 Chess et al. Jun 2011 B2
7970940 van de Ven et al. Jun 2011 B1
7979509 Malmskog et al. Jul 2011 B1
7991910 Richardson et al. Aug 2011 B2
7996404 Wong et al. Aug 2011 B2
7996533 Leighton et al. Aug 2011 B2
7996535 Auerbach Aug 2011 B2
8000724 Rayburn et al. Aug 2011 B1
8001187 Stochosky Aug 2011 B2
8010705 Sebastian et al. Aug 2011 B1
8010707 Elzur et al. Aug 2011 B2
8019869 Kriegsman Sep 2011 B2
8024441 Kommula et al. Sep 2011 B2
8028090 Richardson et al. Sep 2011 B2
8041773 Abu-Ghazaleh et al. Oct 2011 B2
8041809 Sundaram et al. Oct 2011 B2
8041818 Gupta et al. Oct 2011 B2
8042054 White et al. Oct 2011 B2
8051166 Baumback et al. Oct 2011 B1
8065275 Eriksen et al. Nov 2011 B2
8069231 Schran et al. Nov 2011 B2
8073940 Richardson et al. Dec 2011 B1
8079087 Spies et al. Dec 2011 B1
8082348 Averbuj et al. Dec 2011 B1
8099487 Smirnov et al. Jan 2012 B1
8108623 Krishnaprasad et al. Jan 2012 B2
8117306 Baumback et al. Feb 2012 B1
8122098 Richardson et al. Feb 2012 B1
8122124 Baumback et al. Feb 2012 B1
8132242 Wu Mar 2012 B1
8135820 Richardson et al. Mar 2012 B2
8155126 Mao et al. Apr 2012 B1
8156199 Hoche-Long et al. Apr 2012 B1
8156243 Richardson et al. Apr 2012 B2
8161184 Sekar et al. Apr 2012 B2
8165915 Lucash Apr 2012 B1
8175863 Ostermeyer et al. May 2012 B1
8180720 Kovacs et al. May 2012 B1
8190682 Paterson-Jones et al. May 2012 B2
8195605 Chellappa et al. Jun 2012 B2
8195837 McCarthy et al. Jun 2012 B2
8209695 Pruyne et al. Jun 2012 B1
8218965 Uhlhorn et al. Jul 2012 B1
8224942 Presotto et al. Jul 2012 B1
8224971 Miller et al. Jul 2012 B1
8224986 Liskov et al. Jul 2012 B1
8224994 Schneider Jul 2012 B1
8234403 Richardson et al. Jul 2012 B2
8239530 Sundaram et al. Aug 2012 B2
8250135 Driesen et al. Aug 2012 B2
8250211 Swildens et al. Aug 2012 B2
8250219 Raciborski et al. Aug 2012 B2
8260914 Ranjan Aug 2012 B1
8261062 Aura et al. Sep 2012 B2
8266288 Banerjee et al. Sep 2012 B2
8266327 Kumar et al. Sep 2012 B2
8271471 Kamvar et al. Sep 2012 B1
8280998 Joshi Oct 2012 B2
8281035 Farber et al. Oct 2012 B2
8286176 Baumback et al. Oct 2012 B1
8291046 Farber et al. Oct 2012 B2
8291117 Eggleston et al. Oct 2012 B1
8296375 Katzer et al. Oct 2012 B1
8296393 Alexander et al. Oct 2012 B2
8296429 Baumback et al. Oct 2012 B2
8296786 Faust et al. Oct 2012 B2
8301600 Helmick et al. Oct 2012 B1
8301645 Crook Oct 2012 B1
8316124 Baumback et al. Oct 2012 B1
8321568 Sivasubramanian et al. Nov 2012 B2
8321588 Richardson et al. Nov 2012 B2
8331370 Hamilton et al. Nov 2012 B2
8341745 Chat et al. Dec 2012 B1
8356074 Ehrlich et al. Jan 2013 B1
8380831 Barber Feb 2013 B2
8380851 McCarthy et al. Feb 2013 B2
8392928 Forys et al. Mar 2013 B1
8396908 Moore et al. Mar 2013 B2
8402137 Sivasubramanian et al. Mar 2013 B2
8423408 Barnes et al. Apr 2013 B1
8423662 Weihl et al. Apr 2013 B1
8423667 Richardson et al. Apr 2013 B2
8433749 Wee et al. Apr 2013 B2
8443167 Fallone et al. May 2013 B1
8447831 Sivasubramanian et al. May 2013 B1
8447854 Jasinskyj May 2013 B1
8447876 Verma et al. May 2013 B2
8452745 Ramakrishna May 2013 B2
8452870 Baumback et al. May 2013 B2
8452874 MacCarthaigh et al. May 2013 B2
8458360 Richardson et al. Jun 2013 B2
8463877 Richardson Jun 2013 B1
8468222 Sakata et al. Jun 2013 B2
8468245 Farber et al. Jun 2013 B2
8473613 Farber et al. Jun 2013 B2
8478883 Day et al. Jul 2013 B2
8478903 Farber et al. Jul 2013 B2
8489737 Baumback et al. Jul 2013 B2
8504721 Hsu et al. Aug 2013 B2
8504775 Plamondon Aug 2013 B2
8510428 Joshi Aug 2013 B2
8510807 Elazary et al. Aug 2013 B1
8516082 Cadwell et al. Aug 2013 B2
8521851 Richardson et al. Aug 2013 B1
8521876 Goodman et al. Aug 2013 B2
8521880 Richardson et al. Aug 2013 B1
8521885 Richardson et al. Aug 2013 B1
8521908 Holmes et al. Aug 2013 B2
8526405 Curtis et al. Sep 2013 B2
8527639 Liskov et al. Sep 2013 B1
8527645 Proffit et al. Sep 2013 B1
8527658 Holmes et al. Sep 2013 B2
8549646 Stavrou et al. Oct 2013 B2
8572208 Farber et al. Oct 2013 B2
8572210 Farber et al. Oct 2013 B2
8577963 Trahan et al. Nov 2013 B2
8577992 Richardson et al. Nov 2013 B1
8589996 Ma et al. Nov 2013 B2
8606926 Ulevitch Dec 2013 B2
8606996 Richardson et al. Dec 2013 B2
8612565 Schneider Dec 2013 B2
8612588 Ehrlich et al. Dec 2013 B1
8615549 Knowles et al. Dec 2013 B2
8619780 Brandwine Dec 2013 B1
8626950 Richardson et al. Jan 2014 B1
8635340 Schneider Jan 2014 B1
8639817 Sivasubramanian et al. Jan 2014 B2
8645539 McCarthy et al. Feb 2014 B2
8645700 Smith et al. Feb 2014 B2
8667127 Bettis et al. Feb 2014 B2
8676918 Richardson et al. Mar 2014 B2
8683023 Brandwine et al. Mar 2014 B1
8683076 Farber et al. Mar 2014 B2
8688837 Richardson et al. Apr 2014 B1
8694642 Dempsky et al. Apr 2014 B2
8712950 Smith et al. Apr 2014 B2
8732309 Richardson et al. May 2014 B1
8738766 Kazerani et al. May 2014 B1
8745177 Kazerani et al. Jun 2014 B1
8756322 Lynch Jun 2014 B1
8756325 Sivasubramanian et al. Jun 2014 B2
8756341 Richardson et al. Jun 2014 B1
8762526 Baumback et al. Jun 2014 B2
8775553 Cansino et al. Jul 2014 B2
8782207 Qiu et al. Jul 2014 B2
8782236 Marshall et al. Jul 2014 B1
8782279 Eggleston et al. Jul 2014 B2
8788671 Richardson et al. Jul 2014 B2
8812727 Sorenson, III et al. Aug 2014 B1
8819187 Hofmann Aug 2014 B1
8819283 Richardson et al. Aug 2014 B2
8826032 Yahalom et al. Sep 2014 B1
8843625 Baumback et al. Sep 2014 B2
8902897 Hamilton et al. Sep 2014 B2
8904009 Marshall et al. Dec 2014 B1
8914514 Jenkins et al. Dec 2014 B1
8914626 Adogla et al. Dec 2014 B1
8914797 Osogami et al. Dec 2014 B2
8914814 Middleton et al. Dec 2014 B1
8924528 Richardson et al. Dec 2014 B1
8930513 Richardson et al. Jan 2015 B1
8930544 Richardson et al. Jan 2015 B2
8935744 Osterweil et al. Jan 2015 B2
8938526 Richardson et al. Jan 2015 B1
8949161 Borst et al. Feb 2015 B2
8949459 Scholl Feb 2015 B1
8966318 Shah Feb 2015 B1
8971328 Judge et al. Feb 2015 B2
8972580 Fleischman et al. Mar 2015 B2
8976711 Li et al. Mar 2015 B2
9003035 Richardson et al. Apr 2015 B1
9003040 MacCarthaigh et al. Apr 2015 B2
9009286 Sivasubramanian et al. Apr 2015 B2
9009334 Jenkins et al. Apr 2015 B1
9021127 Richardson et al. Apr 2015 B2
9021128 Sivasubramanian et al. Apr 2015 B2
9021129 Richardson et al. Apr 2015 B2
9026616 Sivasubramanian et al. May 2015 B2
9037975 Taylor et al. May 2015 B1
9071502 Baumback et al. May 2015 B2
9075777 Pope et al. Jul 2015 B1
9075893 Jenkins Jul 2015 B1
9083675 Richardson et al. Jul 2015 B2
9083743 Patel et al. Jul 2015 B1
9088460 Baumback et al. Jul 2015 B2
9106701 Richardson et al. Aug 2015 B2
9116803 Agrawal et al. Aug 2015 B1
9118543 Baumback et al. Aug 2015 B2
9118680 Dunlap et al. Aug 2015 B1
9130756 Richardson et al. Sep 2015 B2
9130977 Zisapel et al. Sep 2015 B2
9137210 Joglekar et al. Sep 2015 B1
9137301 Dunlap et al. Sep 2015 B1
9137302 Makhijani et al. Sep 2015 B1
9154551 Watson Oct 2015 B1
9160641 Baumback et al. Oct 2015 B2
9160703 Richardson et al. Oct 2015 B2
9172674 Patel et al. Oct 2015 B1
9176894 Marshall et al. Nov 2015 B2
9185012 Richardson et al. Nov 2015 B2
9191338 Richardson et al. Nov 2015 B2
9191393 Tovar Nov 2015 B2
9191458 Richardson et al. Nov 2015 B2
9195996 Walsh et al. Nov 2015 B1
9208097 Richardson et al. Dec 2015 B2
9210099 Baumback et al. Dec 2015 B2
9210235 Sivasubramanian et al. Dec 2015 B2
9219686 Hilt et al. Dec 2015 B2
9237087 Risbood et al. Jan 2016 B1
9237114 Richardson et al. Jan 2016 B2
9240954 Ellsworth et al. Jan 2016 B1
9246776 Ellsworth et al. Jan 2016 B2
9251112 Richardson et al. Feb 2016 B2
9253065 Richardson et al. Feb 2016 B2
9276812 Nagargadde et al. Mar 2016 B1
9282032 Judge et al. Mar 2016 B2
9294391 Mostert Mar 2016 B1
9300535 Popli et al. Mar 2016 B2
9323577 Marr et al. Apr 2016 B2
9332078 Sivasubramanian et al. May 2016 B2
9367929 Bettis et al. May 2016 B2
9386038 Martini Jul 2016 B2
9391949 Richardson et al. Jul 2016 B1
9407539 Dickinson et al. Aug 2016 B1
9407676 Archer et al. Aug 2016 B2
9407681 Richardson et al. Aug 2016 B1
9407699 Sivasubramanian et al. Aug 2016 B2
9444718 Khakpour et al. Sep 2016 B2
9444759 Richardson et al. Sep 2016 B2
9479476 Richardson et al. Oct 2016 B2
9491073 Baumback et al. Oct 2016 B2
9495338 Hollis et al. Nov 2016 B1
9497259 Richardson et al. Nov 2016 B1
9515949 Richardson et al. Dec 2016 B2
9525659 Sonkin et al. Dec 2016 B1
9544388 Li et al. Jan 2017 B1
9544394 Richardson et al. Jan 2017 B2
9571389 Richardson et al. Feb 2017 B2
9584328 Graham-Cumming Feb 2017 B1
9590946 Richardson et al. Mar 2017 B2
9608957 Sivasubramanian et al. Mar 2017 B2
9621660 Sivasubramanian et al. Apr 2017 B2
9628403 Baumback et al. Apr 2017 B2
9628509 Holloway et al. Apr 2017 B2
9628554 Marshall et al. Apr 2017 B2
9645808 Turpie May 2017 B1
9660890 Baumback et al. May 2017 B2
9703713 Nadgowda Jul 2017 B2
9705922 Foxhoven et al. Jul 2017 B2
9712325 Richardson et al. Jul 2017 B2
9712484 Richardson et al. Jul 2017 B1
9734472 Richardson et al. Aug 2017 B2
9742795 Radlein et al. Aug 2017 B1
9760420 Letz et al. Sep 2017 B1
9769248 Krishnan et al. Sep 2017 B1
9774619 Radlein et al. Sep 2017 B1
9787599 Richardson et al. Oct 2017 B2
9787775 Richardson et al. Oct 2017 B1
9794188 Baumback et al. Oct 2017 B2
9794216 Richardson et al. Oct 2017 B2
9794281 Radlein et al. Oct 2017 B1
9800539 Richardson et al. Oct 2017 B2
9811451 Arguelles et al. Nov 2017 B1
9819567 Uppal et al. Nov 2017 B1
9825831 Baumback et al. Nov 2017 B2
9832141 Raftery Nov 2017 B1
9871794 Joffe et al. Jan 2018 B2
9887914 Bergman Feb 2018 B2
9887915 Richardson et al. Feb 2018 B2
9887931 Uppal et al. Feb 2018 B1
9887932 Uppal et al. Feb 2018 B1
9888089 Sivasubramanian et al. Feb 2018 B2
9893957 Ellsworth et al. Feb 2018 B2
9894168 Sivasubramanian et al. Feb 2018 B2
9900402 Li et al. Feb 2018 B1
9912740 Richardson et al. Mar 2018 B2
9929959 Mostert Mar 2018 B2
9930131 MacCarthaigh et al. Mar 2018 B2
9954934 Sivasubramanian et al. Apr 2018 B2
9985927 Richardson et al. May 2018 B2
9992086 Mizik et al. Jun 2018 B1
9992303 Richardson et al. Jun 2018 B2
9996501 Nelson et al. Jun 2018 B1
10015237 Richardson et al. Jul 2018 B2
10015241 Marr et al. Jul 2018 B2
10021179 Velummylum et al. Jul 2018 B1
10027582 Richardson et al. Jul 2018 B2
10027739 Krishnan et al. Jul 2018 B1
10033627 Howard et al. Jul 2018 B1
10033691 Mizik et al. Jul 2018 B1
10033699 Sullivan et al. Jul 2018 B2
10049051 Baldwin Aug 2018 B1
10063459 Judge et al. Aug 2018 B2
10075551 Baldwin et al. Sep 2018 B1
10079742 Richardson et al. Sep 2018 B1
10091096 Howard et al. Oct 2018 B1
10097398 Richardson et al. Oct 2018 B1
10097448 Howard et al. Oct 2018 B1
10097566 Radlein et al. Oct 2018 B1
10104009 Baumback et al. Oct 2018 B2
10110694 Watson et al. Oct 2018 B1
10116584 Richardson et al. Oct 2018 B2
10135620 Richardson et al. Nov 2018 B2
10148542 Baumback et al. Nov 2018 B2
10157135 Richardson et al. Dec 2018 B2
10158729 Sivasubramanian et al. Dec 2018 B2
10162753 Marshall et al. Dec 2018 B2
10180993 Raftery Jan 2019 B2
10200402 Radlein et al. Feb 2019 B2
10200492 MacCarthaigh et al. Feb 2019 B2
10205644 Baumback et al. Feb 2019 B2
10205698 Petersen et al. Feb 2019 B1
10218584 Ellsworth et al. Feb 2019 B2
10225322 Richardson et al. Mar 2019 B2
10225326 Puchala et al. Mar 2019 B1
10225362 Watson Mar 2019 B2
10225365 Hotchkies et al. Mar 2019 B1
10230819 Richardson et al. Mar 2019 B2
10257307 Baldwin Apr 2019 B1
10264062 Richardson et al. Apr 2019 B2
10270878 Uppal et al. Apr 2019 B1
10284446 Baumback et al. Apr 2019 B2
10305797 Richardson et al. May 2019 B2
10311371 Hotchkies et al. May 2019 B1
10348639 Puchala et al. Jul 2019 B2
10372499 Radhakrishnan et al. Aug 2019 B1
10374955 Mostert Aug 2019 B2
10410085 Bettis et al. Sep 2019 B2
10447648 Bliss et al. Oct 2019 B2
10462025 Baumback et al. Oct 2019 B2
10467042 Mercier et al. Nov 2019 B1
10469355 Uppal et al. Nov 2019 B2
10469513 Uppal et al. Nov 2019 B2
10491534 Richardson et al. Nov 2019 B2
10505961 Uppal et al. Dec 2019 B2
10506029 Hollis et al. Dec 2019 B2
10511567 Richardson et al. Dec 2019 B2
10516590 Mizik et al. Dec 2019 B2
10521348 Marshall et al. Dec 2019 B2
10523783 Richardson et al. Dec 2019 B2
10530874 Sivasubramanian et al. Jan 2020 B2
10542079 Marr et al. Jan 2020 B2
10554748 Sivasubramanian et al. Feb 2020 B2
10574787 Richardson et al. Feb 2020 B2
10601767 Richardson et al. Mar 2020 B2
10616250 Uppal et al. Apr 2020 B2
10623408 Marshall et al. Apr 2020 B1
10630771 Garza et al. Apr 2020 B1
10645149 Sivasubramanian et al. May 2020 B2
10666756 Baldwin et al. May 2020 B2
10691752 Raftery Jun 2020 B2
10742550 Richardson et al. Aug 2020 B2
10742593 Vasquez et al. Aug 2020 B1
10771552 Sivasubramanlan et al. Sep 2020 B2
10778554 Richardson et al. Sep 2020 B2
10783077 Marshall et al. Sep 2020 B2
10785037 Richardson et al. Sep 2020 B2
10797995 Richardson et al. Oct 2020 B2
10812358 Navaneetha et al. Oct 2020 B2
10831549 Radhakrishnan et al. Nov 2020 B1
10931738 Richardson et al. Feb 2021 B2
10938884 Baldwin et al. Mar 2021 B1
10958501 Richardson et al. Mar 2021 B1
20010000811 May et al. May 2001 A1
20010025305 Yoshiasa et al. Sep 2001 A1
20010027479 Delaney et al. Oct 2001 A1
20010032133 Moran Oct 2001 A1
20010034704 Farhat et al. Oct 2001 A1
20010049741 Skene et al. Dec 2001 A1
20010052016 Skene et al. Dec 2001 A1
20010056416 Garcia-Luna-Aceves Dec 2001 A1
20010056500 Farber et al. Dec 2001 A1
20020002613 Freeman et al. Jan 2002 A1
20020004816 Vange et al. Jan 2002 A1
20020004846 Garcia-Luna-Aceves et al. Jan 2002 A1
20020007413 Garcia-Luna-Aceves et al. Jan 2002 A1
20020010783 Primak et al. Jan 2002 A1
20020010798 Ben-Shaul et al. Jan 2002 A1
20020016831 Peled et al. Feb 2002 A1
20020035624 Kim Mar 2002 A1
20020048269 Hong et al. Apr 2002 A1
20020049608 Hartsell et al. Apr 2002 A1
20020049842 Huetsch et al. Apr 2002 A1
20020049857 Farber et al. Apr 2002 A1
20020052942 Swildens et al. May 2002 A1
20020062372 Hong et al. May 2002 A1
20020065910 Dutta May 2002 A1
20020068554 Dusse Jun 2002 A1
20020069420 Russell et al. Jun 2002 A1
20020078233 Biliris et al. Jun 2002 A1
20020082858 Heddaya et al. Jun 2002 A1
20020083118 Sim Jun 2002 A1
20020083148 Shaw et al. Jun 2002 A1
20020083178 Brothers Jun 2002 A1
20020083198 Kim et al. Jun 2002 A1
20020087374 Boubez et al. Jul 2002 A1
20020087797 Adrangi Jul 2002 A1
20020091786 Yamaguchi et al. Jul 2002 A1
20020091801 Lewin et al. Jul 2002 A1
20020092026 Janniello et al. Jul 2002 A1
20020099616 Sweldens Jul 2002 A1
20020099850 Farber et al. Jul 2002 A1
20020101836 Dorenbosch Aug 2002 A1
20020103820 Cartmell et al. Aug 2002 A1
20020103972 Satran et al. Aug 2002 A1
20020107944 Bai et al. Aug 2002 A1
20020112049 Elnozahy et al. Aug 2002 A1
20020112123 Becker et al. Aug 2002 A1
20020116481 Lee Aug 2002 A1
20020116491 Boyd et al. Aug 2002 A1
20020116582 Copeland et al. Aug 2002 A1
20020120666 Landsman et al. Aug 2002 A1
20020120782 Dillon et al. Aug 2002 A1
20020124047 Gartner et al. Sep 2002 A1
20020124098 Shaw Sep 2002 A1
20020129123 Johnson et al. Sep 2002 A1
20020131428 Pecus et al. Sep 2002 A1
20020133741 Maeda et al. Sep 2002 A1
20020135611 Deosaran et al. Sep 2002 A1
20020138286 Engstrom Sep 2002 A1
20020138437 Lewin et al. Sep 2002 A1
20020138443 Schran et al. Sep 2002 A1
20020138649 Cartmell et al. Sep 2002 A1
20020138761 Kanemaki et al. Sep 2002 A1
20020143675 Orshan Oct 2002 A1
20020143798 Lisiecki et al. Oct 2002 A1
20020143989 Huitema et al. Oct 2002 A1
20020145993 Chowdhury et al. Oct 2002 A1
20020147770 Tang Oct 2002 A1
20020147774 Lisiecki et al. Oct 2002 A1
20020150094 Cheng et al. Oct 2002 A1
20020150276 Chang Oct 2002 A1
20020152326 Orshan Oct 2002 A1
20020154157 Sherr et al. Oct 2002 A1
20020156884 Bertram et al. Oct 2002 A1
20020156911 Croman et al. Oct 2002 A1
20020161745 Call Oct 2002 A1
20020161767 Shapiro et al. Oct 2002 A1
20020163882 Bornstein et al. Nov 2002 A1
20020165912 Wenocur et al. Nov 2002 A1
20020169890 Beaumont et al. Nov 2002 A1
20020184368 Wang Dec 2002 A1
20020187935 Redmond et al. Dec 2002 A1
20020188722 Banerjee et al. Dec 2002 A1
20020194324 Guha Dec 2002 A1
20020194382 Kausik et al. Dec 2002 A1
20020198953 O'Rourke et al. Dec 2002 A1
20030002484 Freedman Jan 2003 A1
20030004998 Datta Jan 2003 A1
20030005036 Mitzenmacher Jan 2003 A1
20030005111 Allan Jan 2003 A1
20030007482 Khello et al. Jan 2003 A1
20030009488 Hart, III Jan 2003 A1
20030009591 Hayball et al. Jan 2003 A1
20030026410 Lumsden Feb 2003 A1
20030028642 Agarwal et al. Feb 2003 A1
20030033283 Evans et al. Feb 2003 A1
20030037108 Peiffer et al. Feb 2003 A1
20030037139 Shteyn Feb 2003 A1
20030037284 Srinivasan et al. Feb 2003 A1
20030041094 Lara et al. Feb 2003 A1
20030046343 Krishnamurthy et al. Mar 2003 A1
20030065739 Shnier Apr 2003 A1
20030070096 Pazi et al. Apr 2003 A1
20030074401 Connell et al. Apr 2003 A1
20030074471 Anderson et al. Apr 2003 A1
20030074472 Lucco et al. Apr 2003 A1
20030079027 Slocombe et al. Apr 2003 A1
20030093523 Cranor May 2003 A1
20030099202 Lear et al. May 2003 A1
20030099237 Mitra et al. May 2003 A1
20030101278 Garcia-Luna-Aceves et al. May 2003 A1
20030105829 Hayward Jun 2003 A1
20030105857 Kamen et al. Jun 2003 A1
20030112792 Cranor et al. Jun 2003 A1
20030120741 Wu et al. Jun 2003 A1
20030126387 Watanabe Jul 2003 A1
20030133554 Nykanen et al. Jul 2003 A1
20030135467 Okamoto Jul 2003 A1
20030135509 Davis et al. Jul 2003 A1
20030140087 Lincoln et al. Jul 2003 A1
20030145038 Tariq et al. Jul 2003 A1
20030145066 Okada et al. Jul 2003 A1
20030149581 Chaudhri et al. Aug 2003 A1
20030154239 Davis et al. Aug 2003 A1
20030154284 Bernardin et al. Aug 2003 A1
20030163722 Anderson, IV Aug 2003 A1
20030172145 Nguyen Sep 2003 A1
20030172183 Anderson, IV et al. Sep 2003 A1
20030172291 Judge et al. Sep 2003 A1
20030174648 Wang et al. Sep 2003 A1
20030177321 Watanabe Sep 2003 A1
20030182305 Balva et al. Sep 2003 A1
20030182413 Allen et al. Sep 2003 A1
20030182447 Schilling Sep 2003 A1
20030187935 Agarwalla et al. Oct 2003 A1
20030187970 Chase et al. Oct 2003 A1
20030191822 Leighton et al. Oct 2003 A1
20030200394 Ashmore et al. Oct 2003 A1
20030204602 Hudson et al. Oct 2003 A1
20030206520 Wu et al. Nov 2003 A1
20030221000 Cherkasova et al. Nov 2003 A1
20030229682 Day Dec 2003 A1
20030233423 Dilley et al. Dec 2003 A1
20030233445 Levy et al. Dec 2003 A1
20030233455 Leber et al. Dec 2003 A1
20030236700 Arning et al. Dec 2003 A1
20030236779 Choi et al. Dec 2003 A1
20040003032 Ma et al. Jan 2004 A1
20040010562 Itonaga Jan 2004 A1
20040010563 Forte et al. Jan 2004 A1
20040010588 Slater et al. Jan 2004 A1
20040010601 Afergan Jan 2004 A1
20040010621 Afergan et al. Jan 2004 A1
20040010683 Huitema Jan 2004 A1
20040015584 Cartmell et al. Jan 2004 A1
20040019518 Abraham et al. Jan 2004 A1
20040019781 Chari et al. Jan 2004 A1
20040024841 Becker et al. Feb 2004 A1
20040030620 Benjamin et al. Feb 2004 A1
20040032278 Orii et al. Feb 2004 A1
20040034744 Karlsson et al. Feb 2004 A1
20040039798 Hotz et al. Feb 2004 A1
20040044731 Chen et al. Mar 2004 A1
20040044791 Pouzzner Mar 2004 A1
20040054757 Ueda et al. Mar 2004 A1
20040059805 Dinker et al. Mar 2004 A1
20040064335 Yang Apr 2004 A1
20040064501 Jan et al. Apr 2004 A1
20040068542 Lalonde et al. Apr 2004 A1
20040073596 Kloninger et al. Apr 2004 A1
20040073707 Dillon Apr 2004 A1
20040073867 Kausik et al. Apr 2004 A1
20040078468 Hedin et al. Apr 2004 A1
20040078487 Cernohous et al. Apr 2004 A1
20040083283 Sundaram et al. Apr 2004 A1
20040083307 Uysal Apr 2004 A1
20040098478 Koetke et al. May 2004 A1
20040105544 Haneda et al. Jun 2004 A1
20040114579 Karaoguz et al. Jun 2004 A1
20040117309 Inoue et al. Jun 2004 A1
20040117455 Kaminksy et al. Jun 2004 A1
20040128344 Trossen Jul 2004 A1
20040128346 Melamed et al. Jul 2004 A1
20040148520 Talpade et al. Jul 2004 A1
20040167981 Douglas et al. Aug 2004 A1
20040167982 Cohen et al. Aug 2004 A1
20040170379 Yao et al. Sep 2004 A1
20040172466 Douglas et al. Sep 2004 A1
20040184456 Binding et al. Sep 2004 A1
20040194085 Beaubien et al. Sep 2004 A1
20040194102 Neerdaels Sep 2004 A1
20040203630 Wang Oct 2004 A1
20040205149 Dillon et al. Oct 2004 A1
20040205162 Parikh Oct 2004 A1
20040205374 Poletto et al. Oct 2004 A1
20040215823 Kleinfelter et al. Oct 2004 A1
20040221019 Swildens et al. Nov 2004 A1
20040221034 Kausik et al. Nov 2004 A1
20040246948 Lee et al. Dec 2004 A1
20040249939 Amini et al. Dec 2004 A1
20040249971 Klinker Dec 2004 A1
20040249975 Tuck et al. Dec 2004 A1
20040250119 Shelest et al. Dec 2004 A1
20040254921 Cohen et al. Dec 2004 A1
20040260769 Yamamoto Dec 2004 A1
20040267906 Truty Dec 2004 A1
20040267907 Gustafsson Dec 2004 A1
20050010653 McCanne Jan 2005 A1
20050015471 Zhang et al. Jan 2005 A1
20050021706 Maggi et al. Jan 2005 A1
20050021862 Schroeder et al. Jan 2005 A1
20050027882 Sullivan et al. Feb 2005 A1
20050038967 Umbehocker et al. Feb 2005 A1
20050039019 Delany Feb 2005 A1
20050044270 Grove et al. Feb 2005 A1
20050102683 Branson et al. May 2005 A1
20050108169 Balasubramanian et al. May 2005 A1
20050108262 Fawcett May 2005 A1
20050108529 Juneau May 2005 A1
20050114296 Farber et al. May 2005 A1
20050117717 Lumsden Jun 2005 A1
20050132083 Raciborski et al. Jun 2005 A1
20050147088 Bao et al. Jul 2005 A1
20050149529 Gutmans Jul 2005 A1
20050157712 Rangarajan et al. Jul 2005 A1
20050160133 Greenlee et al. Jul 2005 A1
20050163168 Sheth et al. Jul 2005 A1
20050168782 Kobashi et al. Aug 2005 A1
20050171959 Deforche et al. Aug 2005 A1
20050172080 Miyauchi Aug 2005 A1
20050174989 Chen et al. Aug 2005 A1
20050181769 Kogawa Aug 2005 A1
20050188073 Nakamichi et al. Aug 2005 A1
20050192008 Desai et al. Sep 2005 A1
20050192814 Challener et al. Sep 2005 A1
20050198170 LeMay et al. Sep 2005 A1
20050198200 Subramanian et al. Sep 2005 A1
20050198303 Knauerhase et al. Sep 2005 A1
20050198334 Farber et al. Sep 2005 A1
20050198453 Osaki Sep 2005 A1
20050198571 Kramer et al. Sep 2005 A1
20050201302 Gaddis et al. Sep 2005 A1
20050216483 Armstrong et al. Sep 2005 A1
20050216569 Coppola et al. Sep 2005 A1
20050216674 Robbin et al. Sep 2005 A1
20050223095 Volz et al. Oct 2005 A1
20050228856 Swildens et al. Oct 2005 A1
20050229119 Torvinen Oct 2005 A1
20050232165 Brawn et al. Oct 2005 A1
20050234864 Shapiro Oct 2005 A1
20050240574 Challenger et al. Oct 2005 A1
20050256880 Nam Koong et al. Nov 2005 A1
20050259645 Chen et al. Nov 2005 A1
20050259672 Eduri Nov 2005 A1
20050262248 Jennings, III et al. Nov 2005 A1
20050266835 Agrawal et al. Dec 2005 A1
20050267928 Anderson et al. Dec 2005 A1
20050267937 Daniels et al. Dec 2005 A1
20050267991 Huitema et al. Dec 2005 A1
20050267992 Huitema et al. Dec 2005 A1
20050267993 Huitema et al. Dec 2005 A1
20050278259 Gunaseelan et al. Dec 2005 A1
20050283759 Peteanu et al. Dec 2005 A1
20050283784 Suzuki Dec 2005 A1
20050286564 Hatley Dec 2005 A1
20060005014 Aura et al. Jan 2006 A1
20060013158 Ahuja et al. Jan 2006 A1
20060020596 Liu et al. Jan 2006 A1
20060020684 Mukherjee et al. Jan 2006 A1
20060020714 Girouard et al. Jan 2006 A1
20060020715 Jungck Jan 2006 A1
20060021001 Giles et al. Jan 2006 A1
20060026067 Nicholas et al. Feb 2006 A1
20060026154 Altinel et al. Feb 2006 A1
20060031239 Koenig Feb 2006 A1
20060031319 Nelson et al. Feb 2006 A1
20060031503 Gilbert Feb 2006 A1
20060034494 Holloran Feb 2006 A1
20060036720 Faulk, Jr. Feb 2006 A1
20060036966 Yevdayev Feb 2006 A1
20060037037 Miranz Feb 2006 A1
20060039352 Karstens Feb 2006 A1
20060041614 Oe Feb 2006 A1
20060045005 Blackmore et al. Mar 2006 A1
20060047787 Agarwal et al. Mar 2006 A1
20060047813 Aggarwal et al. Mar 2006 A1
20060059246 Grove Mar 2006 A1
20060063534 Kokkonen et al. Mar 2006 A1
20060064476 Decasper et al. Mar 2006 A1
20060064500 Roth et al. Mar 2006 A1
20060070060 Tantawi et al. Mar 2006 A1
20060074750 Clark et al. Apr 2006 A1
20060075084 Lyon Apr 2006 A1
20060075139 Jungck Apr 2006 A1
20060083165 McLane et al. Apr 2006 A1
20060085536 Meyer et al. Apr 2006 A1
20060088026 Mazur et al. Apr 2006 A1
20060106938 Dini et al. May 2006 A1
20060107036 Randle et al. May 2006 A1
20060112066 Hamzy May 2006 A1
20060112176 Liu et al. May 2006 A1
20060120385 Atchison et al. Jun 2006 A1
20060129665 Toebes et al. Jun 2006 A1
20060129766 Cassia et al. Jun 2006 A1
20060136453 Kwan Jun 2006 A1
20060143293 Freedman Jun 2006 A1
20060143442 Smith Jun 2006 A1
20060146820 Friedman et al. Jul 2006 A1
20060149529 Nguyen et al. Jul 2006 A1
20060155823 Tran et al. Jul 2006 A1
20060155862 Kathi et al. Jul 2006 A1
20060161541 Cencini Jul 2006 A1
20060165051 Banerjee et al. Jul 2006 A1
20060168088 Leighton et al. Jul 2006 A1
20060173855 Turner et al. Aug 2006 A1
20060173957 Robinson Aug 2006 A1
20060179080 Meek et al. Aug 2006 A1
20060184936 Abels et al. Aug 2006 A1
20060188097 Taniguchi et al. Aug 2006 A1
20060190605 Franz et al. Aug 2006 A1
20060193247 Naseh et al. Aug 2006 A1
20060195866 Thukral Aug 2006 A1
20060206568 Verma et al. Sep 2006 A1
20060206586 Ling et al. Sep 2006 A1
20060218265 Farber et al. Sep 2006 A1
20060218304 Mukherjee et al. Sep 2006 A1
20060221971 Andrieux et al. Oct 2006 A1
20060224752 Parekh et al. Oct 2006 A1
20060227740 McLaughlin et al. Oct 2006 A1
20060227758 Rana et al. Oct 2006 A1
20060230137 Gare et al. Oct 2006 A1
20060230265 Krishna Oct 2006 A1
20060233155 Srivastava Oct 2006 A1
20060242227 Rao Oct 2006 A1
20060253546 Chang et al. Nov 2006 A1
20060253609 Andreev et al. Nov 2006 A1
20060255510 Schilling Nov 2006 A1
20060259581 Piersol Nov 2006 A1
20060259690 Vittal et al. Nov 2006 A1
20060259984 Juneau Nov 2006 A1
20060265497 Ohata et al. Nov 2006 A1
20060265508 Angel et al. Nov 2006 A1
20060265720 Cai et al. Nov 2006 A1
20060271641 Stavrakos et al. Nov 2006 A1
20060282505 Hasha et al. Dec 2006 A1
20060282522 Lewin et al. Dec 2006 A1
20060288119 Kim et al. Dec 2006 A1
20060288424 Saito Dec 2006 A1
20070005689 Leighton et al. Jan 2007 A1
20070005801 Kumar et al. Jan 2007 A1
20070005892 Mullender et al. Jan 2007 A1
20070011267 Overton et al. Jan 2007 A1
20070014241 Banerjee et al. Jan 2007 A1
20070021998 Laithwaite et al. Jan 2007 A1
20070028001 Phillips et al. Feb 2007 A1
20070038729 Sullivan et al. Feb 2007 A1
20070038994 Davis et al. Feb 2007 A1
20070041393 Westhead et al. Feb 2007 A1
20070043667 Qawami et al. Feb 2007 A1
20070043859 Ruul Feb 2007 A1
20070050522 Grove et al. Mar 2007 A1
20070050703 Lebel Mar 2007 A1
20070055764 Dilley et al. Mar 2007 A1
20070055765 Lisiecki et al. Mar 2007 A1
20070061440 Sundaram et al. Mar 2007 A1
20070064610 Khandani Mar 2007 A1
20070076872 Juneau Apr 2007 A1
20070086429 Lawrence et al. Apr 2007 A1
20070094361 Hoynowski et al. Apr 2007 A1
20070101061 Baskaran et al. May 2007 A1
20070101377 Six et al. May 2007 A1
20070118667 McCarthy et al. May 2007 A1
20070118668 McCarthy et al. May 2007 A1
20070124309 Takase et al. May 2007 A1
20070134641 Lieu Jun 2007 A1
20070156726 Levy Jul 2007 A1
20070156919 Potti et al. Jul 2007 A1
20070162331 Sullivan Jul 2007 A1
20070168336 Ransil et al. Jul 2007 A1
20070168517 Weller Jul 2007 A1
20070174426 Swildens et al. Jul 2007 A1
20070174442 Sherman et al. Jul 2007 A1
20070174490 Choi et al. Jul 2007 A1
20070183342 Wong et al. Aug 2007 A1
20070198982 Bolan et al. Aug 2007 A1
20070204107 Greenfield et al. Aug 2007 A1
20070208737 Li et al. Sep 2007 A1
20070214232 Belimpasakis et al. Sep 2007 A1
20070219795 Park et al. Sep 2007 A1
20070220010 Ertugrul Sep 2007 A1
20070226294 Pruitt et al. Sep 2007 A1
20070233705 Farber et al. Oct 2007 A1
20070233706 Farber et al. Oct 2007 A1
20070233846 Farber et al. Oct 2007 A1
20070233884 Farber et al. Oct 2007 A1
20070233896 Hilt et al. Oct 2007 A1
20070242824 Vishik Oct 2007 A1
20070243860 Aiello et al. Oct 2007 A1
20070244964 Challenger et al. Oct 2007 A1
20070245022 Olliphant et al. Oct 2007 A1
20070250467 Mesnik et al. Oct 2007 A1
20070250468 Pieper Oct 2007 A1
20070250560 Wein et al. Oct 2007 A1
20070250601 Amlekar et al. Oct 2007 A1
20070250611 Bhogal et al. Oct 2007 A1
20070253377 Janneteau et al. Nov 2007 A1
20070255843 Zubev Nov 2007 A1
20070263604 Tal Nov 2007 A1
20070266113 Koopmans et al. Nov 2007 A1
20070266311 Westphal Nov 2007 A1
20070266333 Cossey et al. Nov 2007 A1
20070270165 Poosala Nov 2007 A1
20070271375 Hwang Nov 2007 A1
20070271385 Davis et al. Nov 2007 A1
20070271560 Wahlert et al. Nov 2007 A1
20070271608 Shimizu et al. Nov 2007 A1
20070280197 Pearlman et al. Dec 2007 A1
20070280229 Kenney Dec 2007 A1
20070281689 Altman et al. Dec 2007 A1
20070288588 Wein et al. Dec 2007 A1
20070291739 Sullivan et al. Dec 2007 A1
20070294419 Ulevitch Dec 2007 A1
20080005057 Ozzie et al. Jan 2008 A1
20080005275 Overton et al. Jan 2008 A1
20080008089 Bornstein et al. Jan 2008 A1
20080016233 Schneider Jan 2008 A1
20080025304 Venkataswami et al. Jan 2008 A1
20080028463 Dagon et al. Jan 2008 A1
20080037536 Padmanabhan et al. Feb 2008 A1
20080046550 Mazur et al. Feb 2008 A1
20080046596 Afergan et al. Feb 2008 A1
20080049615 Bugenhagen Feb 2008 A1
20080056207 Eriksson et al. Mar 2008 A1
20080062997 Nix Mar 2008 A1
20080065724 Seed et al. Mar 2008 A1
20080065745 Leighton et al. Mar 2008 A1
20080066072 Yurekli et al. Mar 2008 A1
20080071859 Seed et al. Mar 2008 A1
20080071987 Karn et al. Mar 2008 A1
20080072264 Crayford Mar 2008 A1
20080082551 Farber et al. Apr 2008 A1
20080082662 Dandliker et al. Apr 2008 A1
20080086434 Chesla Apr 2008 A1
20080086559 Davis et al. Apr 2008 A1
20080086574 Raciborski et al. Apr 2008 A1
20080092242 Rowley Apr 2008 A1
20080101358 Van Ewijk et al. May 2008 A1
20080103805 Shear et al. May 2008 A1
20080104268 Farber et al. May 2008 A1
20080109679 Wright et al. May 2008 A1
20080114829 Button et al. May 2008 A1
20080125077 Velazquez et al. May 2008 A1
20080126706 Newport et al. May 2008 A1
20080134043 Georgis et al. Jun 2008 A1
20080140800 Farber et al. Jun 2008 A1
20080147866 Stolorz et al. Jun 2008 A1
20080147873 Matsumoto Jun 2008 A1
20080155059 Hardin et al. Jun 2008 A1
20080155061 Afergan et al. Jun 2008 A1
20080155613 Benya et al. Jun 2008 A1
20080155614 Cooper et al. Jun 2008 A1
20080155694 Kwon et al. Jun 2008 A1
20080162667 Verma et al. Jul 2008 A1
20080162821 Duran et al. Jul 2008 A1
20080162843 Davis et al. Jul 2008 A1
20080172488 Jawahar et al. Jul 2008 A1
20080175222 Barnea et al. Jul 2008 A1
20080184357 Drako et al. Jul 2008 A1
20080189437 Halley Aug 2008 A1
20080201332 Souders et al. Aug 2008 A1
20080201401 Pugh et al. Aug 2008 A1
20080215718 Stolorz et al. Sep 2008 A1
20080215730 Sundaram et al. Sep 2008 A1
20080215735 Farber et al. Sep 2008 A1
20080215747 Menon et al. Sep 2008 A1
20080215750 Farber et al. Sep 2008 A1
20080215755 Farber et al. Sep 2008 A1
20080222281 Dilley et al. Sep 2008 A1
20080222291 Weller et al. Sep 2008 A1
20080222295 Robinson et al. Sep 2008 A1
20080222647 Taylor et al. Sep 2008 A1
20080225779 Bragiel et al. Sep 2008 A1
20080228574 Stewart et al. Sep 2008 A1
20080228920 Souders et al. Sep 2008 A1
20080235383 Schneider Sep 2008 A1
20080235400 Slocombe et al. Sep 2008 A1
20080256087 Piironen et al. Oct 2008 A1
20080256175 Lee et al. Oct 2008 A1
20080263135 Olliphant Oct 2008 A1
20080270882 Rollins et al. Oct 2008 A1
20080275772 Suryanarayana et al. Nov 2008 A1
20080281946 Swildens et al. Nov 2008 A1
20080281950 Wald et al. Nov 2008 A1
20080288458 Sun et al. Nov 2008 A1
20080288722 Lecoq et al. Nov 2008 A1
20080301670 Gouge et al. Dec 2008 A1
20080312766 Couckuyt Dec 2008 A1
20080319862 Golan et al. Dec 2008 A1
20080320123 Houlihan et al. Dec 2008 A1
20080320269 Houlihan et al. Dec 2008 A1
20090013063 Soman Jan 2009 A1
20090016236 Alcala et al. Jan 2009 A1
20090029644 Sue et al. Jan 2009 A1
20090031042 Phatak Jan 2009 A1
20090031367 Sue Jan 2009 A1
20090031368 Ling Jan 2009 A1
20090031376 Riley et al. Jan 2009 A1
20090043900 Barber Feb 2009 A1
20090049098 Pickelsimer et al. Feb 2009 A1
20090063038 Shrivathsan et al. Mar 2009 A1
20090063704 Taylor et al. Mar 2009 A1
20090070533 Elazary et al. Mar 2009 A1
20090083228 Shatz et al. Mar 2009 A1
20090083279 Hasek Mar 2009 A1
20090083413 Levow et al. Mar 2009 A1
20090086728 Gulati et al. Apr 2009 A1
20090086741 Zhang Apr 2009 A1
20090089869 Varghese Apr 2009 A1
20090094252 Wong et al. Apr 2009 A1
20090103707 McGary et al. Apr 2009 A1
20090106202 Mizrahi Apr 2009 A1
20090106381 Kasriel et al. Apr 2009 A1
20090112703 Brown Apr 2009 A1
20090125393 Hwang et al. May 2009 A1
20090125934 Jones et al. May 2009 A1
20090132368 Cotter et al. May 2009 A1
20090132640 Verma et al. May 2009 A1
20090132648 Swildens et al. May 2009 A1
20090138533 Iwasaki et al. May 2009 A1
20090138582 Turk May 2009 A1
20090144411 Winkler et al. Jun 2009 A1
20090144412 Ferguson et al. Jun 2009 A1
20090150926 Schlack Jun 2009 A1
20090157504 Braemer et al. Jun 2009 A1
20090157850 Gagliardi et al. Jun 2009 A1
20090158163 Stephens et al. Jun 2009 A1
20090164331 Bishop et al. Jun 2009 A1
20090164614 Christian Jun 2009 A1
20090172167 Drai et al. Jul 2009 A1
20090177667 Ramos et al. Jul 2009 A1
20090182815 Czechowski et al. Jul 2009 A1
20090182837 Rogers Jul 2009 A1
20090182945 Aviles et al. Jul 2009 A1
20090187575 DaCosta Jul 2009 A1
20090198817 Sundaram et al. Aug 2009 A1
20090204682 Jeyaseelan et al. Aug 2009 A1
20090210549 Hudson et al. Aug 2009 A1
20090228708 Trostle Sep 2009 A1
20090233623 Johnson Sep 2009 A1
20090241167 Moore Sep 2009 A1
20090248697 Richardson et al. Oct 2009 A1
20090248786 Richardson et al. Oct 2009 A1
20090248787 Sivasubramanian et al. Oct 2009 A1
20090248852 Fuhrmann et al. Oct 2009 A1
20090248858 Sivasubramanian et al. Oct 2009 A1
20090248893 Richardson et al. Oct 2009 A1
20090249222 Schmidt et al. Oct 2009 A1
20090253435 Olofsson Oct 2009 A1
20090254661 Fullagar et al. Oct 2009 A1
20090254989 Achan et al. Oct 2009 A1
20090259588 Lindsay Oct 2009 A1
20090259971 Rankine et al. Oct 2009 A1
20090262741 Jungck et al. Oct 2009 A1
20090265707 Goodman et al. Oct 2009 A1
20090265786 Xie et al. Oct 2009 A1
20090271498 Cable Oct 2009 A1
20090271577 Campana et al. Oct 2009 A1
20090271730 Rose et al. Oct 2009 A1
20090276771 Nickolov et al. Nov 2009 A1
20090279444 Ravindran et al. Nov 2009 A1
20090282038 Subotin Nov 2009 A1
20090287750 Banavar et al. Nov 2009 A1
20090307307 Igarashi Dec 2009 A1
20090327489 Swildens et al. Dec 2009 A1
20090327517 Sivasubramanian et al. Dec 2009 A1
20090327914 Adar et al. Dec 2009 A1
20100005175 Swildens et al. Jan 2010 A1
20100011061 Hudson et al. Jan 2010 A1
20100011126 Hsu et al. Jan 2010 A1
20100020699 On Jan 2010 A1
20100023601 Lewin et al. Jan 2010 A1
20100023621 Ezolt et al. Jan 2010 A1
20100030662 Klein Feb 2010 A1
20100030914 Sparks et al. Feb 2010 A1
20100034470 Valencia-Campo et al. Feb 2010 A1
20100036944 Douglis et al. Feb 2010 A1
20100037314 Perdisci et al. Feb 2010 A1
20100042725 Jeon et al. Feb 2010 A1
20100049862 Dixon Feb 2010 A1
20100057894 Glasser Mar 2010 A1
20100058352 Esfahany et al. Mar 2010 A1
20100070603 Moss et al. Mar 2010 A1
20100070700 Borst et al. Mar 2010 A1
20100074268 Raza Mar 2010 A1
20100082320 Wood et al. Apr 2010 A1
20100082787 Kommula et al. Apr 2010 A1
20100088367 Brown et al. Apr 2010 A1
20100088405 Huang et al. Apr 2010 A1
20100095008 Joshi Apr 2010 A1
20100100629 Raciborski et al. Apr 2010 A1
20100103837 Jungck et al. Apr 2010 A1
20100106934 Calder et al. Apr 2010 A1
20100111059 Bappu et al. May 2010 A1
20100115133 Joshi May 2010 A1
20100115342 Shigeta et al. May 2010 A1
20100121953 Friedman et al. May 2010 A1
20100121981 Drako May 2010 A1
20100122069 Gonion May 2010 A1
20100125626 Lucas et al. May 2010 A1
20100125673 Richardson et al. May 2010 A1
20100125675 Richardson et al. May 2010 A1
20100131646 Drako May 2010 A1
20100138559 Sullivan et al. Jun 2010 A1
20100150155 Napierala Jun 2010 A1
20100161564 Lee et al. Jun 2010 A1
20100161565 Lee et al. Jun 2010 A1
20100161799 Maloo Jun 2010 A1
20100169392 Lev Ran et al. Jul 2010 A1
20100169452 Atluri et al. Jul 2010 A1
20100174811 Musiri et al. Jul 2010 A1
20100191854 Isci et al. Jul 2010 A1
20100192225 Ma et al. Jul 2010 A1
20100217801 Leighton et al. Aug 2010 A1
20100217856 Falkena Aug 2010 A1
20100223364 Wei Sep 2010 A1
20100226372 Watanabe Sep 2010 A1
20100228819 Wei Sep 2010 A1
20100235915 Memon et al. Sep 2010 A1
20100250710 Cadwell et al. Sep 2010 A1
20100257024 Holmes et al. Oct 2010 A1
20100257266 Holmes et al. Oct 2010 A1
20100257566 Matila Oct 2010 A1
20100262964 Uyeda et al. Oct 2010 A1
20100268789 Yoo et al. Oct 2010 A1
20100268814 Cross et al. Oct 2010 A1
20100274765 Murphy et al. Oct 2010 A1
20100281482 Pike et al. Nov 2010 A1
20100293296 Hsu et al. Nov 2010 A1
20100293479 Rousso et al. Nov 2010 A1
20100299427 Joshi Nov 2010 A1
20100299438 Zimmerman et al. Nov 2010 A1
20100299439 McCarthy et al. Nov 2010 A1
20100306382 Cardosa et al. Dec 2010 A1
20100312861 Kolhi et al. Dec 2010 A1
20100318508 Brawer et al. Dec 2010 A1
20100322255 Hao et al. Dec 2010 A1
20100325365 Colglazier et al. Dec 2010 A1
20100332595 Fullagar et al. Dec 2010 A1
20100332601 Walter et al. Dec 2010 A1
20100332658 Elyashev Dec 2010 A1
20110010244 Hatridge Jan 2011 A1
20110016214 Jackson Jan 2011 A1
20110029398 Boudville Feb 2011 A1
20110029598 Arnold et al. Feb 2011 A1
20110035469 Smith et al. Feb 2011 A1
20110040893 Karaoguz et al. Feb 2011 A1
20110051738 Xu Mar 2011 A1
20110055386 Middleton et al. Mar 2011 A1
20110055714 Vemulapalli et al. Mar 2011 A1
20110055921 Narayanaswamy et al. Mar 2011 A1
20110057790 Martin et al. Mar 2011 A1
20110058675 Brueck et al. Mar 2011 A1
20110072138 Canturk et al. Mar 2011 A1
20110072366 Spencer Mar 2011 A1
20110078000 Ma et al. Mar 2011 A1
20110078230 Sepulveda Mar 2011 A1
20110082916 Swanson et al. Apr 2011 A1
20110085654 Jana et al. Apr 2011 A1
20110087769 Holmes et al. Apr 2011 A1
20110093584 Qiu et al. Apr 2011 A1
20110096987 Morales et al. Apr 2011 A1
20110099294 Kapur et al. Apr 2011 A1
20110106949 Patel et al. May 2011 A1
20110113467 Agarwal et al. May 2011 A1
20110125894 Anderson et al. May 2011 A1
20110153938 Verzunov et al. Jun 2011 A1
20110153941 Spatscheck et al. Jun 2011 A1
20110154318 Oshins et al. Jun 2011 A1
20110154350 Doyle et al. Jun 2011 A1
20110161461 Niven-Jenkins Jun 2011 A1
20110132290 Perkins Jul 2011 A1
20110166935 Armentrout et al. Jul 2011 A1
20110191445 Dazzi Aug 2011 A1
20110191446 Dazzi et al. Aug 2011 A1
20110191447 Dazzi et al. Aug 2011 A1
20110191449 Swildens et al. Aug 2011 A1
20110191459 Joshi Aug 2011 A1
20110196892 Xia Aug 2011 A1
20110208876 Richardson et al. Aug 2011 A1
20110208958 Stuedi et al. Aug 2011 A1
20110209064 Jorgensen et al. Aug 2011 A1
20110219120 Farber et al. Sep 2011 A1
20110219372 Agarwal et al. Sep 2011 A1
20110238501 Almeida Sep 2011 A1
20110238793 Bedare et al. Sep 2011 A1
20110239215 Sugai Sep 2011 A1
20110252142 Richardson et al. Oct 2011 A1
20110252143 Baumback et al. Oct 2011 A1
20110255445 Johnson et al. Oct 2011 A1
20110258049 Ramer et al. Oct 2011 A1
20110258614 Tamm Oct 2011 A1
20110270964 Huang et al. Nov 2011 A1
20110276623 Girbal Nov 2011 A1
20110295942 Raghunath et al. Dec 2011 A1
20110296053 Medved et al. Dec 2011 A1
20110296370 Ferris et al. Dec 2011 A1
20110296473 Babic Dec 2011 A1
20110302304 Baumback et al. Dec 2011 A1
20110307533 Saeki Dec 2011 A1
20110320522 Endres et al. Dec 2011 A1
20110320559 Foti Dec 2011 A1
20120011190 Driesen et al. Jan 2012 A1
20120023090 Holloway et al. Jan 2012 A1
20120023226 Petersen et al. Jan 2012 A1
20120031626 Clayton et al. Feb 2012 A1
20120036238 Sundaram et al. Feb 2012 A1
20120041899 Greene et al. Feb 2012 A1
20120041970 Ghosh et al. Feb 2012 A1
20120042381 Antonakakis et al. Feb 2012 A1
20120054860 Wyschogrod et al. Feb 2012 A1
20120066360 Ghosh Mar 2012 A1
20120072600 Richardson et al. Mar 2012 A1
20120072608 Peters et al. Mar 2012 A1
20120078998 Son et al. Mar 2012 A1
20120079096 Cowan et al. Mar 2012 A1
20120079115 Richardson et al. Mar 2012 A1
20120014249 Mao et al. Apr 2012 A1
20120039972 Scheidel et al. Apr 2012 A1
20120089700 Safruti et al. Apr 2012 A1
20120096065 Suit et al. Apr 2012 A1
20120096166 Devarapalli et al. Apr 2012 A1
20120110515 Abramoff et al. May 2012 A1
20120117621 Kondamuru et al. May 2012 A1
20120124184 Sakata et al. May 2012 A1
20120131177 Brandt et al. May 2012 A1
20120136697 Peles et al. May 2012 A1
20120142310 Pugh et al. Jun 2012 A1
20120143688 Alexander Jun 2012 A1
20120159476 Ramteke et al. Jun 2012 A1
20120166516 Simmons et al. Jun 2012 A1
20120169646 Berkes et al. Jul 2012 A1
20120173760 Jog et al. Jul 2012 A1
20120179796 Nagaraj et al. Jul 2012 A1
20120179817 Bade et al. Jul 2012 A1
20120179839 Raciborski et al. Jul 2012 A1
20120198043 Hesketh et al. Aug 2012 A1
20120198071 Black et al. Aug 2012 A1
20120204176 Tian et al. Aug 2012 A1
20120209942 Zehavi et al. Aug 2012 A1
20120224516 Stojanovski et al. Sep 2012 A1
20120226649 Kovacs et al. Sep 2012 A1
20120233329 Dickinson et al. Sep 2012 A1
20120233522 Barton et al. Sep 2012 A1
20120233668 Leafe et al. Sep 2012 A1
20120239725 Hartrick et al. Sep 2012 A1
20120246129 Rothschild et al. Sep 2012 A1
20120246257 Brown Sep 2012 A1
20120254961 Kim et al. Oct 2012 A1
20120257628 Bu et al. Oct 2012 A1
20120259954 McCarthy et al. Oct 2012 A1
20120272224 Brackman Oct 2012 A1
20120278229 Vishwanathan et al. Nov 2012 A1
20120278831 van Coppenolle et al. Nov 2012 A1
20120278833 Tam Nov 2012 A1
20120297009 Amir et al. Nov 2012 A1
20120303785 Sivasubramanian et al. Nov 2012 A1
20120303804 Sundaram et al. Nov 2012 A1
20120311648 Swildens et al. Dec 2012 A1
20120317573 Osogami et al. Dec 2012 A1
20120324089 Joshi Dec 2012 A1
20130003547 Motwani et al. Jan 2013 A1
20130003735 Chao et al. Jan 2013 A1
20130007100 Trahan et al. Jan 2013 A1
20130007101 Trahan et al. Jan 2013 A1
20130007102 Trahan et al. Jan 2013 A1
20130007241 Trahan et al. Jan 2013 A1
20130007273 Baumback et al. Jan 2013 A1
20130013764 Li et al. Jan 2013 A1
20130018945 Vendrow et al. Jan 2013 A1
20130019311 Swildens et al. Jan 2013 A1
20130034099 Hikichi et al. Feb 2013 A1
20130036307 Gagliano et al. Feb 2013 A1
20130041872 Aizman et al. Feb 2013 A1
20130042328 Padinjareveetil Feb 2013 A1
20130046869 Jenkins et al. Feb 2013 A1
20130046883 Lientz et al. Feb 2013 A1
20130054675 Jenkins et al. Feb 2013 A1
20130055374 Kustarz et al. Feb 2013 A1
20130030421 Taylor et al. Mar 2013 A1
20130061306 Sinn Mar 2013 A1
20130067530 Spektor et al. Mar 2013 A1
20130073808 Puthalath et al. Mar 2013 A1
20130080420 Taylor et al. Mar 2013 A1
20130080576 Taylor et al. Mar 2013 A1
20130080577 Taylor et al. Mar 2013 A1
20130080623 Thireault Mar 2013 A1
20130080627 Kukreja et al. Mar 2013 A1
20130080636 Friedman et al. Mar 2013 A1
20130084898 Li et al. Apr 2013 A1
20130086001 Bhogal et al. Apr 2013 A1
20130089005 Li et al. Apr 2013 A1
20130111035 Alapati et al. May 2013 A1
20130117282 Mugali, Jr. et al. May 2013 A1
20130117849 Golshan et al. May 2013 A1
20130130221 Kortemeyer et al. May 2013 A1
20130133057 Yoon et al. May 2013 A1
20130151646 Chidambaram et al. Jun 2013 A1
20130191499 Ludin et al. Jul 2013 A1
20130198341 Kim Aug 2013 A1
20130212300 Eggleston et al. Aug 2013 A1
20130219020 McCarthy et al. Aug 2013 A1
20130227165 Liu Aug 2013 A1
20130246567 Green et al. Sep 2013 A1
20130254269 Sivasubramanian et al. Sep 2013 A1
20130254879 Chesla et al. Sep 2013 A1
20130263256 Dickinson et al. Oct 2013 A1
20130268616 Sakata et al. Oct 2013 A1
20130275549 Field et al. Oct 2013 A1
20130279335 Ahmadi Oct 2013 A1
20130283266 Baset et al. Oct 2013 A1
20130305046 Mankovski et al. Nov 2013 A1
20130305083 Machida Nov 2013 A1
20130311555 Laoutaris et al. Nov 2013 A1
20130311583 Humphreys et al. Nov 2013 A1
20130311605 Richardson et al. Nov 2013 A1
20130311989 Ota et al. Nov 2013 A1
20130339429 Richardson et al. Dec 2013 A1
20130346465 Maltz et al. Dec 2013 A1
20130346470 Obstfeld et al. Dec 2013 A1
20130346567 Richardson et al. Dec 2013 A1
20130346614 Baughman et al. Dec 2013 A1
20140006465 Davis et al. Jan 2014 A1
20140006577 Joe et al. Jan 2014 A1
20140007239 Sharpe et al. Jan 2014 A1
20140013403 Shuster Jan 2014 A1
20140019605 Boberg Jan 2014 A1
20140022951 Lemieux Jan 2014 A1
20140036675 Wang et al. Feb 2014 A1
20140040478 Hsu et al. Feb 2014 A1
20140047104 Rodriguez Feb 2014 A1
20140053022 Forgette et al. Feb 2014 A1
20140059198 Richardson et al. Feb 2014 A1
20140059208 Yan et al. Feb 2014 A1
20140059379 Ren et al. Feb 2014 A1
20140082165 Marr et al. Mar 2014 A1
20140082614 Klein et al. Mar 2014 A1
20140089917 Attalla et al. Mar 2014 A1
20140108474 David et al. Apr 2014 A1
20140108672 Ou et al. Apr 2014 A1
20140119194 Raciborski et al. May 2014 A1
20140122698 Batrouni et al. May 2014 A1
20140122725 Batrouni et al. May 2014 A1
20140137111 Dees et al. May 2014 A1
20140143305 Choi et al. May 2014 A1
20140149601 Carney et al. May 2014 A1
20140164817 Bartholomy et al. Jun 2014 A1
20140165061 Greene et al. Jun 2014 A1
20140181268 Stevens et al. Jun 2014 A1
20140195686 Yeager et al. Jul 2014 A1
20140200036 Egner et al. Jul 2014 A1
20140215019 Ahrens Jul 2014 A1
20140244937 Bloomstein et al. Aug 2014 A1
20140257891 Richardson et al. Sep 2014 A1
20140258523 Kazerani et al. Sep 2014 A1
20140269371 Badea et al. Sep 2014 A1
20140279852 Chen Sep 2014 A1
20140280606 Long Sep 2014 A1
20140280679 Dey et al. Sep 2014 A1
20140297866 Ennaji et al. Oct 2014 A1
20140297870 Eggleston et al. Oct 2014 A1
20140298021 Kwon et al. Oct 2014 A1
20140310402 Giaretta et al. Oct 2014 A1
20140310811 Hentunen Oct 2014 A1
20140324774 Chen et al. Oct 2014 A1
20140325155 Marshall et al. Oct 2014 A1
20140331328 Wang et al. Nov 2014 A1
20140337472 Newton et al. Nov 2014 A1
20140351413 Smith et al. Nov 2014 A1
20140351871 Bomfim et al. Nov 2014 A1
20150006615 Wainner et al. Jan 2015 A1
20150019686 Backholm Jan 2015 A1
20150026407 Mclellan et al. Jan 2015 A1
20150067171 Yum Mar 2015 A1
20150074228 Drake Mar 2015 A1
20150081877 Sethi et al. Mar 2015 A1
20150088586 Pavlas et al. Mar 2015 A1
20150088964 Shiell et al. Mar 2015 A1
20150088972 Brand et al. Mar 2015 A1
20150089621 Khalid Mar 2015 A1
20150095516 Bergman Mar 2015 A1
20150106864 Li et al. Apr 2015 A1
20150149600 Thibeault et al. May 2015 A1
20150149631 Lissack May 2015 A1
20150154051 Kruglick Jun 2015 A1
20150156172 Nandi et al. Jun 2015 A1
20150156279 Vaswani et al. Jun 2015 A1
20150172379 Richardson et al. Jun 2015 A1
20150172407 MacCarthaigh et al. Jun 2015 A1
20150172414 Richardson et al. Jun 2015 A1
20150172415 Richardson et al. Jun 2015 A1
20150180995 Hofmann Jun 2015 A1
20150188734 Petrov Jul 2015 A1
20150189042 Sun et al. Jul 2015 A1
20150195244 Richardson et al. Jul 2015 A1
20150200991 Kwon Jul 2015 A1
20150207733 Richardson et al. Jul 2015 A1
20150215388 Kontothanassis et al. Jul 2015 A1
20150215656 Pulung et al. Jul 2015 A1
20150229710 Sivasubramanian et al. Aug 2015 A1
20150242397 Zhuang Aug 2015 A1
20150244580 Saavedra Aug 2015 A1
20150256647 Richardson et al. Sep 2015 A1
20150264009 Scharber et al. Sep 2015 A1
20150271031 Beevers Sep 2015 A1
20150288647 Chhabra et al. Oct 2015 A1
20150317118 Orikasa et al. Nov 2015 A1
20150319194 Richardson et al. Nov 2015 A1
20150319260 Watson Nov 2015 A1
20150334082 Richardson et al. Nov 2015 A1
20150339136 Suryanarayanan et al. Nov 2015 A1
20150341431 Hartrick et al. Nov 2015 A1
20150358276 Liu et al. Dec 2015 A1
20150358436 Kim et al. Dec 2015 A1
20150363113 Rahman et al. Dec 2015 A1
20150363282 Rangasamy Dec 2015 A1
20160006672 Saavedra Jan 2016 A1
20160021197 Pogrebinsky et al. Jan 2016 A1
20160026568 Marshall et al. Jan 2016 A1
20160028598 Khakpour et al. Jan 2016 A1
20160028644 Richardson et al. Jan 2016 A1
20160028755 Vasseur et al. Jan 2016 A1
20160036857 Foxhoven et al. Feb 2016 A1
20160041910 Richardson et al. Feb 2016 A1
20160065475 Hilt et al. Mar 2016 A1
20160065665 Richardson et al. Mar 2016 A1
20160072669 Saavedra Mar 2016 A1
20160072720 Richardson et al. Mar 2016 A1
20160104346 Ovalle et al. Apr 2016 A1
20160132600 Woodhead et al. May 2016 A1
20160134492 Ellsworth et al. May 2016 A1
20160142251 Contreras et al. May 2016 A1
20160164761 Sathyanarayana et al. Jun 2016 A1
20160164799 Popli et al. Jun 2016 A1
20160182454 Phonsa et al. Jun 2016 A1
20160182542 Staniford Jun 2016 A1
20160205062 Mosert Jul 2016 A1
20160241637 Marr et al. Aug 2016 A1
20160241639 Brookins et al. Aug 2016 A1
20160253262 Nadgowda Sep 2016 A1
20160255042 Newton Sep 2016 A1
20160269927 Kim et al. Sep 2016 A1
20160274929 King Sep 2016 A1
20160294678 Khakpour et al. Oct 2016 A1
20160308959 Richardson et al. Oct 2016 A1
20160337426 Shribman et al. Nov 2016 A1
20160366202 Phillips et al. Dec 2016 A1
20160373789 Tsukagoshi Dec 2016 A1
20170041428 Katsev Feb 2017 A1
20170085495 Richardson et al. Mar 2017 A1
20170099254 Leach et al. Apr 2017 A1
20170099345 Leach Apr 2017 A1
20170109316 Hack et al. Apr 2017 A1
20170126557 Richardson et al. May 2017 A1
20170126796 Hollis et al. May 2017 A1
20170142062 Richardson et al. May 2017 A1
20170153980 Araújo et al. Jun 2017 A1
20170155678 Araújo et al. Jun 2017 A1
20170155732 Araújo et al. Jun 2017 A1
20170163425 Kaliski, Jr. Jun 2017 A1
20170170973 Gill et al. Jun 2017 A1
20170171146 Sharma et al. Jun 2017 A1
20170180217 Puchala et al. Jun 2017 A1
20170180267 Puchala et al. Jun 2017 A1
20170214755 Sivasubramanian et al. Jul 2017 A1
20170214761 Hsu et al. Jul 2017 A1
20170250821 Richardson et al. Aug 2017 A1
20170353395 Richardson et al. Dec 2017 A1
20170374121 Phillips et al. Dec 2017 A1
20180011913 Kapanipathi et al. Jan 2018 A1
20180027040 Bae Jan 2018 A1
20180063027 Rafferty Mar 2018 A1
20180063193 Chandrashekhar et al. Mar 2018 A1
20180077109 Hoeme et al. Mar 2018 A1
20180077110 Huston, III et al. Mar 2018 A1
20180097631 Uppal et al. Apr 2018 A1
20180097634 Uppal et al. Apr 2018 A1
20180097831 Uppal et al. Apr 2018 A1
20180109553 Radlein et al. Apr 2018 A1
20180159757 Uppal et al. Jun 2018 A1
20180159769 Richardson et al. Jun 2018 A1
20180167444 Sivasubramanian et al. Jun 2018 A1
20180167469 Sivasubramanian et al. Jun 2018 A1
20180173526 Prinsloo et al. Jun 2018 A1
20180176615 Hannu et al. Jun 2018 A1
20180183689 Ellsworth et al. Jun 2018 A1
20180191817 Richardson et al. Jul 2018 A1
20180212880 Mostert Jul 2018 A1
20180213052 Maccarthaigh et al. Jul 2018 A1
20180278717 Richardson et al. Sep 2018 A1
20180287916 Mizik et al. Oct 2018 A1
20180302322 Richardson et al. Oct 2018 A1
20180332107 Marr et al. Nov 2018 A1
20180337885 Singh et al. Nov 2018 A1
20180351904 Mizik et al. Dec 2018 A1
20180367498 Bliss et al. Dec 2018 A1
20190007515 Baldwin et al. Jan 2019 A1
20190020562 Richardson et al. Jan 2019 A1
20190028562 Watson et al. Jan 2019 A1
20190044787 Richardson et al. Feb 2019 A1
20190044846 Howard et al. Feb 2019 A1
20190073303 Marshall et al. Mar 2019 A1
20190089542 Richardson et al. Mar 2019 A1
20190089818 Choi Mar 2019 A1
20190098109 Watson Mar 2019 A1
20190121739 Richardson et al. Apr 2019 A1
20190129908 Kumarasamy May 2019 A1
20190140922 Ellsworth et al. May 2019 A1
20190173941 Puchala et al. Jun 2019 A1
20190173972 MacCarthaigh et al. Jun 2019 A1
20190190998 Sivasubramanian et al. Jun 2019 A1
20190222666 Uppal et al. Jul 2019 A1
20190268265 Richardson et al. Jul 2019 A1
20190297137 Richardson et al. Sep 2019 A1
20190327510 Kalagi et al. Oct 2019 A1
20190354484 Marshall et al. Nov 2019 A1
20200065132 Mercier et al. Feb 2020 A1
20200084268 Hollis et al. Mar 2020 A1
20200195677 Uppal et al. Jun 2020 A1
20200195753 Richardson et al. Jun 2020 A1
20200265096 Raftery Aug 2020 A1
20200287817 Howard et al. Sep 2020 A1
20200366638 Vasquez et al. Nov 2020 A1
20200389534 Sivasubramanian et al. Dec 2020 A1
20200389541 Baldwin et al. Dec 2020 A1
20210021692 Richardson et al. Jan 2021 A1
20210042163 Radhakrishnan et al. Feb 2021 A1
Foreign Referenced Citations (47)
Number Date Country
2741 895 May 2010 CA
2765397 Feb 2011 CA
1422468 Jun 2003 CN
1511399 Jul 2004 CN
1605182 Apr 2005 CN
101189598 May 2008 CN
101431539 May 2009 CN
101460907 Jun 2009 CN
101631133 Jan 2010 CN
103731481 Apr 2014 CN
1603307 Dec 2005 EP
1351141 Oct 2007 EP
2008167 Dec 2008 EP
3156911 Apr 2017 EP
07-141305 Jun 1995 JP
2001-0506093 May 2001 JP
2001-249907 Sep 2001 JP
2002-024192 Jan 2002 JP
2002-044137 Feb 2002 JP
2002-323986 Nov 2002 JP
2003-167810 Jun 2003 JP
2003-167813 Jun 2003 JP
2003-522358 Jul 2003 JP
2003188901 Jul 2003 JP
2004-070935 Mar 2004 JP
2004-532471 Oct 2004 JP
2004-533738 Nov 2004 JP
2005-537687 Dec 2005 JP
3748216 Feb 2006 JP
2007-133896 May 2007 JP
2007-207225 Aug 2007 JP
2008-515106 May 2008 JP
2009-071538 Apr 2009 JP
2012-509623 Apr 2012 JP
2012-209623 Oct 2012 JP
WO 2001045349 Jun 2001 WO
WO 2002069608 Sep 2002 WO
WO 2005071560 Aug 2005 WO
WO 2007007960 Jan 2007 WO
WO 2007126837 Nov 2007 WO
WO 2009124006 Oct 2009 WO
WO 2010002603 Jan 2010 WO
WO 2012044587 Apr 2012 WO
WO 2012065641 May 2012 WO
WO 2014047073 Mar 2014 WO
WO 2017106455 Jun 2017 WO
WO 2018236597 Dec 2018 WO
Non-Patent Literature Citations (186)
Entry
“Non-Final Office Action dated Jan. 3, 2012,” U.S. Appl. No. 12/652,541; dated Jan. 3, 2012; 35 pages.
“Final Office Action dated Sep. 5, 2012,” U.S. Appl. No. 12/652,541; dated Sep. 5, 2012; 40 pages.
“Notice of Allowance dated Jan. 4, 2013,” U.S. Appl. No. 12/652,541; dated Jan. 4, 2013; 11 pages.
“Non-Final Office Action dated Apr. 30, 2014,” U.S. Appl. No. 13/842,970; 20 pages.
“Final Office Action dated Aug. 19, 2014,” U.S. Appl. No. 13/842,970; 13 pages.
“Notice of Allowance dated Dec. 5, 2014,” U.S. Appl. No. 13/842,970; 6 pages.
Canonical Name (CNAME) DNS Records, domainavenue.com, Feb. 1, 2001, XP055153783, Retrieved from the Internet: URL:http://www.domainavenue.com/cname.htm [retrieved on Nov. 18, 2014].
“Content delivery network”, Wikipedia, the free encyclopedia, Retrieved from the Internet: URL:http://en.wikipedia.org/w/index.php?title=Contentdelivery network&oldid=6010099 70, XP055153445, Mar. 24, 2008.
“Global Server Load Balancing with ServerIron,” Foundry Networks, retrieved Aug. 30, 2007, from http://www.foundrynet.com/pdf/an-global-server-load-bal.pdf, 7 pages.
“Grid Computing Solutions,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/grid, 3 pages.
“Grid Offerings,” Java.net, retrieved May 3, 2006, from http://wiki.java.net/bin/view/Sungrid/OtherGridOfferings, 8 pages.
“Recent Advances Boost System Virtualization,” eWeek.com, retrieved from May 3, 2006, http://www.eWeek.com/article2/0,1895,1772626,00.asp, 5 pages.
“Scaleable Trust of Next Generation Management (STRONGMAN),” retrieved May 17, 2006, from http://www.cis.upenn.edu/˜dsl/STRONGMAN/, 4 pages.
“Sun EDA Compute Ranch,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://sun.com/processors/ranch/brochure.pdf, 2 pages.
“Sun Microsystems Accelerates UltraSP ARC Processor Design Program With New Burlington, Mass. Compute Ranch,” Nov. 6, 2002, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2002-11/sunflash.20021106.3 .xml, 2 pages.
“Sun N1 Grid Engine 6,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/gridware/index.xml, 3 pages.
“Sun Opens New Processor Design Compute Ranch,” Nov. 30, 2001, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2001-11/sunflash.20011130.1.xml, 3 pages.
“The Softricity Desktop,” Softricity, Inc., retrieved May 3, 2006, from http://www.softricity.com/products/, 3 pages.
“Xen—The Xen virtual Machine Monitor,” University of Cambridge Computer Laboratory, retrieved Nov. 8, 2005, from http://www.cl.cam.ac.uk/Research/SRG/netos/xen/, 2 pages.
“XenFaq,” retrieved Nov. 8, 2005, from http://wiki.xensource.com/xenwiki/XenFag?action=print, 9 pages.
Abi, Issam, et al., “A Business Driven Management Framework for Utility Computing Environments,” Oct. 12, 2004, HP Laboratories Bristol, HPL-2004-171, retrieved Aug. 30, 2007, from http://www.hpl.hp.com/techreports/2004/HPL-2004-171.pdf, 14 pages.
American Bar Association; Digital Signature Guidelines Tutorial [online]; Feb. 10, 2002 [retrieved on Mar. 2, 2010]; American Bar Association Section of Science and Technology Information Security Committee; Retrieved from the internet: (URL: http://web.archive.org/web/20020210124615/www.abanet.org/scitech/ec/isc/dsg-tutorial.html; pp. 1-8.
Armour et al.: “A Heuristic Algorithm and Simulation Approach to Relative Location of Facilities”; Management Science, vol. 9, No. 2 (Jan. 1963); pp. 294-309.
Baglioni et al., “Preprocessing and Mining Web Log Data for Web Personalization”, LNAI 2829, 2003, pp. 237-249.
Barbir, A., et al., “Known Content Network (CN) Request-Routing Mechanisms”, Request for Comments 3568, [online], IETF, Jul. 2003, [retrieved on Feb. 26, 2013], Retrieved from the Internet: (URL: http://tools.ietf.org/rfc/rfc3568.txt).
Bellovin, S., “Distributed Firewalls,”;login;:37-39, Nov. 1999, http://www.cs.columbia.edu/-smb/papers/distfw. html 10 pages, retrieved Nov. 11 2005.
Blaze, M., “Using the KeyNote Trust Management System,” Mar. 1, 2001, from http://www.crypto.com/trustmgt/kn.html, 4 pages, retrieved May 17, 2006.
Brenton, C., “What is Egress Filtering and How Can I Implement It?—Egress Filtering v 0.2,” Feb. 29, 2000, SANS Institute, http://www.sans.org/infosecFAQ/firewall/egress.htm, 6 pages.
Byun et al., “A Dynamic Grid Services Deployment Mechanism for On-Demand Resource Provisioning”, IEEE International Symposium on Cluster Computing and the Grid:863-870, 2005.
Chipara et al, “Realtime Power-Aware Routing in Sensor Network”, IEEE, 2006, 10 pages.
Clark, C., “Live Migration of Virtual Machines,” May 2005, NSDI '05: 2nd Symposium on Networked Systems Design and Implementation, Boston, MA, May 2-4, 2005, retrieved from http://www.usenix.org/events/nsdi05/tech/full_papers/clark/clark.pdf, 14 pages.
Coulson, D., “Network Security Iptables,” Apr. 2003, Linuxpro, Part 2, retrieved from http://davidcoulson.net/writing/lxf/38/iptables.pdf, 4 pages.
Coulson, D., “Network Security Iptables,” Mar. 2003, Linuxpro, Part 1, retrieved from http://davidcoulson.net/writing/lxf/39/Iptables.pdf, 4 pages.
Deleuze, C., et al., A DNS Based Mapping Peering System for Peering CDNs, draft-deleuze-cdnp-dnsmap-peer-00.txt, Nov. 20, 2000, 20 pages.
Demers, A., “Epidemic Algorithms for Replicated Database Maintenance,” 1987; Proceedings of the sixth annual ACM Symposium on Principles of Distributed Computing, Vancouver, British Columbia, Canada, Aug. 10-12, 1987, 12 pages.
Gruener, J., “A Vision of Togetherness,” May 24,2004, NetworkWorld, retrieved May 3, 2006, from, http://www.networkworld.com/supp/2004/ndc3/0524virt.html, 9 pages.
Gunther et al, “Measuring Round Trip Times to determine the Distance between WLAN Nodes”,May 2005, In Proc. of Networking 2005, all pages.
Gunther et al, “Measuring Round Trip Times to determine the Distance between WLAN Nodes”, Dec. 18, 2004, Technical University Berlin, all pages.
Guo, F., Understanding Memory Resource Management in Vmware vSphere 5.0, Vmware, 2011, pp. 1-29.
Hameed, CC, “Disk Fragmentation and System Performance”, Mar. 14, 2008, 3 pages.
Hartung et al.; Digital rights management and watermarking of multimedia content for m-commerce applications; Published in: Communications Magazine, IEEE (vol. 38, Issue; 11 ); Date of Publication: Nov. 2000; pp. 78-84; IEEE Xplore.
Horvath et al., “Enhancing Energy Efficiency in Multi-tier Web Server Clusters via Prioritization,” in Parallel and Distributed Processing Symposium, 2007. IPDPS 2007. IEEE International , vol., No., pp. 1-6, Mar. 26-30, 2007.
Ioannidis, S., et al., “Implementing a Distributed Firewall,” Nov. 2000, (ACM) Proceedings of the ACM Computer and Communications Security (CCS) 2000, Athens, Greece, pp. 190-199, retrieved from http://www.cis.upenn.edu/˜dls/STRONGMAN/Papers/df.pdf, 10 pages.
Joseph, Joshy, et al., “Introduction to Grid Computing,” Apr. 16, 2004, retrieved Aug. 30, 2007, from http://www.informit.com/articles/printerfriendly.aspx?p=169508, 19 pages.
Kalafut et al., Understanding Implications of DNS Zone Provisioning., Proceeding IMC '08 Proceedings of the 8th AMC SIGCOMM conference on Internet measurement., pp. 211-216., ACM New York, NY, USA., 2008.
Kato, Yoshinobu , Server load balancer—Difference in distribution technique and supported protocol—Focus on function to meet the needs, Nikkei Communications, Japan, Nikkei Business Publications, Inc., Mar. 20, 2000, vol. 314, pp. 114 to 123.
Kenshi, P., “Help File Library: Iptables Basics,” Justlinux, retrieved Dec. 1, 2005, from http://www.justlinux.com/nhf/Security/Iptables _ Basics.html, 4 pages.
Liu, “The Ultimate Guide to Preventing DNS-based DDoS Attacks”, Retrieved from http://www.infoworld.com/article/2612835/security/the-ultimate-guide-to-preventing-dns-based-ddos-attacks.html, Published Oct. 30, 2013.
Liu et al., “Combined mining of Web server logs and web contents for classifying user navigation patterns and predicting users' future requests,” Data & Knowledge Engineering 61 (2007) pp. 304-330.
Maesono, et al., “A Local Scheduling Method considering Data Transfer in Data Grid,” Technical Report of IEICE, vol. 104, No. 692, pp. 435-440, The Institute of Electronics, Information and Communication Engineers, Japan, Feb. 2005.
Meng et al., “Improving the Scalability of Data Center Networks with Traffic-Aware Virtual Machine Placement”; Proceedings of the 29th Conference on Information Communications, INFOCOM'10, pp. 1154-1162. Piscataway, NJ. IEEE Press, 2010.
Mulligan et al.; How DRM-based content delivery systems disrupt expectations of “personal use”; Published in: Proceeding DRM '03 Proceedings of the 3rd ACM workshop on Digital rights management; 2003; pp. 77-89; ACM Digital Library.
Ragan, “Three Types of DNS Attacks and How to Deal with Them”, Retrieved from http://www.csoonline.com/article/2133916/malware-cybercrime/three-types-of-dns-attacks-and-how-to-deal-with-them.html, Published Aug. 28, 2013.
Shankland, S., “Sun to buy start-up to bolster N1 ,” Jul. 30, 2003, CNet News.com, retrieved May 3, 2006, http://news.zdnet.com/2100-3513_22-5057752.html, 8 pages.
Sharif et al, “Secure In-VM Monitoring Using Hardware Virtualization”, Microsoft, Oct. 2009 http://research.microsoft.com/pubs/153179/sim-ccs09.pdf; 11 pages.
Strand, L., “Adaptive distributed firewall using intrusion detection,” Nov. 1, 2004, University of Oslo Department of Informatics, retrieved Mar. 8, 2006, from http://gnist.org/˜lars/studies/master/StrandLars-master.pdf, 158 pages.
Takizawa, et al., “Scalable MultiReplication Framework on The Grid” Report of Study of Information Processing Society of Japan, Information Processing Society, vol. 2004, No. 81, pp. 247-252, Japan, Aug. 1, 2004.
Tan et al., “Classification: Basic Concepts, Decision Tree, and Model Evaluation”, Introduction in Data Mining; http://www-users.cs.umn.edu/˜kumar/dmbook/ch4.pdf, 2005, pp. 245-205.
Van Renesse, R., “Astrolabe: A Robust and Scalable Technology for Distributed System Monitoring, Management, and Data Mining,” May 2003, ACM Transactions on Computer Systems (TOCS), 21 (2): 164-206, 43 pages.
Vijayan, J., “Terraspring Gives Sun's N1 a Boost,” Nov. 25, 2002, Computerworld, retrieved May 3, 2006, from http://www.computerworld.com/printthis/2002/0,4814, 76159,00.html, 3 pages.
Virtual Iron Software Home, Virtual Iron, retrieved May 3, 2006, from http://www.virtualiron.com/, 1 page.
Waldspurger, CA., “Spawn: A Distributed Computational Economy,” Feb. 1992, IEEE Transactions on Software Engineering, 18(2): 103-117, 15 pages.
Watanabe, et al., “Remote Program Shipping System for GridRPC Systems,” Report of Study of Information Processing Society of Japan, Information Processing Society, vol. 2003, No. 102, pp. 73-78, Japan, Oct. 16, 2003.
Xu et al., “Decision tree regression for soft classification of remote sensing data”, Remote Sensing of Environment 97 (2005) pp. 322-336.
Yamagata, et al., “A virtual-machine based fast deployment tool for Grid execution environment, ” Report of Study of Information Processing Society of japan, Information Processing Society, vol. 2006, No. 20, pp. 127-132, Japan, Feb. 28, 2006.
Zhu, Xiaoyun, et al., “Utility-Driven Workload Management Using Nested Control Design,” Mar. 29, 2006, HP Laboratories Palo Alto, HPL-2005-193(R.1), retrieved Aug. 30, 2007, from http://www.hpl.hp.com/techreports/2005/HPL-2005-193R1.pdf, 9 pages.
Supplementary European Search Report in Application No. 09729072.0 2266064 dated Dec. 10, 2014.
First Singapore Written Opinion in Application No. 201006836-9, dated Oct. 12, 2011 in 12 pages.
Singapore Written Opinion in Application No. 201006836-9, dated Apr. 30, 2012 in 10 pages.
First Office Action in Chinese Application No. 200980111422.3 dated Apr. 13, 2012.
First Office Action in Japanese Application No. 2011-502138 dated Feb. 1, 2013.
Singapore Written Opinion in Application No. 201006837-7, dated Oct. 12, 2011 in 11 pages.
Supplementary European Search Report in Application No. 09727694.3 dated Jan. 30, 2012 in 6 pages.
Singapore Examination Report in Application No. 201006837-7 dated Mar. 16, 2012.
First Office Action in Chinese Application No. 200980111426.1 dated Feb. 16, 2013.
Second Office Action in Chinese Application No. 200980111426.1 dated Dec. 25, 2013.
Third Office Action in Chinese Application No. 200980111426.1 dated Jul. 7, 2014.
Fourth Office Action in Chinese Application No. 200980111426.1 dated Jan. 15, 2015.
Fifth Office Action in Chinese Application No. 200980111426.1 dated Aug. 14, 2015.
First Office Action in Japanese Application No. 2011-502139 dated Nov. 5, 2013.
Decision of Rejection in Application No. 2011-502139 dated Jun. 30, 2014.
Office Action in Japanese Application No. 2011-502139 dated Aug. 17, 2015.
Singapore Written Opinion in Application No. 201006874-0, dated Oct. 12, 2011 in 10 pages.
First Office Action in Japanese Application No. 2011-502140 dated Dec. 7, 2012.
First Office Action in Chinese Application No. 200980119995.0 dated Jul. 6, 2012.
Second Office Action in Chinese Application No. 200980119995.0 dated Apr. 15, 2013.
Examination Report in Singapore Application No. 201006874-0 dated May 16, 2012.
Search Report in European Application No. 09839809.2 dated May 11, 2015.
Office Action in European Application No. 09839809.2 dated Dec. 8, 2016.
Supplementary European Search Report in Application No. 09728756.9 dated Jan. 8, 2013.
First Office Action in Chinese Application No, 200980119993.1 dated Jul. 4, 2012.
Second Office Action in Chinese Application No. 200980119993.1 dated Mar. 12, 2013.
Third Office Action in Chinese Application No. 200980119993.1 dated Oct. 21, 2013.
First Office Action in Japanese Application No. 2011-503091 dated Nov. 18, 2013.
Office Action in Japanese Application No. 2014-225580 dated Oct. 26, 2015.
Office Action in Japanese Application No. 2014-225580 dated Oct. 3, 2016.
Search Report and Written Opinion issued in Singapore Application No. 201006873-2 dated Oct. 12, 2011.
First Office Action is Chinese Application No. 200980125551.8 dated Jul. 4, 2012.
First Office Action in Japanese Application No. 2011-516466 dated Mar. 6, 2013.
Second Office Action in Japanese Application No. 2011-516466 dated Mar. 17, 2014.
Decision of Refusal in Japanese Application No. 2011-516466 dated Jan. 16, 2015.
Office Action in Japanese Application No. 2011-516466 dated May 30, 2016.
Office Action in Canadian Application No. 2726915 dated May 13, 2013.
First Office Action in Korean Application No. 10-2011-7002461 dated May 29, 2013.
First Office Action in Chinese Application No. 200980145872.4 dated Nov. 29, 2012.
First Office Action in Canadian Application No. 2741895 dated Feb. 25, 2013.
Second Office Action in Canadian Application No. 2741895 dated Oct. 21, 2013.
Partial Supplementary Search Report in European Application No. 09826977.2 dated Oct. 4, 2016.
Search Report and Written Opinion in Singapore Application No. 201103333-9 dated Nov. 19, 2012.
Examination Report in Singapore Application No. 201103333-9 dated Aug. 13, 2013.
Office Action in Chinese Application No. 201310717573.1 dated Jul. 29, 2016.
Office Action in European Application No. 11767118.0 dated Feb. 3, 2017.
International Search Report and Written Opinion in PCT/US2011/053302 dated Nov. 28, 2011 in 11 pages.
International Preliminary Report on Patentability in PCT/US2011/053302 dated Apr. 2, 2013.
First Office Action in Japanese Application No. 2013-529454 dated Feb. 3, 2014 in 6 pages.
Office Action in Japanese Application No. 2013-529454 dated Mar. 9, 2015 in 8 pages.
First Office Action issued in Australian Application No. 2011307319 dated Mar. 6, 2014 in 5 pages.
Search Report and Written Opinion in Singapore Application No. 201301573-0 dated Jul. 1, 2014.
First Office Action in Chinese Application No. 201180046104.0 dated Nov. 3, 2014.
Second Office Action in Chinese Application No. 201180046104.0 dated Sep. 29, 2015.
Third Office Action in Chinese Application No. 201180046104.0 dated Apr. 14, 2016.
Decision of Rejection in Chinese Application No. 201180046104.0 dated Oct. 17, 2016.
Examination Report in Singapore Application No. 201301573-0 dated Dec. 22, 2014.
International Preliminary Report on Patentability in PCT/US2011/061486 dated May 22, 2013.
International Search Report and Written Opinion in PCT/US2011/061486 dated Mar. 30, 2012 in 11 pages.
Office Action in Canadian Application No. 2816612 dated Nov. 3, 2015.
Office Action in Canadian Application No. 2816612 dated Oct. 7, 2016.
First Office Action in Chinese Application No. 201180053405.6 dated Feb. 10, 2015.
Second Office Action in Chinese Application No. 201180053405.6 dated Dec. 4, 2015.
Office Action in Japanese Application No. 2013-540982 dated Jun. 2, 2014.
Written Opinion in Singapore Application No. 201303521-7 dated May 20, 2014.
Office Action in Japanese Application No. 2015-533132 dated Apr. 25, 2016.
Office Action in Canadian Application No. 2884796 dated Apr. 28, 2016.
Office Action in Russian Application No. 2015114568 dated May 16, 2016.
International Search Report and Written Opinion in PCT/US07/07601 dated Jul. 18, 2008 in 11 pages.
International Preliminary Report on Patentability in PCT/US2007/007601 dated Sep. 30, 2008 in 8 pages.
Supplementary European Search Report in Application No. 07754164.7 dated Dec. 20, 2010 in 7 pages.
Office Action in Chinese Application No. 200780020255.2 dated Mar. 4, 2013.
Office Action in Indian Application No. 3742/KOLNP/2008 dated Nov. 22, 2013.
Office Action in Japanese Application No. 2012-052264 dated Dec. 11, 2012 in 26 pages.
Office Action in Japanese Application No. 2013-123086 dated Apr. 15, 2014 in 3 pages.
Office Action in Japanese Application No. 2013-123086 dated Dec. 2, 2014 in 4 pages.
Office Action in Japanese Application No. 2015-075644 dated Apr. 5, 2016.
Office Action in European Application No. 07754164.7 dated Dec. 14, 2015.
Office Action in Chinese Application No. 201310537815.9 dated Jul. 5, 2016.
International Search Report and Written Opinion in PCT/US/2016/066848 dated May 1, 2017.
Supplementary Examination Report in Singapore Application No. 11201501987U dated May 17, 2017.
Office Action in Chinese Application No. 201310537815.9 dated Jun. 2, 2017.
Office Action in Canadian Application No. 2816612 dated Aug. 8, 2017.
Krsul et al., “VMPlants: Providing and Managing Virtual Machine Execution Environments for Grid Computing”, Nov. 6, 2004 (Nov. 6, 2004), Supercomputing, 2004. Proceedings of the ACM/IEEE SC2004 Conference Pittsburgh, PA, USA Nov. 6-12, 2004, Piscataway, NJ, USA, IEEE, 1730 Massachusetts Ave., NW Washington, DC 20036-1992 USA, 12 pages.
Zhao et al., “Distributed file system support for virtual machines in grid computing”, Jun. 4, 2004 (Jun. 4, 2004), High Performance Distributed Computing, 2004. Proceedings. 13th IEEE International Symposium on Honolulu, HI, USA Jun. 4-6, 2004, Piscataway, NJ, USA, IEEE, p. 202-211.
Office Action in Indian Application No. 5937/CHENP/2010 dated Jan. 19, 2018.
Office Action in Chinese Application No. 201310537815.9 dated Feb. 1, 2018.
Office Action in European Application No. 07754164.7 dated Jan. 25, 2018.
International Search Report and Written Opinion in PCT/US2017/055156 dated Dec. 13, 2017.
Office Action in Application No. 09729072.0 dated May 14, 2018.
Office Action in Indian Application No. 6210/CHENP/2010 dated Mar. 27, 2018.
Examination Report in Indian Application No. 6213/CHENP/2010 dated May 23, 2018.
International Preliminary Report on Patentability in PCT/US/2016/066848 dated Jun. 19, 2018.
Cohen et al., “Proactive Caching of DNS Records: Addressing a Performance Bottleneck”, Proceedings of Saint 2001 Symposium on Applications and the Internet; 8-12, Jan. 8, 2001, IEEE Computer Society, pp. 85-94.
JH Software, Moving a DNS Server to a New IP Address, last updated Jan. 26, 2006, 1 page.
Office Action in European Application No. 11767118.0 dated Jul. 25, 2018.
Extended Search Report in European Application No. 18156163 dated Sep. 3, 2018.
Office Action in Chinese Application No. 2013800492635 dated Aug. 30, 2017.
Arends et al., DNS Security Introduction and Requirements, RFC 4033, Mar. 2005, 21 pages.
Ariyapperuma et al., “Security Vulnerabilities in DNS and DNSSEC.” The Second International Conference on Availability, Reliability and Security, IEEE, 2007, 8 pages.
Chandramouli et al., “Challenges in Securing the Domain Name System.” IEEE Security & Privacy4.1 (2006),pp. 84-87.
Eastlake, Donald, Domain Name System Security Extensions, RFC 2535, Mar. 1999, 47 pages.
Office Action in Application No. 09729072.0 dated Dec. 7, 2018.
Office Action in European Application No. 11767118.0 dated Jan. 29, 2019.
Examination Report in Indian Application No. 3105/DELNP/2013, dated Feb. 19, 2019.
Examination Report in Indian Application No. 4487/DELNP/2013 dated Dec. 28, 2018.
Office Action in European Application No. 13770602.4 dated Mar. 11, 2019.
International Preliminary Report on Patentability and Written Opinion in PCT/US2017/055156 dated Apr. 9, 2019.
Frangoudis et al., “PTPv2-based network load estimation and its application to QoE monitoring for Over-the-Top services”, IEEE, The 5th International conference on Information, Intelligence, Systems and Applications, IISA 2014, XP032629858, Jul. 7, 2014, pp. 176-181.
Partial Search Report in European Application No. 16876655.8 dated May 15, 2019.
International Search Report and Written Opinion in PCT/US2018/036634 dated Sep. 11, 2018.
Extended Search Report in European Applicaton No. 19184826.6 dated Jan. 17, 2020.
International Preliminary Report on Patentability and Written Opinion in PCT/US2018/036634 dated Dec. 24, 2019.
Office Action in Brazilian Application No. BR112015005588-5 dated Jan. 14, 2020.
Zaman et al., “Combinatorial Auction-Based Dynamic VM Provisioning and Allocation in Clouds”, Department of Computer Science, Wayne State University, Sep. 2011 http://www.cs.wayne.edu/-dgrosu/pub/ccgrid12-symp.pdf.
Office Action in Indian Application No. 2823/DELNP/2015 dated Oct. 25, 2019.
Extended European Search Report in Application No. 16876655.8 dated Aug. 20, 2019.
Office Action in Chinese Application No. 201810426428.0 dated Jul. 20, 2020 in 25 pages.
Second Office Action in Chinese Application No. 201610828846.3 dated Aug. 5, 2020.
Office Action issued in connection with European Patent Application No. 18734734 dated Oct. 19, 2020.
Related Publications (1)
Number Date Country
20170257340 A1 Sep 2017 US
Continuations (1)
Number Date Country
Parent 12892777 Sep 2010 US
Child 15604451 US