Data feed management

• US 8,713,149 B2
• Filed: 08/29/2011
• Issued: 04/29/2014
• Est. Priority Date: 08/29/2011
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Shkapenyuk, Vladislav, Johnson, Theodore, Srivastava, Divesh
• Primary Examiner(s): NGUYEN, PHUOC H
• Application Number:
  US13/219,744
• Publication Number:
  US 20130054769A1
• Time in Patent Office: 974 Days
• Field of Search: 709/203, 709/223, 709/226
• US Class Current: 709/223
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

The present disclosure is directed to systems, methods, and computer-readable storage media for data feed management. Data feeds can be received at one or more landing directories associated with a feed management system. The feed management system can be configured to map the data feeds in the landing directories to one or more subscribers, and the data feeds can be moved to one or more staging directories associated with the subscribers. The data feeds can be delivered to the one or more subscribers from the staging directories. Receipts indicating delivery of the data feeds can be stored by the feed management system. The feed management system can be configured to manage data feeds, landing directories, and staging directories.

Claims

1. A method comprising:

receiving, at a processor executing data feed analyzer, a data feed at a landing directory associated with a feed management system;

mapping, by the processor, the data feed at the landing directory to a subscriber, wherein mapping the data feed comprises determining if the landing directory is associated with the subscriber;

if a determination is made that the landing directory is associated with the subscriber, determining, by the processor, if matching the subscriber to the landing directory corresponds to a false positive match by

analyzing, by the processor, the data feed,

comparing, by the processor, the data feed to a further data feed in a matched staging directory associated with the matched subscriber, and

determining, by the processor, that the data feed and the further data feed do not share a filename format and a data structure;

if a determination is made that the landing directory is not associated with the subscriber, determining, by the processor, if the failure to match the subscriber to the landing directory corresponds to a false negative;

moving, by the processor, the data feed to a staging directory associated with the subscriber; and

attempting, by the processor, to deliver the data feed to the subscriber via the staging directory.

2. The method of claim 1, further comprising in response to detecting delivery of the data feed to the subscriber:

storing data indicating delivery of the data feed; and

archiving the data feed.

3. The method of claim 2, wherein the data feed is archived at an archiver in communication with the feed management system.

4. The method of claim 1, further comprising in response to detecting a failed delivery of the data feed, placing the data feed in a delivery queue associated with the subscriber for another delivery attempt.

5. The method of claim 1, further comprising creating a recommendation for the matched subscriber in response to determining that the matched subscriber corresponds to the false positive match, the recommendation comprising a suggestion to remove an association associating the data feed with the matched subscriber.

6. The method of claim 5, further comprising determining if the data feed corresponds to a new data feed.

7. The method of claim 1, wherein determining if failure to identify the matched subscriber corresponds to the false negative comprises:

analyzing the data feed;

comparing the data feed to a further data feed in a further staging directory associated with a further subscriber; and

determining that the data feed and the further data feed share a filename format and a data structure.

8. The method of claim 7, further comprising creating a recommendation for the subscriber in response to determining that the failure to identify the matched subscriber corresponds to the false negative, the recommendation comprising a suggestion to add an association associating the data feed with the further staging directory.

9. The method of claim 1, further comprising moving the data feed to the matched staging directory, in response to determining that the matched staging directory does not correspond to the false positive match.

10. A system comprising:

a processor; and

a memory that stores computer executable instructions that, when executed by the processor, cause the processor to perform comprising;

receiving a data feed at a landing directory associated with a feed management system;

mapping the data feed at the landing directory to a subscriber in communication with the feed management system, wherein mapping the data feed comprises determining if the landing directory is associated with the subscriber;

if a determination is made that the landing directory is associated with the subscriber, determining if matching the subscriber to the landing directory corresponds to a false positive match by

analyzing the data feed,

comparing the data feed to a further data feed in a matched staging directory associated with the matched subscriber, and

determining that the data feed and the further data feed do not share a filename format and a data structure;

if a determination is made that the landing directory is not associated with the subscriber, determining, by the processor, if the failure to match the subscriber to the landing directory corresponds to a false negative;

moving the data feed to a staging directory associated with the subscriber;

adding the data feed to a delivery queue associated with the subscriber;

attempting to deliver the data feed to the subscriber via the staging directory;

in response to detecting a failure to deliver the data feed to the subscriber, retaining the data feed in the delivery queue; and

in response to detecting delivery of the data feed to the subscriber, storing a receipt comprising data indicating delivery of the data feed.

11. The system of claim 10, further comprising instructions that, when executed by the processor, cause the processor to perform operations further comprising:

archiving the data feed at the archiver in communication with the feed management system;

receiving a subscription request from a further subscriber; and

providing the data feed to the subscriber, in response to receiving the subscription request.

12. The system of claim 10, further comprising instructions that, when executed by the processor, cause the processor to perform operations further comprising creating a recommendation for the matched subscriber in response to determining that the matched subscriber corresponds to the false positive match, the recommendation comprising a suggestion to remove an association associating the data feed with the matched subscriber.

13. The system of claim 10, further comprising instructions that, when executed by the processor, cause the processor to perform operations further comprising creating a recommendation for the matched subscriber in response to determining that the failure to identify the matched subscriber corresponds to the false negative, the recommendation comprising a suggestion to add an association associating the data feed with the further staging directory.

14. A method comprising:

receiving, by a processor executing a data feed at a landing directory associated with a feed management system;

mapping, by the processor, the data feed at the landing directory to a subscriber in communication with the feed management system, wherein mapping the data feed comprises determining if the landing directory is associated with the subscriber;

if a determination is made that the landing directory is associated with the subscriber, determining, by the processor, if matching the subscriber to the landing directory corresponds to a false positive match by

analyzing, by the processor, the data feed,

comparing, by the processor, the data feed to a further data feed in a matched staging directory associated with the matched subscriber, and

determining, by the processor, that the data feed and the further data feed do not share a filename format and a data structure;

if a determination is made that the landing directory is not associated with the subscriber, determining, by the processor, if the failure to match the subscriber to the landing directory corresponds to a false negative;

moving, by the processor, the data feed to a staging directory associated with the subscriber;

adding, by the processor, the data feed to a delivery queue associated with the subscriber;

attempting, by the processor, to deliver the data feed to the subscriber, the data feed being delivered to the subscriber according to a delivery schedule determined based upon a responsiveness of the subscriber;

in response to detecting a failure to deliver the data feed to the subscriber, retaining, by the processor, the data feed in the delivery queue for a further delivery attempt; and

in response to detecting delivery of the data feed to the subscriber, storing, by the processor, a receipt comprising data indicating delivery of the data feed.

15. The method of claim 14, wherein the delivery schedule is based, at least partially, upon:

a group of subscribers to which the subscriber belongs; and

a delivery algorithm associated with the group of subscribers.

16. The method of claim 14, wherein the delivery schedule comprises delivering the data feed in an order in which the data feed is received at the feed management system.