Distributed Architecture Data Transfer System

• US 20140143349A1
• Filed: 11/19/2012
• Published: 05/22/2014
• Est. Priority Date: 11/19/2012
• Status: Abandoned Application

• Current Assignee: Jason E. Feser
• Original Assignee: Jason E. Feser
• Inventors: Feser, Jason E.
• Application Number:
  US13/680,628
• Publication Number:
  US 20140143349A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments

Abstract

Systems, methods and computer program products for facilitating data transfer and synchronization between computing devices are disclosed. In an aspect, an enterprise editing platform allows a plurality of contributors to access and alter the same data layer without the use of proprietary server architectures. Data layers are edited by users on local devices and synced remotely by the enterprise editing platform. The data layer is updated via changes sent via ports, protocols, and services associated with electronic mail. In as aspect, updates to the data layer are sent and received via email attachments. Users may initiate sending and retrieving updates to the data layer. In another aspect, a module of the enterprise editing platform sends data layer updates to email addresses associated with each contributor.

Claims

1. A computer-implemented method for facilitating the operation of a distributed architecture data transfer platform, the method comprising the steps of:

(a) creating an index file on an infrastructure for a data layer, the index file comprising a plurality of object identifiers, the plurality of object identifiers comprising;

an associated object identifier; and

a reserved object identifier,

wherein the associated object identifier is associated with a portion of the data layer and the reserved object identifier is reserved for later assignment to a change made to the data layer by a contributor;

(b) storing the data layer and the index file in an information database;

(c) sending, from the infrastructure and via a first email message, a data layer to the contributor;

(d) receiving, via a second email message sent by the contributor, a data bundle, the data bundle comprising a contributor change to the data layer;

(e) importing the contributor change to the infrastructure;

(f) assigning the reserved object identifier to the contributor change;

(g) creating an updated data layer by integrating the contributor change into the data layer,

wherein the contributor change integrated with the data layer has been assigned the reserved object identifier;

(h) updating the index file with the assignment of the reserved object identifier; and

(i) sending, from the infrastructure and via a third email message, the updated data layer to the contributor.

2. The method of claim 1, wherein the first email message of step (c) and the second email message of step (i) are sent automatically.

3. The method of claim 1, wherein the second email message received from the contributor was generated and sent automatically by a contributor tool.

4. The method of claim 1, further comprising the step of:

(j) sending, from the infrastructure and via a fourth email message, a correction to the contributor, the correction comprising a rejection or modification of the contributor change,

wherein the rejection or modification was made by a data manager and the correction is configured to prompt the contributor to respond to the rejection or modification.

5. The method of claim 4, wherein the data manager is one of:

an individual and a software module.

6. The method of claim 4, wherein the data manager is an individual and importing step (e) further comprises the steps of:

(i) presenting the contributor change to the data manager via a computing device graphical user interface;

(ii) accessing the stored data layer and stored index file;

(iii) presenting the stored data layer and the stored index file to the data manager via the computing device graphical user interface,

wherein the graphical user interface is configured to allow the data manager to compare the contributor change to at least one of the stored data layer and to the stored index file, and to accept, reject, or modify the contributor change.

7. The method of claim 1, further comprising the step of:

(k) creating a contributions folder within an email client, configured to receive email messages from the contributor containing data bundles,

wherein the contributions folder is governed by at least one folder rule which causes the email client to take a specified action in response to the received email message.

8. The method of claim 1, wherein the infrastructure utilized in step (a) is one of:

a desktop computer;

a laptop computer;

a PDA;

a mobile telephone;

a tablet computer; and

a mobile computer.

9. A computer-implemented method for facilitating the operation of a distributed architecture data transfer platform, the method comprising the steps of:

(a) storing a data layer on a computing device,

wherein the computing device is accessible by a data manager;

(b) creating an index file on the computing device for the data layer, the index file comprising a plurality of object identifiers, the plurality of object identifiers comprising;

an associated object identifier; and

a reserved object identifier,

wherein the associated object identifier is associated with a portion of the data layer and the reserved object identifier is reserved for later assignment to a change made to the data layer by a contributor;

(c) sending, from a data manager email address and via a first email message, a data layer to the contributor;

(d) receiving, via a second email message, sent by the contributor, a data bundle, the data bundle comprising a contributor change to the data layer;

(e) importing the contributor change onto the computing device;

(f) assigning the reserved object identifier to the contributor change;

(g) creating an updated data layer by integrating the contributor change into the data layer,

