Generating schedules for synchronizing bulk data transfers to end node devices in a multimedia network

• US 20020087580A1
• Filed: 10/02/2001
• Published: 07/04/2002
• Est. Priority Date: 11/28/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Navic Systems, Inc. (Microsoft Corporation)
• Inventors: Fagnani, Mark, LaCroix, John
• Granted Patent: US 7,328,231 B2
• Time in Patent Office: Days
• US Class Current: 707/104.1
• CPC Class Codes: G06Q 30/0255 based on user history
• CPC Class Codes: G06Q 30/0264 based upon schedule
• CPC Class Codes: G06Q 30/0269 based on user profile or attribute
• CPC Class Codes: G06Q 30/0277 Online advertisement
• CPC Class Codes: H04N 21/25808 Management of client data terminal profiles in network data switching protocols H04L67/303
• 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/26233 involving content or additional data duration or size, e.g. length of a movie, size of an executable file
• CPC Class Codes: H04N 21/4331 Caching operations, e.g. of an advertisement for later insertion during playback
• CPC Class Codes: H04N 21/44224 Monitoring of user activity on external systems, e.g. Internet browsing
• CPC Class Codes: H04N 21/6405 Multicasting data broadcast and multicast in packet switching networks H04L12/18
• CPC Class Codes: H04N 21/812 involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04N 7/165 Centralised control of user terminal subsequent to an upstream request signal H04N7/17345; Registering at central by two-way working H04N7/17309

Abstract

Promotions may be targeted to one or more device groups. A promotion/device group set relation is maintained for each promotion indicating the device groups to which each promotion should be sent. A device group corresponds to a statistically categorized group of end node devices (e.g. set top boxes) based on demographics or viewership history. A device group may be further subcategorized to include one or more transmission groups corresponding to the physical characteristics of the end node devices (e.g. hardware, memory capacity). A promotion server creates a package containing the promotion for each transmission group of the device group. If a package for a particular transmission group is already created and has sufficient available space, the promotion is simply added to the package. Therefore, a package created for a transmission group may hold promotions intended for different device groups even though not all of the promotions are targeted for the same devices. A schedule process then analyzes a set of packages, building a schedule for each end node device, ultimately assigning promotion identification, transmission times, port numbers, and/or multicast IP addresses for specific device groups. Schedule messages are then send out individually to each end node, so that the expected broadcast (multicast) message time, port, and IP address information is known by each device for each of the promotions which are intended for it to receive. The packaged promotions are then sent via bulk data transmission to the end nodes which is initiated by the generation and delivery of transmission requests to bulk data servers on the network.

Claims

1. A promotion scheduling process for generating schedules notifying end node devices in advance of data transfer, comprising:

selecting a set of promotion packages from a database;

generating transmission schedules for end node devices from the selected packages, each transmission schedule customized for an individual end node device, the transmission schedules preparing the end node devices for subsequent data transfers in advance; and

transmitting the customized transmission schedules to the end node devices.

2. The promotion scheduling process of claim 1, wherein generating transmission schedules further comprises:

selecting a promotion identified in a package;

determining the end node devices targeted for the promotion; and

adding a schedule entry for each device targeted for the promotion, the schedule entry specifying promotion control data, the promotion control data identifies the promotion and specifies transmission parameters and activation criteria for the promotion.

3. The promotion scheduling process of claim 2, wherein a transmission schedule for a device comprises at least one schedule entry corresponding to a promotion targeted for the device.

4. The promotion scheduling process of claim 2, wherein a transmission schedule for a device comprises schedule entries for promotions from different packages.

5. The promotion scheduling process of claim 2, wherein the promotion is identified with a module identifier, the module identifier uniquely identifying promotion content stored in the database.

6. The promotion scheduling process of claim 2, wherein the transmission parameters specified in the schedule entry comprise a package transmission start time, transmission duration, and a network address for selectively receiving promotions from a data transmission.

7. The promotion scheduling process of claim 6, wherein the network address is a multicast address and port number.

8. The promotion scheduling process of claim 2, wherein the transmission parameters specified in the schedule entry comprise a trigger event for initiating reception of promotions from a data transmission.

9. The promotion scheduling process of claim 2, wherein the activation criteria for a promotion specified in the schedule entry comprises a trigger event.

10. The promotion scheduling process of claim 9, wherein the trigger event is a start time.

11. The promotion scheduling process of claim 9, wherein the trigger event is receipt of a start message, the start message directing the device to activate the promotion.

