Patent Application
20220351250
Television networks, such as the American Broadcasting Company (ABC), the Columbia Broadcasting Company (CBS), and the National Broadcasting Company (NBC), have for years broadcast television shows to the masses as a means for generating revenue through advertising. For example, these networks produce television shows and then seek out sponsors to advertise on the shows. The television shows, or “content”, have designated timeslots in which the sponsors' advertisements, or “assets”, are inserted. The content and the inserted assets are then broadcast by the television networks, or “content providers”, to the public over federally licensed communication airways, often referred to as linear video distribution.
This “shotgun” approach to advertising proved to be very successful in the beginning. However, as the number of advertisers wishing to sell their goods and services substantially increased, television evolved into a much more complex system of communications. For example, cable television providers, satellite television providers, streaming content providers (collectively referred to herein as content distributers) now serve as an intermediary between the content providers and the intended public audience. And, the number of content providers has increased accordingly. In this regard, many members of the general public have signed on as customers of the content distributers so as to receive a broader availability of content.
Because the market for content consumption has grown, the number of content distributers has also grown. And, because each of these distributers has its own method of content delivery, the manner in which the content and assets are delivered to the customers has become increasingly complex. Generally, the content providers deliver the content to the content distributers with instructions to insert various advertising (also referred to as “assets”) into the content at certain times. For example, if a company wishes to run a national advertisement campaign targeting a certain television show associated with a particular demographic, the company may purchase one or more timeslots, or “placement opportunities”, within that television show from the content provider to air assets advertising the goods and services of the company. The content provider then provides the content to each of the content distributers with directions to insert the assets within the timeslots purchased by the company. However, as the number of content providers and advertisers has grown and as consumer tastes have become more diverse, it has become more difficult for content providers to directly sell placement opportunities to the advertisers that financially benefit the content providers.
Accordingly, advertisement decisioning systems (ADSs) have been developed to sell advertisement opportunities. These ADSs improve advertising because they can directly target subscribers of content distributors to provide meaningful impressions with the subscribers. This “On Addressability” initiative offers content providers (a.k.a., “programmers”) and their advertisers the ability to target subscribers. However, the content distributors have data privacy laws that generally prevent the communication of any subscriber related data (e.g., names, addresses, ages, etc.) to third-party ADSs in order to protect their respective subscribers.
Systems and methods presented herein provide for audience obfuscation during advertisement insertion in content. In one embodiment, a network element is communicatively coupled to a plurality of content distributers and to a plurality of advertisement decision servers (ADSs). The network element is operable to receive a first set of requests from a first of the content distributers for advertisements to be inserted into content provided by the content distributer, detect, in the requests, Personally Identifiable Information (PII) of subscribers to the first content distributer requesting the content, and remove the PII of the requests to anonymize the requests. The network element is operable to transfer the anonymized requests to a first of the ADSs, receive advertisements from the first ADS for placement into the content of the content distributers, direct the first content distributer to insert the advertisements into the requested content.
The various embodiments disclosed herein may be implemented in a variety of ways as a matter of design choice. For example, the embodiments may take the form of physical machines, computer hardware, software, firmware, or combinations thereof. In another embodiment, a computer readable medium is operable to store software instructions for resolving conflicts related to the directed insertion of assets into content. These software instructions are configured so as to direct a processor or some other processing system to operate in the manner described above.
Other exemplary embodiments are described below.
Some embodiments of the present invention are now described, by way of example only, and with reference to the accompanying drawings. The same reference number represents the same element or the same type of element on all drawings.
The figures and the following description illustrate specific exemplary embodiments of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the invention and are included within the scope of the invention. Furthermore, any examples described herein are intended to aid in understanding the principles of the invention, and are to be construed as being without limitation to such specifically recited examples and conditions. As a result, the invention is not limited to the specific embodiments or examples described below.
In some instances, the audience obfuscation system 10 also obscures Personally Identifiable Information (PII) of the subscribers from some of the ADSs 20, such as household identifications (HHIDs) or subscriber IDs. Although, other PII that the router 15 could receive and obscure may include phone numbers, set top box IDs, media access control address or “MAC” address, addresses, names, recent purchases, or the like. For example, the content distributers 11 have access to the HHIDs and this information is included in the requests to the audience obfuscation system 10. Some of the ADSs 20 are permitted access to this information, however, others are not. In the instances where the ADSs 20 are not permitted access to the PII, the audience obfuscation system 10 strips the PII from the requests before transferring the requests to those ADSs 20.
The requests from the content distributers 11 are Society of Cable Telecommunications Engineers (SCTE) 130-3 requests. However, the interfaces to the ADSs 20 are typically Video Ad Serving Template (VAST) interfaces. So, the audience obfuscation system 10 may also translate the SCTE 130-3 requests into VAST requests. In this regard, the audience obfuscation system 10 may include a router 15 with an SCTE to VAST translator 16 that is operable to translate the SCTE 130-3 requests into VAST requests and then route the VAST request to the appropriate ADSs 20.
Before routing the VAST requests to the ADSs 20, the router 15 may format the requests with a request formatter 17. The request formatter 17 may strip the PII from the VAST request and replace it with an audience segment identifier. For example, based on the PII of a request, the request formatter 17 may identify an audience segment that a subscriber belongs to, such as males between the ages of 25 and 50 who recently purchased or wish to purchase Ford trucks. The request formatter 17 may supply a unifying identifier for each audience segment that is distributed from content providers to the content distributors 11 and into the audience obfuscation system 10. This allows the audience obfuscation system 10 to consolidate audience members (e.g., subscribers to the content distributors 11) across all of the content distributers 11 and thus obfuscate their PII by forming a unified group of subscribers for content providers and advertisers to target with addressable advertising.
The unifying identifier may be represented in a number of ways that allows the segment identifier to rapidly consolidate audience members into a group and to rapidly access the group when adding and/or subtracting audience members. Such an identifier may also be issued a time stamp such that the group can be deleted when the group is no longer necessary (e.g., when an advertising campaign is no longer employed). Examples of the unifying identifier may include “FordIntenders20210108” pertaining to people who may be interested in purchasing a vehicle from the Ford Motor Company for an advertisement campaign taking place on Jan. 10, 2021, “HomeDepotCustomers20210110 pertaining to people who are Home Depot customers for an advertisement campaign taking place on Jan. 10, 2021, etc.
The audience obfuscation system 10 may also generate a consolidated segment ID using content provider names of the content distributors 11 with a segment name hashes that link, but obscure (e.g., anonymize), the PII of a subscriber to an audience segment. The audience obfuscation system 10 may then store that segment ID in the segment database 14. To illustrate, the router 15 may receive SCTE 130-3 requests from a content distributor 11. The translator 16 may translate some of the SCTE 130-3 requests into VAST requests. The request formatter 17 may remove the PII (i.e., the HHID) from some of the translated requests and determine which active audience segments the HHID resides in (e.g., based on demographics, incomes, addresses, purchased products and services, etc.). The request formatter 17 may use the HHID and the content provider to lookup active audience segments that the HHID is a member of for that content provider. The request formatter 17 then places that list of segment names which define the audience segments in an outbound VAST request. In other words, when the request formatter 17 receives requests for advertisements from a content distributor 11, the request formatter 17 may assign the applicable audience segments to each request and transfer VAST requests to the ADS 20 being used by the content distributor 11. The request formatter 17 may then generate uniform resource locators (URLs) to transfer the VAST requests to the ADS 20. These VAST request may communicate, to the ADS, that there has been content streamed on VOD to a subscriber, and that there are available ad opportunities that need to be filled. The VAST requests may also hold a host of other details about the VOD session, such as the segments that a household resides in. The audience obfuscation system 10 may perform this operation for any number of content distributors 11 and/or ADSs 20.
Once the VAST requests are received by an ADS 20, the ADS 20 may transfer advertisements to the audience obfuscation system 10 to fulfill the advertisement requests of the content distributors 11. For example, an ADS 20 may receive a plurality of requests from the router 15 and subsequently fulfill each request with one or more advertisements for insertion into content of the content distributors 11. In doing so, the ADS 20 may determine which advertisements would be most likely viewed by subscribers of the content distributors 11 (e.g., based on the audience segments).
To illustrate using the Ford truck example, the router 15 may transfer requests for advertisements to an ADS 20 based on a Ford truck audience segment (e.g., males between the ages of 25 and 50 who recently purchased Ford trucks). Then, the ADS 20 may fulfill those advertisement requests with advertisements for Ford trucks and/or other Ford vehicles. The ADS 20 may do so by transferring a Video Multiple Ad Playlist (VMAP) Extensible Markup Language (XML) template to the router 15 via a VAST response, which is translated by the SCTE-VAST translator 16 into an SCTE 130-3 response. The VMAP XML template allows the content distributers 11 to describe structure for insertion of advertisement inventory into content. The router 15 may then transfer the response to the content distributor 11 such that the content distributor 11 may retrieve the advertisements from the VMAP XML and insert them into the content being selected by the content distributor 11's subscribers.
In some embodiments, the audience obfuscation system 10 ingests audience segments directly from content distributors 11 with a segment ingestion module 12. Segment ingestion generally refers to mapping an HHID to an audience segment ID and name of each distributor 11. The segment ID in these files may be distributor-specific such that a content provider and segment name may be used to generate a unified segment ID that can be used across content distributers 11. For example, the audience obfuscation system 10 may receive and process audience segment files from content distributors 11 independently. Generally, each segment file includes an identifier for a specific content distributor 11 and the audience segment with an audience segment name (e.g., Ford truck owners, Coca Cola purchasers, etc.). Both of these identifiers may be linked to a list of subscriber identifiers that have been matched to the audience segment. The segment consolidation module 13 receives raw data from the segment ingestion module 12 and persists the identifier to an HHID mapping in the segment database 14.
The audience obfuscation system 10 may also generate a consolidated segment ID by applying an MD5 hash to a concatenated content provider name and segment name. The audience obfuscation system 10 may then publish a consolidated audience segment in the form of a key-value pair to the ADSs 20 for the content distributor 11 that created the segment. Once the audience segment has been loaded, the audience obfuscation system 10 may notify a content provider for campaign targeting and may then ingest active campaigns from the ADSs 20 and their targeted audience segments.
In this regard, the audience obfuscation system 10 may link subscriber IDs to segment name data according to content distributer for all segment names attached to active campaigns. This data may then be utilized by the request formatter 17 during Ad Request Modification in real-time. For example, when the audience obfuscation system 10 receives a request from a content distributer 10 for advertisements, the audience obfuscation system 10 may extract the PII of the request and look up the audience segment(s) to which the subscriber belongs. The audience obfuscation system 10 may then generate a VAST request for the ADSs 20 that fulfills advertisement opportunities in the content that satisfies the audience segment of the subscriber. The audience obfuscation system 10 may also store the content distributor 11's subscriber ID data (e.g., HHID's) and mapping to the segment names in the segment database 14 for subsequent rapid retrieval.
When an audience segment is generated, a segment publication module 18 may publish the audience segments to an ADS 20 such that appropriate advertisement selections can be performed by the ADS 20. While the ADS 20-1 is illustrated as receiving the published audience segments, this illustration just shows how an ADS 20 receives audience segments for the purposes of simplicity. Each of the ADSs 20-1-20-N may receive the published audience segments. Similarly, each of the ADSs 20-1-20-N may receive VAST requests and issues VAST responses as described hereinabove.
Each segment file may include a content distributor-specific ID for the audience segment along with an audience segment name. Both of these identifiers are tied to the list of subscriber IDs that have been matched to the segment. For example, the content distributor 11-1 may insert advertisements into content selections made by subscribers to the content distributor 11-1. The content distributor 11-1 may then generate a file of each subscriber that includes the identification of the content distributor 11-1 and the subscriber's HHID. With this information, the segment ingestion module 12 may classify the subscriber into a global audience segment and tag each of the subscribers with its own global audience segment ID for use with all content distributers 11 communicating with the audience obfuscation system 10, such that more relevant advertisements may be delivered to the subscribers, and the audience segment in general, in the future. The segment ingestion module 12 may then store the information of the subscriber's file in the segment database 14.
The segment ingestion module 12 may map the HHID of the subscriber to the segment ID in the segment database 14. Once this is done, a segment consolidation transfer module 13 may generate the consolidated segment ID by applying an MD5 hash to a combination of a concatenated content provider ID and segment name, as explained above. For example, suppose Discovery Networks creates a segment with a segment_name=“CoffeeLovers20201225”. The content distributers 11 associate the correct HHIDs to this segment based on the PII, and distribute files of the subscriber that contain a segment_name, a segment_id, and a content distributer 11 specific HHID. Although, in some embodiments, the content distributers 11 may remove certain HHIDs that opt out of targeted addressable advertising. The content distributers 11 may then generate a file for the HHID with a content distributer specific segment_id, which is transferred to the audience obfuscation system 10. To illustrate with three specific content distributers 11, this file may contain the segment_id of a particular content distributer 11, the segment_name, and the subscriber_id for the audience segment segment_name=CoffeeLovers20201225 as follows:
comcast_segment_id=AT8928726
charter_segment_id=38266329
cox_segment_id=2x8p38ay9
The segment ingestion module 12 takes these 3 files and ingests the data to generate a unified segment_id (e.g., global across the content distributers 11)) by taking the segment_name, combining it with the content provider that created the segment, and applying an MD5 hash to create a new segment_id as follows:
content provider=Discovery Networks
segment_name=CoffeeLovers20201225
consolidated_segment_id=d4d9c3c407aa4457e97733b39168dc5c
Even though each content distributer 11 may issue a different segment_id to the segment ingestion module 12, the hashing consolidates them into the same consolidated_segment_id and segment_name. Then, the segment ingestion module 12 may use the consolidated_segment_id to represent all HHIDs across all content distributers 11.
The segment consolidation and transfer module 13 may publish the consolidated audience segment (e.g., via the segment publication module 18 of
Alternatively, when the audience segmentation does not require obfuscation, the segment ingestion module 12 may transfer the subscriber file and audience segment from the content distributor 11 directly to the ADS 20. For example, the segment ingestion module 12 may still process the subscriber files from the content distributor 11-N and perform the audience segment classification for individual subscribers of the content distributor 11-N. However, in this instance, the segment ingestion module 12 may publish the subscriber files directly to the ADS 20-N along with the audience segments of those files. In whatever the case, once the audience segment has been loaded into an ADS 20, a segment notifier module 22 may notify a content provider distribution module 23 for targeting advertising campaigns to inform content providers that their audience segments are ready to be targeted on a campaign.
Generally, the audience obfuscation system 10 ingests active advertisement campaigns from all ADSs 20, including their associated audience segment target information. The audience segmentation workflow may ultimately result in audience segments being targetable on campaigns in a downstream ADS. In some embodiments, content providers may create these advertisement campaigns and then use them to target the audience segments.
In some embodiments, the audience obfuscation system 10 collects campaign information from downstream ADS solutions so that there is visibility into what advertisement campaigns the content providers are conducting and what segments they are targeting. These integrations may differ by ADS 20 but generally include implementations like calling an Application Programming Interface (API) or ingesting a .csv file from an SSH File Transfer Protocol (SFTP). The hosting of active campaign data may provide a list of audience segments that the router 15 should include in outbound VAST request URLs and may be limited to audience segments that are targeted on active campaigns. Campaign data collection is important such that older audience segments are not included once the campaign they are targeted on expires. This functionality may be implemented with the segment expiration module 21
In some embodiments, the audience obfuscation system 10 links subscriber_id to segment_name data by content provider 11 for all segment names attached to active campaigns. This data may be utilized during ad request modification. Generally, this is a data manipulation step that allows the router 15 to perform a lookup from a table in real-time using HHIDs and provider names to find the segment_names it needs for a VAST request. This lookup table combines raw audience data from the content distributors 11 and the content provider campaign data collected from the ADS solutions. The table may include the subscriber_id, segment_name, and provider name.
To illustrate the insertion of assets into content,
Also, the invention is not intended be limited to any particular number of content segments 110 or any particular number of asset timeslots. In fact, an asset timeslot 112 may be subdivided for insertion of multiple assets. For example, television commercials are typically 30 seconds in length. Occasionally, however, asset providers can reduce the overall duration of a particular asset (e.g., by removing a portion of a 30 second commercial to reduce it to a 15 second commercial). Accordingly, a 30 second asset timeslot 112 may be configured to accept insertions of two 15 second assets. An example of such is illustrated in
It should be noted that the decisions regarding the direction of asset insertions occur quite rapidly. For example, the ADS 20 may be operable to make asset insertion decisions for a plurality of content distributors 11. And, each content distributor 11 may be operable to provide content to a plurality of CPEs at any given time (e.g., thousands or more at once). Thus, when a content selection is made by a particular CPE, the ADS 20 responds in substantially real time to ensure that the content distributor 11 has ample time to retrieve and insert the assets while processing the content selected by the CPE. In this regard, the audience obfuscation system 10 may be processing/translating thousands or more requests and responses. In some embodiments, the number of requests and responses could number in 1000 per hour, 10,000 per hour, 100,000 per hour, or even 1 million per hour or more.
The AQM 151 is any device or system operable to communicate with the interface 154 to initially qualify assets for insertion within the content. The AQM 151 may exclude certain assets from insertion into the content selected by the CPE. The ARM 152 is any device or system operable to rank the remaining assets (i.e., those not already excluded by the AQM 151) for insertion to the content 110. The ACRM 153 is any device or system operable to remove any ranked assets from insertion into the content 110 based on conflicts between assets. For example, the ACRM 153 may determine that assets from certain advertisers conflict with one another (e.g., Coke and Pepsi). Accordingly, the ACRM 153 may be operable to prevent assets from these advertisers from being inserted within a same timeslot 111 or even within a same content 110. The exemplary operations of the AQM 151, the ARM 152, and the ACRM 153 are explained in greater detail below in
The CPE 107 transfers a content request to the content distributor 11 which in turn retrieves the content. The content distributor 11 may also retrieve active campaigns. For example, each asset provider may generate an advertising campaign with one or more campaign items. Each of these campaign items may be associated with one or more assets of the asset provider designating the desired time, date, content, audience/demographic, etc., for which the assets are to be inserted into selected content. The content distributor 11 may retrieve the active campaigns of the asset providers and generate an asset insertion request for the AQM 151 of the ADS 20.
Upon receiving the request, the AQM 151 may determine certain parameters relating to the placement of the assets. For example, the AQM 151 may determine durations of the assets and various placement opportunities for the assets (i.e., appropriate timeslots within the selected content). The AQM 151 may also process the active campaigns to determine their eligibility within the content to generate a list for the ARM 152 such that the ARM 152 may rank and select eligible campaigns from that list. In doing so, the AQM 151 may exclude certain campaigns from the list based on various criteria, such as whether the asset provider and/or the asset itself are valid and whether the insertion opportunities themselves are valid. An embodiment of the AQM 151 is exemplarily shown in greater detail below in
Once the ARM 152 receives the eligible campaign list, the ARM 152 ranks the various campaign items that include assets of the campaigns for insertion into the content selected by the CPE 107. The ARM 152 may rank the campaign items based on, among other things, their value to the content provider and/or the content distributer 11, the strategy of the campaign, and the priority of the campaign. An embodiment of the ARM 152 is exemplarily shown and described in greater detail below in
Once the ACRM 153 removes conflicts from the ranked list of possible campaigns, the ACRM 153 may transfer URLs of the assets to the content distributor 11, which in turn inserts the assets into the timeslots of the selected content. The ACRM 153 can thus direct insertion of assets “on the fly” whenever opportunities are available in the content.
After the content is delivered to the CPE 107 with the inserted assets, the ADS 20 reports the insertion (e.g., to the content distributor 11 and/or the asset providers) and recomputes and/or synchronizes campaigns for another content selection by a CPE 107. For example, once certain goals have been met for a particular campaign, the achieved goals may lower the ranking of that campaign or even exclude it from future insertions in selected content. Accordingly, the ADS 20 may retain information pertaining to the insertion of assets for use in determining subsequent asset insertions.
In one embodiment, the ADS 20 may receive information from the content distributor 11 indicative of actual views of the inserted assets. For example, the content distributor 11 may be operable to access a CPE 107 to determine when a content selection is stopped such that a portion of the asset insertions are not seen by the viewer of the content selection. This information may be transferred back to the ADS 20 such that the campaign data of those non-viewed assets can be compensated or corrected. In other words, when assets are inserted into content selections and they are not viewed because of some action on the part of the viewer, such as stopping or fast forwarding the content selection, the campaigns of those assets should not be influenced. Accordingly, the ADS 20 may take this information into consideration and recompute how close the campaign is to meeting its targeted goal for views.
It should be noted that the invention is not intended to be limited to any particular messaging format. In some embodiments, the ADS 20 interacts with the audience obfuscation system 10 using the standards established by the Society of Cable Television Engineers (SCTE). In other embodiments, the ADS 20 interacts with the content distributor 11 using an Entertainment Identifier Registry (EIDR). EIDR provides a manner in which content and assets may be tagged with unique identifiers that are operable to distinguish the content and assets from one another. For example, content and assets generally have associated metadata to distinguish themselves from one another based on various aspects, such as age, maturity level, actors, products, and the like. EIDR identifiers are generally capable of incorporating this metadata to provide a compact means for uniquely tagging the content and assets for rapid identification due in part to its central registration. That is, each particular content and asset is identified with a unique EIDR identifier that is maintained by central registration system so that individual content distributors and the like may quickly identify and use the registered content and assets. In other embodiments, the ADS may communicate via VAST signaling.
To provide more context to the operations of the ADS 20, the following example is provided.
The CPE 107 selects a particular episode of the television show “30 Rock” at 8 pm on a Thursday night from a menu of content that is presented by the content distributor 11. As with many other 30-minute situational comedies, this episode of 30 Rock includes two content sections 110-1 and 110-2 and the three timeslots 111-1, 111-2, and 111-3, as illustrated in
1. A Coca-Cola campaign with a total of four assets and 3 campaign items directing placement opportunities of those assets as follows:
a) Asset 1 for 100 views anytime;
b) Asset 2 for any viewing opportunities Monday through Friday between the hours of 5 pm and 10 pm; and
c) Assets 3 and 4 for any viewing opportunities Friday and Saturday between the hours of 5 pm and 10 pm.
2. A Pepsi-Cola campaign with a total of five assets and four campaign items directing placement opportunities of those assets as follows:
a) Asset 1 for 20 views anytime;
b) Asset 2 for 100 views anytime;
c) Asset 3 for 1000 views anytime;
d) Asset 4 for any viewing opportunities Monday through Friday between the hours of 5 pm and 10 pm; and
e) Asset 5 for any viewing opportunities Friday and Saturday between the hours of 5 pm and 10 pm.
3. A Capital One credit card campaign with a total of four assets and three campaign items directing placement opportunities of those assets as follows:
a) Asset 1 for 100 views anytime;
b) Asset 2 for 1000 views anytime; and
c) Assets 3 and 4 for any viewing opportunities Monday through Friday between the hours of 5 pm and 10 pm.
4. A Chrysler Motors campaign with a total of three assets and two campaign items directing placement opportunities of those assets as follows:
a) Asset 1 for 100 views; and
b) Assets 2 and 3 for any viewing opportunities Monday through Friday between the hours of 5 pm and 10 pm.
5. A Nickelodeon campaign with one asset and one campaign item directing placement opportunities of that asset as follows:
a) Asset 1 for 100 views.
Since the television show 30 Rock has a mature theme and since the Nickelodeon campaign is directed towards a younger audience, that campaign item is automatically excluded from the eligible campaign list by the AQM 151. Other remaining campaign items are excluded based on time and date (i.e., campaign items 1c and 2e).
Thus the remaining campaigns of 1a-1b, 2a-2d, 3a-c, 4a-4b are transferred to the ARM 152 for ranking. Based on various factors explained in greater detail below, the ARM 152 ranks the campaigns as follows:
1. Campaign Item 2a
2. Campaign Item 1a
3. Campaign Item 3c
4. Campaign Item 2b
5. Campaign Item 4b
6. Campaign Item 4a
7. Campaign Item 1b
8. Campaign Item 1d
9. Campaign Item 2c
10. Campaign Item 1c
11. Campaign Item 2d
12. Campaign Item 3a
13. Campaign Item 3b
The ARM 152 transfers this ranked list of campaign items to the ACRM 153 to determine conflicts within the ranked list of campaign items. Typically, the six available asset placement opportunities 112-1-6 within the content 110 would be filled by the first six campaign items based on a rank determined by the ARM 152. However, since some conflicts may exist between campaigns within a particular content and/or timeslot, certain campaigns may be excluded from the placement opportunities 112 such that the ranking is reordered. For example, certain criteria may dictate that a Pepsi Cola asset may not be placed within the same content as a Coca-Cola asset. In this regard, the campaign items 1a-1d are removed from the ranked list because the Pepsi-Cola asset has the higher initial ranking, leaving the following campaign items:
1. Campaign Item 2a
2. Campaign Item 3c
3. Campaign Item 2b
4. Campaign Item 4b
5. Campaign Item 4a
6. Campaign Item 2c
7. Campaign Item 2d
8. Campaign Item 3a
9. Campaign Item 3b
With this computed, the ACRM 153 may remove the final three campaign items 7, 8, and 9 from the list as the six placement opportunities can be filled with assets. The ACRM 153 then transfers this information regarding asset placement to the content distributor 11. Other more specific embodiments are shown below.
Returning to
Otherwise, the AQM 151 determines whether the placement request is properly formatted, in the process element 302. For example, messaging formats among content distributors 11 are varied. As part of a means for simplifying the communication for asset placement, the ADS 20 may standardize the format of placement requests from content distributors 11. In one embodiment, the interface 154 of the ADS 20 receives messages from the audience obfuscation system 10 and formats them into placement requests such that content distributors 11 who are not affiliated with the ADS 20 may be rejected according to improperly formatted placement requests. In other words, the formatting of the placement request may act as a form of security to prevent unauthorized content distributors 11 from seeking access to the ADS 20. The AQM 151 then determines whether the message ID and version are valid, in the process element 303. For example, as another security feature, the ADS 20 may assign message identifiers to each authorized content distributor 11 with version numbers to ensure that unauthorized content distributors 11 do not access the ADS 20 be the audience obfuscation system 10. The version numbers may be useful in assuring that authorized content distributors 11 accounts are up to date. That is, even though a content provider may be authorized to access the ADS 20, they may not be able to request placement of assets in their content because they have been temporarily restricted (e.g., due to failures of payment, assets being deemed inappropriate, etc.).
Once the AQM 151 validates the message ID and version of the placement request, the AQM 151 validates the client and target within the placement request. For example, information regarding the CPE 107 may indicate whether the CPE 107 is authorized to receive content. Based on this information, the AQM 151 may validate the CPE 107 and verify that the target of the selected content is indeed that CPE 107. After doing so, the AQM 151 may identify the local date and time of the CPE 107 (e.g., to identify when assets may run in the selected content). The AQM 151 then validates the terminal address of the CPE 107. To illustrate, a stolen CPE 107 may appear as an authorized CPE 107. However, since that stolen CPE 107 has changed locations, the terminal address of that CPE 107 has also changed due to its connection to a new cable link. Accordingly, the AQM 151 verifies that the CPE 107 is indeed located where it is supposed to be located. Alternatively, this functionality may be configured within the content distributor 11.
Afterwards, the AQM 151 identifies an originating Asset Decision Manager (ADM) and Content Information Service (CIS) of the content distributor 11 and then determines whether the ADM is valid, in the process elements 307 and 308. For example, SCTE standard 104 (SCTE-104) defines an interface between automation systems and compression systems that encode a digital video stream (e.g., an MPEG stream of content) at the content distributor 11. Using SCTE-104, the automation system provides instructions and metadata from which a compression system creates SCTE standard 35 messages as private data packets in the digital video stream. SCTE standard 130 (SCTE-130) defines an architecture for communication and interoperation among various systems employed in cable television advertising. The standard may also include a CIS that defines services for subscriber information and placement opportunities within content to support inventory exchange.
Various vendor systems at the content distributor 11 perform the actual contract management, cue message detections, and asset insertions. SCTE-130 defines the interface that isolates the details of each vendor's system and acts as a front-end through which other systems provide and consume cooperating services. The ADS determines how assets are combined with content. The ADM defines messages in support of asset insertion activities. The primary consumer of these messages is the ADS. The message interfaces exposed by the ADM allow for preconfigured asset decisions and real-time asset fulfillment models. An ADM may incorporate some rudimentary asset selection rules, such as asset rotation, but more complex asset decisions are the responsibility of the ADS. The CIS manages metadata describing the assets, advertising and non-advertising, that are available to the other logical services defined by SCTE-130. The CIS provides query and notification interfaces to these logical services. The query service is available on an ad-hoc basis and may be called by any other logical service at any time without any prior registration. Queries specify values or patterns to be sought in the query message metadata and the specified matching information is returned in a response message.
Once the ADM is identified, the AQM 151 validates the ADM to ensure that it is authorized to access the ADS 20, in the process element 308. After validation, the AQM 151 identifies the asset based on its content provider and asset identifier (the “PAID”), in the process element 309, to determine whether the asset provider is valid and active (process element 310) and whether the asset from that provider is valid (process element 311). For example, the AQM 151 may independently verify the existence of each asset at each operator location. To verify the distribution status of assets, the AQM 151 may employ SCTE-130 part 4 (SCTE-130-4) pertaining to CIS logical interfaces. Thus, the AQM 151 may query each operator CIS endpoint using the unique ID of each asset and the provider's unique content provider ID, or PAID. Alternatively or additionally, the ADS 20 may use VAST signaling depending on its configuration.
In this embodiment, the AQM 151 is initiated to check the status of an asset such as when the interface 154 of the ADS 20 receives the placement request 301. The AQM 151 generates and transfers a request to check the asset status (i.e., the PAID) to a SCTE-130-4 interface of the content distributor 11. The content distributor 11 in turn generates and transfers a content query request to a CIS of the content distributor 11. The CIS then sends a request to retrieve the asset status from back office systems of the content distributor 11. For example, the back-office systems may determine whether the asset is available, unavailable, or its availability is unknown. The status is then returned to the CIS and transferred to the interface in a content query response. The interface informs the AQM 151 of this asset status such that the AQM 151 can determine whether such an asset placement would be valid. If it is not valid, the AQM 151 returns the error response E1 as in other instances and then updates the asset availability. If the asset is valid, its status is also updated such that it may be used for placement in content (i.e., an asset placement timeslot).
With the asset identified and validated, the AQM 151 may then identify placement opportunities within the content selected by the CPE 107, in the process element 312. For example, the content may have certain designated placement opportunities for the assets. The number, or counts, of these timeslots and their durations are used by the AQM 151 to assist in the selection and placement of assets. The AQM 151 may also identify and use any control information associated with timeslots that could restrict certain assets. In identifying these placement opportunities, the AQM 151 validates whether the content selected by the CPE 107 has placement opportunities for the assets and what that number is, in the process element 313. If so, the AQM 151 validates whether the placement opportunities are of the appropriate type, in the process element 314. As mentioned, placement opportunities may include control information or metadata that restricts certain assets from being placed within a selected content. For example, age control information of selected content may be used to restrict certain assets from being placed within that content based on age (e.g., children's shows having control information that restricts assets with more mature content and vice versa). If the opportunity times within the content are valid, the AQM 151 determines whether any placement opportunities are still available within the content selected by the CPE 107, in the process element 315.
After the validation process is complete, the AQM 151 qualifies campaigns to determine whether assets of those campaigns can be placed within the selected content, as illustrated in
If campaign items are available for asset placement within the placement opportunities of the content selected by the CPE 107, the AQM 151 evaluates the campaign items in the process element 354. In doing so, the AQM 151 validates the day/time conditions of a campaign item in the process element 355 to ensure that a particular asset in the campaign item is appropriate for the date and time when the content is selected by the CPE 107. For example, a commercial for a mature audience may not be appropriate for viewing until later evening hours when children are not present. Thus, if the content is selected during the afternoon, the AQM 151 may exclude the campaign item containing the mature audience commercial from placement within the selected content. Similarly, if the commercial is intended for children, the information within the campaign item asset may not be relevant to a more mature audience. Thus, if the content is selected during the late evening when children are not present, the AQM 151 may exclude the campaign item from placement within that selected content. So, when the campaign item does not meet the valid date/time conditions, the AQM 151 removes the campaign item from potential insertion into the selected content, in the process element 360. The AQM 151 then determines whether there are any available campaigns remaining from the loaded list of active campaign items, in the process element 361. If there are no available campaigns, the AQM 151 generates an empty placement, in the process element 363 (E2), as described above, and responds to the content distributor 11, in the process element 364. For example, once the AQM 151 evaluates all of the campaign items and excludes all of those campaign items in the process element 354, the AQM 151 then determines if there are any campaigns left for potential placement in the selected content. If there are none, the AQM 151 may generate an empty response and contact the content distributor 11 such that the content distributor 11 may place an asset in the selected content as desires or leave it empty. Otherwise, the AQM 151 transfers the information pertaining to the remaining campaigns, items, and assets to the ARM 152 (B1).
In continuing the evaluation of campaign items, in the process element 354, the AQM 151 validates the metadata conditions of a campaign item, in the process element 356. For example, assets generally have metadata associated with them that describe certain features of the asset, such as a particular actor in the asset, the theme of the asset, targeted audience for the asset, maturity level of the asset, etc. In one embodiment, these metadata features are contained in an EIDR identifier as discussed above. If the assets of the campaign item being evaluated do not meet the desired metadata conditions for the selected content, that campaign item is removed from consideration, in the process element 360. To illustrate, the actor Alec Baldwin has been seen in several Capital One credit card commercials. A campaign item by the Capital One credit card company may wish to have those commercials inserted into the certain content featuring Alec Baldwin as an actor, such as the television show, 30 Rock. Thus, if the selected content does not include Alec Baldwin, that campaign item may be excluded from potential insertion into the selected content. Alternatively or additionally, if the content requires assets of a certain type, the metadata of the assets may be used to exclude the assets from the content. For example, if the content precludes mature content, campaign items having assets with mature themes may be excluded from the selected content based on the metadata of the assets relating to maturity level.
The AQM 151 is also operable to validate break/position conditions of the content selected by the CPE 107, in the process element 357. For example, if the selected content has only 30 second pre roll and post roll timeslots available for asset insertions and the campaign item mandates that the asset be placed at the mid roll timeslot in a content, then the campaign item is excluded and removed in the process element 360.
Once the various conditions for the campaign items have been validated, the AQM 151 then evaluates the individual assets in a particular campaign, in the process element 358. From there, the AQM 151 determines if there are any remaining goals of a particular campaign. If so, the AQM 151 returns to evaluate the remaining campaign items in the campaign (e.g., via process elements 355-358). For example, a campaign may include a campaign item that desires 1000 views of an asset within a certain time period (e.g., a week). Once the asset has been inserted into content 1000 times within that time period, the goal has been reached and the campaign item and/or the asset may be excluded from insertion to the presently selected content and thus removed from consideration, in the process element 360. In other words, once a goal for a campaign item has been met, it may provide little or no value to the content provider and/or the content distributor 11. Accordingly, the AQM 151 may exclude the campaign item from consideration so that other more valuable campaign items may be selected. Examples of campaign goals include campaign duration (e.g., % completion thereof), total number of desired placements, and the like. Otherwise, the AQM 151 adds the campaign item to a list of remaining available campaign items in the process element 362 and continues determining the availability of campaign items, in the process element 353 (B2), to evaluate the campaign items for possible insertion to the selected content.
The AQM 151 is also operable to determine whether an asset is available on the ADM, in the process element 382. These assets are periodically updated as advertisers wish to update their various campaigns with newer assets. Older assets may be removed from the databases making them unavailable for insertion. Thus, even if the older asset exists in the campaign item, that asset is not available for insertion because it does not physically exist. Accordingly, the AQM 151 removes the asset from consideration and returns to evaluating the remaining assets of the campaign item.
The AQM 151 may also be operable to determine whether an asset is available in a target window, in the process element 383. For example, if the asset is only available during a certain time of the day, day of the week, etc., and the content is selected by the CPE 107 outside of that time window, then the AQM 151 removes that asset from consideration. The AQM 151 may also be operable to determine whether an asset is available in a license window, in the process element 384. For example, the ADM may determine if assets are available for insertion into content. However, that asset could include certain licensing information that precludes insertion into content by the content distributor 11 for any of a variety of reasons (e.g., contractual obligations between television provider and network provider have ceased). Thus, the asset may be excluded from insertion into selected content based on its license window. Once the AQM 151 completes evaluation of the assets within a particular campaign item, the AQM 151 returns to continue evaluating the individual campaign items (C2).
The priority score module 401 is any device or system operable to generate priority information for the campaign items provided to the ARM 152 by the AQM 151. A priority score relates to a weighted representation of how important a campaign item is in relation to other items in a campaign. The priority score module 401 may calculate a priority score for each of the campaign items in a campaign based on the function of: (campaign priority value/sum of all priority values for the campaign items)*(parameter weight/100). For the function, the campaign priority value is assigned by the manager that creates the campaign. The parameter weight is a value used to modify how much the priority score figures into the total score.
The value score module 402 is any device or system operable to generate value score information for the campaign items provided to the ARM 152 by the AQM 151. A value score for a campaign item relates to a weighted representation of the income generated by inserting a particular campaign item into content. The value score module 402 may calculate a value score for each of the campaign items in a campaign based on the function of: ((campaign item value)/(the sum of all values for the campaign items in the campaign))*(parameter weight/100). For the function, the campaign item value is the currency value that is assigned for the campaign item. The currency value may be paid upon the campaign item being inserted into the content and/or the campaign item being viewed by a customer (i.e., a user of the CPE 107). The parameter weight is a value used to modify how much the value score figures into the total score.
The strategy score module 403 is any device or system operable to generate strategy scoring information for the campaign items provided to the ARM 152 by the AQM 151. A strategy score for a campaign item relates to a weighted representation of how the campaign item is distributed during an active campaign. Some examples of how the campaign item may be distributed include an even distribution, an “as soon as possible (ASAP)” distribution, etc. The strategy score module 403 may calculate a strategy score for each of the campaign items in a campaign based on the function of: ((campaign item strategy value)/(the sum of all campaign items strategy values for the campaign items in the campaign))*(parameter weight/100). For the function, the campaign item strategy value may be “0” for an even distribution and “1” for an ASAP distribution. Other strategies may exist as any values in between. The parameter weight is a value used to modify how much the strategy score figures into the total score.
The goal score module 404 is any device or system operable to generate goal information for the campaign items provided to the ARM 152 by the AQM 151. A goal score for a campaign item relates to a weighted representation of whether the campaign item is behind schedule, on schedule, or ahead of schedule to meet its goal. The goal score module 404 may calculate a goal score for each of the campaign items based on the function of: ((campaign item health score)/(the sum of all of the campaign item goal values for each of the campaign items in the campaign))*(parameter weight/100). The parameter weight is a value used to modify how much the goal score figures into the total score. The campaign item health score may be determined by the function of: ((% of goal remaining)/(% of time remaining in the campaign)). The “% of goal remaining” may be determined by the function of: ((the campaign item goal−current count))/(campaign item goal). The current count is based on the insertions or views of the campaign item. The “% of time remaining” may be determined by the function of: (hours remaining for the campaign item/total hours for the campaign item), where the hours remaining is a time from the current time through the end of the flight window for the campaign item (e.g., a period of time when the asset is to air). The total hours in the function is the number of hours for the duration of the flight window of the campaign item from beginning to end. Some examples of a goal score are >1 when the campaign is running behind schedule and <1 when the campaign is running ahead of schedule.
The scoring information calculated by modules 401-404 is provided to the weight by flexibility module 405. The weight by the flexibility module 405 is any device or system that is operable to generate flexibility information for the campaign items. The flexibility for a campaign item relates to a representation of how much flexibility exists for a campaign item for placement into the content. For example, a highly flexible campaign item may have little or no restrictions as to what times and/or where the campaign item is placed within the content. In contrast, a campaign item with little or no flexibility may be restricted to a few hours per day or to a few days per week. The weight by the flexibility module 405 may calculate a flexibility score for each of the campaign items based on the function of: (number of days/7)*(average hours/24)*(average number of breaks/program break default)*(average number of positions/program position default). In this function, the number of days is the count of unique days of the week the campaign item is eligible for. For example, if a campaign item is eligible to run Monday, Wednesday, and Friday, then the number of unique days is 3. The average hours may be based on the function of: (the sum of the durations of the campaign item/the count item time instances). The “program break default” in the function is a value assigned by a campaign manager that indicates the standard count of breaks in a session. The average number of breaks may be calculated based on the function of: (the sum of eligible breaks for all positions)/(a count of break positions). The eligible breaks are determined for each position as follows. When the break position is pre-roll or post-roll, the break count is 1. When the break position for the campaign item is “any”, then the break count is “program break default”. When the break position is mid-roll and the mid-roll by number is “null”, then the break count is the (“program break default”—2). When the break position is mid-roll and the number is not null, then the break count is 1. The “program position default” in the function is a value assigned by the campaign content provider that indicates the typical or standard count of positions in a break. The average number of positions may be calculated based on the function of: (the sum of eligible positions for all breaks)/(the count of breaks), where the eligible breaks are determined for each break criteria as follows. When the position is first or last, then the break count is 1 for the break criteria. When the position is “any”, then the break count is “program position default” for the break criteria.
After weight by the flexibility module 405 calculates a flexibility score for each of the campaign items, then the priority score, the value score, the strategy score, the goal score, and the flexibility score are provided to a compute rank module 406. The compute rank module 406 is any device or system operable to generate ranking information for the campaign items. The compute ranking module 406 generates a ranking for each of the campaign items based on the function of: ((priority score+value score+strategy score+goal score)/flexibility score). In some cases, one or more campaign items may have a tie ranking. A compute tiebreaker module 407 may utilize a number of other criteria for determining ranking in cases where campaign items are tied. Some examples of the criteria used by the compute tiebreaker module 407 include random assignment (e.g., “coin toss” algorithm), policies regarding preferred campaigns, etc. The ARM 152 then provides the list of campaign items along with their corresponding rankings to the process element 451 of
It should be noted that the various scores and flexibility may be reconfigured as a matter of preference and that the above equations are merely used as exemplary embodiments. For example, an operator of the content distributor 11 may intrinsically value certain asset campaigns over others for any number of reasons. Accordingly, the operator of the content distributor 11 may direct the ADS 20 to “hard wire” the campaign priority value to a particular value. If the preference of the content distributor 11 operator were to change, then the operator may direct the ADS 20 to change the campaign priority value accordingly. This dynamic change capability allows the ARM 152 to provide more flexibility to content distributors 11 on an as needed basis.
When the time slots for asset placement have been identified in the content selected by the CPE 107, the ACRM 153 evaluates the campaign items in rank order (i.e., as ranked by the ARM 152), in the process element 453. The ACRM 153, as an initial part of a loop process through each of the ranked campaign items, determines whether any campaigns remain in the list of ranked campaign items from the ARM 152, in the process element 454. The ACRM 153 then determines whether a particular campaign being evaluated is adhering to brand separation, in the process element 455. For example, some companies prefer that their assets not be placed near assets of a competitor within the same content. To illustrate, the Coca-Cola Company may desire that an asset relating to a Coca-Cola beverage not be placed next to a Pepsi-Cola asset from the Pepsi-Cola Company so as to show individuality of its particular brand. In other words, the brand of the Coca-Cola asset may become diluted when placed next to a Pepsi-Cola asset because the audience may simply equate the two brands as interchangeable cola products. Thus, if a campaign item being evaluated does not adhere to a certain level of brand separation, the ACRM 153 excludes the assets of the campaign item from insertion and searches for another campaign among the ranked list, in the process element 454. If the campaign item does adhere to brand separation, the ACRM 153 starts a loop to evaluate the individual assets in the campaign item, in the process element 457 (F1), by first determining whether any assets remain in the campaign item, in the process element 456. In other words, the ACRM 153 loops through the assets in each campaign item to determine their potential for insertion into the selected content. Once the asset(s) of the campaign item being evaluated has also been evaluated, the asset(s) is placed in a list that directs the selection of the asset(s) for insertion to the selected content. Afterwards, the ACRM 153 returns to the process element 456 to loop through the remaining assets of the campaign item. If no assets remain in the campaign item, the ACRM 153 loops through the evaluation of the individual campaign items in rank order, in the process element 453.
Once all of the campaign items at each campaign have been evaluated and no campaigns remain (i.e., process element 454) or once all of the placement opportunities have been filled, the ACRM 153 directs the content distributor 11 to retrieve the assets based on the list generated, in the process element 458. For example, the list may be included in a report message that is transferred to the content distributor 11 to direct the content distributor 11 to insert the assets into the content selected by the CPE 107. It is possible that all of the assets have been excluded during the processes described herein. Thus, the ACRM 153 may then direct the content distributor 11 to not place any assets in the content selected by the CPE 107.
The ACRM 153 may also direct the content distributor 11 to place assets relating to content, programming, or even services provided by the content provider. For example, if no assets remain, standard programming information, such as time and date, pertaining to the selected content may be configured as an asset and placed in the selected content. To further illustrate, when an episode of “Modern Family” is selected by a CPE 107 and no assets remain for insertion into the available time slots of that episode, the ACRM 153 may direct the content distributor 11 to present the user of the CPE 107 with the date and time when the next episode of Modern Family can be seen. However, the invention is not intended to be limited to any particular type of noncommercial asset.
Since it is also possible that not all of the assets in the list may be placed as there may be more assets than available opportunities, the ACRM 153 may weight the assets prior to placement in the selected content, in the process element 461. For example, certain assets may provide greater value to the content distributor 11 and/or the content provider. In this regard, the ACRM 153 may rank the remaining assets in a manner that provides the most monetary compensation to the content distributor 11/content provider. Thus, the ACRM 153 may reduce the list of available assets for insertion to the amount of opportunities, or timeslots, in the selected content to provide this value to the content distributor 11/content provider. In any case, the ACRM 153 directs the content distributor 11 to place the assets in the selected content based on the ranked list, in the process element 462. Once placement has been directed, the ACRM 153 generates a placement report and transfers that report to the content distributor 11 so that the content distributor 11 can track marketing views (e.g., for later negotiations between television providers and marketers). For example, when a marketer can know how many views of a particular asset there were in a selected content, the marketer can assign a value to that asset that may be used in negotiating price for additional views of the asset in future selected content.
In
The ACRM 153 may also determine whether a particular asset is of the proper duration, in the process element 503. For example, some timeslots within content are only available in 30 second “chunks”. Thus, if the asset under evaluation is only 15 seconds, there would be a period of 15 seconds of unoccupied airtime in the content. The ACRM 153, in this regard, may then exclude that asset from insertion into the selected content. Alternatively, the ACRM 153 may search for another 15 second asset within the potential assets for insertion alongside the 15 second asset to fully occupy the placement opportunity and prevent missing a placement opportunity in the content. The ACRM 153 may also determine whether the asset is the correct video definition for insertion into the content, in the process element 504. For example, content may vary in terms of definition from selection to selection. Some content selections may be of a standard definition (SD) format whereas the assets may be in a high definition (HD) format. To ensure that the assets can be placed in the selected content and played at the same format of the SD content selection, the ACRM 153 may exclude those HD formatted assets (and vice versa).
As part of an extension to the exclusion process by the AQM 151, the ACRM 153 may also be configured to communicate with the ADM to determine whether the asset is available at the ADM (process element 505), whether the assets is available in the target window (process element 506), and whether the asset is available in the license window (process element 507). The process element 457 ends (F2) with the placement of the asset in the list for selection in the process element 458 of
The network 222 may be any type of communication link capable of providing communication between the ADS 20 and the audience obfuscation system 10 and the content distributor 11. For example, the network 222 may be the Internet, an Intranet, or some other type of data network. Alternatively, the network 222 may be an analog network operable to communicate content, such as analog television networks and analog radio networks. The network 222 may also be implemented as a virtual private network via the Internet. In any case, the ADS 20 and the audience obfuscation system 10 may communicate through the network 222 using standard cable television protocols such as the SCTE standards and/or VAST standards.
The CPE 107 may be a computer or a mobile computing device capable of displaying video from the network 222 (e.g., via streaming video over the Internet). For example, a CPE 107 may select a desired content from an Internet website hosted with the server 230 through the network 222. Once selected, the content distributor 11 may retrieve the content for Internet delivery to the selecting CPE 107. The ADS 20, being communicatively coupled to the content distributor 11, processes information pertaining to the content selection and selects assets for insertion into that content. The ADS 20 may do so based in part on the campaigns of the asset providers 221 and in a manner that provides value to the content providers 220.
The computer readable storage medium 612 can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor device. Examples of computer readable storage medium 612 include a solid-state memory, a magnetic tape, a removable computer diskette, a random-access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W), and digital versatile disc (DVD).
The processing system 600, being suitable for storing and/or executing the program instructions, includes at least one processor 602 coupled to memory elements 604 through a system bus 650. Memory elements 604 can include local memory employed during actual execution of the program instructions, bulk storage, and cache memories that provide temporary storage of at least some program e and/or data in order to reduce the number of times the program instructions and/or data are retrieved from bulk storage during execution.
Input/output (I/O) devices 606 (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the processing system 600 either directly or through intervening I/O controllers. Network adapter interfaces 608 may also be coupled to the system to enable the processing system 600 to become coupled to other processing systems or storage devices through intervening private or public networks. Modems, cable modems, IBM Channel attachments, SCSI, Fibre Channel, and Ethernet cards are just a few of the currently available types of network or host interface adapters. A presentation device interface 610 may be coupled to the system to interface to one or more presentation devices, such as printing systems and displays for presentation of presentation data generated by the processor 602.
While the term “content distributor” generally suggests the distribution center or office of a cable television operator or MSO, the term is not intended to be so limited. The term content distributor as used herein is any system operable to deliver content to a viewer (e.g., a customer or user of the CPE). For example, the term content distributor may encompass internet servers delivering content when selected by a user from a device, such as a computer, a tablet, or a mobile phone. A content distributor may also refer to a telecom provider that distributes content to mobile phones and other devices. Also, the term “asset”, as used herein, includes any type of media for which an owner desires promotion. Examples of such include traditional television commercials, advertisements, streaming video commercials, promotional materials, marketing information, and the like. The term “content”, as used herein is any type of media, such as audio and/or video, in which assets may be inserted. For example, the content operable within the delivery systems described herein may be streamed Internet audio/video, analog cable television feeds, digital cable television feeds, digital satellite television feeds, or digital satellite radio feeds. Thus, the content has described herein is intended to encompass linear content and Video on Demand (VOD) found in modern cable television including pay-per-view (PPV) content delivered by both modern cable television and satellite television.
While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description is to be considered as exemplary and not restrictive in character. Certain embodiments described hereinabove may be combinable with other described embodiments and/or arranged in other ways. Accordingly, it should be understood that only the preferred embodiment and variants thereof have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected.
