IP Library Patent Application 12417377
Patent Application
App. No. 12/417,377

Methods, Systems, And Computer Program Products For Providing A Mashup Using A Pub/Sub Tuple

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 None
App. No.
12/417,377
Abstract

Methods and systems are described for providing a mashup using a pub/sub tuple. In one aspect, mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple is received. A mashup pub/sub tuple is created including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider. A pub/sub principal is subscribed to the mashup pub/sub tuple. The first content and the second content is provided to the pub/sub principal pursuant to the subscription to the mashup pub/sub tuple.

Claims (102)

1 . A method for providing a mashup using a pub/sub tuple, the method comprising:

receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

creating a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider;

subscribing a pub/sub principal to the mashup pub/sub tuple; and

providing the first content and the second content to the pub/sub principal pursuant to the subscription to the mashup pub/sub tuple,

wherein at least one of the preceding actions is performed on at least one electronic hardware component.

2 . The method of claim 1 wherein receiving mashup information includes receiving one or more messages according to a pub/sub protocol.

3 . The method of claim 1 wherein receiving mashup information identifying a content provider includes receiving a uniform resource identifier (URI) identifying content provided by a content provider.

4 . The method of claim 1 wherein receiving mashup information identifying a content provider includes receiving information identifying a pub/sub client, a hypertext transfer protocol (HTTP) server, an remote procedure call (RPC) server, and a really simple syndication (RSS) service.

5 . The method of claim 1 wherein receiving mashup information includes receiving one or more messages from at least one of a pub/sub principal represented by the existing pub/sub tuple and the identified content provider.

6 . The method of claim 1 wherein creating a mashup pub/sub tuple includes establishing a subscription to the existing pub/sub tuple for the mashup pub/sub tuple based on the subscription information and obtaining the first content from the existing pub/sub tuple pursuant to the subscription to the existing pub/sub tuple.

7 . The method of claim 1 wherein creating a mashup pub/sub tuple includes providing for obtaining the second content from the content provider according to a synchronous protocol.

8 . The method of claim 1 wherein creating a mashup pub/sub tuple includes providing for polling the content provider to obtain the second content.

9 . The method of claim 1 wherein creating a mashup pub/sub tuple includes:

creating or updating a first one of the first and second elements; and

creating or updating a second one of the first and second elements based on information obtained from the creating or updating of the first one of the first and second elements.

10 . The method of claim 1 wherein at least one of the first content and the second content is metadata of a resource for locating the resource.

11 . The method of claim 1 wherein subscribing a pub/sub principal to the mashup pub/sub tuple includes receiving a pub/sub subscribe message.

12 . The method of claim 1 wherein subscribing a pub/sub principal to the mashup pub/sub tuple includes subscribing a pub/sub principal represented by the existing pub/sub tuple.

13 . The method of claim 1 wherein subscribing a pub/sub principal to the mashup pub/sub tuple includes determining whether to subscribe the pub/sub principal to the mashup pub/sub tuple based on information obtained from creating or updating the first and second elements.

14 . The method of claim 1 wherein providing the first content and the second content to the pub/sub principal includes sending a pub/sub notification message to the pub/sub principal.

15 . The method of claim 1 wherein providing the first content and the second content to the pub/sub principal includes translating the contents into a format suitable for presentation by a client of the pub/sub principal.

16 . A method for providing a mashup using a pub/sub tuple, the method comprising:

receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

generating a pub/sub message configured to provide a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider; and

providing the generated pub/sub message to a pub/sub service for providing the first content and second content to a pub/sub principal pursuant to a subscription to the mashup pub/sub tuple;

wherein at least one of the preceding actions is performed on at least one electronic hardware component.

17 . The method of claim 16 wherein receiving mashup information includes receiving one or more messages according to a pub/sub protocol.

18 . The method of claim 16 wherein receiving mashup information identifying a content provider includes receiving a uniform resource identifier (URI) identifying content provided by a content provider.

19 . The method of claim 16 wherein receiving mashup information identifying a content provider includes receiving information identifying a pub/sub client, an HTTP server, an RPC server, and an RSS service.

20 . The method of claim 16 wherein receiving mashup information includes receiving one or more messages from at least one of a pub/sub principal represented by the existing pub/sub tuple and the identified content provider

21 . The method of claim 16 wherein generating a pub/sub publish message configured to provide a mashup pub/sub tuple includes establishing a subscription to the existing pub/sub tuple for the mashup pub/sub tuple based on the subscription information and obtaining the first content from the existing pub/sub tuple pursuant to the subscription to the existing pub/sub tuple.