12. The promotion scheduling process of claim 9, wherein the trigger event is capture of a start tag transmitted in the video blanking interval during a program broadcast.

13. The promotion scheduling process of claim 12, wherein the start tag is an ATVEF tag.

14. The promotion scheduling process of claim 9, wherein the trigger event is a channel change event.

15. The promotion scheduling process of claim 9, wherein the trigger event is a power event.

16. The promotion scheduling process of claim 2, wherein a transmission schedule is a stack of data objects, each data object representing a schedule entry.

17. The promotion scheduling process of claim 1, wherein transmitting the customized transmission schedules to the end node devices, further comprises:

generating a schedule message for each of the end node devices targeted for at least one promotion; and

transmitting a customized transmission schedule within a schedule message to the targeted end node device.

18. The promotion scheduling process of claim 17, wherein one or more schedule messages are generated to transmit a transmission schedule to a device.

19. The promotion scheduling process of claim 1, wherein packages are selected in order of earliest package start time.

20. The promotion scheduling process of claim 1, wherein packages are selected at a variable polling rate.

21. The promotion scheduling process of claim 20, wherein the polling rate for selecting packages decreases when the number of packages previously processed remains constant or increases.

22. The promotion scheduling process of claim 20, wherein the polling rate for selecting packages increases when the number of packages previously processed decreases.

23. The promotion scheduling process of claim 20, wherein the polling rate increases when less system resources are available for processing packages.

24. The promotion scheduling process of claim 20, wherein the polling rate decreases when more system resources are available for processing packages.

26. The promotion scheduling process of claim 25, wherein a transmission request is a data object comprising parameters controlling transmission of promotions from a package.

27. The promotion scheduling process of claim 25, wherein a transmission request is generated for the set of packages in order of earliest package start time.

28. The promotion scheduling process of claim 25, wherein generating a transmission request for a selected package, further comprises:

identifying promotions referenced in the package;

determining module identifiers for each of the promotions, a module identifier identifying promotion content in the database selected for transmission; and

adding the module identifiers to the transmission request.

30. The promotion scheduling process of claim 29, wherein determining the bulk data servers to process the transmission request further comprises:

resolving each package into a list of networks hosting end node devices targeted for at least one promotion; and

transmitting the transmission request to each bulk data server serving the networks identified.

25. A promotion scheduling process for initiating data transmissions, comprising:

selecting a set of promotion packages from a database, the selected set of promotions whose transmission schedules have been distributed to targeted end node devices;

generating a transmission request for each selected package; and

transmitting the transmission request to a bulk data server, the bulk data server initiating the data transmission of promotions identified in the set of packages.

29. A promotion scheduling process for initiating data transmissions, comprising:

selecting a set of promotion packages from a database, the selected set of promotions whose transmission schedules have been distributed to targeted end node devices;

generating a transmission request for each selected package;

determining one or more bulk data servers to process the transmission request initiating the data transmission of promotions identified in the set of packages, each bulk data server serving a subnetwork within a multimedia network; and

transmitting the transmission request to the one or more bulk data servers.

31. A promotion scheduling system for generating schedules notifying end node devices in advance of data transfer, comprising:

a promotion manager server;

the promotion manager server selecting a set of promotion packages from a database;

the promotion manager server generating transmission schedules for end node devices from the selected packages, each transmission schedule customized for an individual end node device, the transmission schedules preparing the end node devices for subsequent data transfers in advance; and

the promotion manager server transmitting the customized transmission schedules to the end node devices.

32. A promotion scheduling system for initiating data transmissions, comprising:

a promotion manager server;

a bulk data server;

the promotion manager server selecting a set of promotion packages from a database, the selected set of promotions whose transmission schedules have been distributed to targeted end node devices;

the promotion manager server generating a transmission request for each selected package;

the promotion manager server transmitting the transmission request to the bulk data server; and

the bulk data server initiating the data transmission of promotions identified in the set of packages.

33. A promotion scheduling system for initiating data transmissions, comprising:

a promotion manager server;

one or more bulk data servers;

the promotion manager server selecting a set of promotion packages from a database, the selected set of promotions whose transmission schedules have been distributed to targeted end node devices;

the promotion manager server generating a transmission request for each selected package;

the promotion manager server determining the one or more bulk data servers to process the transmission request initiating the data transmission of promotions identified in the set of packages, each bulk data server serving a subnetwork within a multimedia network; and

the promotion manager server transmitting the transmission request to the one or more bulk data servers.