Patent US3647214A successfully refreshed from Google Patents.
Patent US6052787A successfully refreshed from Google Patents.
US6052787A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Process for group-based cryptographic code management between a first computer unit and group computer units
Assignee: Siemens AG
•
Filing: 1997-05-16
•
Granted: 2000-04-18
•
Expires: 2017-05-16
Abstract
Abstract A group-based cryptographic code management method is proposed, in which a security policy which is used in a further communication is negotiated between group computer units and a first computer unit.
Inventors
- 👤 Martin Euchner
- 👤 Wolfgang Klasen
- 👤 Volker Kessler
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-09 08:14
CPC Classifications
H; H04; H04L; H04L9/00; H04L9/08; H04L9/0816; H04L9/0819; H04L9/083; H04L9/0833
Claims Analysis
Total Claims: 14
Claim 1
Independent Claim
248 words
A method for group-based declaration of a cryptographic, common security policy between a first computer unit and group computer units, comprising the steps of: forming in the first computer unit a first message; providing in the first message at least a first security policy proposal and a first identity checking variable; transmitting the first message from the first computer unit to at least some of the group computer units; carrying out the following steps in the group computer units; receiving the first message by a respective group computer unit of the group computers; checking integrity of the first security policy proposal based on the first identity checking variable; forming a second message in each case, the second message having at least a second security policy proposal and a second identity checking variable; transmitting the second messages from the group computer units to the first computer unit; receiving the second messages by the first computer unit; checking integrity of each respective second security proposal using the corresponding second identity checking variable; forming a third message by the first computer unit; providing in the third message at least one group security policy and a third identity checking variable; transmitting the third message from the first computer unit to at least some of the group computer units; carrying out the following steps in the group computer units; receiving the third message by respective group computer units; and checking the integrity of the group security policy using the third identity checking variable.
Claim 2
Independent Claim
248 words
A method for group-based declaration of a cryptographic, common security policy between a first computer unit and group computer units, comprising the steps of: forming in the first computer unit a first message; providing in the first message at least a first security policy proposal and a first identity checking variable; transmitting the first message from the first computer unit to at least some of the group computer units; carrying out the following steps in the group computer units; receiving the first message by a respective group computer unit of the group computers; checking integrity of the first security policy proposal based on the first identity checking variable; forming a second message in each case, the second message having at least a second security policy proposal and a second identity checking variable; transmitting the second messages from the group computer units to the first computer unit; receiving the second messages by the first computer unit; checking integrity of each respective second security proposal using the corresponding second identity checking variable; forming a third message by the first computer unit; providing in the third message at least one group security policy and a third identity checking variable; transmitting the third message from the first computer unit to at least some of the group computer units; carrying out the following steps in the group computer units; receiving the third message by respective group computer units; and checking the integrity of the group security policy using the third identity checking variable.
Claim 3
Dependent Claim
62 words
The method according to claim 1, wherein at least one of the first message and the third message is in each case encrypted using a public code of the group computer unit, and wherein at least one of the first message and the third message is decrypted in the group computer unit using a secret code of the respective group computer unit.
Claim 4
Dependent Claim
21 words
The method according to claim 1, wherein each of the first, second and third messages has at least one random number.
Claim 5
Dependent Claim
19 words
The method according to claim 1, wherein the first message has a code certificate of the first computer unit.
Claim 6
Dependent Claim
94 words
The method according to claim 1, wherein before transmission of the first message, a first authentication message is formed in the first computer unit, wherein the first authentication message has at least one code certificate of the first computer unit, wherein the first authentication message has at least one code certificate of the first computer unit, wherein the first authentication message is transmitted from the first computer unit to at least some of the group computer units, and wherein the group computer units verify and store the code certificate of the first computer unit.
Claim 7
Dependent Claim
89 words
The method according to claim 1, wherein before transmission of the first message and in at least some of the group computer units, a second authentication message is in each case formed in the group computer units, wherein the second authentication messages in each case have at least code certificates of the group computer units, wherein the second authentication messages are transmitted from the group computer units to the first computer unit, and wherein the first computer unit verifies and stores the code certificates of the group computer units.
Claim 8
Dependent Claim
53 words
The method according to claim 6, wherein each of the first, second and third message has at least one random number, wherein the second authentication messages have an authentication identity checking variable, and wherein at least some of the second authentication messages are encrypted using a public code of the first computer unit.
Claim 9
Dependent Claim
56 words
The method according to claim 1, wherein, after checking the integrity of the group security policy, each of the group computer units forms an acknowledgment message, wherein the acknowledgment messages are transmitted from the group computer units to the first computer unit, and wherein the acknowledgment messages are checked for integrity, in the first computer unit.
Claim 10
Dependent Claim
42 words
The method according to claim 1, wherein at least one of the following identity checking variables is formed using a hash function: the first identity checking variable, the second identity checking variable, the third identity checking variable, the authentication identity check variable.
Claim 11
Dependent Claim
37 words
The method according to claim 1, wherein the group security policy contains at least one group distribution code for encryption and distribution of group conference codes which continue to be used, or of a group conference code.
Claim 12
Dependent Claim
32 words
The method according to claim 1, wherein a plurality of further messages having further security policy proposals are formed and transmitted by the first computer unit and by the group computer units.
Claim 13
Dependent Claim
18 words
The method according to claim 1, wherein a multicast mechanism is provided for copying messages to be transmitted.
Claim 14
Dependent Claim
21 words
The method according to claim 1, wherein at least some of the identity checking variables are formed using a digital signature.
References Cited (Backward Citations)
EP0307627A1
Cited
EP0402083A2
Cited
US5220604A
Cited
US5224163A
Cited
US5315657A
Cited
US5577209A
Cited
WO1995008885A1
Cited
US5748736A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-04-18 | 2003-10-18 | 2004-04-18 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-04-18 | 2007-10-18 | 2008-04-18 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-04-18 | 2011-10-18 | 2012-04-18 | $7700.00 | Window Closed / Lapsed |