22 . The method of claim 16 wherein generating a pub/sub publish message configured to provide a mashup pub/sub tuple includes providing for obtaining the second content from the content provider according to a synchronous protocol.

23 . The method of claim 16 wherein generating a pub/sub publish message configured to provide a mashup pub/sub tuple includes providing for polling the content provider to obtain the second content.

24 . The method of claim 16 wherein generating a pub/sub publish message configured to provide a mashup pub/sub tuple includes:

creating or updating a first one of the first and second elements; and

creating or updating a second one of the first and second elements based on information obtained from the creating or updating of the first one of the first and second elements.

25 . The method of claim 16 wherein at least one of the first content and the second content is metadata of a resource for locating the resource.

26 . The method of claim 16 wherein providing the generated pub/sub message to a pub/sub service includes sending a pub/sub publish message to the pub/sub service.

27 . The method of claim 16 wherein providing the generated pub/sub message to a pub/sub service includes sending a pub/sub subscribe message to the pub/sub service.

28 . The method of claim 16 wherein providing the generated pub/sub publish message to a pub/sub service.

29 . A system for providing a mashup using a pub/sub tuple, the system comprising:

means for receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

means for creating a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider;

means for subscribing a pub/sub principal to the mashup pub/sub tuple; and

means for providing the first content and the second content to the pub/sub principal pursuant to the subscription to the mashup pub/sub tuple;

wherein at least one of the means includes at least one electronic hardware component.

30 . A system for providing a mashup using a pub/sub tuple, the system comprising system components including:

a message router component configured to receive mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

a mashup handler component configured to create a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider;

a subscription handler component configured to subscribe a pub/sub principal to the mashup pub/sub tuple; and

a notification handler component configured to provide the first content and the second content to the pub/sub principal pursuant to the subscription to the mashup pub/sub tuple;

wherein at least one of the system components includes at least one electronic hardware component.

31 . The system of claim 30 wherein the message router component is configured to receive mashup information by receiving one or more messages according to a pub/sub protocol.

32 . The system of claim 30 wherein the message router component is configured to receive mashup information identifying a content provider by receiving a uniform resource identifier (URI) identifying content provided by a content provider.

33 . The system of claim 30 wherein the message router component is configured to receive mashup information identifying a content provider by receiving information identifying a pub/sub client, an HTTP server, an RPC server, and an RSS service.

34 . The system of claim 30 wherein the message router component is configured to receive mashup information by receiving one or more messages from at least one of a pub/sub principal represented by the existing pub/sub tuple and the identified content provider.

35 . The system of claim 30 wherein the mashup handler component is configured to create a mashup pub/sub tuple by establishing a subscription to the existing pub/sub tuple for the mashup pub/sub tuple based on the subscription information and obtaining the first content from the existing pub/sub tuple pursuant to the subscription to the existing pub/sub tuple.

36 . The system of claim 30 wherein the mashup handler component is configured to create a mashup pub/sub tuple by providing for obtaining the second content from the content provider according to a synchronous protocol.

37 . The system of claim 30 wherein the mashup handler component is configured to create a mashup pub/sub tuple by providing for polling the content provider to obtain the second content.

38 . The system of claim 30 wherein the mashup handler component is configured to create a mashup pub/sub tuple by:

creating or updating a first one of the first and second elements; and

creating or updating a second one of the first and second elements based on information obtained from the creating or updating of the first one of the first and second elements.

39 . The system of claim 30 wherein at least one of the first content and the second content is metadata of a resource for locating the resource.

40 . The system of claim 30 wherein the subscription handler component is configured to subscribe a pub/sub principal to the mashup pub/sub tuple by receiving a pub/sub subscribe message.

41 . The system of claim 30 wherein the subscription handler component is configured to subscribe a pub/sub principal to the mashup pub/sub tuple by subscribing a pub/sub principal represented by the existing pub/sub tuple.

42 . The system of claim 30 wherein the subscription handler component is configured to subscribe a pub/sub principal to the mashup pub/sub tuple by determining whether to subscribe the pub/sub principal to the mashup pub/sub tuple based on information obtained from creating or updating the first and second elements.

43 . The system of claim 30 wherein the notification handler component is configured to provide the first content and the second content to the pub/sub principal by sending a pub/sub notification message to the pub/sub principal.

