SUBSCRIBER DRIVEN MEDIA AGNOSTIC CONTENT DELIVERY ACROSS NETWORKS

• US 20090177794A1
• Filed: 01/04/2008
• Published: 07/09/2009
• Est. Priority Date: 01/04/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ramanathan, Sri, Schaffa, Frank A., Trevathan, Matthew B., ALEXANDER, Michael E.
• Granted Patent: US 8,234,410 B2
• Time in Patent Office: Days
• US Class Current: 709/237
• 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 of a first media type over a network;

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; and

notifying at least the receiving client that the content is to be received by the preferred device.

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

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

a list of preferred devices to receive the content;

a location preference of the receiving client;

a list of desired notification types to inform the sending client and/or the receiving client of receipt of the content;

a desired media format (media type) for the receiving client to receive the content;

a media size limit; and

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

4. The method of claim 1, wherein the preferred devices are IMS (IP Multimedia Subsystem) or non-IMS enabled devices and the sending uses IMS based core networks and non-IMS based networks, respectively, to deliver the content of 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 one of a peer to peer distribution and delivery of the content and supported on a completely wireless broadband based architecture.

6. The method of claim 1, wherein the sending includes routing the content of 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 one of:

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 order for the receiving client to view the content in the preferred media type, wherein the first media type is different than the preferred 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. A method for sending subscriber driven media agnostic content delivery across different networks, comprising a computer infrastructure being operable to parse preferences of a sending client and a receiving client in order to send content or a reference to the content to the receiving client in a preferred media type and to a preferred device and to notify at least the receiving client that the content is to be received by the preferred device.

13. The method of claim 12, wherein the computing infrastructure is operable to request and receive location information of the receiving client in order to send the content or the reference to the content to the preferred device.

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

a list of preferred devices to receive the content;

a location preference of the receiving client;

a list of desired notification types to inform the sending client and/or the receiving client of receipt of the content;

a desired media format (media type) for the receiving client to receive the content;

a media size limit; and

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

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

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

17. The method of claim 12, wherein the computing infrastructure is operable to register the preferences with a Home Subscriber Service (HSS) Profile Manager in case of IMS content.

18. The method of claim 12, 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.

19. The method of claim 12, wherein the computing infrastructure is operable to, based on a preference of the receiving client, transcode the content in order for the receiving client to view the content in the preferred media type.

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

21. A network infrastructure, comprising at least 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 a notification to the receiving client on a first device that the second media type is ready to be downloaded on a preferred device; and

send the second media type to the preferred device of the receiving client which is compatible with the second media type.

22. The network infrastructure of claim 21, further comprising requesting and receiving location information of the receiving client in order to send the content or a reference to the content to the preferred device.

23. The network infrastructure of claim 21, wherein the preferences include at least one of:

a list of preferred devices to receive the content;

a location preference of the receiving client;

a list of desired notification types to inform the sending client and/or the receiving client of receipt of the content;

a desired media format (media type) for the receiving client to receive the content;

a media size limit; and

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

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

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 notification can be provided via any of the supported Messaging Gateway Framework protocols.

25. A computer program product for managing subscriber driven media agnostic content delivery across networks, the computer program product comprising:

a computer readable media;

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

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

third program instructions to send 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; and

fourth program instructions to notify at least the receiving client that the content is to be received by the preferred device; and

wherein

the first, second, third and fourth program instructions are stored on the computer readable media.