WO2004100443A1 - Systeme de gestion d'informations - Google Patents

Systeme de gestion d'informations Download PDF

Info

Publication number
WO2004100443A1
WO2004100443A1 PCT/JP2003/005844 JP0305844W WO2004100443A1 WO 2004100443 A1 WO2004100443 A1 WO 2004100443A1 JP 0305844 W JP0305844 W JP 0305844W WO 2004100443 A1 WO2004100443 A1 WO 2004100443A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
common key
terminal device
content execution
content
Prior art date
Application number
PCT/JP2003/005844
Other languages
English (en)
Japanese (ja)
Inventor
Yukitoshi Maeda
Original Assignee
Stark Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Stark Co., Ltd. filed Critical Stark Co., Ltd.
Priority to AU2003235920A priority Critical patent/AU2003235920A1/en
Priority to PCT/JP2003/005844 priority patent/WO2004100443A1/fr
Publication of WO2004100443A1 publication Critical patent/WO2004100443A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0838—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/12—Transmitting and receiving encryption devices synchronised or initially set up in a particular manner
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/60—Digital content management, e.g. content distribution

Definitions

  • the present invention provides a server device that transmits content and content execution information relating to the execution of the content, and an encryption key (a common key scheme) for distributing the information secretly between terminal devices that receive the content and information. (A common key).
  • encryption technology keys used to keep information confidential (a common key method is common) or the information generated by the key is transmitted between the information sending side and the receiving side through a communication network or the like. They were trying to share between the two by interacting through. For example, there are the following conventional technologies.
  • the client has a common key of the common key method used for encrypting information and a public key of the public key method (corresponding to the secret key of the server) for encrypting the common key.
  • the common key is encrypted with the public key and transmitted to the server
  • the server decrypts the common key encrypted with the public key with its own private key, which allows the server and the client to share the common key. After that, information encrypted with the common key is exchanged with a server and a client (Japanese Patent Application Laid-Open No. 2002-305515).
  • the present invention provides a common key shared between a sender and a receiver of information without transmitting and receiving the common key between the sender and the receiver of the information. Provide a mechanism that can be easily changed.
  • the present invention utilizes an information management system or the like including a server device for transmitting content and content execution information relating to execution of the content, and a terminal device for receiving the server and the terminal device.
  • the common key shared in the system of the present invention is mainly for protecting the content execution information.
  • the server device and the terminal device have the same usage condition information.
  • the usage condition information is information relating to any one or more of the number of usages of the content, the usage period, the usage period, and the content ID that are allowed for the terminal device, that is, information indicating a range in which the execution of the content is allowed.
  • the method by which the server device and the terminal device first have the same usage condition information does not matter.
  • the server and terminal share a common key by the following mechanism. First, the server device and the terminal device share each other based on the usage condition information. Generate a passkey. As described above, since the server device and the terminal device share the usage condition information, a corresponding common key is generated for each.
  • the common key can be shared between the server device and the terminal device.
  • the present invention further updates the usage condition information in each of the server device and the terminal device so that the server device and the terminal device have the same usage condition information even after the update.
  • This is characterized in that a shared key newly generated based on the updated usage condition information can be shared between the server device and the terminal device.
  • Update of usage condition information is performed as follows.
  • the server device encrypts the content execution information, which is information relating to the execution of the content executed by the terminal device, using the common key generated by itself, and transmits the encrypted content execution information to the terminal device. Further, the server device updates its own use condition information based on the content execution information.
  • the terminal device receives the encrypted content execution information transmitted from the server device, decrypts the content execution information with the common key generated based on the usage condition information (before updating) as described above, and executes the content execution information. Get. Then, the terminal device updates its own use condition information based on the decrypted content execution information. Since the server device and the terminal device update their own usage condition information based on the same content execution information, the updated usage condition information is also the same. Therefore, even when the server device and the terminal device newly generate a common key based on the updated usage condition information, respectively, the generated common key corresponds to the server device and the terminal device, and the shared key is generated between the two devices. Can share a common key. BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 is a diagram illustrating an example of the concept of the embodiment.
  • FIG. 2 is a diagram illustrating an example of the configuration of the embodiment.
  • Figure 3 shows an example of updating the usage condition information based on the content execution information. It is a figure showing an example of an example.
  • FIG. 4 is a diagram illustrating an example of a processing flow according to the embodiment.
  • FIG. 5 is a diagram illustrating an example of the configuration of the embodiment.
  • FIG. 6 is a diagram illustrating an example of content execution information used in the embodiment. BEST MODE FOR CARRYING OUT THE INVENTION
  • FIG. 1 is a diagram showing an example of the concept of the present invention. An example of the concept of the present invention will be described with reference to FIG.
  • the present invention relates to a key (common key) used for encrypting and decrypting the content execution information and the like in a system including a server device that transmits the content and the content execution information and a terminal device that receives the content and the content execution information. ) Is shared between the server device and the terminal device.
  • the server device and the terminal device shared usage condition information A.
  • the usage condition information is information relating to one or more of the number of usages, the usage expiration date, the usage period, and the content ID in which the terminal device is allowed to execute the content.
  • the content could not be executed only with this usage condition information, and content execution information regarding the execution of the content was required for each individual content. Therefore, the terminal device requested the super device to deliver the content execution information A.
  • the server generates a common key A of the common key system based on the usage condition information A shared with the terminal, and transmits the encrypted content execution information A obtained by encrypting the content execution information A to the terminal. .
  • the terminal device received the encrypted content execution information A and generated a common key A based on the usage condition information A shared with the server device. Server as described above Since the device also generated the common key A based on the same usage condition information A, the server device and the terminal device could share the common key A. Then, the terminal device decrypts the encrypted content execution information A with the common key A.
  • the server device updates its own use condition information A to use condition information B based on the content execution information A that has been encrypted.
  • the usage condition information A was managed based on the content execution information A.
  • the terminal device also updates its own use condition information A to use condition information B based on the decrypted content execution information A.
  • the usage condition information A was managed based on the content execution information A in the same manner as the server device.
  • the terminal device requested the server device to deliver the content execution information B relating to the execution of another content.
  • the server device encrypted the content execution information B with the common key B generated based on the updated usage condition information B and transmitted it to the terminal device.
  • the terminal device also generated a common key B based on the updated usage condition information B.
  • the server device and the terminal device could share the common key B.
  • the common key B or the generated information of the common key B was not transmitted and received between the server device and the terminal device.
  • FIG. 2 is a diagram illustrating an example of a functional block according to the present embodiment. An example of the configuration of the present embodiment will be described with reference to FIG.
  • the present embodiment is an information management system including a server device 0200 and a terminal device 0210. '
  • Server device 0 2 0 0 is a server device side use condition information management unit 0 2 0 1, a server-side common key generation unit 202, an encryption unit 202, and a transmission unit 204.
  • the “server device usage condition information management unit 0 201” associates the terminal device 0 210 with the number of times of use of content, the usage period, the usage period, Use condition information, which is information about one or more of the content IDs, is managed based on the content rate information, which is information about the execution of content.
  • “Managing usage condition information based on content execution information” means that the present embodiment mainly updates usage condition information based on content execution information. For example, as shown in the figure, the use condition information A is updated to the use condition information B based on the content execution information.
  • the “usage condition information” is information relating to any one or more of the number of times of use, the expiration date, the usage period, and the content ID permitted for the terminal device 0210.
  • the use condition information indicates a range in which the content execution is permitted in the terminal device 0 210, but the content cannot be executed only by the terminal device 0 210 having this use condition information.
  • content execution information is required.
  • the usage condition information may be, for example, information indicating that the number of times the content is allowed to be used by the terminal device 210 is 10 times. Further, the usage condition information may be, for example, information obtained by converting the number of times of use and the like into points.
  • This usage condition information has the same contents in the server-side usage condition information management unit 0201 and the terminal device-side usage condition information management unit 0221 of the terminal device 210 described later. Prerequisite, that is, sharing. First, share the usage condition information.
  • the same usage condition information may be input to the server device 0210 and the terminal device 0200 without passing through the communication network, or the communication network may be connected from one to the other. May be transmitted via the Internet.
  • the use condition information is updated on each device based on the same content execution information. Be managed. Therefore, the updated usage condition information is not transmitted / received between the server device 0200 and the terminal device 0210, and the server device-side usage condition information management unit 0201 and the terminal device 201 are not transmitted / received. It is shared by the device side use condition information management unit 0 2 1 1. In other words, it can be said that the usage condition information is synchronized without using communication.
  • the use condition information is also used for generating a common key, as described later.
  • Content execution information is information relating to the execution of content executed by the terminal device. As described above, content execution information is required to execute content on a terminal device. The terminal device can execute the content based on the content execution information within the “permitted range of content execution” indicated by the usage condition information. Specifically, the content execution information may include a content ID of a specific content, an execution file of the content associated with the content ID, and the like. The content ID may be managed in a server device and a terminal device to be described later by a table configured to be associated with information on what content should be used to update the usage condition information. .
  • FIG. 3 is a diagram illustrating an example in which the usage condition information is similarly updated in each of the server device and the terminal device based on the content execution information.
  • the usage condition information is converted into a point
  • the content execution information includes a content ID associated with a point required to execute the content.
  • Figure A is included in the content execution information. This is an example of a table configured by associating a content ID to be executed with a point required for executing the content specified by the content ID. As shown in FIG. A, the content ID “001” of the movie A is managed in association with the point “3 points” required for executing the content of the movie A.
  • the content ID “002” of document B is managed in association with a point “2 points” required for executing the content of the document.
  • the content ID “003” of the content of the sport C is managed in association with the point “1 point” required for executing the content of the sport C. In this case, based on the content ID included in the content execution information, a point required for executing the content in the server device and a terminal device described later is specified.
  • Figure B shows that the usage condition information “100 points” first shared by the server device and the terminal device is necessary for the execution of specific content because they are registered in the server device and the terminal device.
  • the content execution information includes the content ID. Therefore, if the server device and the terminal device acquire the same content execution information, etc., the same "point required for content execution" can be specified in both devices based on the table shown in Fig. A. Can be done. Then, based on the specified “points required for executing the content”, the server device and the terminal device can update the usage condition information points and can share the updated usage condition information points.
  • the server device and the terminal For example, based on the content execution information including the content ID “001” of movie A, three points are required to execute the content of movie A, and the server device and the terminal The point of the usage condition information of the device is updated from the first shared point of 100 to 97 points (update point A;). Furthermore, based on the content execution information including the content ID “002” of documentary B. In this case, the number of bytes required to execute the contents of the document is 2 points, and the usage condition information of the super-unit and the terminal device is from the updated 97 points mentioned above. The content is updated to 95 points (updated point B) t In addition , if the content execution information including the content ID “003” of sports C is included, the sports content is executed. The required point is one point, and the usage condition information of the server device and the terminal device is updated from 95 points after the above-mentioned update to 94 points (update) Point C).
  • the “server device-side common key generation unit 0202” generates a common key based on the use condition information. For example, as shown in the figure, a common key is generated based on the usage condition information A managed by the server-side usage condition information management unit 0201. After the usage rule information A is updated to the usage rule information B in the server side usage rule information management unit 0201, a common key is generated based on the updated usage rule information B. In this case, the common key generated based on usage condition information A is different from the common key generated based on usage condition information B. In other words, if the usage condition information is different, the generated common key is also different.
  • the generation of the common key based on the usage condition information can be realized by calculating using a function with a numerical value or the like indicated by the usage condition information as an initial value. That is, the calculation result is used as a common key.
  • This common key is a key for encrypting and decrypting information in the common key cryptography.
  • the public key used for information encryption must be transmitted and received between the information transmitting side and the information receiving side. Therefore, the public key is used as a key to secure the secret for decryption. The key may be compromised.
  • the common key is generated based on the use condition information shared by the server device and the terminal device described later and updated with the same content.
  • the common key can be transferred between the server and the terminal.
  • the common key can be shared without transmitting and receiving to and from the device, and there is no risk of unauthorized decryption unlike the public key method.
  • the invention of the present application uses the usage condition information originally used for allowing the execution of the content also for generating the common key, so that the information necessary only for generating the common key is transmitted to the server device and the terminal. There is no need to send and receive between devices. That is, the amount of information transmitted and received between the server device and the terminal device can be reduced.
  • the server device and the terminal device share a common key does not only mean that the server device and the terminal device hold the same common key when they are the same.
  • “a server device and a terminal device share a common key” means that information encrypted by one device is replaced by a key corresponding to the key used for encryption by the other device.
  • the server device side use condition information management unit 0201 and the terminal device side use condition information management unit 0221 share the use condition information first. Accordingly, the common key generated by the server-side common key generation unit 0 202 based on the use condition information and the terminal-side common key generation unit 0 2 12 of the terminal device 0 210 described later correspond to each other. I do. In other words, the server device 0200 and the terminal device 0210 can share a common key. Further, as described above, the usage condition information is updated and managed based on the content execution information. Then, as described above, the updated usage condition information is also used by the server-side usage condition information management unit 0 201 of the server device 200 and the terminal-side usage condition information of the terminal device 210.
  • the common key generated by the server-side common key generation unit 0 202 and the terminal-device-side common key generation unit 0 212 based on the updated usage condition information correspond to each other. That is, the server device 0200 and the terminal device 0210 can also share a common key generated based on the updated usage condition information. At this time, a common key generated based on the pre-update usage condition information and a post-update None of the generated common keys are transmitted and received between the server device 0200 and the terminal device 0210.
  • the “encryption unit 0203” encrypts the content execution information using the common key generated by the common key generation unit 0202.
  • the content execution information to be encrypted by the encryption unit 0 203 is specified based on a content execution information distribution request, which is a request for distribution of the content execution information transmitted from the terminal device, as described later. It can be acquired.
  • a common key can be shared without transmitting and receiving between the server device 0200 and the terminal device 0210, so that information can be shared using the common key. It can be safely shared.
  • the information to be securely shared may be “other common key” or the “information for generating another common key”.
  • the problem is that the server device 200 needs to encrypt and transmit the content to each of the terminal devices using a specific common key.
  • the burden becomes a serious problem.
  • the content encrypted with the key can be transmitted and received between the terminal devices. it can. In this case, the load on the server device 200 is reduced.
  • the “other common key” that is common between the server device 0200 and the plurality of terminal devices 0210 is referred to as the server device 0200 and the terminal device 0210.
  • the advantage is that it can be safely shared between
  • the “transmission unit 0 204” transmits the encrypted content execution information encrypted by the encryption unit 0 203.
  • Terminal device 0 2 1 0 '' is composed of a receiving unit 0 2 13, a terminal device side usage condition information management unit 0 2 1 1, a terminal device side common key generation unit 0 2 1 2, and a decryption unit 0 2 1 4. Having.
  • the “receiving unit 0 2 1 3” receives the encrypted content execution information.
  • the “terminal-side use condition information management unit 0 2 1 1” manages the use condition information based on the content execution information.
  • the content execution information is obtained by using a common key generated by a terminal-side common key generation unit 0 2 12 described later.
  • the encrypted content execution information received by the reception unit 0 2 13 is decrypted by a decoding process described later. Are decrypted by the converting unit 0 2 1 4.
  • the use condition information has the same content in the server device use condition information management unit 0201 and the terminal device use condition management unit 0221, that is, it is shared. Is assumed. Further, as described above, the method for sharing the usage condition information first does not matter. Thus, the same usage condition information as the server device Since the usage condition information updated based on the same content execution information is managed on the basis of the above, the transmission and reception of the updated usage condition information is not performed directly between the server device and the terminal device. Can be shared at
  • the “terminal device side common key generation unit 0 2 1 2” generates a common key based on the usage condition information managed by the terminal device side usage condition information management unit 0 2 1 1.
  • the common key is generated based on the use condition information A managed by the terminal device side use condition information management unit 0 211.
  • the usage condition information A is updated to the usage condition information B based on the content execution information by the terminal device side usage condition information management unit 0 2 1 1
  • a common key is generated based on the usage condition information B. I do.
  • the common key generated based on the use condition information A is different from the common key generated based on the use condition information B.
  • the usage condition information managed by the terminal device side usage condition information management unit is shared between the server device 0200 and the terminal device 0210.
  • the common key generated by the common key generation unit 0 2 1 2 corresponds to the common key generated by the server-side common key generation unit 0 2 0 2, and the server device 0 2 0 0 and the terminal The devices 0 210 can share a common key.
  • the “decryption unit 0 2 1 4” uses the common key generated by the terminal-side common key generation unit 0 2 12 to encrypt the encrypted content execution information received by the reception unit 0 2 13. Decrypt and obtain content execution information.
  • the content execution information is information related to content execution, and may include a content ID, a content execution file associated with the content ID, and the like. Therefore, by decoding the content execution information, the terminal device can execute the content specified by the content ID. Further, as described above, the content execution information includes a common key other than the common key generated based on the use condition information or generation information (key generation information) of the other common key. In some cases, the content is encrypted with the other common key.
  • the encrypted content execution information is decrypted with the common key generated by the terminal-side common key generation unit 0 2 12 to obtain the other common key and the like, and the encrypted content execution information is encrypted with the other common key.
  • the content can be decrypted (see Fig. 6).
  • FIG. 4 is a diagram showing an example of the processing flow of the present embodiment. An example of the processing flow of the present embodiment will be described with reference to FIG.
  • the processing shown in the figure can be executed by a program to be executed by a computer (terminal device or the like), and this program must be recorded on a recording medium readable by the computer (terminal device). Can be.
  • Usage condition information which is information relating to one or more of the number of times the content is used, the expiration date, the usage period, and the content ID, which are allowed in the terminal device in association with the terminal device.
  • a common key is generated based on the managed key (server device-side common key generation step S0401).
  • the content execution information is encrypted by using the common key generated in step 0401 (content execution information encryption step S0402). Further, the encrypted content execution information encrypted in step 0402 is transmitted to the terminal device (encrypted content execution information transmission step S0403). Further, the use condition information managed by the server device is managed based on the content execution information that has been encrypted in step 0401 (use condition information management step S04). 0 4).
  • step 0403 receives the encrypted content execution information transmitted in step 0403 (encrypted content execution information receiving step S0405).
  • a common key is generated based on the usage condition information managed by the terminal device (terminal device side common key generation step S0406).
  • the encrypted content execution information received in step 0405 is decrypted using the common key generated in step 0406 to obtain content execution information (content execution information decryption).
  • Conversion step S 0 4 0 7 the use condition information managed by the terminal device is managed based on the content execution information obtained by decoding in the step S 407 (the terminal device side use condition information management step S 0 4 0 8).
  • the content execution information to be encrypted by the encryption unit 0203 is specified based on the content execution information distribution request that is a request for distribution of the content execution information transmitted from the terminal device.
  • a content execution information delivery request receiving unit 0505 is further provided in the server device 0500, and the content execution information delivery unit is provided in the terminal device 0510.
  • a request input section 0 5 15 and a content execution information distribution request transmission section 0 5 16 are further provided.
  • the content execution information distribution request input unit 0 5 15 transmits the content execution information distribution request input from the content execution information distribution request transmission unit 0 5 16, and the content execution information distribution request reception unit Receive with 0 5 0 5.
  • the server device 0500 receives the content execution information distribution request transmitted from the terminal device 0510, and identifies the content execution information based on the content execution information distribution request. can do.
  • a common key (or key generation information) is not transmitted and received between the server device and the terminal device, and the common key is exchanged between the two devices. And easily share a common key shared between both devices. You can change it.
  • the other terminal device cannot generate a common key. This is because, in order to generate a common key, it is necessary to obtain usage condition information possessed by the terminal device that should originally receive the encrypted content execution information.
  • the usage condition information is illegally acquired depending on the method of sharing the usage condition information between the terminal device and the server device first.
  • the usage condition information is first shared by the server device and the terminal device, and then updated by each device based on the content execution information. Then, the updated usage condition information is not transmitted and received between the server device and the terminal device.
  • the use condition information is updated, the updated use condition information is directly obtained from the terminal device illegally, or the first use condition information and all the content execution information used for the update are illegally obtained. Otherwise, the secret key cannot be obtained fraudulently. In the latter case, it is hard to imagine it because a person trying to use the common key illegally must constantly monitor the transmission and reception of information between a specific terminal device and a server device. Therefore, if the present invention is used, the common key can be safely shared between the server device and the terminal device.
  • the invention of the present application originally uses the usage condition information used for executing the content to generate the common key, information necessary only for generating the common key is transmitted between the server device and the terminal device. There is no transmission or reception.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)

