Method for abstracting messages of various protocols into objects for storage in a database

• US 5,794,039 A
• Filed: 12/18/1996
• Issued: 08/11/1998
• Est. Priority Date: 12/18/1996
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Guck, Randal Lee
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/769,200
• Time in Patent Office: 601 Days
• Field of Search: 707/10, 707/4, 707/103, 395/200.33, 395/200.36, 395/683
• US Class Current: 1/1
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 2201/60 Medium conversion
• CPC Class Codes: H04M 3/53 Centralised arrangements for recording incoming messages , i.e. mailbox systems
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

In accordance with the disclosed invention there is provided a method in a system server for storing and retrieving messages of various formats in an object database coupled to a network including a multiplicity of clients also coupled to the network. The server includes a CPU and at least one storage device coupled thereto for storing objects of the database. The method includes steps for driving a database that solves the problem of transforming incoming messages into objects for storage in the database and organizing the transformed messages into a hierarchy of objects in accordance with the purpose and destination of such incoming messages for storage in the database.

Claims

1. In a system server for storing messages of various formats in an object database coupled to a network including a multiplicity of clients also coupled to said network, said server having a CPU and at least one storage device coupled thereto, said storage device being disposed for storing messages as objects of said database, a method for storing messages of various formats received from one or more of said clients in said database, said method comprising the steps of:

a. receiving a message in said server from one of said clients, wherein said received message includes content and transmission information;

b. determining if said received message can be accepted by said server, and if so;

c. creating a virtual message object of a type corresponding to said received message;

d. parsing an envelope of said received message and creating a message header object for each message field found;

e. connecting said message header created in the previous step to said virtual message object;

f. creating a message posting object corresponding to said received message, and connecting said message posting object to both a message board object and said virtual message object; and

,

g. after said received message has been posted to said message board, returning a result thereof to said one of said clients.

2. The method as in claim 1 further comprising the steps of returning an error and aborting request to store said received message if it cannot be accepted by said server.

3. The method as in claim 1 wherein said received message is an e-mail message, said step of creating a virtual message object includes of creating a mail message object.

4. The method as in claim 1 wherein said received message is a news message, said step of creating a virtual message includes creating a news message object.

5. The method as in claim 1 wherein said received message includes an envelope and body and further comprising the step of storing said message envelope and body within said virtual message object.

6. The method as in claim 1, wherein for each subscription object connected to said message board, updating each of said subscription objects to reflect a new message posting.

7. The method as in claim 6 wherein said step of updating includes the step of connecting said message posting object as a new unread message.

8. The method as in claim 1 further including the step of updating said message board object to reflect a newly posted message.

9. The method as in claim 8 wherein said step of updating said message board object, and said message board object is a news group object, further including the step of reflecting a new total message count.

10. The method as in claim 8 wherein said step of updating said message board object, and said message board object is a news group object, further including the step of reflecting a new last updated time stamp.

11. In a system server for storing messages of various formats in an object database coupled to a network including a multiplicity of clients also coupled to said network, said server having a CPU and at least one storage device coupled thereto, said storage device being disposed for storing objects of said database, a method for retrieving messages of various formats stored in said database, said method comprising of the steps of:

a. connecting one of said clients to said server using a protocol, and transmitting a "get" request;

b. determining if said "get" request is for content, and if not;

c. determining if said "get" request is for a list of attachments; and

if so;

d. requesting a list of the immediate attachments of a multi-part message stored in said database;

e. identifying a message using a message reference;

f. identifying a message board;

g. locating a message board object corresponding to said message board identified in step f hereof;

h. determining if said message board object was located, and if so;

i. locating a "global" virtual message object indicated by said message reference identified in step e hereof;

j. locating a message posting object connecting said identified message board and said "global" virtual message object;

k. marking said "global" virtual message object as a "perspective" virtual message object;

l. determining if at least one virtual message object is connected to said "perspective" virtual message object as an "embedded" object;

m. determining if reference for said "embedded" message refers to a valid attachment relevant to a current one of said "perspective" objects, and if so;

n. locating a virtual message object corresponding to said referenced attachment and marking it as a new "perspective" object;

o. locating each immediate message object of said "perspective" object and forming a response; and

,

p. transmitting a response to said one of said clients.

12. The method as in claim 11 wherein said "get" request is for content, further including the steps of:

a. requesting envelope and body of a specific message; and

,

b. extracting envelope and body of said "perspective" object and forming them into a response; and

,

c. transmitting said response to said one of said clients.

13. The method as in claim 11 herein said "perspective" object has no embedded message objects, transmitting a "null list" response to said one of said clients.

14. The method as in claim 11 wherein said step of marking said "global" virtual message object, further including the steps of:

a. determining if said message reference identified in step e. refers to an attachment, and if not,

b. locating each immediate message object of said "perspective" object, and forming a response; and

,

c. transmitting a response to said one of said clients.

15. The method as in claim 11 wherein said step of determining if reference for "embedded" message refers to a valid attachment further comprises the steps of:

a. determining if said "perspective" virtual message object has an embedded message, and if not;

b. parsing envelope of said "perspective" object to find a separator field value;

c. parsing body of said "perspective" object to find each embedded message which will be delimited by said separator field value;

d. creating a new virtual message object;

e. connecting said new virtual message object to said "perspective" object as an embedded message;

f. connecting said new virtual message object to said "global" virtual message object as an "ancestor" object; and

,

g. determining if there are more embedded messages, and if so, repeating steps d, e and f hereof.