US5615266A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Secure communication setup method
Assignee: General Dynamics Mission Systems Inc
•
Filing: 1996-01-11
•
Granted: 1997-03-25
•
Expires: 2016-01-11
Abstract
Abstract A call is connected between secure terminals (16) through a network (12). If a network address for the call is included on an approved list (46), a secure call setup procedure (54) is performed automatically. One terminal (16) automatically sends an auto-secure signal. If the other terminal detects the auto-secure signal, secure call setup procedure (54) is performed automatically. The secure call setup procedure (54) determines a current user-identity for the opposing party. If the current user-identity corresponds to a user-identity included on an approved list (76), an abbreviated secure call setup process (80) is performed. If the current user identity is not approved, a full secure call setup process (78) is performed. The abbreviated process (80) differs from the full process (78) in that it uses a traffic key obtained from a prior secure communication session and may be performed more quickly.
Inventors
- 👤 Barry N. Altschuler
- 👤 Douglas A. Hardy
- 👤 James A. Stephens
- 👤 Joseph Kish, III
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-09 05:11
CPC Classifications
H; H04; H04L; H04L9/00; H04L9/08; H04L9/0891
Claims Analysis
Total Claims: 17
Claim 1
Independent Claim
203 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: maintaining a list of approved network addresses; obtaining a current network address for said one remote terminal; determining whether said current network address corresponds to one of said approved network addresses; automatically initiating a secure call setup procedure when said current network address corresponds to one of said approved network addresses; performing a full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; establishing a plain-text communication session with said one remote terminal; receiving, after said automatically initiating step, a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and effecting said abbreviated secure call setup process performing step when said current identity corresponds to one of said approved user-identities.
Claim 2
Independent Claim
203 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: maintaining a list of approved network addresses; obtaining a current network address for said one remote terminal; determining whether said current network address corresponds to one of said approved network addresses; automatically initiating a secure call setup procedure when said current network address corresponds to one of said approved network addresses; performing a full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; establishing a plain-text communication session with said one remote terminal; receiving, after said automatically initiating step, a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and effecting said abbreviated secure call setup process performing step when said current identity corresponds to one of said approved user-identities.
Claim 3
Dependent Claim
44 words
A method of engaging in a secure communication session as claimed in claim 1 additionally comprising the step of sending an auto-secure signal to said one remote terminal, said auto-secure signal serving to request said one remote terminal to automatically send said current identity.
Claim 4
Dependent Claim
71 words
A method of engaging in a secure communication session as claimed in claim 1 wherein said method additionally comprises the step of effecting said full secure call setup process performing step when said current identity does not correspond to one of said approved user-identities, and said full secure call setup process performing step comprises the steps of: obtaining a new traffic key; and encrypting session data using said new traffic key.
Claim 5
Dependent Claim
38 words
A method of engaging in a secure communication session as claimed in claim 3 wherein said obtaining a new traffic key step comprises the step of engaging in a public key exchange to generate said new traffic key.
Claim 6
Independent Claim
173 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: establishing a plain next communication session; detecting the receipt of an auto-secure signal from said one remote terminal; automatically initiating a secure call setup procedure in response to said auto-secure signal; performing a full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; receiving, after said automatically initiating step, a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and effecting said abbreviated secure call setup process performing step when said current identity corresponds to one of said approved user-identities.
Claim 7
Independent Claim
173 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: establishing a plain next communication session; detecting the receipt of an auto-secure signal from said one remote terminal; automatically initiating a secure call setup procedure in response to said auto-secure signal; performing a full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; receiving, after said automatically initiating step, a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and effecting said abbreviated secure call setup process performing step when said current identity corresponds to one of said approved user-identities.
Claim 8
Dependent Claim
44 words
A method of engaging in a secure communication session as claimed in claim 5 additionally comprising the step of sending an auto-secure signal to said one remote terminal, said auto-secure signal serving to request said one remote terminal to automatically send said current identity.
Claim 9
Independent Claim
189 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: detecting the receipt of an auto-secure signal from said one remote terminal; automatically initiating a secure call setup procedure in response to said auto-secure signal; performing said full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; initiating a plain-text communication session with said one remote terminal; receiving a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and when said current identity corresponds to one of said approved user-identities, encrypting session data using one of said approved traffic keys that is associated in said list with one approved user-identity to which said current identity corresponds.
Claim 10
Independent Claim
189 words
A method of engaging in a secure communication session with one of a plurality of remote terminals, said method comprising the steps of: detecting the receipt of an auto-secure signal from said one remote terminal; automatically initiating a secure call setup procedure in response to said auto-secure signal; performing said full secure call setup process when no prior secure communication session has been conducted with said one remote terminal; performing an abbreviated secure call setup process when a prior secure communication session has been conducted with said one remote terminal; maintaining a list in which approved user-identities are associated with approved traffic keys, said approved user-identities serving to identify at least some users of said remote terminals; initiating a plain-text communication session with said one remote terminal; receiving a current identity from said one remote terminal; determining whether said current identity corresponds to one of said approved user-identities from said list; and when said current identity corresponds to one of said approved user-identities, encrypting session data using one of said approved traffic keys that is associated in said list with one approved user-identity to which said current identity corresponds.
Claim 11
Dependent Claim
59 words
A method of engaging in a secure communication session as claimed in claim 7 additionally comprising the steps of: obtaining a new traffic key when said current identity does not correspond to one of said approved user-identities; and encrypting session data using said new traffic key when said current identity does not correspond to one of said approved user-identities.
Claim 12
Dependent Claim
34 words
A method of engaging in a secure communication session as claimed in claim 8 wherein said obtaining step comprises the step of engaging in a public key exchange to generate said new traffic key.
Claim 13
Dependent Claim
47 words
A method of engaging in a secure communication session as claimed in claim 7 additionally comprising the steps of: generating a future approved traffic key; and updating said list to associate said future approved traffic key with said one approved user-identity to which said current identity corresponds.
Claim 14
Dependent Claim
47 words
A method of engaging in a secure communication session as claimed in claim 10 wherein: said secure communication session occurs during said encrypting step; said communication session continues for a variable duration; and said generating and updating steps occur approximately at the beginning of said variable duration.
Claim 15
Dependent Claim
80 words
A method of engaging in a secure communication session as claimed in claim 7 wherein said maintaining step additionally records a list of approved network addresses, and said initiating step comprises the steps of: obtaining a current network address for said one remote terminal; determining whether said current network address corresponds to one of said approved network addresses; and automatically performing said receiving, determining, and encrypting steps when said current network address corresponds to one of said approved network addresses.
Claim 16
Dependent Claim
46 words
A method of engaging in a secure communication session as claimed in claim 7 additionally comprising the steps of: detecting the receipt of an auto-secure signal from said one remote terminal; and interpreting said auto-secure signal as a request to automatically establish a secure communication session.
Claim 17
Dependent Claim
44 words
A method of engaging in a secure communication session as claimed in claim 7 wherein said initiating step comprises the step of sending an auto-secure signal to said one remote terminal, said auto-secure signal requesting said one remote terminal to transmit said current identity.
References Cited (Backward Citations)
US4578531A
Cited
US4802220A
Cited
US4888801A
Cited
US4989211A
Cited
US4888802A
Cited
US4941176A
Cited
US4924514A
Cited
US5103478A
Cited
US5003593A
Cited
US5029206A
Cited
US5010572A
Cited
US5093860A
Cited
US5193114A
Cited
US5179591A
Cited
US5465300A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-03-24 | 2000-09-23 | 2001-03-25 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-03-24 | 2004-09-23 | 2005-03-25 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-03-24 | 2008-09-23 | 2009-03-25 | $7700.00 | Window Closed / Lapsed |