Subscriber driven media agnostic content delivery across networks

• US 8,234,410 B2
• Filed: 01/04/2008
• Issued: 07/31/2012
• Est. Priority Date: 01/04/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Alexander, Michael E., Ramanathan, Sri, Schaffa, Frank A., Trevathan, Matthew B.
• Primary Examiner(s): BIAGINI, CHRISTOPHER D
• Application Number:
  US11/969,550
• Publication Number:
  US 20090177794A1
• Time in Patent Office: 1,670 Days
• Field of Search: 709/246
• US Class Current: 709/246
• CPC Class Codes: G06F 16/435 Filtering based on additional data, e.g. user or group profiles

Abstract

A system and method is provided to facilitate subscriber driven media agnostic content delivery across same or different networks. The method includes receiving preferences from a sending client and a receiving client and receiving content of a first media type over a network. The method further includes sending the content or a reference to the content to the receiving client in a preferred media type and to a preferred device in accordance with at least one preference of the receiving client. The method also includes notifying at least the receiving client that the content is to be received by the preferred device.

Claims

1. A method, comprising:

receiving preferences from a sending client and a receiving client;

receiving content in a first media type over a network;

sending the content in a second media type or a reference to the content in the second media type, to a first device of the receiving client in accordance with the preferences;

notifying the first device and a second device of the receiving client that the content in the second media type is to be received by the first device in accordance with the preferences, the preferences including a request by the receiving client to receive notifications on the first device and the second device that the content in the second media type is to be received by the first device; and

notifying, by an agent, the sending client that the receiving client has at least one of received the notifications and received the content in the second media type,

wherein the preferences include at least a media size limit.

2. The method of claim 1, further comprising requesting and receiving location information of the receiving client in order to send the content in the second media type or a reference to the content in the second media type, to the first device.

3. The method of claim 1, wherein the preferences include at least:

a list of devices to receive the content in the second media type;

a location preference of the receiving client;

a list of notification types to inform the sending client and/or the receiving client of receipt of the content in the second media type;

a media format (media type) for the receiving client to receive the content in the first media type; and

a request by the receiving client to view same content on multiple devices.

4. The method of claim 1, wherein the first and second devices are IMS (IP Multimedia Subsystem) or non-IMS enabled devices, and the sending uses IMS based core networks and non-IMS based networks, to deliver the content in different media types to the receiving client.

5. The method of claim 1, wherein the sending is subscriber driven media agnostic content delivery across networks and is of a peer to peer distribution and delivery of the content in different media types or supported on a completely wireless broadband based architecture.

6. The method of claim 1, wherein the sending includes routing content in different types over different types of networks and at least one of different protocols and to disparate devices based on the preferences.

7. The method of claim 1, wherein the sending is routed through a Messaging Gateway Framework which supports at least:

XMPP (Extensible Messaging and Presence Protocol);

MMSC (Multimedia Messaging Switching Center);

WAP (Wireless Application Protocol);

SMS (Short Message Service) and SMTP (Simple Mail Transfer Protocol), including out of band notifications;

IMS Handsets via a SIP (Session Initiation Protocol) client;

Web Services (SOAP and REST); and

STB (Set Top Box).

8. The method of claim 7, wherein the preferences are received from the receiving client and the sending client via the Messaging Gateway Framework in any of the protocols.

9. The method of claim 1, further comprising, at least one of:

based on a preference of the receiving client, transcoding the content in the first media type in order for the receiving client to view the content in the second media type, wherein the first media type is different than the second media type; and

converting a protocol of the first media type.

10. The method of claim 1, wherein a service provider performs the steps of claim 1 on a fee or a subscription basis.

11. The method of claim 1, wherein the steps of claim 1 are provided on a computing infrastructure which is at least one of maintained, deployed, supported and created by a service provider.

12. The method of claim 1, wherein:

the notifying the sending client is in accordance with the preferences;

the preferences include a list of notification types to inform the sending client of receipt of the content; and

the preferences include a list of best times to at least one of send and receive the content.

13. The method of claim 1, wherein the sending client and the receiving client update the preferences in a Home Subscriber Service (HSS) Profile Manager when the content in the second media type is of an IMS (IP Multimedia Subsystem) network.

14. The method of claim 13, further comprising receiving the preferences via a Diameter protocol so as to remain synchronized with the HSS Profile Manager.

15. The method of claim 14, further comprising, based on a preference of the receiving client, transcoding the content in the first media type in order for the receiving client to view the content in the second media type, wherein the first media type is different than the second media type.

16. The method of claim 15, wherein the sending client transcodes the content in the first media type in order for the receiving client to view the content in the second media type when resources are available on the sending client.

17. The method of claim 16, wherein each of the notifications comprise a baseline representation of the content in the second media type that is written in Extensible Markup Language (XML) and comprises one or more recipients, a subject, a body, a preview type, an uncompressed type, and a compressed type.

18. A method for sending subscriber driven media agnostic content delivery across different networks, comprising:

parsing, by a computer infrastructure, preferences of a sending client and a receiving client in order to send content in a media type preferred by at least one of the sending client and a receiving client, or a reference to the content in the media type, to a first device of the receiving client; and

notifying the first device and a second device of the receiving client that the content in the media type is to be received by the first device in accordance with the preferences, the preferences including a request by the receiving client to receive notifications on the first device and the second device that the content in the media type is to be received by the first device,

