System and method for data transmission and reception

• US 20060173921A1
• Filed: 11/17/2003
• Published: 08/03/2006
• Est. Priority Date: 11/20/2002
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Jalonen, Esa
• Application Number:
  US10/536,044
• Publication Number:
  US 20060173921A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1101 Session protocols
• 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/70 Media network packetisation
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Systems and methods for file transmission and reception that involve augmenting protocols such as real time protocol (RTP), a protocol for transmitting and receiving real-time data such as audio, video and simulation data, so that they may be used for file transmission and reception. Further systems and methods for file transmission and reception allow for one or more files to be transmitted for presentation in synchrony with media such as audio, video, or the like.

Claims

1. A method for transmitting a file, comprising:

dividing said file into a plurality of blocks;

transmitting to a recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node.

2. The method of claim 1, wherein said each of said custom metadata headers contains a file structure location indication.

3. The method of claim 1, wherein said each of said custom metadata headers contains a file name.

4. The method of claim 1, wherein said each of said custom metadata headers contains a file size.

5. The method of claim 1, wherein said each of said custom metadata headers contains a sequence number.

6. The method of claim 1, wherein said each of said custom metadata headers contains a content-offset indication.

7. The method of claim 1, wherein said each of said custom metadata headers contains a block size indication.

8. A method for transmission of a file, comprising:

dividing said file into a plurality of blocks;

transmitting to a recipient node a media presentation, wherein first timing data is transmitted with said media presentation;

transmitting to said recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks, each packet further containing second timing data;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node; and

wherein said first timing data and said second timing data are employed in synchronized presentation of said file and said media presentation at said recipient node.

9. The method of claim 8, wherein said each of said custom metadata headers contains a file structure location indication.

10. The method of claim 8, wherein said each of said custom metadata headers contains a file name.

11. The method of claim 8, wherein said each of said custom metadata headers contains a file size.

12. The method of claim 8, wherein said each of said custom metadata headers contains a sequence number.

13. The method of claim 8, wherein said each of said custom metadata headers contains a content-offset indication.

14. The method of claim 8, wherein said each of said custom metadata headers contains a block size indication.

15. A method for file transmission, comprising:

receiving from a recipient node a request for a media presentation;

consulting a store correlating media presentations and files to determine a file associated with said media presentation.

dividing said file into a plurality of blocks;

transmitting to said recipient node said media presentation, wherein first timing data is transmitted with said media presentation;

transmitting to said recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks, each packet further containing second timing data;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node; and

wherein said first timing data and said second timing data are employed in synchronized presentation of said file and said media presentation at said recipient node.

16. The method of claim 15, wherein said each of said custom metadata headers contains a file structure location indication.

17. The method of claim 15, wherein said each of said custom metadata headers contains a file name.

18. The method of claim 15, wherein said each of said custom metadata headers contains a file size.

19. The method of claim 15, wherein said each of said custom metadata headers contains a sequence number.

20. The method of claim 15, wherein said each of said custom metadata headers contains a content-offset indication.

21. The method of claim 15, wherein said each of said custom metadata headers contains a block size indication.

22. A system for transmitting a file, comprising:

a memory having program code stored therein; and

a processor operatively connected to said memory for carrying out instructions in accordance with said stored program code;

wherein said program code, when executed by said processor, causes said processor to perform the steps of;

dividing said file into a plurality of blocks;

transmitting to a recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node.

23. The system of claim 22, wherein said each of said custom metadata headers contains a file structure location indication.

24. The system of claim 22, wherein said each of said custom metadata headers contains a file name.

25. The system of claim 22, wherein said each of said custom metadata headers contains a file size.

26. The system of claim 22, wherein said each of said custom metadata headers contains a sequence number.

27. The system of claim 22, wherein said each of said custom metadata headers contains a content-offset indication.

28. The system of claim 22, wherein said each of said custom metadata headers contains a block size indication.

29. A system for transmission of a file, comprising:

a memory having program code stored therein; and

a processor operatively connected to said memory for carrying out instructions in accordance with said stored program code;

wherein said program code, when executed by said processor, causes said processor to perform the steps of;

dividing said file into a plurality of blocks;

transmitting to a recipient node a media presentation, wherein first timing data is transmitted with said media presentation;

transmitting to said recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks, each packet further containing second timing data;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node; and

wherein said first timing data and said second timing data are employed in synchronized presentation of said file and said media presentation at said recipient node.

30. The system of claim 29, wherein said each of said custom metadata headers contains a file structure location indication.

31. The system of claim 29, wherein said each of said custom metadata headers contains a file name.

32. The system of claim 29, wherein said each of said custom metadata headers contains a file size.

33. The system of claim 29, wherein said each of said custom metadata headers contains a sequence number.

34. The system of claim 29, wherein said each of said custom metadata headers contains a content-offset indication.

35. The system of claim 29, wherein said each of said custom metadata headers contains a block size indication.

36. A system for file transmission, comprising:

a memory having program code stored therein; and

a processor operatively connected to said memory for carrying out instructions in accordance with said stored program code;

wherein said program code, when executed by said processor, causes said processor to perform the steps of;

receiving from a recipient node a request for a media presentation;

consulting a store correlating media presentations and files to determine a file associated with said media presentation.

dividing said file into a plurality of blocks;

transmitting to said recipient node said media presentation, wherein first timing data is transmitted with said media presentation;

transmitting to said recipient node a plurality of real time protocol packets, each packet containing at least one of said blocks, each packet further containing second timing data;

wherein each of said packets contains a custom metadata header, the custom metadata headers allowing for reconstruction of said file at said recipient node; and

wherein said first timing data and said second timing data are employed in synchronized presentation of said file and said media presentation at said recipient node.

37. The system of claim 36, wherein said each of said custom metadata headers contains a file structure location indication.

38. The system of claim 36, wherein said each of said custom metadata headers contains a file name.

39. The system of claim 36, wherein said each of said custom metadata headers contains a file size.

40. The system of claim 36, wherein said each of said custom metadata headers contains a sequence number.

41. The system of claim 36, wherein said each of said custom metadata headers contains a content-offset indication.

42. The system of claim 36, wherein said each of said custom metadata headers contains a block size indication.