Abstract

L'objectif de cette invention est de fournir une technique de partage d'une clé commune entre un côté émission d'informations et un côté réception sans émission/réception de cette clé commune entre les côtés émission d'informations et réception. A cet effet, un système de gestion d'informations utilisé comprend un dispositif serveur, destiné à émettre une information de contenu et d'exécution de contenu associée à l'exécution du contenu, ainsi qu'un dispositif terminal conçu pour recevoir cette information. Le dispositif serveur et le dispositif terminal génèrent respectivement une clé commune en fonction d'informations de condition d'utilisation qui sont des informations sur la zone d'autorisation d'exécution de contenu dans le dispositif terminal. Ces informations de condition d'utilisation sont d'abord partagées par le dispositif serveur et le dispositif terminal puis mises à jour et gérées par les deux dispositifs en fonction de l'information d'exécution de contenu émise/reçue entre les deux dispositifs. En conséquence, les informations de condition d'utilisation partagées initialement par le dispositif serveur et le dispositif terminal sont partagées par les deux dispositifs même après leur mise à jour avec l'information d'exécution de contenu et ces deux dispositifs peuvent partager la clé commune générée en fonction des informations de condition d'utilisation.
PCT/JP2003/005844 2003-05-09 2003-05-09 Systeme de gestion d'informations WO2004100443A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2003235920A AU2003235920A1 (en) 2003-05-09 2003-05-09 Information management system
PCT/JP2003/005844 WO2004100443A1 (fr) 2003-05-09 2003-05-09 Systeme de gestion d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2003/005844 WO2004100443A1 (fr) 2003-05-09 2003-05-09 Systeme de gestion d'informations

