Protocol extensions to increase reliability of bulk data transmissions

• US 20020065929A1
• Filed: 11/02/2001
• Published: 05/30/2002
• Est. Priority Date: 11/28/2000
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Navic Systems, Inc. (Microsoft Corporation)
• Inventors: Kamentsky, Lee, Hall, Peter, Kanojia, Chaitanya, LaCroix, John
• Application Number:
  US10/004,223
• Publication Number:
  US 20020065929A1
• Time in Patent Office: Days
• US Class Current: 709/231
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A multimedia network involves sending an initial schedule message prior to broadcast or multicast of a content file. The content file could be a promotion or other file that must be efficiently sent to a large number of end node devices, such as television set top boxes. The schedule message contains at least a bulk transfer end time for the content file so that the end node devices are aware of when the later bulk data transmission of the content file should be completed. The schedule message may contain other parameters such as promotion identification, message start time, duration, frequency, multicast address and port number. The bulk message containing the promotion is then sent using an efficient bulk transfer messaging technique, such as a multicast Universal Data Protocol (UDP) message which does not require acknowledgment of individual packets or individual addresses of the end node devices to be maintained. At the expected end of the transmission time, a determination is made as to whether or not the expect bulk message has been received. If not, the network device reports a message failure to the original scheduling process, which in turn retransmits the promotion package to the previously failing network device via a reliable transport protocol, such as TCP.

Claims

1. A method for content push synchronization for bulk data transfer in a multimedia network, comprising:

scheduling transmission of bulk data content;

notifying a plurality of end node devices of the scheduled bulk data transmission, such notification including information indicating an expected end time for the scheduled transmission;

transmitting the bulk data content via broadcast;

attempting to selectively receive a subset of the content during the scheduled transmission;

at the expected end time for the scheduled transmission, determining if the bulk data content was received as expected; and

if not received as expected, sending a failure indication.

2. A method as in claim 1 additionally comprising:

retransmitting the bulk content to the failing network device via a unicast.

3. A method as in claim 2 wherein the failure indication indicates a subset of unreceived content and, transmitting only the indicated subset.

4. A method as in claim 1 wherein the step of transmitting the bulk content additionally comprising using a unicast UDP protocol.

5. A method as in claim 1 wherein the step of notifying the end node devices includes an expected start time and duration information.

6. A method as in claim 1 wherein the step of notifying the plurality of end node devices comprises:

delivering transmission schedules to the plurality of end node devices prior to the scheduled transmissions of bulk content.

7. A method as in claim 1 wherein the content control data comprise destination port addresses and data transmission times for the subset of content.

8. A method as in claim 4, wherein the step of selectively receiving content comprises:

listening to the scheduled transmissions for the subset of content on the destination port addresses at the data transmission times;

selecting the subset of content during the scheduled transmissions; and

receiving the subset of content.

9. A method as in claim 4 wherein the destination port addresses are multicast port addresses.

10. A method as in claim 4 wherein the destination port addresses are broadcast port addresses.

11. A method as in claim 1 wherein the content is a plurality of promotions.

12. A method as in claim 1 wherein the scheduled transmissions are scheduled multicast transmissions.

13. A method as in claim 1 wherein the scheduled transmissions are scheduled broadcast transmissions.

14. A method as in claim 1 wherein the content is transmitted multiple times during the scheduled transmissions to ensure that the plurality of end node devices receive the subset of content.

15. A method as in claim 3 wherein a failure indication is sent again if the retransmission fails.

16. A method as in claim 5 wherein a module ID is included in the failure notification.