IP Library › Granted Patent US 8,495,228
Granted Patent B2
US 8,495,228 · App. 12/104,304 · Granted Jul 23, 2013

System and method for optimizing download user service delivery to roaming clients

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,495,228
App. No.
12/104,304
Granted
Jul 23, 2013
Kind
B2
Abstract

A system and method for providing MBMS content distribution using unicast bearers. According to various embodiments, MBMS download user services are delivered to pieces of user equipment by delivering a FLUTE file delivery table via an OMA Push message. One of a number of different additional actions may be used in the delivery of the MBMS download user services. These actions include (1) making a single HTTP GET request using simple URL-encoding format to retrieve all files of the FDT; (2) making a single HTTP GET request using “group” field of FDT in URL-encoding to retrieve a logical group of files of the FDT; (3) making pipelined HTTP GET requests where each HTTP GET request retrieves at least one file of the FDT; (4) making serialized HTTP GET requests where each HTTP GET request retrieves at least one file of the FDT; (5) making pipelined HTTP GET requests where each HTTP GET request retrieves at least one logical group of files of the FDT; (6) making serialized HTTP GET requests where each HTTP GET request retrieves at least one logical group of files of the FDT; (7) delivering the serviceID of the MBMS user service in the above mentioned OMA PUSH message but not including the serviceID in the FLUTE FDT; (8) an HTTP request to de-register the MBMS UE from the BM-SC for stopping the unicast delivery of the MBMS download user service; and (9) delivering the FDT Instance ID of the FDT Instance in an OMA Push message.

Claims (92)

1. A method, comprising:

registering with one of a server and a broadcast multicast switching center;

receiving a push message according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier;

using the service identifier to identify a multimedia broadcast multicast service user service;

identifying one or more files to be downloaded from the multimedia broadcast multicast service user service using a file delivery table instance; and

fetching at least one of the one or more files using at least one HTTP GET request.

2. The method of claim 1 , wherein the at least one of the one or more files comprises all files identified in the file delivery table instance, and wherein all of the files in the file delivery table instance are fetched using a single HTTP GET request.

3. The method of claim 1 , wherein the at least one of the one or more files comprises a logical group of files, and wherein the logical group of files are fetched using a single HTTP GET request.

4. The method of claim 1 , wherein the at least one of the one or more files comprises a single file, and wherein the single file is fetched using a single HTTP GET request.

5. The method of claim 1 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the multiple unrelated files are fetched using multiple HTTP GET requests.

6. The method of claim 1 , wherein the at least one file of the one or more files comprises multiple logical groups of files and wherein the multiple logical groups of files are fetched using multiple HTTP GET requests.

7. The method of claim 1 , wherein the at least one file comprises a combination of multiple unrelated files and multiple logical groups of files, and wherein the combination is fetched using multiple HTTP GET requests.

8. The method of claim 1 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the multiple unrelated files are fetched using a single HTTP GET request.

9. The method of claim 1 , wherein the at least one of the one or more files comprises multiple logical groups of files, and wherein the multiple logical groups of files are fetched using a single HTTP GET request.

10. The method of claim 1 , wherein the at least one of the one or more files comprises at least one unrelated file and at least one logical group of files, and wherein the at least one unrelated file and the at least one logical group of files are fetched using a single HTTP GET request.

11. The method of claim 1 , further comprising transmitting an HTTP request to deregister from the broadcast multicast switching center.

12. A non-transitory memory including computer-executable instructions which, when executed by a processor, cause an apparatus to

register with one of a server and a broadcast multicast switching center;

receive a push message according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier;

use the service identifier to identify a multimedia broadcast multicast service user service;

identify one or more files to be downloaded from the multimedia broadcast multicast service user service using the file delivery table; and

fetch at least one of the one or more files using at least one HTTP GET request.

13. An apparatus, comprising:

a processor; and

memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus at least to:

register with one of a server and a broadcast multicast switching center;

receive a push message according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier;

use the service identifier to identify a multimedia broadcast multicast service user service;

identify one or more files to be downloaded from the multimedia broadcast multicast service user service using the file delivery table instance; and

fetch at least one of the one or more files using at least one HTTP GET request.

14. The apparatus of claim 13 , wherein the at least one of the one or more files comprises all files identified in the file delivery table instance, and wherein all of the files in the file delivery table instance are fetched using a single HTTP GET request.

15. The apparatus of claim 13 , wherein the at least one of the one or more files comprises a logical group of files, and wherein the logical group of files are fetched using a single HTTP GET request.

16. The apparatus of claim 13 , wherein the at least one of the one or more files comprises a single file, and wherein the single file is fetched using a single HTTP GET request.

17. The apparatus of claim 13 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the multiple unrelated files are fetched using multiple HTTP GET requests.

18. The apparatus of claim 13 , wherein the at least one of the one or more files comprises multiple logical groups of files and wherein the multiple logical groups of files are fetched using multiple HTTP GET requests.

19. The apparatus of claim 13 , wherein the at least one of the one or more files comprises a combination of multiple unrelated files and multiple logical groups of files, and wherein the combination is fetched using multiple HTTP GET requests.

20. The apparatus of claim 13 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the multiple unrelated files are fetched using a single HTTP GET request.

21. The apparatus of claim 13 , wherein the at least one of the one or more files comprises multiple logical groups of files, and wherein the multiple logical groups of files are fetched using a single HTTP GET request.

22. The apparatus of claim 13 , wherein the at least one of the one or more files comprises at least one unrelated file and at least one logical group of files, and wherein the at least one unrelated file and the at least one logical group of files are fetched using a single HTTP GET request.

