Key management interface to multiple and simultaneous protocols

• US 20030059053A1
• Filed: 07/12/2002
• Published: 03/27/2003
• Est. Priority Date: 09/26/2001
• Status: Abandoned Application

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: General Instrument Corporation (CommScope Holding Company, Inc.)
• Inventors: Medvinsky, Alexander, Peterka, Petr
• Application Number:
  US10/194,922
• Publication Number:
  US 20030059053A1
• Time in Patent Office: Days
• US Class Current: 380/277
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 63/0457 wherein the sending and receiving network entities apply dynamic encryption, e.g. stream encryption cryptographic mechanisms or cryptographic arrangements for stream encryption H04L9/065
• 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 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/70 Media network packetisation

Abstract

A system and method for interfacing protocol applications with a daemon to perform secure key management between the a computer system and a second computer system. The method includes providing a first protocol application running on the first computer, and specifying an application role value from the first protocol application to the daemon, the application role for identifying the first protocol application. Further, the method includes specifying an object containing application data specific to the first protocol application, and employing the object and the application role value for performing key management in order to secure communication of real-time data between the first computer system and the second computer systems.

Claims

1. A key management interface system for interfacing with multiple protocols to perform secure key management, the key management interface system comprising:

one or more applications comprising,

a first application for streaming real-time data;

a second application for provisioning real-time data;

a daemon for performing key management, the daemon interfacing with the first application to secure cryptographic keys for securely streaming the real-time data; and

the daemon interfacing with the second application to secure cryptographic keys for secure provisioning of the real-time data.

2. The interface system of claim 1 wherein the first application comprises one or more software instructions for specifying an application role value, the application role value for uniquely identifying the first application.

15. The system of claim 1 further comprising

one or more software instructions for specifying an object having application data specific to the first application.

3. In a communication system having a daemon running on a first computer, a method for interfacing protocol applications with the daemon to perform secure key management, the method comprising:

providing a first protocol application running on the first computer;

specifying a role value for identifying the first protocol application;

specifying an object containing application data specific to the first protocol application; and

using the object and the application role value for performing key management in order to secure communication of real-time data.

4. The method of claim 3 wherein the daemon is a client daemon, and the method further comprises

sending a key request message to a second computer, the key request message having the role value and the object.

5. The method of claim 4 further comprising

providing a server daemon on the second computer;

receiving the key request message containing the role value and the object;

identifying a third protocol application by using the role value and

forwarding the object to the third protocol application.

6. The method of claim 5 wherein the object contains session rights for accessing the real-time data stream.

7. The method of claim 5 further comprising

validating the session rights;

forwarding a response to the server daemon based on the validation; and

forwarding a key reply message to the client daemon, the key reply message containing the response.

8. The method of claim 3 further comprising

providing a second protocol application running on the first computer system;

specifying an application role value for identifying the second protocol application;

specifying an object containing application data specific to the second protocol application; and

employing the object and the application role value for performing key management in order to secure communication of real-time data between the first and second computer systems.

13. The method of claim 3 wherein the daemon is a peer daemon, the method further comprising

forwarding a key request message to the second computer, the key request message containing the application role value and the object.

14. The method of claim 4 further comprising

providing a peer daemon on the second computer;

receiving, by the peer daemon, the key request message containing the application role value and the object; and

forwarding the object to the third protocol application corresponding to the application role value.

9. A key management interface for interfacing with multiple to securely transfer real-time data, the key management interface comprising:

a first computer system further comprising

a first protocol application;

a second protocol application;

a daemon for performing key management;

upon request for key management from the first protocol application, the daemon interfaces with the first protocol application to perform a first function relating to secure transfer of the real-time data; and

upon request for key management from the second protocol application, the daemon interfaces with the second protocol application to perform a second function relating to secure transfer of the real-time data.

10. The interface of claim 9 wherein the first function is for streaming the real-time data between the first computer system and a second computer system;

and the second function is for performing provisioning relating to the real-time data.

11. The interface of claim 9 wherein upon start-up the first and the second protocol applications register with the daemon.

12. The interface of claim 9 wherein the first protocol specifies to the daemon an application role value for identifying the first protocol.

16. A key management interface system comprising:

a first computer system further comprising

a first protocol application;

a second protocol application; and

a daemon for performing key management;

upon request, the daemon interfaces with the first protocol application and the second protocol application to perform at least one key management function.

17. The interface system of claim 16 further comprising a role value for identifying the first protocol application;

and

an object containing application data specific to the first protocol application, wherein the object and the application role value perform key management in order to secure communication of real-time data.