CA-3002025-C - CONTENT MANAGEMENT ON REMOTE DISPLAYS USING URL REWRITING

Abstract

Technologies are disclosed herein for providing content management for deploying and updating a fleet of resources. A system for providing content management may include a web server or other apparatus configured to receive a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device. The web server may be further configured to analyze the local content request to determine if the URL matches one or more rewrite rules, formulate a response to the local content request based on the analyzing, and transmit the formulated response

Inventors

• Andrew JARNAGIN

Assignees

• THE COCA-COLA COMPANY

Dates

Publication Date

20260505

Application Date

20161014

Priority Date

20151016

Claims (17)

1. CLAIMS WHAT IS CLAIMED IS: 1. A non-transitory computer-readable storage medium having computerexecutable instructions stored thereupon which, when executed by a server computer, cause the server computer to: receive a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyze the local content request to determine if the canonical URL matches a rewrite rule; rewrite the canonical URL based on the rewrite rule to point to desired content in a content store at the server computer as specified in a mapping database; and upon determining the appropriate rewriting for the URL, respond to the local content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request.
2. 2. The non-transitory computer-readable storage medium of claim 1, wherein the computer executable instructions, when executed by the server computer, further cause the server computer to: receive a further local content request from the local device for at least one of the set of resources identified in the manifest; and respond to the further local content request with the at least one of the set of resources.
3. 3. The non-transitory computer-readable storage medium of claim 2, wherein the computer executable instructions, when executed by the server computer, further cause the server computer to: write the rewrite rule, using an application programming interface (API), as a configuration file in the server computer, wherein the API writes the rewrite rule to rewrite the canonical URL to point to the the desired content for the local device as specified in the mapping database. 21
4. 4. The non-transitory computer-readable storage medium of claim 3, wherein the computer executable instructions, when executed by the server computer, further cause the server computer to: manipulate, using the API, the mapping database based on a content change request from a console device, wherein the mapping database maps the canonical URL to the desired content.
5. 5. The non-transitory computer-readable storage medium of claim 4, wherein the computer executable instructions, when executed by the server computer, further cause the server computer to: create a rule change in response to the content change request from a console device; and write a changed rewrite rule, using the API, as the configuration file in the server computer based on the rule change.
6. 6. The non-transitory computer-readable storage medium of claim 5, wherein the changed rewrite rule rewrites the canonical URL to point to desired content for the local device.
7. 7. The non-transitory computer-readable storage medium of claim 6, wherein more than one canonical URL is mapped to the manifest in the mapping database.
8. 8. The non-transitory computer-readable storage medium of claim 7, wherein the computer executable instructions, when executed by the server computer, further cause the server computer to: receive a further local content request from the local device for at least one of a second set of resources identified in the manifest, wherein the at least one of the second set of resources comprises new content to be displayed on the local device; and respond to the further local content request with the at least one of the second set of resources.
9. 9. An apparatus comprising: a processor; and 22 memory having instructions stored thereon that, when executed by the processor, cause the apparatus to: receive a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyze the local content request to determine if the canonical URL matches a rewrite rule; rewrite the canonical URL based on the rewrite rule to point to desired content in a content store at a server computer as specified in a mapping database; and upon determining the appropriate rewriting for the URL, respond to the local content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request.
10. 10. The apparatus of claim 9, wherein the instructions further cause the apparatus to: receive a further local content request from the local device for at least one of the set of resources identified in the manifest; and respond to the further local content request with the at least one of the set of resources.
11. 11. The apparatus of claim 10, wherein the instructions further cause the apparatus to: write the rewrite rule, using an application programming interface (API), as a configuration file in the server computer, wherein the API writes the rewrite rule to rewrite the canonical URL to point to the desired content for the local device as specified in the mapping database.
12. 12. The apparatus of claim 11, wherein the instructions further cause the apparatus to: manipulate, using the API, the mapping database based on a content change 23 request from a console device, wherein the mapping database maps the canonical URL to the desired content.
13. 13. The apparatus of claim 12, wherein the instructions further cause the apparatus to: create a rule change in response to the content change request from a console device; and write a changed rewrite rule, using the API, as the configuration file in the server computer based on the rule change.
14. 14. The apparatus of claim 13, wherein the changed rewrite rule rewrites the canonical URL to point to desired content for the local device.
15. 15. The apparatus of claim 14, wherein more than one canonical URL is mapped to the manifest in the mapping database.
16. 16. The apparatus of claim 15, wherein the instructions further cause the apparatus to: receive a further local content request from the local device for at least one of a second set of resources identified in the manifest, wherein the at least one of the second set of resources comprises new content to be displayed on the local device; and respond to the further local content request with the at least one of the second set of resources.
17. 17. A method comprising: receiving a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyzing the local content request to determine if the canonical URL matches a rewrite rule; rewriting the canonical URL based on the rewrite rule to point to desired content in a content store at a server computer as specified in a mapping database; and 24 upon determining the appropriate rewriting for the URL, responding to the local content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request.