23. The apparatus of claim 13 , wherein the memory and computer program code are further configured to, with the processor, cause the apparatus at least to transmit an HTTP request to deregister from the broadcast multicast switching center.

24. An apparatus, comprising:

means for registering with one of a server and a broadcast multicast switching center;

means for receiving a push message according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier;

means for using the service identifier to identify a multimedia broadcast multicast service user service of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier;

means for identifying one or more files to be downloaded from the multimedia broadcast multicast service user service using the file delivery table instance; and

means for fetching at least one of the one or more files using at least one HTTP GET request.

25. The apparatus of claim 24 , wherein the at least one of the one or more files is fetched using a single HTTP GET request.

26. The apparatus of claim 24 , wherein the at least one of the one or more files is fetched using multiple HTTP GET requests.

27. A method, comprising:

transmitting a push message to a registered device according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier, and the service identifier identifying a multimedia broadcast multicast service user service;

receiving a fetch request for one or more files from the registered device, the fetch request comprising at least one HTTP GET request; and

providing at least one of the one or more files in accordance with the at least one HTTP GET request.

28. The method of claim 27 , wherein the at least one of the one or more files comprises all files identified in a file delivery table instance, and wherein the fetch request comprises a single HTTP GET request.

29. The method of claim 27 , wherein the at least one of the one or more files comprises a logical group of files, and wherein the fetch request comprises a single HTTP GET request.

30. The method of claim 27 , wherein the at least one of the one or more files comprises a single file, and wherein the fetch request comprises a single HTTP GET request.

31. The method of claim 27 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the fetch request comprises multiple HTTP GET requests.

32. The method of claim 27 , wherein the at least one of the one or more files comprises multiple logical groups of files and wherein the fetch request comprises multiple HTTP GET requests.

33. The method of claim 27 , wherein the at least one of the one or more files comprises a combination of multiple unrelated files and multiple logical groups of files, and wherein the fetch request comprises multiple HTTP GET requests.

34. The method of claim 27 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the fetch request comprises a single HTTP GET request.

35. The method of claim 27 , wherein the at least one of the one or more files comprises multiple logical groups of files, and wherein the fetch request comprises a single HTTP GET request.

36. The method of claim 27 , wherein the at least one of the one or more files comprises at least one file and at least one logical group of files, and wherein the fetch request comprises a single HTTP GET request.

37. The method of claim 27 , further comprising:

receiving a HTTP request from the registered device to have the registered device deregistered; and

deregistering the registered device.

38. A non-transitory memory including computer-executable instructions which, when executed by a processor, cause an apparatus to:

transmit a push message to a registered device according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier, and the service identifier identifying a multimedia broadcast multicast service user service;

receive a fetch request for one or more files from the registered device, the fetch request comprising at least one HTTP GET request; and

provide at least one of the one or more files in accordance with the at least one HTTP GET request.

39. An apparatus, comprising:

a processor; and

memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus at least to:

transmit a push message to a registered device according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier, and the service identifier identifying a multimedia broadcast multicast service user service;

receive a fetch request for one or more files from the registered device, the fetch request comprising at least one HTTP GET request; and

provide at least one of the one or more files in accordance with the at least one HTTP GET request.

40. The apparatus of claim 39 , wherein the at least one of the one or more files comprises all files identified in a file delivery table instance, and wherein the fetch request comprises a single HTTP GET request.

41. The apparatus of claim 39 , wherein the at least one of the one or more files comprises a logical group of files, and wherein the fetch request comprises a single HTTP GET request.

42. The apparatus of claim 39 , wherein the at least one of the one or more files comprises a single file, and wherein the fetch request comprises a single HTTP GET request.

43. The apparatus of claim 39 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the fetch request comprises multiple HTTP GET requests.

44. The apparatus of claim 39 , wherein the at least one of the one or more files comprises multiple logical groups of files and wherein the fetch request comprises multiple HTTP GET requests.

45. The apparatus of claim 39 , wherein the at least one of the one or more files comprises a combination of multiple unrelated files and multiple logical groups of files, and wherein the fetch request comprises multiple HTTP GET requests.

46. The apparatus of claim 39 , wherein the at least one of the one or more files comprises multiple unrelated files, and wherein the fetch request comprises a single HTTP GET request.

47. The apparatus of claim 39 , wherein the at least one of the one or more files comprises multiple logical groups of files, and wherein the fetch request comprises a single HTTP GET request.

48. The apparatus of claim 39 , wherein the at least one of the one or more files comprises at least one unrelated file and at least one logical group of files, and wherein the fetch request comprises a single HTTP GET request.

49. The apparatus of claim 39 , wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus at least to:

receive a HTTP request from the registered device to have the registered device deregistered; and

deregister the registered device.

50. An apparatus, comprising:

means for transmitting a push message to a registered device according to a push protocol, the push message comprising a file delivery table instance identifier and a service identifier of a multimedia broadcast multicast service protocol, the service identifier being separate data from a file delivery table instance identified by the file delivery table instance identifier, and the service identifier identifying a multimedia broadcast multicast service user service;

means for receiving a fetch request for one or more files from the registered device, the fetch request comprising at least one HTTP GET request; and

means for providing at least one of the one or more files in accordance with the at least one HTTP GET request.

51. The apparatus of claim 50 , wherein the fetch request comprises a single HTTP GET request.

52. The apparatus of claim 50 , wherein the fetch request comprises multiple HTTP GET requests.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 1, 2015
From: NOKIA CORPORATION
To: NOKIA TECHNOLOGIES OY
Reel/Frame 035544/0616 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2008
From: BOUAZIZI, IMED; VEDANTHAM, RAMAKRISHNA
To: NOKIA CORPORATION
Reel/Frame 021950/0579 →