US 6,629,243 B1Grant
Secure communications system
Issue Date:2003-09-30
•19 Claims
•3 Drawing Sheets
Abstract
A key distribution method for distributing, via a communications network, a key in a multicast communications system in which each one of a plurality of communications is directed to an associated multicast group including a plurality of recipients intended to receive the one communication. The method includes providing a plurality of implemented key distribution methods, dynamically choosing one implemented key distribution method of the plurality of key distribution methods, and distributing at least one key using the one implemented key distribution method.
Related apparatus and methods are also provided.
Metadata
Assignee
- NDS Limited
Inventors
- Amit Kleinman
- Shlomo Kipnis
Application Information
Application Number:US 09/414,061
Filing Date:1999-10-07
Priority Date:1998-10-07
Art Unit:7
Classifications
IPC:
A04L 908
Field of Search:
713163713171
Patent Drawings (3 sheets)
Description
FIELD OF THE INVENTION
[0003] The present invention relates to multicast communications systems in general, and in particular to key distribution mechanisms suitable for use in multicast communications systems.
BACKGROUND OF THE INVENTION
[0004] Multicast communications systems, particularly Internet Protocol (IP) multicast communication systems, are well-known in the art. As is well-known in the art, in an IP multicast message, a single address is used by the sender to indicate a multicast comprising plurality of recipients, possibly including recipients at many different locations.
[0005] Multicast is an internetwork service that provides efficient delivery of data from a source to multiple recipients. It reduces sender transmission overhead, network bandwidth requirements, and the latency observed by receivers. IP Multicast enables efficient, many-to-many datagram distribution over an IP network.
[0006] Multicast is more susceptible to attacks than unicast for many reasons. Multicast presents many more opportunities for interception of traffic. When an attack on a multicast service does take place, a larger number of principals is affected. It is easier for an attacker to target an attack, as multicast services are generally well advertised and their addresses are well-known. Lastly, multicast services typically involve a “crowd” of principals, making it potentially easier for an attacker to pose as another (legitimate) principal or to try to attack in parallel at several locations.
[0007] The following references discuss multicast technology and related security issues known in the art:
[0008] R. Canetti, B. Pinkas, “A taxonomy of multicast security issues”, draft-canetti-secure-multicast-taxonomy-00.txt, May 1998.
[0009] D. Harkins and D. Carrel, “The Internet Key Exchange (IKE)”, draft-ietf-ipsec-isakmp-oakley07.txt, March 1998.
[0010] A. Aziz, T. Markson, and H. Prafullchandra, “Simple Key-Management for Internet Protocols (SKIP)”.
[0011] D. Maughan, M. Schertler, M. Schneider, and J. Turner, “Internet Security Association and Key Management Protocol (ISAKMP)”, draft-ietf-ipsec-isakmp-09.txt, March 1998.
[0012] H. Orman, “The OAKLEY Key Determination Protocol”, draft-ietf-ipsec-oakley-02.txt, July 1997.
[0013] H. Krawczyk, “SKEME: A Versatile Secure Key Exchange Mechanism for Internet”. IEEE Proceedings of the 1996 Symposium on Network and Distributed Systems Security.
[0014] P. Karn and W. Simpson, “Photuris: Session-Key Management Protocol”, draft-simpson-photuris-17.txt, November 1997.
[0015] H. Harney and C. Muckenhim, “Group Key Management Protocol (GKMP) Specification +Architecture”, RFC2093 & RFC2094, July 1997.
[0016] A. Aziz, T. Markson, and H. Prafullchandra, “SKIP Extensions for IP Multicast”.
[0017] A. Ballardie, “Scalable Multicast Key Distribution”, RFC1949, May 1996.
[0018] T. Hardjono, B. Cain, N. Doraswamy, “A Framework for Group Key Management for Multicast Security”, draft-ietf-gkmframework-00.txt, July 98.
[0019] D. Harkins and N. Doraswamy, “A Secure Scalable Multicast Key Management Protocol,” ETF, IETF Draft draft-ietf-ipsecond-00.txt, November 1997.
[0020] S. Mittra, “The Iolus Framework for Scalable Secure Multicasting,” presented at Proceedings of ACM SIGCOMM97, 1997.
[0021] M. Handley and V. Jacobson, “SDP: Session Description Protocol”, RFC 2327, April 1998.
[0022] A television system for controlling access to broadcast transmissions is described in U.S. Pat. Nos. 5,282,249 and 5,481,609, both to Cohen et al.
[0023] The disclosures of all references mentioned above and throughout the present specification are hereby incorporated herein by reference.
SUMMARY OF THE INVENTION
[0024] The present invention seeks to provide improved apparatus and methods for key distribution, suitable for use in a multicast communication system. While the apparatus and methods of the present invention are particularly suited to an Internet Protocol (IP) Multicast system, it is appreciated that the present invention would also be applicable to other types of Multicast systems, with appropriate modifications as will be appreciated by persons skilled in the art. Without limiting the generality of the foregoing, the example of IP Multicast will generally be used throughout the present specification, and the example of IP Multicast will be taken to include Multicast over an Intranet wherever applicable.
[0025] In securing IP Multicast traffic from one source to multiple recipients, it is desirable to implement security apparatus and methods to authenticate the source, to authenticate and to ensure integrity of the data, and possibly to encrypt and/or sign the data At first glance, it appears that these services can be provided using standard authentication, integrity, and encryption methods, based either on symmetric-key or asymmetric-key designs. One might look to known schemes, such as well-known pay television schemes, to provide such standard methods and apparatus.
[0026] A major problem in Secure Multicast systems involves distributing, in real time, the appropriate cryptographic keys from the multicast source to all the authorized recipients of the multicast. The keys used for authentication, integrity, and confidentiality may change frequently, either due to policies that determine that keys need to change, for example, every few seconds, or in response to changes in the membership of the multicast group. A multicast group membership change might comprise an existing member having just left or a new member having just joined the group.
[0027] Generally, the goal of multicast key distribution is to securely deliver common keys to all the authorized members of a multicast group. Having such keys allows a sender to authenticate and/or to encrypt the traffic destined for a multicast group. Thus, the group keys also afford membership-enforcement by allowing only key holders to verify and/or decrypt the multicast traffic. A sender must authenticate and/or encrypt all traffic that it sends to the group in order to maintain secure delivery.
[0028] In certain prior art systems, the key distribution function is assigned to a central network entity, sometimes known as the Key Distribution Center (KDC). However, this method does not scale well for wide-area multicasting, where group members may be distributed across many networks and a wide-area group may be densely populated. Even more complicated is the problem of distributing sender-specific keys in a scalable manner, sender-specific keys being required when data is to be authenticated on a per-sender basis. Pair-Wise key-management protocols and Key Distribution Centers do not provide scalable solutions for the multicast key-management problem.
[0029] Completely automatic protocols for multicast key distribution are currently not considered mature enough for use. For small multicast groups, manual. key distribution or multiple invocations of a unicast (point-to-point) key distribution protocol, such as authenticated Diffie-Hellman, appear adequate. However, for large multicast groups, new scalable techniques and protocols are needed.
[0030] In P Multicast systems, unlike in broadcast TV systems, the multicast traffic is typically routed from the sender to multiple recipients over the existing Internet infrastructure. This means that traffic may pass through intermediate nodes and that it can be listened in to in an unauthorized manner by interested parties. In addition, multicast traffic in the Internet is not synchronized in the way that broadcast over a satellite or over cables is synchronized. Due to the fact that data flows through routers, some packets may be lost, some packets may be delayed, and some packets may come out of order. Finally, the nature of the connectivity in Internet systems may make the use of different key-distribution methods than the ones used in TV broadcasting desirable.
[0031] Known multicast key-distribution methods include:
[0032] 1. Star methods—where the multicast sender corresponds directly with each one of the clients, and keys are handed over securely over point-to-point connections.
[0033] 2. Multicast methods—where keys are sent in multicast packets from the multicast sender to many recipients, and each key in the multicast packet is encrypted specifically for one client, typically using a personal key for that client.
[0034] 3. Group methods—where there are logical or physical subgroups, and each sub-group has a Group Controller that receives the keys from the multicast sender and distributes them inside the group, typically using one of the methods mentioned here.
[0035] 4, Tree methods—where each client is associated with a leaf in a logical tree, and each leaf contains the keys of all the nodes on the path from the root to it. This enables communicating securely with each client or with sub-groups of clients with a small number of keys involved. The number of keys is typically logarithmically related to the number of clients in the system.
[0036] Each of the above-mentioned methods is useful and has merits in a different range of parameters of multicast traffic. These parameters include:
[0037] 1. The size of the multicast group.
[0038] 2. The dynamics of the multicast group (few/many joins, few/many leaves).
[0039] 3. The locality/remoteness of the multicast group members; this may include an absolute location of one or more group members, typically comprising a distance of one or more group members from the key distributor, or a relative location of one or more group members in terms of other group members.
[0040] 4. The existence/nonexistence of client clusters in well defined logical or physical sub-domains.
[0041] 5. The reason for key distribution (periodic mode vs. event-driven mode).
[0042] It is appreciated that other appropriate parameters may also be used.
[0043] More generally, the parameters mentioned above may also be considered to fall into the following groups:
[0044] a characteristic of the associated multicast group;
[0045] a location of at least one recipient comprised in the multicast group;
[0046] a characteristic of the key; and
[0047] a characteristic of the multicast traffic.
[0048] The present invention provides apparatus and methods to support multiple key-distribution methods in a multicast system and a methodology for selecting the method that is best suited for a given set of parameters and for switching between methods, including dynamically switching between methods, even at run time, based on a change in the parameters.
[0049] The apparatus at the sender side preferably comprises:
[0050] a generator of keys, or a repository of keys, the keys intended to be distributed to a multicast group,
[0051] multiple key-distribution sender-side methods, such as, for example, star, multicast, group, tree, as described above;
[0052] a selector that selects and activates a specific method to be used;
[0053] a decision-maker component that evaluates the multicast parameters at run-time; and
[0054] a controller that sends instructions, comprising either in-band instructions, out-of-band instructions, or any appropriate combination thereof, to client receptors regarding the method to use.
[0055] The apparatus at the client side preferably comprises:
[0056] multiple key-distribution client-side methods, corresponding to those mentioned above;
[0057] a selector that selects and activates the specific method to be used;
[0058] a control receiver that receives control instructions from the sender's controller regarding which method to use; and
[0059] a key interpretation component, or a repository of keys received.
[0060] At the sender side the set of multicast parameters is preferably evaluated at run time and a decision is reached as to which method is best under the circumstances.
[0061] Preferably, the decision may be based on decision tables and rules for ranges of the parameters. By way of example, some appropriate rules might look like:
[0062] 1. For small groups, up to X members, use the star method.
[0063] 2. For medium groups, having more than Y and less than Z members, switch to the multicast method.
[0064] 3. For large groups, having more than Z members. use the group method or tree method.
[0065] 4. If groups are logically or physically segmented and there are more than W members in a cluster, then pick a group controller for that cluster. If the rate of membership change is low, use the star method or multicast method. If the rate of membership change is high, use the group or tree methods.
[0066] In the above example, X, Y, Z, and W are parameters of the system for which specific appropriate values could be determined.
[0067] Preferably, there would be a large number of rules in practice.
[0068] Since there could be conflicts between rules, it could be determined that some rules are dominant over others. Alternatively, a weight could be given to each rule, and the result will be based on the conclusion that has gathered the most weight.
[0069] There is thus provided in accordance with a preferred embodiment of the present invention a key distribution method for distributing, via a communications network, a key in a multicast communication system in which each one of a plurality of communications is directed to an associated multicast group including a plurality of recipients intended to receive the one communication, the method including providing a plurality of implemented key distribution methods, dynamically choosing one implemented key distribution method of the plurality of key distribution methods, and distributing at least one key using the one implemented key distribution method.
[0070] Further in accordance with a preferred embodiment of the present invention the step of dynamically choosing includes choosing based, at least in part. on at least one of the following: a characteristic of the associated multicast group, a location of at least one recipient included in the multicast group, a characteristic of the key, a multicast traffic characteristic, a multicast content characteristic and a characteristic of the multicast group.
[0071] Still further in accordance with a preferred embodiment of the present invention the characteristic of the associated multicast group includes at least one of the following: a size of the multicast group, and a dynamic parameter associated with the multicast group.
[0072] Additionally in accordance with a preferred embodiment of the present invention the location includes at least one of the following: an absolute location, typically comprising a distance from the key distributor, a relative location; and an association between the at least one recipient and a sub-domain of the communications network.
[0073] Further in accordance with a preferred embodiment of the present invention the characteristic of the multicast traffic may include at least one of the following: streaming real-time feed; and non-real time transfer.
[0074] Moreover in accordance with a preferred embodiment of the present invention characteristic of the key includes a distribution characteristic.
[0075] Further in accordance with a preferred embodiment of the present invention the communications network includes the Internet.
[0076] Still further in accordance with a preferred embodiment of the present invention the communications network includes an Intranet.
[0077] Additionally in accordance with a preferred embodiment of the present invention the plurality of implemented key distribution methods includes at least one of the following: a star distribution method, a multicast distribution method, a group distribution method, and a tree distribution method.
[0078] There is also provided in accordance with another preferred embodiment of the present invention key distribution apparatus for distributing, via a communications network, a key in a multicast communication system in which each one of a plurality of communications is directed to an associated multicast group including a plurality of recipients intended to receive the one communication, the apparatus including a plurality of implemented key distribution methods, a decision maker and selector for dynamically choosing one implemented key distribution method from the plurality of implemented key distribution methods, and a multicast distribution unit for distributing at least one key using the one implemented key distribution method.
[0079] There is also provided in accordance with another preferred embodiment of the present invention key reception apparatus for receiving, via a communications network, a key in a multicast communication system in which each one of a plurality of communications is directed to an associated multicast group including a plurality of recipients intended to receive the one communication, the key being distributed using one implemented key distribution method chosen from a plurality of methods, and indication of the one implemented key distribution method being transmitted via the communications network, the apparatus including a plurality of implemented key distribution methods, a selector, responsive to the indication of the one implemented key distribution method, for dynamically choosing the one implemented key distribution method from the plurality of implemented key distribution methods, and utilization apparatus for utilizing the key in accordance with the one implemented key distribution method.
[0080] dr
BRIEF DESCRIPTION OF THE DRAWINGS
[0081] The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:
[0082] FIG. 1 is a simplified block diagram illustration of a multicast communication system constructed and operative in accordance with a preferred embodiment of the present invention;
[0083] FIG. 2 is a simplified block diagram illustration of a preferred implementation of a portion of the system of FIG. 1; and
[0084] FIG. 3 is a simplified flowchart illustration of a preferred method of operation of the apparatus of FIG. 2.
DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT
[0085] Reference is now made to FIG. 1 which is a simplified block diagram illustration of a multicast communication system constructed and operative in accordance with a preferred embodiment of the present invention. The system of FIG. 1 comprises a multicast communication system 100, which is designed to allow secure multicast communication, Generally, in the multicast communication system 100 of FIG. 1, multicast communications are authenticated and/or encrypted and validation and/or decryption keys necessary to read the multicast communication arc distributed in a secure way by a central server. One possible method for key distribution involves changing keys every few seconds, as is well-known in the art of pay television. It is well known in pay television systems to encrypt each key using a key known to all receivers or only to authorized receivers. It is also known in pay television systems to send a seed to a one-way function used for generating the decryption key at the receiver end. It is appreciated that similar techniques may be used, separately or in combination, in the present invention.
[0086] The multicast communication system 100 preferably comprises a central site 110, also termed herein a server site 110. The multicast communication system also preferably comprises a plurality of client sites 120, some or preferably all of which comprise key-capable client sites such as a key-capable client site 130.
[0087] Only one server site 110 is shown in FIG. 1 for purposes of simplicity of description, but it is appreciated that a plurality of server sites, possibly but not necessarily in operative communication with each other, may also be used. Only three client sites 120 are shown in FIG. 1. for purposes of simplicity of description, but it is appreciated that a large number of client sites 120, including a large multiplicity such as millions of client sites 120, may preferably be used. It is also appreciated that components and functions shown as being comprised in the server site 110 may alternatively be distributed in different locations.
[0088] Each key-capable client site 130 preferably comprises a client key manager 135 operative to process received keys. A preferred implementation of the client key manager 135 is described in more detail below with reference to FIG. 2.
[0089] The server site 110 preferably comprises the following components, each of which may be implemented in a combination of hardware and software, as is well-known in the art:
[0090] 1. A system management unit 140, operative to control and direct distribution of secure multicast items by the server site 110. The system management unit 140 is preferably operative to manage: individual items, also termed herein articles; predefined collections of items, also termed herein packages; security attributes; and user groups. The term article, as used herein, may also be understood as referring to a part of a multicast transmission, transmitted on a specific channel and having well-defined starting and ending points. Generally, an article is the minimum part of the transmission that can be consumed by a consumer as a content unit; if a consumer or customer has authorization to view an article the consumer or customer has authorization to view the entire article. Typically, an article is the basic unit used for scheduling a multicast in the present invention.
[0091] The system management unit 140 also is preferably operative to enable configuration setup, such as setup of IP address of servers and control of multicast channels. The system management unit 140 may also be operative to perform one or more of the following tasks:
[0092] Extend configuration data
[0093] Provide an interface to a Multicast Address Allocation Server (MAAS) 210 as is well-known in the art, preferably acquiring multicast addresses for the logical multicast channels from the MAAS 210.
[0094] Provide an interface to one or more content providers, such as a content provider 220.
[0095] Analyze the taxonomy of a planned multicast session and adjust the system to the session characteristics. The system management unit 140 may take into consideration the parameters of the multicast groups.
[0096] Set key distribution policy and send the policy to a key manager 160, described below.
[0097] Support different security policies, allowing the system administrator to control the granularity at which a security service is offered. The system management unit 140 preferably incorporates facilities for specifying which security services to use in what combinations, and the security methods. It may take into consideration parameters of the multicast groups. The system management unit 140 preferably allows specification of who may grant access to content objects.
[0098] Manage multicast content items.
[0099] Enable packaging of multicast content items to product items for sale, the package thus produced typically comprising a plurality of content items packaged for sale.
[0100] Provide an interface for a system administrator (not shown), typically a person well versed in operation of the multicast communications system 100, to manage the multicast communication system 100 and to configure operation policies.
[0101] Manage the multicast transportation in the infrastructure that is under the scope of the system:
[0102] Enable/disable multicast transportation to different network segments
[0103] Manage multicast aspects at multicast routers
[0104] Manage scope zones
[0105] 2. A user manager 150, operative to store information about each registered user of the multicast communication system 100 in an appropriate database (not shown), as is well known in the art, and to authorize users for access to each multicast item based on user information such as, for example, a stored user profile, an authentication ID, or a key. It is appreciated that users may be aggregated by the user manager 150 according to common interest, enterprise hierarchy, or any other appropriate criterion. Furthermore, the user manager 150 may store any appropriate user information such as, for example, user preferences and one or more spending limits associated with a user The user manager 150 may also be operative to perform one or more of the following tasks:
[0106] Manage users profiles. User attributes comprised in user profiles are preferably accessible only to the system administrator mentioned above.
[0107] Manage user authentication and user admissions to the multicast communication system 100, typically receiving from a user a request to login to the multicast communication system 100, authenticating the user by validating the user's identity using any appropriate validation method and creating a shared secret key with the user for the session, Methods of creating a shared secret key for a session are well known in the art, and any appropriate method may be used.
[0108] Support user registration for an item and manage access to the item, typically by receiving a user request for accessing a specific multicast item, validating the authorizations of the user to access the item, requesting and receiving a key from a key manager 160, described below, for the item and finally sending the key or keys to the user.
[0109] Support user revocation, typically by receiving a request to terminate a multicast transportation of a specific stream for a specific user from either a user/client application or the system management unit 140 or the system administrator and handling the request appropriately, such as by sending a key revocation request to a key manager 160, described below.
[0110] Support termination of client session, typically by receiving a logoff request from a user/client and handling the request appropriately, such as by sending a key revocation requests to a key manager 160 described below, if appropriate, completing a measurement of time or data volume that was consumed by the user during the session, or by carrying out any other appropriate action.
[0111] Support online package purchase.
[0112] Manage and monitor the active users of the multicast communication system 100, typically including monitoring user behaviors, preferably in an attempt to identify one or more suspicious user behaviors. Suspicious user behaviors might include one or more of the following: a high rate of login/logout attempts, particularly unsuccessful attempts; login/logout attempts, particularly unsuccessful attempts, on different terminals within a short period of time; or other suspicious behaviors, as are well known in the art. When identifying suspicious activity the user manager 150 preferably reacts as follows, including one or more of the following actions:
[0113] Terminate a current session in progress.
[0114] Block new session attempts that match a criterion, such as a criterion related to an identified suspicious activity, over a specified time period, such as a predefined time period.
[0115] Notify users of any unsuccessful login attempts that may have been made since their last login.
[0116] Block one or more suspicious user accounts.
[0117] Report to the system administrator on the above activities and on actions taken.
[0118] Enable tracking of user activities, such as for purposes of auditing and/or accounting, by maintaining one or more user activity logs.
[0119] Enhance access options to user profiles by carrying out one or more of the following:
[0120] Support updates of some of the user attributes by the user.
[0121] Support retrieve of some of the user attributes by content providers.
[0122] 3. A key manager 160, operative to manage keys within the multicast communication system 100. Some of the interactions of the key manager 160 have been described above with reference to other elements of the system of FIG. 1.
[0123] The key manager 160 preferably handles, controls and directs the issuing, deploying and storage of encryption keys. The key manager 160 preferably receives a key distribution policy from the system management unit 140. The key distribution policy preferably specifies the frequency of key distribution and sets procedures by which the key manager can grant, deploy and revoke keys.
[0124] The key manager 160 may also be operative to perform one or more of the following tasks:
[0125] Receive requests for keys and generate the keys.
[0126] Create key encryption keys (KEKs). As described above, the multicast communication system 100 is preferably operative to change keys frequently during the multicast of an item, such as, for example, once every several seconds, using a method similar to methods which are well known in the pay television field. Typically, each new key is encrypted with a key encryption key (KEK); managing distribution of the KEK such that only authorized users receive each KEK is an important function of the present invention.
[0127] Distribute the KEKs to the authorized registered users, typically using one of the key distribution methods previously described in a case where a multicast distribution method is chosen.
[0128] Pass the KEK to a multicast distribution unit 190, described below,
[0129] Receive requests, typically from the user manager 150, for key revocation for a specific client/content combination, determine the method for key revocation and revoke the keys.
[0130] Determine the appropriate key distribution method.
[0131] A preferred implementation of the key manager 160 is described in more detail below with reference to FIG. 2.
[0132] 4. A scheduler 170, preferably operative to manage a schedule of articles or items to be multicast by the multicast communication system 100. The scheduler 170 preferably receives requests for article transmission times from the system management unit 140, assembles a transmission schedule based, at least in part, on the received requests, and allows an operator to modify and store the transmission schedule, which is ultimately acted upon by a multicast distribution unit 190, described below. The scheduler 170 is also preferably operative to perform one or more of the following tasks:
[0133] Automatic/manual scheduling of articles across logical channels and time tables; that is, an article is typically assigned to a specific logical channel or set of logical channels at a specific time.
[0134] Support scheduling rules.
[0135] Support scope zone and multicast address allocation.
[0136] 5. An encryption engine 180, preferably operative to receive as input multicast content and/or multicast control information, typically received from a multicast distribution unit 190, described below. The encryption engine 180 also typically receives one or more keys from the key manager 160. The encryption engine 180 is preferably operative to encrypt and/or sign the multicast content and/or multicast control information according to an appropriate encryption method. The encryption method used preferably enables encoding and or signing of the content and/or control information using a cryptographic key, as is well known in the art.
[0137] The encryption engine 180 is also preferably operative to perform one or more of the following tasks:
[0138] Set and get encryption key; typically, the multicast distribution unit 190 gets a key from the key manager 160 and sets the key to the encryption engine 110 for encryption and/or signing.
[0139] Receive plain unencrypted data, including multicast content or multicast control information, and apply an encryption method to the data, producing encrypted data as output.
[0140] Set and get configuration data, typically getting configuration data from the system management unit 140 and setting the data to the encryption engine 180.
[0141] Support data signing, preferably using any appropriate method, such as a method well-known in the art.
[0142] 6. A multicast distribution unit 190, typically operative to perform one or more of the following tasks:
[0143] Receive content from an appropriate source, preferably comprising the external content provider 220, according to a specified schedule, typically specified by the scheduler 170. The content provider 220 may comprise any appropriate content provider, as is well-known in the art, and may alternatively be comprised within the server site 110.
[0144] Encrypt and/or authenticate received content, preferably in conjunction with the encryption engine 180 and by using the encryption engine 180 as described above, with content protection keys, preferably received from the key manager 160.
[0145] Encrypt and/or authenticate the content protection keys, preferably in conjunction with the encryption engine 180 and by using the encryption engine 180 as described above, with KEKs received from the key manager 160.
[0146] Multicast the encrypted data multiplexed with the encrypted content keys, using any appropriate multiplexing method such as an appropriate method well-known in the art.
[0147] Convey SDP messages to clients in a proactive fashion, that is, the SDP messages are not explicitly requested by the clients. SDP messages, as is well known in the art, are messages that conform to the format specified in the Session Description Protocol 2327 RFC, as described in M. Handley and V. Jacobson, “SDP: Session Description Protocol”, RFC 2327, April 1998.
[0148] Assign multicast addresses for multicast channels in the planned schedule.
[0149] The server site 110 is preferably in operative communication with the following related external components, some or all of which may alternatively be comprised in the server site 110:
[0150] a security manager 200, which preferably generates and maintains user authentication data and which may, for example, comprise a password server or a certificate server, and
[0151] a subscriber management system (SMS) 205, which preferably handles maintenance, billing, control and general supervision of subscribers to conditional access technology multicast services, typically comprising either an automatic system where subscribers order entitlement by entering information online, typically via a PC or a telephone, and/or a manual system in which subscribers speak with an operator who manually enters their entitlement requests.
[0152] The operation of the system of FIG. 1 is now briefly further described. The system management unit 140 is preferably responsible for content management. The system management unit 140 preferably enables an administrator of the system of FIG. 1 to define articles and packages and to manage them.
[0153] The user manager 150 preferably enables the administrator to define users and to manage their profile and authorizations. The scheduler 170 preferably enables the administrator to create a schedule for multicasting articles. The multicast distribution unit 190 preferably multicasts articles according to a schedule plan. In case an article needs to be encrypted, it being appreciated that one or more articles may not necessarily need to be encrypted, the article is preferably encrypted by the encryption engine 180, preferably using content keys which are generated by the key manager 160.
[0154] The key manager 160 also preferably encrypts the content keys using KEKs. The multicast content, preferably comprising a plurality of articles, is multiplexed with multicast control information preferably including for example, encrypted content keys. The multiplexed multicast content is preferably distributed by the multicast distribution unit 190 via a multicast delivery infrastructure, typically comprising multicast enabled routers and switches within the Internet, as is well known in the art.
[0155] A client 120, typically comprising a key-enabled client 130, preferably begins use of the system of FIG. 1 by registering for a client session. The registration process includes authentication of the client 130 and the server site 110. The client then typically orders an article and upon a successful validation of the client's authorization by the user manager 150, the client typically receives one or more KEKs, which are used for decrypting the multicast content keys, typically either from the user manager 150 or within a multicast stream that is distributed by the multicast distribution unit 190 during the session. The content is received by the client where it is decrypted, typically including processing by the client key manager 135, and used by the appropriate applications.
[0156] Reference is now made to FIG. 2, which is a simplified block diagram illustration of a preferred implementation of a portion of the system of FIG. 1. The portion of the system of FIG. 1 shown in FIG. 2 includes the key manager 160 of the server site 110 and a client key manager 135 of a client 130 of FIG. 1. Other elements of FIG. 1 are omitted from FIG. 2 for purposes of simplicity of description. The apparatus of FIG. 2 is designed to implement an improved method of multicast key distribution.
[0157] The apparatus of FIG. 2 includes the following components, each of which may be implemented in any appropriate combination of hardware and software, except as otherwise described below:
[0158] Preferably comprised in the key manager 160, a plurality of implemented distribution methods 222, each implemented distribution method 222 being implemented in any appropriate combination of hardware and software such as, for example: stored in an appropriate fashion, such as stored in the form of a computer program; implemented in special purpose hardware; or implemented in any other appropriate manner. Each implemented distribution method 222 typically comprises a key distribution method, either a method well-known in the art or any other appropriate method. Without limiting the generality of the foregoing, the following methods, known in the art, comprise some examples of appropriate implemented distribution methods 222:
[0159] Star methods—where the multicast sender corresponds directly with each one of the clients, and keys are handed over securely over point-to-point connections.
[0160] Multicast methods—where keys are sent in multicast packets from the multicast sender to many recipients, and each key in the multicast packet is encrypted specifically for one client, typically using a personal key for that client.
[0161] Group methods—where there are logical and/or physical sub-groups, and each sub-group has a Group Controller that receives the keys from the source and distributes them inside the group, typically using one of the methods mentioned here.
[0162] Tree methods—where each client is associated with a leaf in a logical tree, and each leaf contains the keys of all the nodes on the path from the root to it. This enables communicating securely with each client or with sub-groups of clients with small number of keys involved, the number of keys being typically logarithmically related to the number of clients in the system.
[0163] Preferably comprised in the key manager 160, a selector 225, a key source 228, a decision maker 230, and a controller 240. The selector 225 is typically responsible, under control of the decision maker 230, to select a method for distribution of a key received from the key source 228. The decision maker 230 preferably decides on a key distribution method from among the plurality of implemented distribution methods 222 in accordance with appropriate criteria. For example, the decision may be based on decision tables and rules for ranges of the parameters. By way of example, some appropriate rules might include rules like the following:
[0164] 1. For small groups, up to X members, use the star method.
[0165] 2. For medium groups, having more than Y and less than Z members, switch to the multicast method.
[0166] 3. For large groups, having more than Z members, use the group method or tree method.
[0167] 4. If groups are physically segmented and there are more than W members in a cluster, then pick a group controller for that cluster. If the rate of membership change is low, use the star method or multicast method. If the rate of membership change is high, use the group or tree methods.
[0168] Preferably, there would be a large number of rules in practice.
[0169] Since there could be conflicts between rules, it could be determined that some rules are dominant over others. Alternatively, a weight could be given to each rule, and the result will be based on the conclusion that has gathered the most weight.
[0170] The controller 240 is preferably operative to transmit the keys and associated control information.
[0171] The following example provides one particularly detailed example of how relevant factors might be taken into account by the decision maker 230:
| FACTOR |
[0172] The following are sample values for the attributes in the above example.
Grades
[0173] Very good=4
[0174] Good=3
[0175] Fair=2
[0176] Weak 1
[0177] Not Recommended=0
Number of Members
[0178] Few :Size<50
[0179] Small :50<=Size<500
[0180] Medium :500<=Size<5000
[0181] Large :5000<=Size<50000
[0182] Very large :Size>=50000
Rate of Key Distribution
[0183] X=first threshold of key exchange per time
[0184] Y=second threshold key exchange per time
[0185] Low: Rate<X
[0186] Medium: X<=Rate<Y
[0187] High: Y<=Rate
[0188] It is believed that actual values for X and Y would need to be determined for each particular system configuration.
[0189] It is appreciated that the above example is one possible example only, that many other examples are possible, and that the above example is not intended to be limiting.
[0190] The decision maker 230 preferably acts dynamically; that is, a new method from the plurality of methods 222 may be chosen at any appropriate time, due to a change in any factor on which the decision maker 230 bases a decision.
[0191] Preferably comprised in the key manager 160 is a controller 240. The controller 240 is preferably operative to receive information from the selector 225, preferably comprising a key and sufficient information to allow the controller 240 to carry out distribution of the key in accordance with the method selected by the selector 225 from among the plurality of methods 222. The controller 240 preferably transmits control information, the control information preferably including one or more keys and information identifying a distribution method being used. It is appreciated that particular details of key distribution in each case will preferably be based on the distribution method being used, as is well-known in the art.
[0192] The control information is typically received at a client key manager 135. While the client key manager 135 is shown as being comprised in a key-enabled client 130, it is appreciated that the client key manager 135 may also be comprised, for example, in a server in an Intranet, the Intranet comprising one or more clients 120 and/or key-enabled clients 130; in a regional server (not shown); in a corporate server (not shown); or in any other appropriate client or appropriate server, as is well-known in the art.
[0193] The client key manager 135 preferably comprises a control receiver 250. which is preferably operative to receive the control information sent by the controller 240. In response to the information identifying the distribution method being used, the controller 240 is preferably operative to direct a selector 225 to select an appropriate key distribution method from a plurality of implemented distribution methods 222. The key is then processed appropriately such as, for example, by being utilized within the client key manager 135, including by being stored in a key store 160, or by being supplied to another component of the system of FIG. 1, or otherwise processed as appropriate.
[0194] Reference is now made to FIG. 3, which is a simplified flowchart illustration of a preferred method of operation of the apparatus of FIG. 2. The method of FIG. 3 is self-explanatory with reference to the above discussion.
[0195] It is appreciated that various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable subcombination.
[0196] It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the invention is defined only by the claims which follow:
Claims
What is claimed is:
1. A key distribution method for distributing, via a communications network, a key in a multicast communications system in which each one of a plurality of communications is directed to an associated multicast group comprising a plurality of recipients intended to receive the one communication, the method comprising:
providing a plurality of implemented key distribution methods;
dynamically choosing one implemented key distribution method of the plurality of key distribution methods; and
distributing at least one key using the one implemented key distribution method.
2. A method according to claim 1 and wherein the step of dynamically choosing comprises choosing based, at least in part, on at least one of the following:
a characteristic of the associated multicast group;
a location of at least one recipient comprised in the multicast group;
a characteristic of the key;
a multicast traffic characteristic; and
a multicast content characteristic.
3. A method according to claim 2 and wherein the characteristic of the associated multicast group comprises at least one of the following:
a size of the multicast group; and
a dynamic parameter associated with the multicast group.
4. A method according to claim 2 and wherein the location comprises at least one of the following:
an absolute location;
a relative location; and
an association between the at least one recipient and a sub-domain of the communications network.
5. A method according to claim 3 and wherein the location comprises at least one of the following:
an absolute location;
a relative location; and
an association between the at least one recipient and a sub-domain of the communications network.
6. A method according to claim 2 and wherein the characteristic of the key comprises a distribution characteristic.
7. A method according to claim 3 and wherein the characteristic of the key comprises a distribution characteristic.
8. A method according to claim 1 and wherein the communications network comprises the Internet.
9. A method according to claim 2 and wherein the communications network comprises the Internet.
10. A method according to claim 1 and wherein the communications network comprises an Intranet.
11. A method according to claim 2 and wherein the communications network comprises an Intranet.
12. A method according to claim 1 and wherein the plurality of implemented key distribution methods comprises at least one of the following:
a star distribution method;
a multicast distribution method;
a group distribution method; and
a tree distribution method.
13. A method according to claim 2 and wherein the plurality of implemented key distribution methods comprises at least one of the following:
a star distribution method;
a multicast distribution method;
a group distribution method; and
a tree distribution method.
14. Key distribution apparatus for distributing, via a communications network, a key in a multicast communications system in which each one of a plurality of communications is directed to an associated multicast group comprising a plurality of recipients intended to receive the one communication the apparatus comprising:
a plurality of implemented key distribution methods;
a decision maker and selector for dynamically choosing one implemented key distribution method from the plurality of implemented key distribution methods, and
a multicast distribution unit for distributing at least one key using the one implemented key-distribution method.
15. Apparatus according to claim 14 and wherein the plurality of implemented key distribution methods comprises at least one of the following:
a star distribution method;
a multicast distribution method;
a group distribution method; and
a tree distribution method.
16. Apparatus according to claim 14 and wherein said dynamically choosing comprises choosing based, at least in part, on at least one of the following:
a characteristic of the associated multicast group;
a location of at least one recipient comprised in the multicast group;
a characteristic of the key;
a multi cast traffic characteristic; and
a multicast content characteristic.
17. Key reception apparatus for receiving, via a communications network, a key in a multicast communications system in which each one of a plurality of communications is directed to an associated multicast group comprising a plurality of recipients intended to receive the one communication, the key being distributed using one implemented key distribution method chosen from a plurality of methods, and indication of the one implemented key distribution method being transmitted via the communications network, the apparatus comprising:
a plurality of implemented key distribution methods;
a selector, responsive to the indication of the one implemented key distribution method, for dynamically choosing the one implemented key distribution method from the plurality of implemented key distribution methods; and
utilization apparatus for utilizing the key in accordance with the one implemented key distribution method.
18. Apparatus according to claim 17 and wherein the plurality of implemented key distribution methods comprises at least one of the following:
a star distribution method;
a multicast distribution method;
a group distribution method; and
a tree distribution method.
19. Apparatus according to claim 17 and wherein said dynamically choosing comprises choosing based, at least in part, on at least one of the following:
a characteristic of the associated multicast group;
a location of at least one recipient comprised in the multicast group;
a characteristic of the key;
a multicast traffic characteristic; and
a multicast content characteristic.
Patent Citations (10)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4611272(A) | 1986-09-01 | Lomet | Examiner |
| US5210794(A) | 1993-05-01 | Brunsgard | Examiner |
| US5282249(A) | 1994-01-01 | Cohen et al. | Applicant |
| US5481609(A) | 1996-01-01 | Cohen et al. | Applicant |
| US5644768(A) | 1997-07-01 | Periwal et al. | Applicant |
| US5708709(A) | 1998-01-01 | Rose | Applicant |
| US5720036(A) | 1998-02-01 | Garfinkle et al. | Applicant |
| US5748736(A) | 1998-05-01 | Mittra | Applicant |
| US5761500(A) | 1998-06-01 | Gallant et al. | Applicant |
| EP887982(A2) | 1998-06-01 | Applicant |
Non-Patent Literature (14)
- D. Maughan et al., “Internet Security Association and Key Management Protocol,” Materials Collected From the World Wide Web, http://www.ietf.org/internet-drafts/draft-ietf-ipsec-isakmp-09.txt, Mar. 10, 1998, pp. 1-73.Applicant
- A. Aziz et al., “Simple Key-Management for Internet Protocols (SKIP),” Internet Memorandum, Jan. 27, 1998, pp. 1-20.Applicant
- R. Canetti et al., “A Taxonomy of Multicast Security Issues,” IBM Research and the Weizmann Institute, Internet Memorandum, May 1998, pp. 1-12.Applicant
- H. Orman, “The Oakley Key Determination Protocol,” University of Arizona, Dept. of Computer Science, Internet Memorandum, Sep. 10, 1997, http://ftp.ietf.org/internet-drafts/draft-ietf-ipsec-oakley-02.txt, pp. 1-41.Applicant
- P. Karn et al., “Photuris: Session-Key Management Protocol,” Internet Memorandum, Nov. 1997, http://www.physnet.uni-hamburg.de/provos/photuris/draft-simpson-photuris-current.txt, pp. 1-61.Applicant
- T. Hardjono et al., “A Framework for Group Key Management for Multicast Security,” Bay Networks, Internet Memorandum, Jul. 1998, http://www.ietf.org/internet-drafts/draft-ietf-ipsec-gkmframework-00.txt, pp. 1-19.Applicant
- M. Handley et al., “SDP: Session Description Protocol,” Network Working Group Memorandum, Apr. 1998, pp. 1-42.Applicant
- A. Aziz et al., “Skip Extensions for IP Multicast,” Internet Memorandum, Feb. 23, 1998, http:/www.skip.org/spec/eipm.html, pp. 1-5.Applicant
- H. Harney et al., “Group Key Management Protocol (GKMP) Specification,” Sparta, Inc. Internet Memorandum, Jul. 1997, http://andrew2.andrew.cmu.edu/rfc/rfc2093.html, pp. 1-20.Applicant
- H. Harney et al., “Group Key Management Protocol (GKMP) Architecture,” Sparta, Inc. Internet Memorandum, Jul. 1997, http://andrew2.andrew.cmu.edu/rfc/rfc2094.html, pp. 1-18.Applicant
- A. Ballardie, “Scalable Multicast Key Distribution,” University College, London, Internet Memorandum, Jun. 20, 1995, pp. 1-16.Applicant
- D. Harkins et al., “The Internet Key Exchange (IKE),” Cisco Systems, Internet Memorandum, Nov. 1998, http://www.ietf.org/rfc/rfc2409.txt, pp. 1-34.Applicant
- S. Mittra, “IOLUS: A Framework for Scalable Secure Multicasting,” Proceedings of ACM SIGCOMM '97, Sep. 1997, pp. 1-12.Applicant
- H. Krawczyk, “SKEME: A Versatile Secure Key Exchange Mechanism for Internet,” IEEE Proceedings of the 1996 Symposium on Network and Distributed Systems Security, Feb. 1996, pp. 114-127.Applicant