wherein the preferences include at least a list of notification types to inform the sending client of receipt of the content in the media type, and a media size limit.

19. The method of claim 18, wherein the computing infrastructure is operable to request and receive location information of the receiving client in order to send the content in the media type or the reference to the content in the media type, to the first device.

20. The method of claim 18, wherein the computing infrastructure is operable to store the preferences which include at least:

a list of devices to receive the content in the media type;

a location preference of the receiving client;

a list of notification types to inform the receiving client of receipt of the content in the media type; and

a request by the receiving client to view same content on multiple devices.

21. The method of claim 18, wherein the first and second devices are IMS (IP Multimedia Subsystem) or non-IMS enabled devices, and the sending uses IMS based core networks and non-IMS based networks, to deliver content of different media types to the receiving client.

22. The method of claim 18, wherein the computing infrastructure is operable to route content of different types over different types of networks and/or protocols and/or to disparate devices based on the preferences.

23. The method of claim 18, wherein the computing infrastructure is operable to register the preferences with a Home Subscriber Service (HSS) Profile Manager when the content in the media type is of an IMS (IP Multimedia Subsystem) network.

24. The method of claim 18, wherein the computing infrastructure is operable to receive the preferences from the receiving client and the sending client via a Messaging Gateway Framework, regardless of protocol and media type.

25. The method of claim 18, wherein the computing infrastructure is operable to, based on a preference of the receiving client, transcode the content in an original media type in order for the receiving client to view the content in the media type.

26. The method of claim 18, wherein the computing infrastructure is at least one of maintained, deployed, supported and created by a service provider.

27. The method of claim 18, wherein:

the computer infrastructure is operable to notify the sending client that the receiving client has at least one of received a notification of the content and received the content;

the notifying the sending client is in accordance with the preferences; and

the preferences include a list of best times to at least one of send and receive the content.

28. A network infrastructure, comprising at least a computing device comprising an agent which is configured to:

receive and store preferences of a sending client and a receiving client; and

based on the preferences;

convert a first media type sent from the sending client to a second media type requested by the receiving client;

send notifications to a first device and a second device of the receiving client that the second media type is ready to be downloaded on the first device in accordance with the preferences, the preferences including a request by the receiving client to receive the notifications on the first device and the second device; and

send the second media type to the first device which is compatible with the second media type,

wherein the preferences include at least a list of best times to at least one of send and receive the second media type, and a media size limit.

29. The network infrastructure of claim 28, further comprising requesting and receiving location information of the receiving client in order to send content in the second media type or a reference to the content in the second media type, to the first device.

30. The network infrastructure of claim 28, wherein the preferences include at least:

a list of devices to receive content in the second media type;

a location preference of the receiving client;

a list of notification types to inform the sending client and/or the receiving client of receipt of the content in the second media type;

a media format (media type) for the receiving client to receive the content in the first media type; and

a request by the receiving client to view same content on multiple devices.

31. The network infrastructure of claim 28, wherein the receiving and storing of the preferences, the sending of the notifications and the sending of the second media type is routed through a Messaging Gateway Framework which support at least:

XMPP (Extensible Messaging and Presence Protocol);

MMSC (Multimedia Messaging Switching Center);

WAP (Wireless Application Protocol);

SMS (Short Message Service) and SMTP (Simple Mail Transfer Protocol), including out of band notifications;

IMS Handsets via a SIP (Session Initiation Protocol) client;

Web Services (SOAP and REST); and

STB, and

wherein the notifications can be provided via any of the supported Messaging Gateway Framework protocols.

32. The network infrastructure of claim 28, wherein:

the agent is configured to notify the sending client that the receiving client has at least one of received a notification of content and received the content;

the notifying the sending client is in accordance with the preferences; and

the preferences include a list of notification types to inform the sending client of receipt of the content.

33. A computer readable storage medium for managing subscriber driven media agnostic content delivery across networks, the computer readable storage medium comprising:

first program instructions to receive preferences from a sending client and a receiving client;

second program instructions to receive content in a first media type over a network;

third program instructions to send the content in a second media type or a reference to the content in the second media type, to a first device in accordance with the preferences; and

fourth program instructions to notify the first device and a second device of the receiving client that the content in the second media type is to be received by the first device in accordance with the preferences, the preferences including a request by the receiving client to receive notifications on the first device and the second device that the content in the media type is to be received by the first device; and

fifth program instructions to notify the sending client that the receiving client has at least one of received the notifications and received the content in the second media type,

wherein the preferences include at least a media size limit, and

wherein the first, second, third, fourth and fifth program instructions are stored on the computer readable storage medium.

34. The computer readable storage medium of claim 33, wherein:

the notifying the sending client is in accordance with the preferences;

the preferences include a list of notification types to inform the sending client of receipt of the content; and

the preferences include a list of best times to at least one of send and receive the content.

35. A method, comprising:

receiving preferences from a sending client and a receiving client;

receiving content of a first media type over a network;

sending the content in a second media type or a reference to the content in the second media type, to a first device in accordance with the preferences; and

notifying the first device and a second device of the receiving client that the content in the second media type is to be received by the first device in accordance with the preferences, the preferences including a request by the receiving client to receive notifications on the first device and the second device that the content in the second media type is to be received by the first device,

wherein the preferences include at least a request by the receiving client to view same content on multiple devices.