TARGETED ADVERTISEMENT INSERTION FOR STREAMING MEDIA DATA

• US 20150269629A1
• Filed: 03/23/2015
• Published: 09/24/2015
• Est. Priority Date: 03/24/2014
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Lo, Charles Nung, Stockhammer, Thomas, Walker, Gordon Kent, Wang, Jun, Naik, Nagaraju, Pazos, Carlos Marcelo Dias
• Granted Patent: US 10,902,474 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/0269 based on user profile or attribute
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/765 intermediate
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04N 21/25883 being end-user demographical data, e.g. age, family status or address arrangements for identifying locations of users in broadcast systems H04H60/52
• CPC Class Codes: H04N 21/25891 being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/44209 Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network arrangements for maintenance or administration in data switching networks involving bandwidth and capacity management H04L41/0896
• CPC Class Codes: H04N 21/4524 involving the geographical location of the client retrieval from the Internet by querying based on geographical locations G06F16/9537; systems specially adapted for using geographical information in broadcast systems H04H60/70; protocols in which the network application is adapted for the location of the user terminal in communication control or processing H04L67/52; services making use of the location of users or terminals in wireless networks H04W4/02; locating users or terminals in wireless networks H04W64/00
• CPC Class Codes: H04N 21/4532 involving end-user characteristics, e.g. viewer profile, preferences monitoring of user activities for profile generation for accessing a video database G06F16/739; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/812 involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04N 21/8456 by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04N 21/85406 involving a specific file format, e.g. MP4 format

Abstract

In one example, a method of retrieving media data includes, by a multimedia broadcast multicast service (MBMS) client of a client device: receiving advertisement media data of one or more advertisement groups, receiving an identifier value for one of the advertisement groups from a dynamic adaptive streaming over HTTP (DASH) client of the client device, extracting the advertisement media data of the advertisement group corresponding to the identifier value, and providing the extracted advertisement media data to the DASH client.

Claims

1. A method of retrieving media data, the method comprising, by a dynamic adaptive streaming over HTTP (DASH) client:

determining a set of advertisement group identifiers associated with advertisement media data of a plurality of advertisement groups, wherein the advertisement media data is to be played during an advertisement break for main media content, wherein the main media content is associated with a manifest file;

retrieving an update to the manifest file, wherein the update defines a remote Period that corresponds to the advertisement media data, wherein the update to the manifest file specifies a template for an extensible markup language (XML) linking language (XLink) uniform resource locator (URL) including an identifier attribute;

selecting, based at least in part on characteristics of a user for the DASH client, one of the advertisement groups from the set;

assigning, according to the template, an identifier value corresponding to the selected advertisement group to the identifier attribute of the XLink URL according to the template;

dereferencing the XLink URL including the identifier value corresponding to the selected advertisement group to retrieve advertisement media data of the selected advertisement group from the remote Period; and

providing the advertisement media data to a media application.

2. The method of claim 1, wherein the DASH client is included in a client device, and wherein dereferencing the XLink URL comprises sending a request specifying the XLink URL including the identifier value to a multimedia broadcast multicast service (MBMS) client of the client device.

3. The method of claim 1, wherein the DASH client is included in a client device, the method further comprising, by a multimedia broadcast multicast service (MBMS) client of the client device:

receiving the XLink URL including the identifier value from the DASH client;

receiving data for the remote Period via a broadcast transport or a multicast transport;

determining that the data for the remote Period matches the XLink URL when a file delivery table (FDT) for the broadcast transport or the multicast transport includes an identifier value that matches the identifier value of the XLink URL; and

in response to determining that the data for the remote Period matches the XLink URL, delivering the data for the remote Period to the DASH client.

4. The method of claim 3, wherein receiving the data for the remote Period comprises receiving data for each of the advertisement groups.

5. The method of claim 3, wherein receiving the data for the remote Period comprises discarding data for all of the advertisement groups other than the advertisement group corresponding to the identifier value of the XLink URL.

6. The method of claim 1, wherein the DASH client is included in a client device, the method further comprising, by a multimedia broadcast multicast service (MBMS) client of the client device:

receiving the XLink URL including the identifier value from the DASH client;

receiving data for the remote Period via a broadcast transport or a multicast transport;

determining that the data for the remote Period matches the XLink URL when a value of a groupIDFilter syntax element of a Filter Description fragment corresponds to the identifier value of the XLink URL; and

in response to determining that the data for the remote Period matches the XLink URL, delivering the data for the remote Period to the DASH client.

7. The method of claim 1, wherein retrieving comprises:

obtaining data that defines a manifest file update period,

wherein retrieving the update comprises retrieving the update according to the manifest file update period.

8. The method of claim 7, wherein the data defining the manifest file update period comprises an MPD@minimumUpdatePeriod element of the manifest file.

9. The method of claim 1, wherein the manifest file comprises a media presentation description.

10. The method of claim 1, wherein the DASH client is included in a client device, the method further comprising:

providing, by the DASH client, state information related to the user or device to a multimedia broadcast multicast service (MBMS) client of the client device;

receiving, by the MBMS client, the advertisement media data via a broadcast transport or a multicast transport; and

mapping, by the MBMS client, the state information to a unique advertisement group identifier.

11. The method of claim 10, wherein the state information includes one or more of cookies, subscription information, User Preference &

Profile (UP/P) data, and usage history.

