US 11,968,084 B2
Subscriber configuration ingestion in a content delivery network
Laurence Lipstone, Calabasas, CA (US); Christopher Newton, Westlake Village, CA (US); William Crowder, Camarillo, CA (US); Vikas Dogra, Westlake Village, CA (US); and Kevin Johns, Erie, CO (US)
Assigned to Level 3 Communications, LLC, Broomfield, CO (US)
Filed by Level 3 Communications, LLC, Broomfield, CO (US)
Filed on Mar. 3, 2023, as Appl. No. 18/117,164.
Application 18/117,164 is a continuation of application No. 15/961,686, filed on Apr. 24, 2018, abandoned.
Prior Publication US 2023/0208711 A1, Jun. 29, 2023
Int. Cl. H04L 41/0813 (2022.01); H04L 67/10 (2022.01)
CPC H04L 41/0813 (2013.01) [H04L 67/10 (2013.01)] 14 Claims
OG exemplary drawing
 
1. A computer-implemented method operable on at least one device in a content delivery network (CDN), wherein the CDN distributes content on behalf of one or more subscribers, the method comprising:
receiving configuration information from a particular subscriber of the one or more subscribers, the configuration information relating to at least one property of the particular subscriber, wherein the particular subscriber is a content provider;
in response to the receiving, generating subscriber-specific platform configuration information for the at least one property of the particular subscriber;
storing the subscriber-specific platform configuration information in platform configuration storage;
receiving, by at least one CDN component, a request for the at least one property of the particular subscriber, wherein the at least one CDN component comprises a delivery server;
receiving, by the delivery server, the subscriber-specific platform configuration information, wherein the subscriber-specific platform configuration information includes at least a first match rule group, containing at least a first match rule having a first match rule identifier (ID) and a second match rule have a second match rule ID, and a second match rule group, containing at least a third match rule having a third match rule ID and a fourth match rule having a fourth match rule ID;
processing the subscriber-specific platform configuration information by processing the first match rule group until a first match is found for the first match rule and then jumping to the third match rule of the second match rule group and processing the second match rule group until a second match is found; and
causing the at least one property of the particular subscriber to be delivered according to the processed subscriber-specific platform configuration information, wherein the first match rule and the third match rule both reference at least a first match set identifier,
wherein a first match set corresponding to the first match set identifier comprises at least a fifth match rule and a sixth match rule,
wherein the subscriber-specific platform configuration information further includes a first map of the configuration data,
wherein the first map of the configuration data includes a map name and at least one value equal to the match set identifier, and
wherein the processing further includes processing a first map function call to the map name and a key value identifying the at least one property.