44 . The system of claim 30 wherein the notification handler component is configured to provide the first content and the second content to the pub/sub principal by translating the contents into a format suitable for presentation by a client of the pub/sub principal.

45 . A system for providing a mashup using a pub/sub tuple, the system comprising:

means for receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

means for generating a pub/sub message configured to provide a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider; and

means for providing the generated pub/sub message to a pub/sub service for providing the first content and second content to a pub/sub principal pursuant to a subscription to the mashup pub/sub tuple;

wherein at least one of the means includes at least one electronic hardware component.

46 . A system for providing a mashup using a pub/sub tuple, the system comprising system components including:

a mashup service component configured to receive mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

a user agent component configured to generate a pub/sub message configured to provide a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider; and

a protocol agent component configured to provide the generated pub/sub message to a pub/sub service for providing the first content and second content to a pub/sub principal pursuant to a subscription to the mashup pub/sub tuple;

wherein at least one of the system components includes at least one electronic hardware component.

47 . The system of claim 46 wherein the mashup service component is configured to receive mashup information by receiving one or more messages according to a pub/sub protocol.

48 . The system of claim 46 wherein the mashup service component is configured to receive mashup information identifying a content provider by receiving a uniform resource identifier (URI) identifying content provided by a content provider.

49 . The system of claim 46 wherein the mashup service component is configured to receive mashup information identifying a content provider by receiving information identifying a pub/sub client, an HTTP server, an RPC server, and an RSS service.

50 . The system of claim 46 wherein the mashup service component is configured to receive mashup information by receiving one or more messages from at least one of a pub/sub principal represented by the existing pub/sub tuple and the identified content provider

51 . The system of claim 46 wherein the user agent component is configured to generate a pub/sub publish message configured to provide a mashup pub/sub tuple by establishing a subscription to the existing pub/sub tuple for the mashup pub/sub tuple based on the subscription information and obtain the first content from the existing pub/sub tuple pursuant to the subscription to the existing pub/sub tuple.

52 . The system of claim 46 wherein the user agent component is configured to generate a pub/sub publish message configured to provide a mashup pub/sub tuple by providing for obtaining the second content from the content provider according to a synchronous protocol.

53 . The system of claim 46 wherein the user agent component is configured to generate a pub/sub publish message configured to provide a mashup pub/sub tuple by providing for polling the content provider to obtain the second content.

54 . The system of claim 46 wherein the user agent component is configured to generate a pub/sub publish message configured to provide a mashup pub/sub tuple by:

creating or updating a first one of the first and second elements; and

creating or updating a second one of the first and second elements based on information obtained from the creating or updating of the first one of the first and second elements.

55 . The system of claim 46 wherein at least one of the first content and the second content is metadata of a resource for locating the resource.

56 . The system of claim 46 wherein the protocol agent component is configured to provide the generated pub/sub message to a pub/sub service by sending a pub/sub publish message to the pub/sub service.

57 . The system of claim 46 wherein the protocol agent component is configured to provide the generated pub/sub message to a pub/sub service by sending a pub/sub subscribe message to the pub/sub service.

58 . The system of claim 46 wherein the protocol agent component is configured to provide the generated pub/sub publish message to a pub/sub service.

59 . A computer readable medium storing a computer program, executable by a machine, for providing a mashup using a pub/sub tuple, the computer program comprising executable instructions for:

receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

creating a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider;

subscribing a pub/sub principal to the mashup pub/sub tuple; and

providing the first content and the second content to the pub/sub principal pursuant to the subscription to the mashup pub/sub tuple.

60 . A computer readable medium storing a computer program, executable by a machine, for providing a mashup using a pub/sub tuple, the computer program comprising executable instructions for:

receiving mashup information identifying a content provider and having subscription information for creating a subscription to an existing pub/sub tuple;

generating a pub/sub message configured to provide a mashup pub/sub tuple including a first element including information for obtaining first content from the existing pub/sub tuple based on the subscription information and a second element including information for obtaining second content from the identified content provider; and

providing the generated pub/sub message to a pub/sub service for providing the first content and second content to a pub/sub principal pursuant to a subscription to the mashup pub/sub tuple.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 11, 2017
From: SWIFT CREEK SYSTEMS, LLC
To: SCENERA TECHNOLOGIES, LLC
Reel/Frame 044830/0065 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 22, 2009
From: MORRIS, ROBERT P.
To: SWIFT CREEK SYSTEMS, LLC
Reel/Frame 022577/0750 →