Teleconferencing method for a secure key management system.
Abstract
A secure teleconferencing method for a key management system is shown. This method directly establishes a secure teleconference among a number of terminals without the intervention of a certifying authority. The terminals (A-D) of this system have been previously certified by a common certification authority. Upon detection of a secure teleconference, the terminals orient themselves in a master/slave (1-16,22,23) configuration. The terminals exchange certification messages (24-43,45). As a result, each terminal determines the identity of the other terminals (44,46). Under the supervision of the master terminal, the terminals establish a single session, session key which permits secure communication among the terminals (47-58). A new session key is randomly generated for each teleconference call. A minimum number of messages is exchanged to establish the secure teleconference.

Term
Term ended
Projected expiry passed 4 June 2010, 16.3 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
18 claims: 3 independent, 15 dependent
- 1A secure teleconferencing method for a key management system included a plurality of terminals (A-D) previously certified by a common authority of said key management system, said secure teleconferencing method comprising the steps of:connecting (1-2) at least three of said terminals in an unsecure teleconference call via a switching network;selecting (3-6,11,12) any one of said connected terminals to be a master terminal;selecting (7,9,10,13,16) all of said connected terminals, except said master terminal, as slave terminals;establishing (44,46) by each terminal that each of said remaining connected terminals is certified by a common certification authority;directly developing (46-58) a single-session session key among said connected terminals;and initiating a secure teleconference call among each of said connected terminals to provide for secure voice and data communication among said connected terminals.
- 17A secure teleconferencing method via a switching network for establishing a secure teleconference among a plurality of interconnected terminals (A-D) which have been previously certified by a common authority, said secure teleconferencing method comprising the steps of:selecting (3-6,11,12) any one of said connected terminals to be a master terminal;selecting (7,9.10,13,16) all of said connected terminals, except said master terminal, as slave terminals;establishing (44,46) by each terminal that each of said remaining interconnected terminals is certified by a common certification authority;directly developing (46-58) a single-session session key among said connected terminals;and initiating a secure teleconference call among each of said interconnected terminals to provide for secure voice and data communication among said interconnected terminals.
- 18A secure teleconferencing method via a switching network for establishing a secure teleconference among a plurality of interconnected terminals (A-D) which have been previously certified by a common authority, said secure teleconferencing method comprising the steps of:selecting (3-6,11,12) any one of said connected terminals to be a master terminal;selecting (7,9,10,13,16) all of said connected terminals, except said master terminal, as slave terminals;establishing (44,46) by each terminal that each of said remaining interconnected terminals is certified by a common certification authority;and directly developing (46-58) a single-session session key among said connected terminals for providing secure voice and data communication among said interconnected terminals.
Independent claims3
42 paragraphs, as filed
Background of the Invention
0001The present invention pertains to secure communications among users of a key management system and more particularly to a method for providing secure teleconferencing through the use of an unforgeable certification process.
0002In modern day telephony, specialized circuitry within the switching system provides for teleconferencing. Teleconferencing is simultaneous voice or data exchange between three or more users of a communication system. Typically, specialized networks and circuitry within the network of a switching system provide for interconnecting a number of users in a teleconference.
0003In secure communications systems, the problems of establishing connections among multiple users for voice or data exchange is further complicated by various security protocols. Establishing a secure teleconference between multiple users via a secure network of a switching system is very difficult. This is due to the fact that the terminal devices in a secure teleconferencing system may demand point-to-point, on-line establishment of traffic keys.
0004Further, establishing a session key between terminal devices connected to a secure network of a switching system requires transmission of many messages between the system and the users. This is very cumbersome and time consuming.
0005An object of the present invention is to provide a method to enable any number of terminal devices connected to a switching network to establish a secure conference arrangement by establishing an unforgeable certification method to provide a single session traffic key with a minimal number of point-to-point message exchanges between the terminal devices.
Summarv of the Invention
0006In accomplishing the object of the present invention, a novel teleconferencing method for a secure key management system is shown.
0007A secure teleconferencing method is achieved among a number of interconnected terminals via a switching network. Each of the terminals have previously been certified by a common authority. The secure teleconferencing method first establishes that all the teleconferenced terminals have previously been certified. Each terminal established that all the remaining terminals have been previously certified by a common authority. Then, the terminals collectively develop a unique, single session, session key for providing secure voice and data communication among the interconnected terminals.
Brief Description of the Drawing
0008<ul id="ul0001" list-style="none"><li>FIG. 1 is a block diagram of a teleconferencing arrangement via a switching network.</li><li>FIGS. 2A and 2B are flow charts of a secure teleconferencing method embodying the principles of operation of the present invention.</li><li>FIGS.3A and 3B are timing diagrams of inter-terminal message transmission.</li><li>FIG. 4 is a block diagram depicting the exclusive-OR operation of each terminal.</li></ul>
Description of the Preferred Embodiment
0009FIG. 1 depicts a number of terminals (A, B, C and D) connected to a switching network. This switching network includes circuitry which can provide for teleconferencing among these four terminals. Four terminals are shown here by way of example and not by way of limitation. Almost any number of terminals may be connected in the teleconferencing arrangement. The only limitations are the number of terminals which may physically be interconnected by the switching system.
0010In the present system, each of the terminals is a secure voice and data terminal. Each terminal includes the present secure teleconferencing method. This method may typically be implemented in software. However, hardware implementations are also possible.
0011The secure terminals A-D are designed for both full duplex and half duplex voice and data communication. Half duplex voice and data communication takes place over two wire communication networks. Full duplex voice and data communication occurs over four-wire telecommunication networks. For full duplex transmission, information is received and transmitted over two separate pairs of wires (channels) simultaneously. In half duplex transmission, a terminal puts energy on the line only when transmitting information. When its transmission is complete, its energy is removed allowing another terminal to transmit on the same channel. Teleconferencing is much more straight forward in the half duplex configuration, since energy is on the line only when a particular terminal is transmitting.
0012The present method pertains more readily to the half duplex communication mode. However, via time sharing existing channels or establishing a new channel, one per added terminal, this method is also applicable to the full duplex transmission mode. Each of the terminals A-D include a half duplex modem. Each terminal includes input devices such as a push button for indicating that the teleconferencing mode is selected and that the secure mode is selected. Each terminal also includes the ability to display the identify of each of the other teleconferencers. These identities may be scrolled on a visual display for the user of each terminal.
0013For security, each of the terminals employ a type of asymmetric RSA public encryption and private decryption process. The encryption process is noted by EM and the decryption process is noted by DM.
0014Turning now to FIGS. 2A and B, the secure teleconferencing method is shown. First, the users go off hook, block 1. Next, all the users are established in an unsecured teleconferenced arrangement via a usually switching system procedures, block 2. This is accomplished in the typical manner through conference circuitry in the switching network. The call or data transmission at this point is unsecured.
0015To accomplish the teleconference, each of the users of terminals A-D selects the conference mode via pushing a conference push button on his or her terminal. Next, one of the users presses the secure key on his or her terminal, block 3. This serves two functions. First, that terminal becomes the master terminal for controlling the teleconference function. Since all of the terminals include the present method, any of the terminals may be the master for the teleconference. The determination of the master terminal for teleconference is determined by the first to press the secure key on his terminal.
0016The second function of the master terminal is to transmit its access domain message in half duplex to each of the other conferenced terminals. To accomplish this, the master transmits P1800 data, block 3, stops transmitting for 256 bits (block 4), and sends P1800 data of 776 bits (block 5) followed by SCR1 data (scrambled ones for synchronization), block 6. Meanwhile, the slaves are set in the half duplex mode, block 7. The slave confirms the stop gap, block 8. The slaves detect the P1800 data, block 9, and train their modem to receive, 10. The master sends the access domain message (ADM), 11. This is followed by an end of message (EOM) indication, block 12.
0017Next, each slave receives the access domain message and stores it for later processing, block 13. The access domain messages of the master and other slave terminals are processed when the master's authentication message has been received.
0018The transmission of master's access domain message occurs as shown in FIG. 3A. The master first sends a P1800 protocol, followed by a gap, followed by another P1800 protocol, an SCR1 (scrambled 1's and 0's for modem synchronization) bit stream and then the bit stream of the access domain message, followed by an end of message (not shown). Each slave then responds in an appropriate time slot, is determined by a queue index function. This queue index function may be implemented in a number of ways, such as, a strictly arbitrary sequence.
0019The master terminal then sets its modem in the receive mode, blocks 14 and 15.
0020Next, each slave in the teleconference responds with its access domain message in the selected time slot. Since the slave terminals have received the master's access domain message, the NO path has been followed from block 16 to block 17. Next, it is the slave's turn to send its access domain message, the YES path is followed from block 17 to block 18. In FIG. 3A, slave 1 responds with its P1800 protocol (block 18) followed by SCR1 (block 19), and its access domain message ADM block 20 followed by EOM, block 21. Similarly, each slave responds in its time slot. Slave 2 responds in time slot 2. Slave n responds in time slot n. The master terminal receives all the access domain messages of each of the slaves, block 22. Block 23 determines whether all the slaves have responded. If all the slaves have not responded, block 23 transfers control to block 14 to wait for a response. When all the slave terminals respond, the master (block 24) processes the access domain messages of each of the slaves.
0021Next, the master sends its authentication message to each of the slaves, blocks 25 through 28. The authentication message of the master terminal is given by equation (1). AM<sub>m</sub> = [(ID<sub>master</sub>,EM<sub>master</sub>)]xDM<sub>kca</sub> Equation (1) The Authentication Message identifies the particular master terminal, its public or encrypt key and the private decrypt key of its certification authority (KCA). This message is valid only if it is certified by the key certification authority. Further, each of the other terminals may decode this message only if they are certified under the same key certification authority.
0022Block 16 determines for each slave terminal that this is the authentication message. As a result, block 16 transfers control to block 29 which processes the master access domain message (ADM<sub>m</sub>) and the other slaves' access domain messages (ADM<sub>sn</sub>′S). Once the access domain messages have been thereby exchanged, each terminal can determine the identity of the terminal to which it is connected via the teleconference and that they are certified by a common certifying authority such as a KCA. FIG. 3B depicts this transmission of the master. This transmission consists of the 1800 protocol followed by the SRC1 bits, followed by the authorization message and an EOM (not shown). The master terminal sets itself to receive the authentication messages of the slaves, blocks 31 and 32. Next, each slave terminal processes the authentication message of the master (AM<sub>m</sub>), block 30. Each slave terminal generates a unique random number (RN<sub>s</sub>)and a random component message (RCM) from the random number, block 33. The RCM is made by encrypting the slave's unique random number in the master's public key as shown in Equation (2). (RN<sub>s(n)</sub>) X EM<sub>master</sub> = RCM<sub>s(n)</sub> Equation (2) Each slave, then, stores a copy of its unique random number for later use in the final stages of this process. Each slave then responds in its appropriate time slot with its authorization message followed by its random component message. The slave authorization message is similar to the master's authorization message. It is shown in Equation (3). AM<sub>s</sub> = [(ID<sub>slave</sub>,EM<sub>slave</sub>)]XDM<sub>kca</sub> Equation (3) It includes the identity of the slave, the public key of the slave covered by the private key of the certifying authority or KCA.
0023When each slave determines that its time slot is present, that slave "broadcasts" its authorization message (AM<sub>s</sub>), block 34. The slave terminal initialize its modem, blocks 35 and 36. Next, the authorization message (AM<sub>s</sub>) and random component message (RCM<sub>s</sub>) of each slave is transmitted to each of the other slaves, including the master terminal, block 37, followed by an end of message (EOM), block 38. Block 38 transfers control to block 34. Since this slave terminal has transmitted its AM<sub>s</sub> and RCM<sub>s</sub>, block 34 transfers control to block 39.
0024The transmission for slave 1 is shown in FIG. 3B. First the 1800 protocol is sent, then the SCR1 bits, the authorization message of slave 1, followed by approximately 200 milliseconds of filler which is a predefined binary bit pattern and finally the random component message of the slave 1 and end of message indication (not shown). Each slave similarly responds in its assigned time slot.
0025Each slave terminal sets its modem to receive the other terminals AM<sub>s</sub> and RCM<sub>s</sub> messages, blocks 40 and 41. Each slave terminal receives the other slave terminals, AM<sub>s</sub> and RCM<sub>s</sub>, block 42. Also, simultaneously the master terminal receives each of the slave terminals' AM<sub>s</sub> and RCM<sub>s</sub> messages, block 43.
0026When all the slave terminals have responded, each block 39 of each slave terminal transfers control to block 44. Simultaneously, when the master terminal has received all the AM<sub>s</sub> and RCM<sub>s</sub> messages, block 45 transfers control to block 46.
0027The random component message of each terminal includes a unique random number generated by that terminal. This random number is transmitted to the master terminal and is also stored within the terminal. The random number is encrypted with the master's public key to form the random component message. Therefore, even through all of the other slave terminals in the teleconference may receive the RCM, they will not be able to decrypt it.
0028As a result of these transmissions, each slave terminal receives all the authorization messages of the other terminals. Each slave then processes each of the authorization messages of the other slaves, block 44. This includes extracting the identity of each of the other slaves which have been covered by the private key of the certifying authority. The identity of each of the slaves is then scrolled on a viewing device of the terminal in the order in which they are received. As a result, each terminal has established the certified identity of each of the other conferees.
0029The master terminal has also received each of the authentication messages of the other terminals and processed them similarly to that described above for the slave, block 46. Next, the master decrypts each of the slave's random component message, block 46. Since each of the slave's random component message has been covered with the master's public key, the master may decrypt them by applying his private key since this is an asymmetric or one-way function. Each slave sets its modem to receive a message from the master terminal, blocks 47 and 48.
0030When the master terminal receives each of the authorization messages, it decodes each of the other terminals' identification. In addition, the master terminal then scrolls each of the identities of the slave terminals on each visual display on the terminal. Next, the master terminal decrypts each of the slave's random component message. Since each of the slaves have covered their random component with the master's public encrypt key, only the master is able to decode each of the random component messages by application of his private decrypt key. The random component is a predetermined number of bits of information. The random component is, as its name implies, generated randomly by each of the terminals. The larger in terms of bits the random component is, the more difficult this component is to determine for purposes of listening. As a result, the master terminal obtains each of the slave terminals random components. In addition, the master terminal has stored its previously generated random component.
0031Next, the master terminal generates a set of random numbers based upon each of the slave's random numbers and the master's random component or number, block 49. The equations for generating this set of random numbers are shown by Equation Set (4).<maths id="math0001" num=""><img file="EP0402083A2_D0001.tif" /></maths>
0032Examining the last equation of the sets of equations in Equation Set (4) as an example, it can be seen that the new random number for slave 1 RNs(1)′ is comprised of each of the random numbers of the other slaves and the master. These random numbers are exclusive-ORd. Each of the + symbols represents an exclusive-OR operation. The new random number for slave 2 RNs(2)′ is an exclusive-OR of each of the other terminal's random numbers except terminal 2. As a result, the master terminal generates one new random number for each of the terminals in the teleconference which is an exclusive-OR of all the other terminals in that teleconferenced random number except the terminal to which that random number is to be sent.
0033The terminal to which the random number is to be sent has previously stored its own random number. Therefore in FIG. 4, when a given terminal receives the new random number from the master terminal, it must simply exclusive-OR 99 its own stored random number with the primed random number sent from the master terminal. As a result, the terminals have developed a session key. This session key is useful only for this session and is generated for each teleconference call. The generation and transmission of the session key also obeys the "two-man rule", in that interception of a single message will not result in obtaining the random component and hence, the session key.
0034The master terminal covers each of the newly generated primed random numbers with the public encrypt key of the slave terminal to receive that random number as shown in Equation Set (5):<maths id="math0002" num=""><img file="EP0402083A2_D0002.tif" /></maths> Again, since the new primed random number is covered by the slave public encrypt key, only that particular slave may decode using his private decrypt key the new primed random component message. The master generates one such random component message for each slave, covering that message with the slave's public encrypt key.
0035Next, the master generates a crypto synchronization pattern (CS), block 50. The master terminal now formats the final secure call setup message. This message is formulated with the P1800 protocol (block 51) followed by the SCR1 information (block 52), followed by the random component message of each slave in the appropriate time slot. A predetermined amount of filler bits follow the last random component message. After the filler bits, the crypto synchronization message is sent to all terminals by the master. The crypto synchronization message indicates the point at which the symmetric encrypt/decrypt function is to begin. The master terminal then transmits the formatted message (corresponding primed random number) followed by crypto synchronization message, block 53, followed by an EOM, block 54.
0036Each slave terminal then receives its new primed random component message, block 55. In addition, each terminal receives the crypto synchronization message, block 56. Next, each terminal processes the new primed random component message by exclusive-ORing the primed random component which it received with its own previously stored random component, block 57. This exclusive-OR produces a session key. Each of the terminals now have this session key. Therefore, this session key may be used by each terminal's symmetric encrypt/decrypt process to provide secure communications between each of the terminals in a teleconferencing arrangement. A minimal number of messages has been used to achieve security.
0037Lastly, each terminal processes the crypto synchronization message, block 58. This starts each of the symmetric encrypt/decrypt functions at a predetermined point. Therefore, since each terminal has the key and the starting point, it can encode and decode information transmitted to and received from the other terminals in a secure manner.
0038Although the preferred embodiment of the invention has been illustrated, and that form described in detail, it will be readily apparent to those skilled in the art that various modifications may be made therein without departing from the spirit of the invention or from the scope of the appended claims.
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US6993651B2 | Cited by | United States of America | Applicant |
| EP0604911A3 | Cited by | European Patent Office (EPO) | Search report |
| US7340601B2 | Cited by | United States of America | Applicant |
| US6052787A | Cited by | United States of America | Search report |
| US6952768B2 | Cited by | United States of America | Applicant |
| SG80562A1 | Cited by | Singapore | Search report |
| EP0604911A2 | Cited by | European Patent Office (EPO) | Search report |
| GB2357227A | Cited by | United Kingdom | Search report |
| US7237107B2 | Cited by | United States of America | Applicant |
| US7036010B2 | Cited by | United States of America | Applicant |
| WO9747108A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| GB2357227B | Cited by | United Kingdom | Search report |
| US4691347A | Cites | United States of America | Search report |
12 members in 7 offices; this record represents the family
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 36189889 | United States of America | A | |
| 361898 | United States of America | – | |
| US19890361898 | – | – | – |
| 361898 | – | – | – |
Members12
| Document | Office | Kind | |
|---|---|---|---|
| AU5615590A | Australia | A | |
| EP0402083A2This record | European Patent Office (EPO) | A2 | |
| US5003593A | United States of America | A | |
| KR920003783A | Republic of Korea | A | |
| EP0402083A3 | European Patent Office (EPO) | A3 | |
| AU629641B2 | Australia | B2 | |
| EP0402083B1 | European Patent Office (EPO) | B1 | |
| DE69029877D1 | Germany | D1 | |
| ES2097134T3 | Spain | T3 | |
| DE69029877T2 | Germany | T2 | |
| KR0155164B1 | Republic of Korea | B1 | |
| HK1007261A1 | Hong Kong, China | A1 |
42 legal events, as 3 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Announcement of lapse in spainLapsedFD2A | FD2A | ES | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Nl: lapsed or anulled due to non-payment of the annual feeLapsedNLV4 | NLV4 | EP | |
| Se: european patent has lapsedLapsedEUG | EUG | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Change of the address of the representativeCRONIN INTELLECTUAL PROPERTY;CHEMIN DE PRECOSSY 31;1260 NYON (CH)PCAR | PCAR | CH | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Transfer of patentPC2A | PC2A | ES | |
| New agentNV | NV | CH | |
| AssignmentPUE | PUE | CH | |
| Nl: assignments of ep-patentsNLS | NLS | EP | |
| Se: european patent has lapsedLapsedEUG | EUG | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Definitive protectionFG2A | FG2A | ES | |
| Corresponds to:REF | REF | EP | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| New agentNV | NV | CH | |
| Designated contracting statesAK | AK | EP | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOS IGRAGRAH | GRAH | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOS IGRAGRAH | GRAH | EP | |
| Despatch of communication of intention to grantORIGINAL CODE: EPIDOS AGRAGRAG | GRAG | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 0402083
- Publication, DOCDB
- 0402083
- Publication, EPODOC
- EP0402083
- Application
- 90306071
- Application, DOCDB
- 90306071
- Application, EPODOC
- EP19900306071
Titles6
- German
- Telekonferenzverfahren für Verwaltungssystem mit Sicherheitstaste.
- English
- Teleconferencing method for a secure key management system.
- French
- Méthode de téléconférence dans un système de gestion avec touche de sécurité.
- German
- Telekonferenzverfahren für Verwaltungssystem mit Sicherheitstaste
- English
- Teleconferencing method for a secure key management system
- French
- Méthode de téléconférence dans un système de gestion avec touche de sécurité
Classification
- CPC, 5
- H04M3/16
- H04L9/0833
- H04M3/56
- H04M11/06
- H04M2203/609
- IPC, 3
- H04L9 08
- H04M3 56
- H04M11 06
Designated states7
- Contracting states, 7
- Switzerland
- Germany
- Spain
- United Kingdom
- Liechtenstein
- Netherlands (Kingdom of the)
- Sweden