PATENT CLAIM ANALYSIS

Application Number: 15947913
Application Type: Utility
Filing Date: 2018-04
Publication Date: 2018-10
Patent Classification: ["709", "203000"]

Abstract:
Described herein are improved systems, methods, and devices for delivering and managing metadata in a distributed computing platform such as a content delivery network (CDN) so as to configure content servers to handle client requests. The teachings hereof provide, among other things, scalable and configurable solutions for delivering and managing metadata, preferably by leveraging dynamically obtained control information. For example, in one embodiment, a given content server may store metadata, e.g., in a configuration file, that references dynamic, late-bound control information for use in satisfying dependencies. This dynamic control information can be requested by the CDN content server, typically from a remote host, when needed to parse and execute the metadata.

Claim (Index 21):
A system, comprising:\n a first server managed by a content delivery network (CDN) service provider and comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the first server to:\n receive a first request from a client device over a network interface, the first request comprising an application programming interface (API) request; \n in response to the first request, determine a configuration file stored at the first server to apply for handling the request; \n identify, within the configuration file, a control that indicates how to handle the first request from within a set of controls stored at the first server in the configuration file; \n wherein the control has a reference to an API endpoint policy that controls, at least, client authentication; \n extract an identifier from the first request received from the client; \n in response to the identification of the control with the reference to the API endpoint policy, send a second request that includes the extracted identifier to a remote host for the API endpoint policy; \n receive the API endpoint policy from the remote host in response to the second request, the API endpoint policy comprising any of data and a routine, for authenticating any of the client device, client user, and client application; \n apply the control to the request at least by applying the API endpoint policy to determine whether any of the client device, client user, and client application, is authenticated; \n based at least in part on applying the control and the API endpoint policy and successfully authenticating any of the client device, client user, and client application, send at least a portion of the first request to a second server, the second server being an API origin for the API; \n the remote host comprising circuitry forming one or more processors coupled to memory holding non-transitory computer-program instructions to be executed by the one or more processors to cause the remote host to:\n receive the second request from the first server, with the extracted identifier; \n based at least in part on the extracted identifier, select the API endpoint policy from amongst a plurality of API endpoint policies stored at the remote host; \n send the API endpoint policy to the first server, in response to the second request; \n wherein the first server is one of a plurality of distributed CDN servers, the first request is for a service accessible via the API, and the service enables any of: (i) interaction with a multi-tenant storage system operated by the CDN service provider on behalf of content providers, (ii) interaction with a multi-tenant computing system operated by the CDN service provider on behalf of content providers, and (iii) configuration by a CDN user of a CDN content delivery service, said configuration comprising configuration of CDN features and services for delivering any of a website and a web application on the CDN user's behalf over the CDN.

Metadata:
- Claim Count in Document: 50.0
- Percentile: 91.0
- Lexical Diversity: 1.58537
- Patent Class: 709.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['15341850', '14135179', '14135158', '14135172', '15473279']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.2982430927982896
- 35 USC 102 Novelty (BERT): 0.5758276519450769
- Combined Prediction Score: 0.3260015487129684
- Mean Citation Score: 406.116906
- Max Citation Score: 458.75427
- Similarity Product: 454.2569118087495

Labels:
- Claim Label 101: 1
- Claim Label 102: 1
- Claim Label 103: 1
- Claim Label 112: 1
- Combined Label: 1
- Label 101 Adjusted: 1

Dataset: test