US6122372A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for encapsulating transaction messages with verifiable data generated identifiers
Assignee: MOORE NANCY BARCLAY
•
Filing: 1997-06-04
•
Granted: 2000-09-19
•
Expires: 2017-06-04
Abstract
Abstract A data structure and method are disclosed for encapsulating a message with a verifiable message ID and a verifiable identification of message interpretation information. The encapsulated message includes a message set and a data generated message identifier. The message set includes a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body. The data generated message identifier is a hash function of the message set that includes the message body and the data generated interpretation identifier. The data generated message identifier is determined such that the data generated message identifier verifiably identifies the message set.
Inventors
- 👤 Eric G. Hughes
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 06:34
CPC Classifications
H; H04; H04L; H04L9/00; H04L9/32; H04L9/3247; H04L9/3236; H04L2209/00; H04L2209/56; H04L2209/60
Claims Analysis
Total Claims: 58
Claim 1
Independent Claim
95 words
An encapsulated message data structure embodied in a computer readable media comprising: a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body; and a data generated message identifier that is a hash function of the message set that includes the message body and the data generated interpretation identifier, the data generated message identifier being determined such that the data generated message identifier verifiably identifies the message set.
Claim 2
Dependent Claim
95 words
An encapsulated message data structure embodied in a computer readable media comprising: a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body; and a data generated message identifier that is a hash function of the message set that includes the message body and the data generated interpretation identifier, the data generated message identifier being determined such that the data generated message identifier verifiably identifies the message set.
Claim 3
Dependent Claim
24 words
A message data structure as recited in claim 1 wherein the data generated message identifier is a cryptographic hash function of the message set.
Claim 4
Dependent Claim
25 words
A message data structure as recited in claim 1 wherein the data generated interpretation identifier is a cryptographic hash function of a message interpretation file.
Claim 5
Dependent Claim
23 words
A message data structure as recited in claim 1 wherein the interpretation file specifies a format for data items in the message body.
Claim 6
Dependent Claim
24 words
A message data structure as recited in claim 1 wherein the interpretation file is a template used to interpret items in the message body.
Claim 7
Dependent Claim
33 words
A message data structure as recited in claim 1 wherein the interpretation file is a contract that describes the relationship of a sending party that is sending the message to a second party..
Claim 8
Dependent Claim
28 words
A message data structure as recited in claim 6 wherein the second party is a receiving party that receives a message arranged according to the message data structure.
Claim 9
Dependent Claim
36 words
A message data structure as recited in claim 6 wherein the second party is a recipient party that has a relationship with a receiving party that receives a message arranged according to the message data structure.
Claim 10
Dependent Claim
33 words
A message data structure as recited in claim 1 wherein the interpretation file is a protocol that describes the proper manner of response to a message arranged according to the message data structure.
Claim 11
Dependent Claim
18 words
A message data structure as recited in claim 1 wherein the computer readable media is a communication link.
Claim 12
Dependent Claim
18 words
A message data structure as recited in claim 1 further comprising a plurality of data generated interpretation identifiers.
Claim 13
Dependent Claim
24 words
A message data structure as recited in claim 11 wherein the interpretation identifiers include a template identifier, a protocol identifier and a contract identifier.
Claim 14
Dependent Claim
19 words
A message data structure as recited in claim 11 wherein the message set further includes a message information item.
Claim 15
Dependent Claim
18 words
A message data structure as recited in claim 11 wherein the message information item is a time stamp.
Claim 16
Dependent Claim
18 words
A message data structure as recited in claim 11 wherein the message information item is an arbitrary tag.
Claim 17
Dependent Claim
26 words
A message data structure as recited in claim 11 wherein the message information item is a sender identification item that identifies the sender of the message.
Claim 18
Dependent Claim
26 words
A message data structure as recited in claim 11 wherein the message information item is a sender authentication item that authenticates the sender of the message.
Claim 19
Dependent Claim
34 words
A message data structure as recited in claim 17 wherein the sender authentication item is an encryption function of a hash of a portion of a message arranged according to the message data structure.
Claim 20
Dependent Claim
70 words
A message data structure as recited in claim 18 wherein the encryption function is a digital signature of the hash of a portion of the message arranged according to the message data structure wherein the digital signature is created using a private key known to the message sender and wherein the private key corresponds to a public key associated with the message sender that is known to a message receiver.
Claim 21
Independent Claim
108 words
A method of encapsulating a message comprising the steps of: creating a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body; creating a data generated message identifier that is a hash function of the message set that includes the message body and the data generated interpretation identifier, the data generated message identifier being created such that the data generated message identifier verifiably identifies the message set; encapsulating the message set and the data generated message identifier into an encapsulated message.
Claim 22
Independent Claim
108 words
A method of encapsulating a message comprising the steps of: creating a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body; creating a data generated message identifier that is a hash function of the message set that includes the message body and the data generated interpretation identifier, the data generated message identifier being created such that the data generated message identifier verifiably identifies the message set; encapsulating the message set and the data generated message identifier into an encapsulated message.
Claim 23
Dependent Claim
26 words
A method of encapsulating a message as recited in claim 20 wherein the data generated message identifier is a cryptographic hash function of the message set.
Claim 24
Dependent Claim
27 words
A method of encapsulating a message as recited in claim 20 wherein the data generated interpretation identifier is a cryptographic hash function of the message interpretation file.
Claim 25
Dependent Claim
25 words
A method of encapsulating a message as recited in claim 20 wherein the interpretation file specifies a format for data items in the message body.
Claim 26
Dependent Claim
26 words
A method of encapsulating a message as recited in claim 20 wherein the interpretation file is a template used to interpret items in the message body.
Claim 27
Dependent Claim
35 words
A method of encapsulating a message as recited in claim 20 wherein the interpretation file is a contract that describes the relationship of a sending party that is sending the message to a second party.
Claim 28
Dependent Claim
24 words
A method of encapsulating a message as recited in claim 20 further including sending the message from a message sender to a message receiver.
Claim 29
Dependent Claim
24 words
A method of encapsulating a message as recited in claim 20 wherein the message set further comprises a plurality of data generated interpretation identifiers.
Claim 30
Dependent Claim
26 words
A method of encapsulating a message as recited in claim 27 wherein the interpretation identifiers include a template identifier, a protocol identifier and a contract identifier.
Claim 31
Dependent Claim
21 words
A method of encapsulating a message as recited in claim 27 wherein the message set further includes a message information item.
Claim 32
Dependent Claim
20 words
A method of encapsulating a message as recited in claim 27 wherein the message information item is a time stamp.
Claim 33
Dependent Claim
20 words
A method of encapsulating a message as recited in claim 27 wherein the message information item is an arbitrary tag.
Claim 34
Dependent Claim
28 words
A method of encapsulating a message as recited in claim 27 wherein the message information item is a sender identification item that identifies the sender of the message.
Claim 35
Dependent Claim
28 words
A method of encapsulating a message as recited in claim 27 wherein the message information item is a sender authentication item that authenticates the sender of the message.
Claim 36
Dependent Claim
99 words
An encapsulated message data structure embodied in a computer readable media comprising: a message body that contains the content of a message; a data generated interpretation identifier associated with the message body, the data generated interpretation identifier being arranged to verifiably identify an interpretation file that may be used to interpret the message body; and a data generated message identifier that is a hash function of the message body and the data generated interpretation identifier, the data generated message identifier being determined such that the data generated message identifier verifiably identifies the message and the data generated interpretation identifier.
Claim 37
Dependent Claim
99 words
An encapsulated message data structure embodied in a computer readable media comprising: a message body that contains the content of a message; a data generated interpretation identifier associated with the message body, the data generated interpretation identifier being arranged to verifiably identify an interpretation file that may be used to interpret the message body; and a data generated message identifier that is a hash function of the message body and the data generated interpretation identifier, the data generated message identifier being determined such that the data generated message identifier verifiably identifies the message and the data generated interpretation identifier.
Claim 38
Independent Claim
72 words
A method of encapsulating a message comprising the steps of: associating an interpretation identifier with a message body, the interpretation identifier being arranged to verifiably identify an interpretation fie that may be used to interpret the message body; creating a data generated message identifier that is a function of the contents of the message body; encapsulating the message body, the interpretation identifier and the data generated message identifier into an encapsulated message.
Claim 39
Independent Claim
72 words
A method of encapsulating a message comprising the steps of: associating an interpretation identifier with a message body, the interpretation identifier being arranged to verifiably identify an interpretation fie that may be used to interpret the message body; creating a data generated message identifier that is a function of the contents of the message body; encapsulating the message body, the interpretation identifier and the data generated message identifier into an encapsulated message.
Claim 40
Dependent Claim
50 words
An encapsulated message data structure embodied in a computer readable media comprising: a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body.
Claim 41
Dependent Claim
50 words
An encapsulated message data structure embodied in a computer readable media comprising: a message set, the message set including a message body that contains the content of a message and a data generated interpretation identifier that verifiably identifies an interpretation file that may be used to interpret the message body.
Claim 42
Dependent Claim
25 words
A message data structure as recited in claim 36 wherein the data generated interpretation identifier is a cryptographic hash function of a message interpretation file.
Claim 43
Dependent Claim
23 words
A message data structure as recited in claim 36 wherein the interpretation file specifies a format for data items in the message body.
Claim 44
Dependent Claim
24 words
A message data structure as recited in claim 36 wherein the interpretation file is a template used to interpret items in the message body.
Claim 45
Dependent Claim
33 words
A message data structure as recited in claim 36 wherein the interpretation file is a contract that describes the relationship of a sending party that is sending the message to a second party.
Claim 46
Dependent Claim
28 words
A message data structure as recited in claim 40 wherein the second party is a receiving party that receives a message arranged according to the message data structure.
Claim 47
Dependent Claim
36 words
A message data structure as recited in claim 40 wherein the second party is a recipient party that has a relationship with a receiving party that receives a message arranged according to the message data structure.
Claim 48
Dependent Claim
33 words
A message data structure as recited in claim 36 wherein the interpretation file is a protocol that describes the proper manner of response to a message arranged according to the message data structure.
Claim 49
Dependent Claim
18 words
A message data structure as recited in claim 36 wherein the computer readable media is a communication link.
Claim 50
Dependent Claim
18 words
A message data structure as recited in claim 36 further comprising a plurality of data generated interpretation identifiers.
Claim 51
Dependent Claim
24 words
A message data structure as recited in claim 45 wherein the interpretation identifiers include a template identifier, a protocol identifier and a contract identifier.
Claim 52
Dependent Claim
19 words
A message data structure as recited in claim 45 wherein the message set further includes a message information item.
Claim 53
Dependent Claim
18 words
A message data structure as recited in claim 45 wherein the message information item is a time stamp.
Claim 54
Dependent Claim
18 words
A message data structure as recited in claim 45 wherein the message information item is an arbitrary tag.
Claim 55
Dependent Claim
26 words
A message data structure as recited in claim 45 wherein the message information item is a sender identification item that identifies the sender of the message.
Claim 56
Dependent Claim
26 words
A message data structure as recited in claim 45 wherein the message information item is a sender authentication item that authenticates the sender of the message.
Claim 57
Dependent Claim
34 words
A message data structure as recited in claim 51 wherein the sender authentication item is an encryption function of a hash of a portion of a message arranged according to the message data structure.
Claim 58
Dependent Claim
70 words
A message data structure as recited in claim 52 wherein the encryption function is a digital signature of the hash of a portion of the message arranged according to the message data structure wherein the digital signature is created using a private key known to the message sender and wherein the private key corresponds to a public key associated with the message sender that is known to a message receiver.
References Cited (Backward Citations)
US5337360A
Cited
US5475826A
Cited
US5724425A
Cited
US5781629A
Cited
US5638443A
Cited
US5883956A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-09-19 | 2004-03-20 | 2004-09-19 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-09-19 | 2008-03-20 | 2008-09-19 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-09-19 | 2012-03-20 | 2012-09-19 | $7700.00 | Window Closed / Lapsed |