Internet protocol telephony security architecture

• US 7,568,223 B2
• Filed: 07/15/2004
• Issued: 07/28/2009
• Est. Priority Date: 04/09/1999
• Status: Expired due to Term

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: General Instrument Corporation (CommScope Holding Company, Inc.)
• Inventors: Anderson, Steven E., Fellows, Jonathan A., Medvinsky, Alexander, Sprunk, Eric J., Moroney, Paul
• Primary Examiner(s): Zand; Kambiz
• Assistant Examiner(s): Lipman; Jacob
• Application Number:
  US10/893,047
• Publication Number:
  US 20050027985A1
• Time in Patent Office: 1,839 Days
• Field of Search: 380/279, 380/266, 726/10
• US Class Current: 726/10
• CPC Class Codes: G06F 12/1408 by using cryptography for digital transmission H04L9/00
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 2207/7219 Countermeasures against side channel or fault attacks
• CPC Class Codes: G06F 2211/008 Public Key, Asymmetric Key, Asymmetric Encryption
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04L 9/0841 involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823

Abstract

A secure Internet Protocol (IP) telephony system, apparatus, and methods are disclosed. Communications over an IP telephony system can be secured by securing communications to and from a Cable Telephony Adapter (CTA). The system can include one or more CTAs, network servers, servers configured as signaling controllers, key distribution centers (KDC), and can include gateways that couple the IP telephony system to a Public Switched Telephone Network (PSTN). Each CTA can be configured as secure hardware and can be configured with multiple encryption keys that are used to communicate signaling or bearer channel communications. The KDC can be configured to periodically distribute symmetric encryption keys to secure communications between devices that have been provisioned to operate in the system and signaling controllers. The secure devices, such as the CTA, can communicate with other secure devices by establishing signaling and bearer channels that are encrypted with session specific symmetric keys derived from a symmetric key distributed by a signaling controller.

Claims

1. A secure IP telephony system, the system comprising:

a signaling controller within an IP telephony network and in communication with at least one Cable Telephony Adapter (CTA), and configured to perform call set up and tear down and to generate a symmetric sub-key in response to a request from the at least one CTA, the request including a signaling controller ticket;

wherein the signaling controller ticket comprises a signaling controller session key, an identity of the at least one CTA, and an identity of the signaling controller;

the signaling controller further configured to distribute the symmetric sub-key to the at least one CTA in response to the signaling controller ticket; and

a Key Distribution Center (KDC) within the IP telephony network and coupled to the signaling controller, and configured to generate and distribute the signaling controller ticket and said signaling controller session key to the at least one CTA using public key encryption,

wherein said at least one CTA generates an additional symmetric key specific for a given call based on the symmetric sub-key provided by the signaling controller.

2. The system of claim 1, wherein the signaling controller is configured to generate and distribute the symmetric sub-key in response to a Kerberos request from the at least one CTA.

3. The system of claim 1, wherein the signaling controller distributes the sub-key encrypted with the signaling controller session key.

4. The system of claim 1, wherein the signaling controller receives from the at least one CTA the signaling controller ticket, wherein a portion of the signaling controller ticket is encrypted with a signaling controller server key.

5. The system of claim 1, wherein the request comprises a Kerberos Application Request having the signaling controller ticket and encrypted data including a name of the at least one CTA.

6. The system of claim 1, wherein the request includes a timestamp.

7. The system of claim 1, wherein the signaling controller authenticates the at least one CTA using the signaling controller ticket.

8. The system of claim 1, wherein the signaling controller communicates with the CTA in an IPsec ESP session in response to receiving a valid signaling controller ticket.

9. The system of claim 1, wherein the signaling controller ticket comprises a Kerberos ticket.

10. The system of claim 1, wherein the signaling controller ticket further comprises an expiration time.

11. The system of claim 1, wherein the KDC distributes to the at least one CTA the signaling controller ticket and a copy of the session key outside of the signaling controller ticket encrypted with a CTA public key.

12. The system of claim 1, wherein the KDC distributes the signaling controller ticket to the at least one CTA, and also distributes to the at least one CTA a copy of the session key outside of the signaling controller ticket encrypted using a shared secret derived from a Diffie-Hellman exchange.

13. The system of claim 1, wherein said additional symmetric key is valid for a single call.

14. The system of claim 1, wherein the KDC generates and distributes the signaling controller ticket in a Kerberos exchange with the at least one CTA.

15. The system of claim 9, further comprising a Provisioning Certificate Authority (CA) in communication with the IP telephony network configured to receive a manufacturer signed CTA certificate and distribute an operator network-specific certificate to the at least one CTA.