Multi-way interactive email performing functions of networks and the web

• US 20020107931A1
• Filed: 02/07/2002
• Published: 08/08/2002
• Est. Priority Date: 02/07/2001
• Status: Abandoned Application

• Current Assignee: Servzone.Com, Inc.
• Original Assignee: Servzone.Com, Inc.
• Inventors: Scott, Richard A., Singh, Kul
• Application Number:
  US10/072,445
• Publication Number:
  US 20020107931A1
• 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: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An improved system that enables interactive networks to be configured and delivered to HTML enabled email systems providing common access to applications and data between two or more parties. The system also provides the capability to link interactive components within the email that, upon execution, dynamically affect the content of the email. The system permits the construction and delivery of dynamic network content enabling email to serve as an ad-hoc, impromptu intranet or extranet. The system internally manages the identification of each node of the email network and creates and tracks security authorization and entitlements ensuring that only authenticated recipients see authorized information. The system combines robust networking capability with two-way interactivity, creating efficiencies for the purposes of information sharing, collaboration, customer relationship management, and online marketing. Anytime the recipient either re-opens the email or refreshes it, the body of the email will reflect the latest transmitted data. The system creates a private and secure network when enterprises or individual users email one or more recipients.

Claims

1. A method of emailing comprising:

creating a network ID for an email originator and each email recipient;

assigning a sub-network ID that uniquely identifies each email recipient;

creating, using said network ID and said sub-network IDs, an email network for said email originator and said email recipients; and

providing server-side executables for allowing said email network to access the Internet such that an email recipient can access the Internet directly from within an email and for refreshing information in said email after said email is sent from said email originator.

2. The method of emailing of claim 1, further comprising refreshing said email after being sent from one of said email recipients.

3. The method of emailing of claim 2, wherein said refreshing occurs each time the email is opened.

4. The method of emailing of claim 2, wherein said refreshing occurs when said email is refreshed.

5. An email server architecture for sending and receiving email that are updateable after being sent comprising:

an email application interface (API) that is adapted to interface with a server side executed email application in order to enable the email application to function within a predetermined network;

a network email engine, in communication with said email API, for creating, maintaining and tracking a plurality of network IDs and sub-network IDs; and

an email delivery engine for originating requests for new email networks and for formatting emails for use with an Internet based email system, said email delivery system adapted for being in communication with said server side executed email application;

said email API further adapted to communicate with said server side executed email application order to send or receive real-time information to a previously sent email within said predetermined network having a particular network ID and sub-network ID via said email delivery engine in order to update information in said previously sent email.

6. The email server architecture of claim 5, wherein a sent or received updateable email passes through said email delivery engine in order to make said sent or received updateable email compatible with substantially most internet based email systems.

7. The email server architecture of claim 5, wherein said email delivery engine makes said sent or received updateable email compatible with substantially all internet based email systems.

8. The email server architecture of claim 5, further comprising:

a component data base, in communication with said network email engine, for storing shared objects for use by said email API such that each time said server side executed email application is executed, information collected from said executed application is written to said component data base for usage in updating said previously sent email.

9. An email system comprising:

means for sending an email from an origination to a destination, said email comprising a network ID, a sub-network ID and refreshable data; and

means for refreshing said refreshable data after said email is sent.

10. The email system of claim 9, wherein said means for sending an email comprises:

a server side executed application accessed from email;

a delivery engine, in communication with said server side executed application, for delivering said email and for delivering said refreshable data.

11. The email system of claim 9, wherein said email is sent to a plurality of destinations, each said plurality of destinations having a different sub-network ID.

12. The email delivery system of claim 11, wherein said means for sending an email creates a network among said plurality of destinations and said origination.

13. A method of sending an updateable email comprising:

Sending email from an origination to a destination, each said email comprising a network ID, a different sub-network ID and refreshable data, and

Refreshing said refreshable data after said email is sent.