wherein the contributor change integrated with the data layer has been assigned the reserved object identifier;

(h) updating the index file with the assigned object identifier; and

(i) sending, from the data manager email address and via a third email message, the updated data layer to the contributor.

10. The method of claim 9, further comprising the step of:

(j) sending, from the data manager email address and via a fourth email message, a correction to the contributor, the correction comprising a rejection or modification of the contributor change,

wherein the rejection or modification was made by the data manager and the correction is configured to prompt the contributor to respond to the rejection or modification.

11. The method of claim 10, wherein the computing device further comprises a graphical user interface and wherein importing step (e) further comprises the steps of:

(i) presenting the contributor change to the data manager via the graphical user interface;

(ii) accessing the stored data layer and stored index file;

(iii) presenting the stored data layer and the stored index file to the data manager via the computing device graphical user interface,

wherein the graphical user interface is configured to allow the data manager to compare the contributor change to at least one of the stored data layer and to the stored index file, and to accept, reject, or modify the contributor change.

12. The method of claim 9, further comprising the step of:

(k) creating a contributions folder within an email client, configured to receive email messages from the contributor containing data bundles,

wherein the contributions folder is governed by at least one folder rule which causes the email client to take a specified action in response to the received email message.

13. A computer-implemented method for facilitating the operation of a distributed architecture data transfer platform, the method comprising the steps of:

(a) receiving, via a first email message sent to a contributor, a data layer;

(b) storing the data layer on a contributor computing device;

(c) updating the stored data layer via integrating contributor-supplied changes into the data layer;

(d) generating a data bundle, the data bundle comprising a contributor change to the data layer;

(e) sending, via a second email message, the data bundle to a contributions email address,

wherein the contributions email address has been configured to receive contributor data bundles; and

(f) receiving, via a third email message, an updated data layer.

14. The method of claim 13, further comprising the step of:

(g) receiving, via a fourth email message, a correction comprising a rejection or modification of a sent contributor change,

wherein the correction is configured to prompt the contributor to respond to the rejection or modification.

15. The method of claim 14, further comprising the step of:

(h) sending, via a fifth email message, a response to the correction received in step (g).

16. A computer readable storage medium for storing computer readable instructions, the computer readable instructions facilitating the operation of a distributed architecture data transfer platform, the computer readable instructions comprising:

logic configured to create an index file on an infrastructure for a data layer, the index file comprising a plurality of object identifiers, the plurality of object identifiers comprising;

an associated object identifier; and

a reserved object identifier,

wherein the associated object identifier is associated with a portion of the data layer and the reserved object identifier is reserved for later assignment to a change made to the data layer by a contributor;

logic configured to store the data layer and the index file in an information database;

logic configured to send from the infrastructure and via a first email message, a data layer to the contributor;

logic configured to receive, via a second email message, sent by the contributor, a data bundle, the data bundle comprising a contributor change to the data layer;

logic configured to import the contributor change to the infrastructure;

logic configured to assign the reserved object identifier to the contributor change;

logic configured to create an updated data layer by integrating the contributor change into the data layer,

wherein the contributor change integrated with the data layer has been assigned the reserved object identifier;

logic configured to update the index file with the assignment of the reserved object identifier; and

logic configured to send from the infrastructure and via a third email message, the updated data layer to the contributor.

17. The computer readable storage medium of claim 16, further comprising:

logic configured to send from the infrastructure and via a fourth email message, a correction to the contributor comprising a rejection or modification of the contributor change,

wherein the rejection or modification was made by a data manager and the correction is configured to prompt the contributor to respond to the rejection or modification.

18. The computer readable storage medium of claim 17, wherein the data manager is one of:

an individual and a software module.

19. The computer readable storage medium of claim 17, wherein the data manager is an individual and the computer readable storage medium further comprises:

logic configured to present the contributor change to the data manager via a computing device graphical user interface;

logic configured to access the stored data layer and stored index file;

logic configured to present the stored data layer and the stored index file to the data manager via the computing device graphical user interface,

wherein the graphical user interface is configured to allow the data manager to compare the contributor change to at least one of the stored data layer and to the stored index file, and to accept, reject, or modify the contributor change.

20. The computer readable storage medium of claim 16, further comprising:

logic configured to create a contributions folder within an email client, configured to receive email messages from the contributor containing data bundles,

wherein the contributions folder is governed by at least one folder rule which causes the email client to take a specified action in response to the received email message.