Description

1 CONTENT MANAGEMENT ON REMOTE DISPLAYS USING URL REWRITING [0001] COCA-COLA® is a registered trademark of The Coca-Cola Company, Atlanta, Ga., U.S.A. Other names, symbols, designs, or logos used herein may be registered trademarks, trademarks, or product names of The Coca-Cola Company or other companies. FIELD OF THE INVENTION [0002] This invention relates to digital displays and human-machine interfaces, and in particular, relates to systems and methods for providing content management across a fleet of digital displays, human-machine interfaces, and other graphical displays and devices. BACKGROUND [0003] Generally, digital content can be distributed across a fleet of digital displays, humanmachine interfaces, and other graphical displays and devices. The digital content may be generated and stored at each device during an install or repair procedure. For example, new or updated digital content may be transferred to an associated device via a computer-readable storage medium, such as a universal serial bus (USB) mass storage device. It follows that as a size of the fleet of devices increases, the cost and effort associated with updating the content increases dramatically. Furthermore, a total update time for managing content across the fleet of devices may increase difficulty in coordinating content changes in a timely manner, or with regard to a desired rollout period or targeted time for coordinated content updates. [0004] The disclosure made herein is presented with respect to these and other considerations. SUMMARY OF THE INVENTION [0004a] According to an aspect of the invention is a non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by a server computer, cause the server computer to: receive a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyze the local content request to determine if the canonical URL matches a rewrite rule; 1a rewrite the canonical URL based on the rewrite rule to point to desired content in a content store at the server computer as specified in a mapping database; and upon determining the appropriate rewriting for the URL, respond to the local content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request. [0004b] According to a further aspect is an apparatus comprising: a processor; and memory having instructions stored thereon that, when executed by the processor, cause the apparatus to: receive a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyze the local content request to determine if the canonical URL matches a rewrite rule; rewrite the canonical URL based on the rewrite rule to point to desired content in a content store at a server computer as specified in a mapping database; and upon determining the appropriate rewriting for the URL, respond to the local content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request. [0004c] According to a further aspect is a method comprising: receiving a local content request from a local device of a fleet of resources, the local content request comprising a canonical uniform resource locator (URL) that uniquely identifies the local device; analyzing the local content request to determine if the canonical URL matches a rewrite rule; rewriting the canonical URL based on the rewrite rule to point to desired content in a content store at a server computer as specified in a mapping database; and upon determining the appropriate rewriting for the URL, responding to the local 1b content request with a manifest for the URL, wherein the manifest identifies the desired content as a set of resources to be displayed on the local device; and wherein the local content request is periodic and includes a manifest request. BRIEF DESCRIPTION OF THE DRAWINGS [0005] FIG. 1 is a system architecture diagram showing aspects of the configuration and operation of a system for content management, in one configuration presented herein; [0006] FIG. 2 is a flow diagram illustrating aspects of the operation of a server instance, in one configuration disclosed herein; WO 2017/066503 PCT/US2016/0:'i6934 [0007] FIG. 3 is a flow diagram illustrating aspects of the operation of a local device, in one configuration disclosed herein; [0008] FIG. 4 is a diagram illustrating aspects of the operation of a server computer or other computing device, in one configuration