12. The method of claim 1, wherein selecting comprises selecting based on at least one of user preference and profile data, content consumption history, or an advertisement recommendation engine.

13. A method of retrieving media data, the method comprising, by a multimedia broadcast multicast service (MBMS) client of a client device:

receiving advertisement media data of one or more advertisement groups;

receiving an extensible markup language (XML) linking language (Xlink) uniform resource locator (URL) including an identifier value for one of the advertisement groups from a dynamic adaptive streaming over HTTP (DASH) client of the client device;

extracting the advertisement media data of the advertisement group corresponding to the identifier value; and

providing the extracted advertisement media data to the DASH client.

14. The method of claim 13, wherein receiving the identifier value comprises receiving, from the DASH client, state information related to the client device.

15. The method of claim 14, wherein the state information includes one or more of cookies, subscription information, User Preference &

Profile (UP/P) data, and usage history.

16. A computer-readable storage medium having stored thereon instructions that, when executed, cause a processor of a client device to:

determine a set of advertisement group identifiers associated with advertisement media data of a plurality of advertisement groups, wherein the advertisement media data is to be played during an advertisement break for main media content, wherein the main media content is associated with a manifest file;

retrieve an update to the manifest file, wherein the update defines a remote Period that corresponds to the advertisement media data, wherein the update to the manifest file specifies a template for an extensible markup language (XML) linking language (XLink) uniform resource locator (URL) including an identifier attribute;

select, based at least in part on characteristics of a user of the client device, one of the advertisement groups from the set;

assign, according to the template, an identifier value corresponding to the selected advertisement group to the identifier attribute of the XLink URL according to the template;

dereference the XLink URL including the identifier value corresponding to the selected advertisement group to retrieve advertisement media data of the selected advertisement group from the remote Period; and

provide the advertisement media data to a media application.

17. The computer-readable storage medium of claim 16, wherein the instructions that cause the processor to dereference the XLink URL comprise instructions that cause the processor to send a request specifying the XLink URL including the identifier value to a multimedia broadcast multicast service (MBMS) client of the client device.

18. The computer-readable storage medium of claim 16, wherein the instructions are for a dynamic adaptive streaming over HTTP (DASH) client, further comprising instructions for a multimedia broadcast multicast service (MBMS) client, wherein the instructions for the MBMS client cause the processor to:

receive the XLink URL including the identifier value from the DASH client;

receive data for the remote Period via a broadcast transport or a multicast transport;

determine that the data for the remote Period matches the XLink URL when a file delivery table (FDT) for the broadcast transport or the multicast transport includes an identifier value that matches the identifier value of the XLink URL; and

in response to determining that the data for the remote Period matches the XLink URL, deliver the data for the remote Period.

19. The computer-readable storage medium of claim 18, wherein the instructions that cause the processor to receive the data for the remote Period comprise instructions that cause the processor to receive data for each of the advertisement groups.

20. The computer-readable storage medium of claim 18, wherein the instructions that cause the processor to receive the data for the remote Period comprise instructions that cause the processor to discard data for all of the advertisement groups other than the advertisement group corresponding to the identifier value of the XLink URL.

21. The computer-readable storage medium of claim 16, further comprising instructions that cause a multimedia broadcast multicast service (MBMS) client of the client device to:

receive the XLink URL including the identifier value from the DASH client;

receive data for the remote Period via a broadcast transport or a multicast transport;

determine that the data for the remote Period matches the XLink URL when a value of a groupIDFilter syntax element of a Filter Description fragment corresponds to the identifier value of the XLink URL; and

in response to determining that the data for the remote Period matches the XLink URL, deliver the data for the remote Period to the DASH client.

22. The computer-readable storage medium of claim 16, wherein the instructions that cause the processor to retrieve the update comprise instructions that cause the processor to obtain data that defines a manifest file update period, wherein the instructions that cause the processor to retrieve the update comprise instructions that cause the processor to retrieve the update according to the manifest file update period.

23. The computer-readable storage medium of claim 22, wherein the data defining the manifest file update period comprises an MPD@minimumUpdatePeriod element of the manifest file.

24. The computer-readable storage medium of claim 16, wherein the manifest file comprises a media presentation description.

25. A method of retrieving media data, the method comprising, by a multimedia broadcast multicast service (MBMS) client of a client device:

receiving an extensible markup language (XML) linking language (XLink) uniform resource locator (URL) including an identifier attribute for a remote Period that corresponds to advertisement media data from a dynamic adaptive streaming over HTTP (DASH) client of the client device;

receiving data for the remote Period via a broadcast transport or a multicast transport;

determining that the data for the remote Period matches the XLink URL when data of the broadcast transport or the multicast transport includes an identifier value that matches the identifier value of the XLink URL; and

in response to determining that the data for the remote Period matches the XLink URL, delivering the data for the remote Period to the DASH client.

26. The method of claim 25, wherein the data that includes the identifier value comprises a file delivery table (FDT) for the broadcast transport or the multicast transport.

27. The method of claim 25, wherein the data that includes the identifier value comprises a Filter Description fragment including a groupIDFilter syntax element.

28. The method of claim 25, wherein receiving the data for the remote Period comprises receiving data for each of a plurality of advertisement groups.

29. The method of claim 25, wherein receiving the data for the remote Period comprises discarding data for advertisement groups other than the advertisement group corresponding to the identifier value of the XLink URL.