Publications (1)

Publication Number Publication Date
WO2004100443A1 true WO2004100443A1 (fr) 2004-11-18

Family

ID=33428602

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2003/005844 WO2004100443A1 (fr) 2003-05-09 2003-05-09 Systeme de gestion d'informations

Country Status (2)

Country Link
AU (1) AU2003235920A1 (fr)
WO (1) WO2004100443A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0983507A (ja) * 1995-09-19 1997-03-28 Hitachi Inf Syst Ltd 暗号鍵の生成および共有方法
JP2002304330A (ja) * 2001-04-06 2002-10-18 Sony Corp 通信方法、通信システム、コンテンツ提供システムおよびコンテンツ取得装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0983507A (ja) * 1995-09-19 1997-03-28 Hitachi Inf Syst Ltd 暗号鍵の生成および共有方法
JP2002304330A (ja) * 2001-04-06 2002-10-18 Sony Corp 通信方法、通信システム、コンテンツ提供システムおよびコンテンツ取得装置

Also Published As

Publication number Publication date
AU2003235920A1 (en) 2004-11-26

Similar Documents

Publication Publication Date Title
KR102265652B1 (ko) 블록체인 기반의 디지털 권리 관리
EP1714459B1 (fr) Acces a des donnees protegees dans une memoire reseau a partir de multiples dispositifs
US8233627B2 (en) Method and system for managing a key for encryption or decryption of data
US8824674B2 (en) Information distribution system and program for the same
EP2677682B1 (fr) Système de gestion de clés
US8694783B2 (en) Lightweight secure authentication channel
EP1852799B1 (fr) Gestion indépendante d'un dispositif pour des informations cryptographiques
US20080209231A1 (en) Contents Encryption Method, System and Method for Providing Contents Through Network Using the Encryption Method
CN101094394A (zh) 一种保证视频数据安全传输的方法及视频监控系统
JP2000261427A (ja) 暗号通信端末、暗号通信センター装置、暗号通信システム及び記憶媒体
JPH11275068A (ja) 鍵管理サーバ、チャットシステムの端末装置、チャットシステム及び記録媒体
WO2012111714A1 (fr) Dispositif serveur de fichiers et système serveur de fichiers
WO2013178019A1 (fr) Procédé, dispositif et système pour la mise en œuvre d'un traitement de données multimédias
WO2012161417A1 (fr) Procédé et dispositif de gestion de la distribution de droits d'accès dans un environnement de nuage informatique
US20020021804A1 (en) System and method for data encryption
JP2000347566A (ja) コンテンツ管理装置、コンテンツ利用者端末及びプログラムを記録したコンピュータ読み取り可能な記録媒体
KR20120091507A (ko) 데이터 접근 권한 관리 방법 및 장치
KR102385328B1 (ko) 프록시 재암호화를 통해 데이터 배포 제어가 가능한 drm 시스템 및 방법
KR101220180B1 (ko) Drm이 적용된 디지털시네마 콘텐츠의 극장 내 장치 간 공유 방법 및 시스템
JP2006279269A (ja) 情報管理装置、情報管理システム、ネットワークシステム、ユーザ端末、及びこれらのプログラム
CN112035820B (zh) 一种用于Kerberos加密环境下的数据解析方法
KR100989371B1 (ko) 개인 홈 도메인을 위한 디지털 저작권 관리방법
KR20110127789A (ko) Ｓｙｎｋ 데이터베이스 암호화 시스템 및 그 방법
WO2004100443A1 (fr) Systeme de gestion d'informations
JP2001285278A (ja) 暗号通信方法及び暗号通信システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1) EPC OF 070206, FORM 1205A

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

122 Ep: pct application non-entry in european phase