JP2006113848A - Data nullification recognizing method, computer for recognizing data nullification and terminal equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data nullification recognizing method for easily and reliably recognizing the nullification of electronic data in terminal device. <P>SOLUTION: A cabinet management server 6 manages the contents use quota and contents storage status of a terminal device 1. A portal server 3 and the cabinet management server 6 instructs the distribution of contents to a contents delivery server 5 in response to a contents distribution request from the terminal device 1. In distributing the contents, the remaining quota of the contents use quota of the terminal device 1 is searched based on information related with contents available in the terminal device 1 and erased contents, and the distribution of the contents is instructed within the range of the remaining quota. Whether or not the contents have been already erased is determined by comparing the contents storage status managed by the cabinet management server 6 with the contents storage status managed by the terminal device 1 to be transmitted from the terminal device 1. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a data discard recognition method, a data discard recognition computer, and electronic data for recognizing that electronic data stored in a terminal device is discarded using a computer connected to a network. It relates to a terminal device.

  It is easy to receive content distribution via the network. When receiving content distribution, it is preferable for the content user that the procedures for content distribution and use be as simple as possible, and it is preferable that as much content as possible can be used at low cost. In addition, it is also required for the content provider that the procedure for content distribution is as simple as possible. In particular, paid content distribution services are required to be as simple as possible with a minimum number of billing procedures.

  Patent Document 1 describes a flat-rate content distribution system. In this system, a user makes a contract with a fixed amount rental frame in advance with a content provider, and the content provider distributes content corresponding to the contracted frame to the user. The user can use the distributed content within the contract period, but can delete it within the contract period when unnecessary content is included in the content distributed at a fixed amount. In this case, when information regarding the deleted content is transmitted to the contract management center, the billing fee at the time of contract is discounted by the amount corresponding to the deleted content.

  Patent Document 2 describes a paid content usage system that returns a paid usage fee according to a usage period. When using this system, the user pays a provisional fee to the provider when delivering paid content. When the user deletes the paid content that is no longer necessary after using the paid content, the provider returns a part of the provisional price to the user. The amount to be returned is calculated according to the usage period of the content. Then, after a certain period, the rental fee becomes equal to the purchase fee, so it is regarded as “purchased”.

  In these systems, if the user deletes the distributed content and disables the use of the content, the fee will be discounted at the time of contract and the paid price will be returned. It is indispensable for the operation of the system that information indicating that is deleted (content use is disabled) to be highly reliable. However, Patent Documents 1 and 2 only describe that information indicating that the content has been deleted is transmitted, and false declaration is also possible.

  As an example of outputting a signal proving deletion of content stored in a computer storage device, there is a content operation management device described in Patent Document 3. In this apparatus, another computer that has received the content deletion notification checks the contents of the hard disk in which the content is stored, and confirms the content deletion. However, this technique cannot be applied to content deletion confirmation in a user terminal via a network.

JP 2001-195464 A JP 2001-325234 A JP 2003-242037 A

  The present invention has been made in view of the above circumstances, and a data discard recognition method, a data discard recognition computer, and such a data discard recognition capable of easily and reliably recognizing discard of electronic data in a terminal device. An object of the present invention is to provide a terminal device that outputs information to be performed.

  The data discard recognition method of the present invention is a data discard recognition method for recognizing that electronic data held in a terminal device has been discarded using a computer connected to a network, wherein A status management step for managing status information indicating a storage state of electronic data as management-side status information for each terminal device; and a status report receiving step for receiving a status report based on the status information from the terminal device. The status management step compares the status update step for updating the management-side status information based on the status report, the management-side status information, and the status information included in the status report. Also includes a status confirmation step to determine if has been destroyed It is. According to the present invention, it is possible to easily and reliably recognize the destruction of electronic data in the terminal device.

  In the data discard recognition method of the present invention, the status information includes at least the identification information of the electronic data, the data discard information indicating the discard of the electronic data, and the storage location information of the electronic data in the terminal device, In the status confirmation step, when the identification information and the storage location information of the electronic data included in the status report match the identification information and the storage location information included in the management-side status information, the data discarding Includes information that is deemed valid.

  In the data discard recognition method of the present invention, the status information includes a part of the contents of the electronic data held in the terminal device, and the status check step includes the data discard information included in the status report. The electronic data indicates that the electronic data is discarded, and the electronic data included in the status report does not match a part of the electronic data included in the management-side status information. Includes data that is deemed to have been destroyed.

  In the data discard recognition method of the present invention, the status report when the electronic data is stored in the terminal device includes the status information when the electronic data is stored, and the electronic data is discarded in the terminal device. The status report includes discard presentation information obtained by performing a predetermined calculation on at least a part of the status information after discarding the electronic data, and the status confirmation step includes the discard presentation information included in the status report And management side determination information obtained by performing a predetermined calculation on at least a part of the management side status information, and determining that the electronic data has been discarded if they match.

  The data discard recognition method according to the present invention includes a method in which the electronic data is content distributed via the network, and the status information is content storage state information indicating a storage state of the content. According to the present invention, it is possible to easily and reliably recognize the destruction of content distributed to a terminal device, and to reduce the processing burden for management when performing a content distribution service.

  A data discard recognition computer according to the present invention is a data discard recognition computer that recognizes by using a network that electronic data held in a terminal device has been discarded. A status management unit that manages status information indicating a storage state as management-side status information for each terminal device; and a reception unit that receives a status report based on the status information from the terminal device, the status management unit Whether the electronic data has been discarded by comparing the status update function for updating the management status information based on the status report, the management status information, and the status information included in the status report. It has a status confirmation function to determine whether or not.

  In the data discard recognition computer according to the present invention, the status information includes at least the identification information of the electronic data, the data discard information indicating the discard of the electronic data, and the storage location information of the electronic data in the terminal device. When the status confirmation function matches the identification information and the storage location information of the electronic data included in the status report with the identification information and the storage location information included in the management-side status information, the data Includes items for which the discard information is valid.

  In the data discard recognition computer according to the present invention, the status information includes a part of the content of the electronic data held in the terminal device, and the status confirmation function includes the data discard information included in the status report. Indicates that the electronic data is discarded, and a part of the content of the electronic data included in the status report does not match a part of the content of the electronic data included in the management-side status information. Includes those that determine that electronic data has been destroyed.

  In the data discard recognition computer according to the present invention, the status report when the electronic data is stored in the terminal device includes the status information when the electronic data is stored, and the electronic device discards the electronic data. The later status report includes discard presentation information obtained by performing a predetermined operation on at least a part of the status information after the electronic data is discarded, and the status confirmation function is included in the status report. The discard presentation information is compared with the management determination information obtained by performing a predetermined calculation on at least a part of the management status information, and when the two match, it is determined that the electronic data has been discarded. Including things.

  In the data discard recognition computer according to the present invention, the electronic data is content distributed via the network, and the status information is content storage status information indicating a storage status of the content.

  The terminal device of the present invention is a terminal device that holds electronic data, a status holding unit that stores status information indicating a storage state of the electronic data, and a status report generation unit that generates a status report based on the status information A status report output unit that outputs the status report generated by the status report generation unit, and a status change unit that changes a storage state of the electronic data including discarding the electronic data. The electronic data includes at least identification information of the electronic data, data discard information indicating that the electronic data is discarded, and storage location information of the electronic data.

  In the terminal device according to the present invention, the status information includes a piece of content of the electronic data.

  In the terminal device of the present invention, the status report at the time of storing the electronic data includes the status information at the time of storing the electronic data, and the status report after the discarding of the electronic data is It includes information including discard presentation information obtained by performing a predetermined calculation on at least a part of the status information after discarding.

  In the terminal device of the present invention, the electronic data is content distributed via the network, and the status information is content storage state information indicating a storage state of the content.

  The data discard recognition program of the present invention is a data discard recognition program for executing each step in the above-described data discard recognition method using a computer.

  The program of the present invention is a content distribution service program for realizing the storage state management unit and the receiving unit in the data discarding recognition computer described above.

  The terminal program of the present invention is a terminal program for realizing the status report generation unit, the status report output unit, and the content status change unit in the terminal device described above using a computer.

  As is apparent from the above description, according to the present invention, a data discard recognition method, a data discard recognition computer, and such a data discard capable of easily and reliably recognizing discard of electronic data in a terminal device. A terminal device that outputs information for recognition can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the content distributed to the terminal device via the network is the electronic data that should be recognized as discarded, but it may be license data for using the content instead of the content itself. Moreover, it is not restricted to the electronic data delivered via the network.

(First embodiment)
FIG. 1 shows a schematic configuration of a content distribution system for explaining an embodiment of the present invention. 1 includes a terminal device 1, a portal server 3, a content database (hereinafter simply referred to as “content DB”) 4, a content delivery server 5, a cabinet management server 6, and a billing server 7. The terminal device 1, portal server 3, content delivery server 5, and cabinet management server 6 are connected to a network 2 such as the Internet.

  In FIG. 1, only one terminal device 1 is shown, but more terminal devices are actually connected. Further, although the portal server 3, the content delivery server 5, and the cabinet management server 6 are described as being configured by separate computers, any two or all of these servers may be realized by a single computer.

  The content DB 4 stores content distributed to the terminal device 1 via the network 2 and information associated therewith. Information accompanying the content includes a content name, an artist name, a price (evaluation amount), a content size, and the like.

  The portal server 3 provides information serving as an entrance for content distribution services, that is, a portal page. The portal page includes a list of contents that can be provided among the contents stored in the content DB 4 and information on a content distribution service (such as service description, news, artist information, links to affiliate sites, advertisements, etc.). . In addition, when performing procedures for receiving content distribution and procedures for purchasing content usage frames (hereinafter referred to as “cabinets”), which are frames for receiving content distribution, the necessary information is transmitted and received. This is performed with the terminal device 1. Further, the user of the provided content distribution service and the information on the sales amount are notified to the billing server, and the collection of the price is requested.

  The billing server 7 performs a price collection process associated with the use of the content distribution service. Specifically, when a cabinet purchase, which will be described later, is performed, a billing process for collecting the price of the purchased cabinet is performed according to an instruction from the portal server 3. As the price collection method, various methods such as credit settlement are well-known, and the description is omitted.

  The content delivery server 5 receives the request from the portal server 3 and delivers the content stored in the content DB 4 to the terminal in cooperation with the content delivery client 12 of the terminal device 1. The content to be delivered is content that has received a content distribution request from the terminal device 1.

  The cabinet management server 6 manages the state of the cabinet of the terminal device 1 and the storage state of the distributed content corresponding to the cabinet, and also verifies the storage state of the content in the terminal device 1.

  The cabinet management server 6 includes a status report input unit 121, a storage status holding unit 122, a status report verification unit 123, and a verification number management table 124. The storage state holding unit 122 holds cabinet information held by the terminal device 1, that is, content storage state information indicating the storage state of content as management-side content storage state information. A content storage status report is received from the status report output means 115 of the device 1. The status report verification unit 123 verifies whether the received content storage status report is correct. The verification number management table 124 indicates the verification number generated when the verification processing result is correct as the verification number. Is stored together with the expiration date. The storage state holding unit 122 generates and updates the management-side content storage state information based on the content storage state report received from the state report output unit 115. The management-side content storage state information is updated by the status report. This is performed when the verification result in the verification unit 123 is correct.

  When there is a cabinet purchase request from the terminal device 1, the cabinet management server 6 generates a cabinet corresponding to the requested terminal device and instructs the charging server via the portal server 3 to perform charging processing. Further, the portal server 3 instructs the content delivery server 5 to distribute the content in accordance with the content distribution request from the terminal device 1. At this time, the verification result of the status report verification unit 123 is determined with reference to the verification number management table 124, and content distribution is instructed only when the verification result is successful. Furthermore, the remaining frame of the cabinet of the terminal device 1 is obtained based on the information regarding the usable content and the deleted content in the terminal device 1, and the distribution of the content is instructed within the range of the remaining frame.

  In this way, the portal server 3 and the cabinet management server 6 manage the content distribution service in cooperation. As described above, the portal server 3 and the cabinet management server 6 may be realized by the same computer.

  The terminal device 1 is a user terminal used by a user who receives a content distribution service, for example, a portable wireless terminal. The terminal device 1 includes a cabinet management client 11, a content delivery client 12, a browser 13, a player 14, a wireless communication unit 15, an information holding unit 111, and an information changing unit 113. These means are realized mainly by a computer that executes a predetermined program, and a system management program for receiving a content distribution service is distributed and installed before using the service.

  The cabinet management client 11 manages the status of the cabinet in the terminal device 1 and includes a storage status holding unit 112, a status report generation unit 114, and a status report output unit 115. The storage state holding unit 112 stores content storage state information indicating a storage state of the distributed content in the terminal device 1 and change history information indicating a change history of the content storage state. The status report generation unit 114 generates a content storage status report including content storage status information, and the status report output unit 115 outputs the generated content storage status report to the status report input unit of the cabinet management server 6. To do. Note that transmission / reception of information between the terminal device 1 and the portal server 3, the content delivery server 5, and the cabinet management server 6 is performed via the wireless communication unit 15 and the network 2.

  The content delivery client 12 downloads content on the content DB 4 in cooperation with the content delivery server 5, and the downloaded content is stored in the information holding unit 111 via the information change unit 113.

  The browser 13 is a user interface used when a user uses the terminal device 1 to distribute content, use the distributed content, or the like. Specifically, the browser 13 inquires of the cabinet management client 11 to acquire and display the status of the cabinet, acquires and displays a list of distributable contents from the portal server 3, content distribution, and cabinet purchase procedures. Processing for providing a GUI in the exchange with the portal server 3 at the time is performed. In addition, when the content is distributed, a process for starting the content delivery client 12 is performed.

  The player 14 reproduces content (video, audio, animation, etc.) stored in the information holding means 111, and the wireless communication means 15 controls wireless communication via the network 2 in the terminal device 1. It is.

  The information holding unit 111 holds the distributed content. The information changing unit 113 changes the state of the content held by the information holding unit 111, and notifies the storage state holding unit 112 of the changed content when changing. The change of the content state includes new saving and rewriting.

  FIG. 2 shows an example of content storage state information held in the storage state holding unit 112 of the cabinet management client 11. The content storage status information shown in FIG. 2 includes content identification information (content ID), cabinet identification information (cabinet ID), status, content storage path, and content details, and is managed by an information number for each distributed content. As the content storage state information, a new entry is generated every time content is distributed. The content storage status information is assigned identification information (ID) for each terminal device (in FIG. 2, “C87911” is assigned), and the cabinet management server 6 stores content based on this ID. Status information is managed.

  The content ID is identification information attached to the content provided to the distribution service, and the cabinet ID is identification information attached to the cabinet used for content distribution. The status is information indicating the status of the distributed content, “available” indicates that the content can be used in the terminal device 1, and “deleted” indicates that the content is deleted and cannot be used. It is shown that. The content storage path indicates an address where the content is stored. The content content indicates binary data of a part of the content held in the information holding unit 111.

  Note that the content is deleted, that is, discarded by rewriting at least part of the data of the content, and cannot be used.

  FIG. 3 shows an example of the change history information held in the storage state holding unit 112 of the cabinet management client 11. The content change history shown in FIG. 3 includes a change time, a change type, a cabinet ID, a content ID, and a server report time, and is managed by a change number for each change history. As the change history information, a new entry is generated every time a cabinet is purchased, contents are distributed, and contents are deleted. The change history information is assigned identification information (ID) for each terminal device (in FIG. 2, “H28719” is assigned), and the cabinet management server 6 uses the change history information based on this ID. Is managed.

  The change time indicates the time when the content storage state (cabinet state) is changed. For example, “20030612151029” indicates 15:10:29 on June 21, 2003. The change type indicates one of cabinet purchase, content distribution, and content deletion. “Buy” indicates cabinet purchase, “add” indicates content distribution, and “del” indicates content deletion. The cabinet ID and content ID are the same as those described in FIG.

  The server report time indicates the time when the change history information of the change number was reported to the cabinet management server 6. In the example of FIG. 3, the server report time is not held in the change history information of the change number “e00007”, but this is not reported to the cabinet management server 6 although the content state has been changed in the terminal device 1. It is shown that. That is, the change history information of the change number “e00007” is deleted at 19:53:22 on June 15, 2003, with the content ID “cnt5945” held in the cabinet with the cabinet ID “cab1903944”. However, the history information has not been reported to the cabinet management server 6.

  As described above, the storage state holding unit 112 includes the content storage state information indicating the state of the content corresponding to the cabinet, and the change history information indicating the change of the distributed content, for example, new storage, deletion, and cabinet purchase. Is memorized.

  The same content storage state information and change history information for each terminal device are held in the storage state holding unit 122 of the cabinet management server 6 as management content storage state information and management side change history information. The generation of the management-side content storage state information and the management-side change history information will be described later.

  Next, content storage status report generation processing performed by the status report generation unit 114 of the cabinet management client 11 will be described. The status report generation unit 114 generates a content storage status report using the content storage status information and the change history information.

  FIG. 4 shows a schematic flow of content storage status report generation processing. In step S101, the content held in the information holding unit 111 is compared with the content included in the content storage state information (see FIG. 2). This step is performed to confirm that the content storage status information is normal (not broken). If it is determined in step S102 that the comparison result does not match, the cabinet is broken. (Step S108), and the process ends. When the cabinet is broken, the content storage state information is acquired from the cabinet management server 6 and repaired. When content is deleted, the content is rewritten with random data. However, in some cases, the file indicated by the content storage path cannot be accessed thereafter. In that case, since the contents of the deleted content do not match, the content of the deleted content may not be compared.

  If the contents match, the content storage status information is copied and stored in a status report storage area (secured in a work memory not shown) in step S103. Next, in step S104, it is checked whether there is unreported change history information with reference to the change history information (see FIG. 3). If there is unreported change history information, the information is stored in the status report storage area. Remember. Whether or not the change history information has been reported to the cabinet management server 6 is determined by whether or not the server report time of the change history information is stored as described above.

  In step S105, a predetermined calculation is performed using the stored content storage state information and change history information, and verification information is generated. As an operation used for generating the verification information, for example, a hash operation can be used. Further, the hash calculation may be performed on all of the stored content storage state information and change history information, or may be performed on a part thereof. Then, the generated verification information is encrypted using the secret key of the terminal device 1 (step S106) and stored in the status report storage area (step S107). The information system management program for the type of calculation and the calculation target is obtained when the program is distributed.

  5 and 6 show an example of the generated content storage status report. This example is generated using the content storage status information of FIG. 2 and the change history information of FIG. 3, FIG. 5 conceptually shows the content storage status report, and FIG. 6 shows the data to be transmitted. .

  5A stores the content storage state information shown in FIG. 2 as it is, and FIG. 5B shows only the change history information of the change number “e00007” in the change history information shown in FIG. I remembered it. FIG. 5C shows the encryption verification information generated in step S107 of FIG. In FIG. 5, content storage state information and change history information are partially omitted.

  FIG. 6 shows the content storage status report shown in FIG. 5 with tagged text data. The portion 601 is change history information of the change number “e00007”, the portion 602 is content storage status information, and the portion 603 is Corresponds to encryption verification information.

  In the above description, the change history information included in the content storage status report is unreported change history information. However, not only unreported information but also reported change history information may be included in the content storage status report. Good.

  Next, content storage status report verification processing performed by the status report verification means 123 of the cabinet management server 6 will be described. The status report verification unit 123 uses the content storage status report input via the status report input unit 121 and the management-side content storage status information and management-side change history information held in the storage status holding unit 122. The input content storage status report is verified.

  FIG. 7 shows a schematic flow of content storage state report verification processing. In step S201, the content state included in the management-side content storage state information held in the storage state holding unit 122 is compared with the content state included in the content storage state information of the input content storage state report. The management-side content storage status information is included in the input change history information because it matches the content storage status information of the terminal device 1 at that time when the previous content storage status report was input, as will be described later. Should match except for content. Therefore, in this step, it is determined whether or not all the items except the content included in the input change history information match. In addition, among the contents included in the change history information, those whose “state” is “deleted” are newly deleted in the terminal device 1, so items other than “state” and “content details” match. Determine whether or not.

  If it is determined in step S202 that the comparison results do not match, it is determined that the verification has failed, and in step S209, the verification failure is notified and the process ends. Therefore, even if there is content whose “state” is “deleted” among the contents included in the change history information, it is not determined that the content has been deleted. The operation in the case of verification failure will be described later.

  If the contents match, the encryption verification information included in the content storage status report is decrypted in step S203. Decryption is performed using the public key of the terminal device 1. The public key of the terminal device 1 is obtained in advance when making a contract for the content distribution service.

  In step S204, management-side verification information is generated using the input content storage state report and the management-side change history information held in the storage state holding unit 122. Specifically, the input change history information is added to the management side change history information, the management side change history information and the input content storage state information are subjected to arithmetic processing such as a hash operation, and the management side verification information Is generated. In step S205, the generated management-side verification information is compared with the decrypted verification information.

  If it is determined in step S206 that the comparison results do not match, it is determined that the verification has failed, the verification failure is notified in step S209, and the process ends.

  If it is determined in step S206 that the comparison results match, it is determined that the verification is successful, a verification number is generated and registered in the verification number management table 124, and the generated verification number is notified. The verification number is used for subsequent content distribution processing.

  FIG. 8 shows an example of the verification number management table 124. In the verification number table 124, the registration date and the expiration date are registered for each verification number. In this example, the expiration date is set to 1 hour. For example, the verification number “ver8194271” is registered at 23:18:42 on June 15, 2003 and indicates that it is valid until 0:18:42 on June 16, 2003.

  If it is determined that the verification is successful, the storage state holding unit 122 is instructed to update the content state information held in the storage state holding unit 122, that is, the management side content storage state information and the management side change history information (step S208), the process ends.

  Specifically, a case where the content storage status report shown in FIG. 5 is input in a state where the management-side content storage status information shown in FIG. 9 and the management-side change history information shown in FIG. 10 are stored in the storage status holding means. I'll think about it. In step S201, the contents of the content excluding the content whose content ID is “cnt5945” indicated by the change history information of the input change number “e0007” are compared. Since the comparison results match, the processing after step S203 is performed.

  When generating the management-side verification information in step S204, change history information in which the change history information of the input change number “e0007” is added to the management-side change history information shown in FIG. 10, and the input content storage State information is used. Therefore, the generated management-side verification information matches the decrypted verification information, and it is determined that the verification is successful.

  Since it is determined that the verification is successful, the management-side content storage state information held in the storage state holding unit 122 is updated with the input content storage state information, and the same information as shown in FIG. Stored as information. Further, change history information of the change number “e0007” is added to the management side change history information held in the storage state holding unit 122, and the same information as shown in FIG. 3 is stored as the management side change history information. The

  As described above, the content storage status report including the content status information and the change history information stored in the terminal device 1 is received by the cabinet management server 6 and the management-side content storage status information managed by the cabinet management server 6 The verification is performed using the management-side change history information and the received content storage status report, and the management-side content storage status information and the management-side change history information are updated according to the verification result. Can be surely grasped. Further, verification information obtained by computation such as hash computation is added to the content storage status report, and the cabinet management server 6 compares it with the management-side validation information obtained from other data to obtain a more reliable grasp. Can do.

  For example, as shown in this example, when the content is deleted, the change of the content storage state information can be recognized with certainty, so that it can be determined that the corresponding content has been deleted. In addition, since at least a part of the content is included in the content storage status information, even if there is a content storage status report indicating false content deletion, it can be reliably detected that the report is false. That is, even if a content storage status report including information indicating that the content has been deleted is made, if the content has not been changed, it can be detected that the report is false.

  Therefore, as will be described later, it can be determined that the cabinet corresponding to the deleted content has been emptied, and new content can be distributed in the same cabinet. As described above, in the system of FIG. 1, the deletion, that is, the destruction of the content that is the electronic data held in the terminal device 1 is performed using the content storage state information that is the status information indicating the storage state of the electronic data. This is recognized on the side (cabinet management server 6 and portal server 3).

  Next, an operation in the case of receiving content distribution using the content distribution system shown in FIG. 1 will be described. FIG. 11 shows an operation when browsing various information for the content distribution service. Here, a contract or the like for receiving a service is provided (billing method notification or the like), a predetermined system management program is installed in the terminal device 1, at least one cabinet is purchased, and storage state holding means is stored. Assume that an area for storing content storage state information and change history information is secured in 112.

  When browsing various information for the content distribution service, the user inputs a rental page browsing request F101 to the browser 13. Specifically, it is performed by inputting a URL indicating a rental page. The browser 13 that has received the rental page browsing request F <b> 101 transmits a status report transmission request F <b> 102 to the cabinet management client 6.

  The cabinet management client 6 that has received the status report transmission request F102 generates a content storage status report (P101). The content storage status report is generated according to the procedure shown in FIG. 4, and the generated content storage status report F103 is transmitted to the cabinet management server 6. The cabinet management server 6 uses the received content storage status report F103. Then, status report verification processing is performed (P102). The status report verification process is performed according to the procedure shown in FIG. 7, and the verification result F104 is transmitted to the cabinet management client 11, and the cabinet management client 11 transmits the verification result F105 to the browser 13. When the verification result is successful, the verification number is transmitted together with the verification results F104 and F105.

  If the verification result is verification failure, the browser 13 displays a screen as shown in FIG. 27 and ends. The screen in FIG. 27 will be described later.

  If the verification result is a verification success, the browser 13 transmits a rental page request F106 to the portal server 3. At this time, a verification number is also transmitted. The portal server 3 that has received the rental page request F106 transmits a content status request F107 to the cabinet management server 6 together with the verification number. The cabinet management server 6 that has received the content status request F107 confirms the received verification number (P103), and if it can be confirmed, performs a content status notification F108 together with the confirmation result. The content state notification includes management-side content storage state information and management-side change history information stored in the storage state holding unit 122. The verification number confirmation process (P103) is performed with reference to the verification number management table 124 depending on whether the verification time has passed the expiration date of the verification number. If the expiration date has passed, it is necessary to generate, transmit, and verify the content storage status report again.

  Upon receiving the content status notification F108, the portal server 3 generates list information and cabinet information of contents that can be distributed (rented) (P104).

  FIG. 12 shows a schematic operation flow of the list information and cabinet information generation processing. In step S301, the contents DB 4 is referred to extract contents that can be disclosed. FIG. 13 shows an example of a content information table provided in the content DB. As shown in FIG. 13, in the content information table, in association with the content ID, information on the title of the content, the artist name indicating the creator of the content, and information on the genre of the content, as well as the publication start date and time information and the publication end date and time information. It is remembered.

  In step S302, the management-side content storage state information transmitted from the cabinet management server 6 is referred to and compared with a list of contents that can be published, and the contents that are being published are extracted. In step S303, a publicly available content list that identifies the publicly available content is generated. FIG. 14 shows an example of a content list that can be disclosed. As shown in FIG. 14, the content with the content ID “cnt1905” that is distributed and can be used at present is distinguished as being rented based on the management-side content storage state information.

  In step S304, the management side change history information transmitted from the cabinet management server 6 is referred to generate cabinet information. The cabinet information is information for recognizing how much the content distributed using the purchased cabinet is available, that is, how much the cabinet is free.

  FIG. 15 shows an example of cabinet information. The cabinet information in FIG. 15 is generated based on management-side content storage state information similar to that shown in FIG. 2 and management-side change history information similar to that shown in FIG. FIG. 15 shows that the cabinet with the cabinet ID “cab1844927” has no vacancy, and the cabinet with the cabinet ID “cab1903944” has four vacancies. The capacity of each cabinet can be recognized from the cabinet ID. In this example, the first two digits of the number is “18”, the capacity is 2, and the first two digits of the number is “19”. The one has a capacity of 4.

  Returning to FIG. 11, when the list information and cabinet information are generated, the portal server 3 transmits the generated list information and cabinet information to the browser 13 and transmits a confirmation result and a rental page generation instruction F109. The browser 13 generates rental page information using the received list information and cabinet information, and presents the rental page F110.

  FIG. 22 shows a display example of the rental page screen. An icon 1001 in FIG. 22 indicates a cabinet with a capacity of 2 and is occupied by the content indicated by the icons 1011 and 1012. On the other hand, an icon 1002 indicates a cabinet with a capacity of 4, indicating that it is not occupied by content. Such display information is generated using the cabinet information of FIG.

  A table 1021 shows a list of contents that are being published, and is generated using the list of contents that can be published in FIG. Table 1021 displays information related to the contents during the four public periods, of which the contents with the title “title DEF” are being rented (distributed and still available). ing. This table 1021 shows the contents that can be released by the rental shop indicated by the icon 1006. If there is another rental shop, an icon indicating another rental shop is displayed, and by selecting the icon, , Another table showing the contents that can be published is displayed.

  The icon 1003 is used to play back content, the icon 1004 is used to return or delete the delivered content, and the icon 1005 is used to newly purchase a cabinet. Is. When returning the content, the content icon occupying the cabinet is dragged to the icon 1004.

  16 and 17 show the operation when purchasing a cabinet.

  When purchasing a cabinet, the user inputs a cabinet purchase instruction F201 to the browser 13. Specifically, the input is performed by selecting an icon 1005 for performing cabinet sales in a state where a rental page screen as shown in FIG. 22 is displayed. When the icon 1005 is selected, an icon indicating the type of cabinet that can be purchased is displayed, and the desired type of cabinet can be selected.

  FIG. 23 shows a display example of the cabinet purchase screen. In the display screen shown in FIG. 23, the already purchased cabinet has only the capacity 2 indicated by the icon 1001 and there are three types of cabinets that can be sold (respectively indicated by the icons 1031, 1032, and 1033). The state in the case where it is desired to purchase the cabinet "19" is shown. When an icon indicating a cabinet desired to be purchased (in this case, icon 1032) is dragged to position 1132, a confirmation dialog 1041 is displayed. When the “Yes” button is selected, the type of cabinet is input to browser 13. .

  When the type of cabinet desired to be purchased is input, the browser 13 transmits a cabinet addition preparation request F202 to the portal server 3, and the portal server 3 transmits a cabinet addition preparation request F203 to the cabinet management server 6. At this time, the type of cabinet desired to be purchased and the verification number acquired previously are transmitted.

  When the cabinet management server 6 receives the cabinet addition preparation request F203, it first checks the verification number (similar to the processing in P103). If it can be confirmed, it generates a cabinet ID (P201) and notifies the cabinet addition preparation completion notice. F204 is transmitted to the portal server 3 together with the generated cabinet ID and confirmation result.

  The portal server 3 that has received the cabinet addition preparation completion notification F204 transmits a cabinet addition preparation completion notification F205 to the browser 13 together with the cabinet ID and the confirmation result. Upon receiving the cabinet addition preparation completion notification F205, the browser 13 transmits the cabinet addition request F206 together with the received cabinet ID. If the confirmation in the cabinet management server 6 fails, the cabinet ID is not generated, and only the confirmation result is transmitted to the browser 13, so the content storage status report is generated and transmitted again.

  Upon receiving the cabinet addition request F206, the cabinet management client 11 adds a cabinet and generates a content storage status report (P202). To add a cabinet, an entry with a new change number is added to the change history information of the storage state holding means 112. The content storage status report is generated according to the procedure shown in FIG.

  The cabinet management client 11 transmits a content storage status report F207 to the cabinet management server 6, and the cabinet management server 6 verifies the received content storage status report (P203). The content storage status report is verified by the procedure shown in FIG. 7, and the verification result F <b> 208 is transmitted to the cabinet management client 11. Then, the cabinet management client 11 transmits the cabinet addition result F209 to the browser 13. If the verification in process P203 is successful, the verification number is transmitted together with the verification result F208 and the cabinet addition result F209.

  If the verification result is verification failure, the browser 13 displays a screen as shown in FIG. 27 and ends. The screen in FIG. 27 will be described later.

  If the verification result is a verification success, the browser 13 transmits the charging request F210 to the portal server 3 together with the verification number, and the portal server 3 that has received the charging request F210 sends the content status request F211 to the cabinet management server 6 together with the verification number. Send.

  The cabinet management server 6 that has received the content status request F211 confirms the verification number (P204), and if it can confirm, performs the content status notification F212 together with the confirmation result. The content state notification includes management-side content storage state information and management-side change history information stored in the storage state holding unit 122. The verification number is confirmed in the same manner as in the process of P103.

  The portal server 3 that has received the content status notification F212 transmits a charging request F213 to the charging server 7. At this time, the terminal device ID (if the user ID can be acquired from the terminal device ID, the user ID may be used) and the billing amount are transmitted. Upon receipt of the accounting request F213, the accounting server 7 performs accounting processing (P205). The billing process is performed for a person specified by the terminal device ID or the user ID. When the billing process ends, the billing server 7 transmits a billing completion notification F214 to the portal server 3.

  Upon receiving the accounting completion notification F214, the portal server 3 generates list information and cabinet information of contents that can be distributed (rented) (P206). This process is the same as the process P104 in the description of FIG. When the list information and cabinet information are generated, the portal server 3 transmits an accounting completion notification F215 to the browser 13 and also transmits the generated list information and cabinet information.

  The browser 13 generates rental page information using the received list information and cabinet information, and presents the rental page F216. FIG. 22 shows a display example of the rental page screen. Thereafter, content can be received using a newly purchased cabinet.

  18, 19, and 20 show an operation when receiving distribution of content (rental content).

  When renting content, the user inputs a rental instruction F301 to the browser 13. Specifically, in a state where a rental page screen as shown in FIG. 22 is displayed, an icon indicating a rentable content is input by dragging it to an icon indicating a cabinet.

  An example of the rental page screen when the icon indicating the content is dragged is shown in FIG. FIG. 24 shows the display screen when the icon 1013 indicating the content is dragged to the position 1113 on the icon 1002 indicating the cabinet in order to rent the content whose title is “title JKL”. When such an operation is performed, the browser 13 determines that the content whose title is “title JKL” is to be rented using the cabinet specified by the icon 1002, and displays a dialog 1042.

  In this state, when the “Yes” button in the dialog 1042 is pressed, the browser 13 transmits a rental delivery preparation request F302 to the portal server 3 together with the content ID, cabinet ID, and verification number desired to be rented. Upon receiving the rental delivery preparation request F302, the portal server 3 transmits a content status request F303 together with the verification number to the cabinet management server 6. The cabinet management server 6 that has received the content status request F303 confirms the received verification number (P301), and if it can be confirmed, performs the content status notification F304 along with the confirmation result. The content state notification includes management-side content storage state information and management-side change history information stored in the storage state holding unit 122. The verification number is confirmed in the same manner as in the process of P103.

  Upon receiving the content status notification F304, the portal server 3 transmits a content delivery preparation request F305 to the content delivery server 5. At that time, the content ID desired to be delivered and the cabinet ID of the delivery destination are also transmitted. Upon receiving the content delivery preparation request F305, the content delivery server 5 confirms the content ID and generates a delivery number (P302). Then, a content delivery preparation completion notification F 306 is transmitted to the portal server 3 together with the content ID confirmation result (confirmation result as to whether there is deliverable content), the delivery preparation completion content ID, the delivery destination cabinet ID, and the delivery number. .

  Upon receiving the content delivery preparation completion notification F306, the portal server 3 transmits a rental delivery preparation completion notification F307 to the browser 13 together with the confirmation result of the content ID and the delivery number.

  Upon receiving the rental delivery preparation completion notification F307, the browser 13 transmits a reception start request F308 to the content delivery client 12 together with a delivery preparation completion content ID, a delivery destination cabinet ID, and a delivery number.

  The content delivery client 12 that has received the reception start request F308 transmits a content delivery start request F309 to the content delivery server 5 together with the delivery number. The content delivery server 5 confirms the match between the delivery number generated when the content delivery preparation request is received from the portal server 3 and the received delivery number (P303). If they match, the content delivery start notification F310 is sent to the content delivery start notification F310. It is transmitted to the delivery client 12. At this time, a delivery number, a delivery URL indicating a delivery source, and a content size are also transmitted.

  Upon receiving the content delivery start notification F310, the content delivery client 12 performs content delivery with the content delivery server 5 based on the delivery URL (P304). When the delivery of the content is completed, a content storage request F311 is transmitted to the information changing unit 113. At this time, the content ID of the content delivered together, the cabinet ID, and the path of the temporary file for delivery are transmitted. The information changing unit 113 transmits a data storage request F312 to the information holding unit 111 together with the file path of the content storage destination.

  The information holding unit 111 stores the delivered content in the position indicated by the received file path, and transmits a data storage completion notification F313 to the information changing unit 113 after the storage is completed. In this state, the delivered new content is held in a predetermined area of the terminal device 1.

  The information changing unit 113 that has received the data storage completion notification F313 transmits a content status change request F314 to the cabinet management client 11 together with the content ID of the newly stored content, the cabinet ID, and the file path to the content.

  The cabinet management client 11 that has received the content status change request F314 changes the content status of the content status holding unit 112 (P305). Specifically, a new entry is added to the change history information, and the change time, change type (in this case, “add” because content is distributed), cabinet ID, and content ID are stored. Also, new content is added to the content storage status information, and the content ID, cabinet ID, status (in this case, “available”, so “available”), content storage path, content details (from the information holding unit 111 to the content) A part of binary data is read out).

  When the change of the content state is completed, the cabinet management client 11 transmits a content state change completion notification F315 to the information change unit 113, and the information change unit 113 transmits a content storage completion notification F316 to the content delivery client 12. Then, the content delivery client 12 transmits a reception completion notification F317 to the browser 13.

  Upon receiving the reception completion notification F317, the browser 13 transmits a status report transmission request F318 to the cabinet management client 11.

  The cabinet management client 11 that has received the status report transmission request F318 generates a content storage status report (P306). The content storage status report is generated according to the procedure shown in FIG. 4, and the generated content storage status report F319 is transmitted to the cabinet management server 6. The cabinet management server 6 uses the received content storage status report F319. Then, the status report verification process is performed (P307). The status report verification process is performed according to the procedure shown in FIG. 7, the verification result F320 is transmitted to the cabinet management client 11, and the cabinet management client 11 transmits the verification result F321 to the browser 13. When the verification result is successful, the verification number is transmitted together with the verification results F320 and F321.

  When the verification result is a verification success, the browser 13 transmits a rental page request F322 to the portal server 3. At this time, a verification number is also transmitted. The portal server 3 that has received the rental page request F322 transmits the content status request F323 to the cabinet management server 6 together with the verification number. The cabinet management server 6 that has received the content status request F323 confirms the received verification number (P308), and if it can confirm, performs the content status notification F324 together with the confirmation result. The content state notification includes management-side content storage state information and management-side change history information stored in the storage state holding unit 122. The verification number is confirmed in the same manner as in the process of P103.

  Upon receiving the content status notification F324, the portal server 3 generates list information and cabinet information of contents that can be distributed (rented) (P309). This process is performed in the same manner as the process P104 in FIG.

  When the list information and cabinet information are generated, the portal server 3 transmits the generated list information and cabinet information to the browser 13 and transmits a confirmation result and a rental page generation instruction F325. The browser 13 generates rental page information using the received list information and cabinet information, and presents a rental page F326.

  Note that when a user drags an icon indicating rentable content to an icon indicating a cabinet in order to input the rental instruction F301, the purchased cabinet has no empty space in the cabinet indicated by the icon and there are other empty spaces. If there is no, the browser 13 prompts the user to return the distributed content or purchase an additional cabinet.

  FIG. 25 shows an example of the display screen of the browser in that case. FIG. 25 is a display screen when the icon 1013 indicating the rentable content is dragged to the icon 1001 indicating the cabinet. The capacity of the cabinet indicated by the icon 1001 is 2, and the two contents indicated by the icons 1011 and 1012 are rented using the cabinet. Therefore, since it is impossible to rent more content, a dialog 1045 is displayed to prompt the user to return the rented content or purchase additional cabinets.

  FIG. 21 shows an operation when content is returned (content is deleted).

  When returning the content, the user inputs a return instruction F401 to the browser 13. Specifically, in the state where the rental page screen as shown in FIG. 22 is displayed, an icon indicating the rented content is input by dragging it to an icon indicating return. The return process can be performed not only in the online state connected to the portal server 3 but also in the offline state. In this case, the browser 13 holds the data used for the rental page screen last time (during online operation or offline operation), and displays the data using the data.

  An example of the rental page screen when the icon indicating the content is dragged is shown in FIG. FIG. 26 shows a display screen when the icon 1013 indicating the content is dragged onto the icon 1004 indicating the return in order to return the rented content whose content title is “title JKL”. . When such an operation is performed, the browser 13 determines that the content whose title is “title JKL” is to be returned, and displays a dialog 1043.

  In this state, when the “Yes” button in the dialog 1043 is pressed, the browser 13 transmits a content deletion request F402 to the information changing unit 113 together with the content ID and cabinet ID desired to be returned. The information changing unit 113 that has received the content deletion request F402 transmits a data change request F403 to the information holding unit 111 together with the file path. The information holding unit 111 that has received the data change request F403 overwrites the content with a random value so that the content becomes unusable based on the received file path (P401). When the overwriting is completed, a data change completion notification F404 is transmitted to the information changing unit 113.

  The information changing unit 113 transmits a content status change request F405 to the cabinet management client 11 together with the content ID, cabinet ID, and file path of the deleted content.

  The cabinet management client 11 that has received the content status change request F405 changes the content status (P402). Specifically, a new entry is added to the change history information of the storage state holding unit 112, and the change time, change type (in this case, “del” because content is deleted), cabinet ID, and content ID are added. Remember. In addition, the content information corresponding to the content storage state information is rewritten. That is, the content state of “available” is rewritten to “deleted”, a part of the binary data of the content is read using the file path, and the content content is rewritten. At this time, since the data in the corresponding storage area of the information holding unit 111 is overwritten with random data, the content content of the content storage state information is also rewritten with random data.

  When the change of the content state is completed, the cabinet management client 11 transmits a content state change completion notification F406 to the information change unit 113, and the information change unit 113 transmits a content deletion completion notification F407 to the browser 13. Then, the browser 13 presents a return completion F408 to the user.

  When the content return process is performed offline, the content storage state information and the change history information stored in the storage state holding unit 112 of the cabinet management client 11 are stored in the storage state holding unit 122 of the cabinet management server 6. Side content storage status information does not match the management-side change history information, but there is no problem because it matches the next time it comes online.

  When the content storage status report is verified (for example, processing P102 in FIG. 11, processing P203 in FIG. 16, processing 307 in FIG. 19), if the verification fails, a screen as shown in FIG. Prompt to reinstall. In that case, icons 1051, 1052, 1061, and 1062 indicating that the cabinet and contents are broken are displayed, and a dialog 1044 is displayed to prompt re-installation.

  In the above explanation, the value (price) of the content provided for distribution is constant and the value is not reduced at the time of return. However, the value is different for each content, and the value at the time of return is also changed. Also good. In this case, information indicating the value of each content is displayed when a list of contents that can be published is displayed and when a return content is selected. When renting content, the value corresponding to the empty part of the cabinet and the value of the content to be rented may be compared to determine whether the rental is possible, or the difference between the two may be charged. Good.

  As described above, in the content distribution system of the present invention, the system can be operated by money settlement only at the time of cabinet purchase. In addition, users and providers of content do not need to manage the expiration date of distributed content. In other words, the supplier only needs to manage the content that is available at that time for each user, and the user need only manage the content only when there is content to be newly used. It is. Since it is possible for the server on the distribution service side to reliably recognize that the distributed content has been deleted, new content can be rented as much as the cabinet is freed by deletion.

  Therefore, the user can use an almost infinite number of contents at a fixed cost by shortening the use period of each content. In addition, if necessary, specific content can be used permanently as in the case of purchase.

(Second Embodiment)
The second embodiment is also realized by the content distribution system of FIG. The second embodiment is basically the same as the first embodiment except that the information included in the content storage status report is different. Therefore, different parts will be described below, and common parts will be described. Description is omitted. In the first embodiment, the content storage state generation report includes the content storage state information of all the contents distributed to the terminal device 1, but in the second embodiment, the content storage state information is changed. Only content storage status information is included.

  Now, assuming that the content storage state information shown in FIG. 2 and the change history information shown in FIG. 3 are stored in the storage state holding unit 112, the state report generation unit 114 has the information number “inf00003” in FIG. A content storage status report including only the content storage status information. That is, only the content storage state information of the content corresponding to the unreported change history is included in the content storage state report. Also, when a new distribution of content is received, the content is stored in the information holding unit 111, the content state of the content state holding unit 112 is changed (P305 in FIG. 19), and then a status report transmission request F318 in FIG. The status report generation means 114 that received the message generates a content storage status report including only the content storage status information of the content.

  When such a content storage status report is received, a part of the management-side content storage status information is updated based on the content storage status information included in the received content storage status report.

  When only the content storage status information of the changed content is included in the content storage status report, the content storage status report can be further simplified. That is, when the content is deleted, the content storage status information itself is not included in the content storage status report, and a predetermined amount is included in a part of the content storage status information (specifically, content ID and content storage path). The deletion presentation information obtained by performing an operation, for example, a hash operation is included in the content storage status report.

  FIG. 28 shows a schematic flow of content storage status report generation processing according to the second embodiment. This flow is for using deletion presentation information. In step S401, the content held in the information holding unit 111 is compared with the content included in the content storage state information (see FIG. 2). This step is performed to confirm that the content storage state information is normal (not broken). If it is determined in step S402 that the comparison result is inconsistent, the cabinet is broken. (Step S410), and the process ends.

  If the content contents match, it is determined in step S403 whether the content storage status information included in the content storage status report is for the deleted content, and if it is for the deleted content. In step S405, deletion presentation information is generated and stored in the status report storage area together with the information number. If it is not about the deleted content, in step S404, the content storage status information to be reported is copied and stored in the status report storage area.

  Next, similarly to the content storage state report generation process shown in FIG. 4, storage of unreported change history information (step S406), generation of verification information (step S407), encryption of verification information (step S408), The encryption verification information is stored (step S409). Steps S406 to S409 are the same as steps S104 to S107 in FIG.

  FIG. 29 shows a schematic flow of content storage status report verification processing according to the second embodiment. This flow is for receiving a content storage status report generated by the procedure shown in FIG. In step S501, it is determined whether deletion presentation information is included in the content storage status report.

  When the deletion presentation information is included, the management-side deletion storage information is generated by referring to the management-side content storage state information based on the corresponding information number. The items and calculations used for generating the management-side deletion presentation information are the same as the items and calculations used for generating the deletion presentation information in the terminal device 1, and the contents of those items match, so the content storage of the terminal device 1 If there is no problem in the status information, the received deletion presentation information matches the management side deletion presentation information. Both deletion presentation information is compared in step S504, and if they do not match, it is determined that the verification has failed, and in step S511, the verification failure is notified and the process ends.

  If the deletion presentation information matches, and if the deletion storage information is not included in the content storage status report, decryption of the encryption verification information (step S505), generation of management side verification information (step S506), verification Information comparison (step S507), matching determination (step S508), verification number generation, registration, notification (step S509), content status information update instruction (step S510), and verification failure notification (step S511). Do. Steps S505 to S511 are the same as steps S203 to S209 in FIG.

  When the content storage status report shown in FIGS. 28 and 29 is generated and verified, the content content included in the content storage status information shown in FIG. 2 can be omitted. The use of the change history information and the verification information is unique to the content distribution system shown in FIG. 1, and can be omitted when applied to deletion recognition of other electronic data.

  The present invention is useful as a data discard recognition method that can easily and reliably recognize discard of electronic data in a terminal device.

The figure which shows schematic structure of the content delivery system for describing the 1st Embodiment of this invention The figure which shows an example of the content storage state information in the content delivery system for describing the 1st Embodiment of this invention The figure which shows an example of the change log information in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows the schematic flow of the content storage state report production | generation process in the content delivery system for demonstrating the 1st Embodiment of this invention. The figure which shows notionally an example of the content storage state report in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the transmission data of an example of the content storage state report in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the schematic flow of the content storage state report verification process in the content delivery system for describing the 1st Embodiment of this invention The figure which shows an example of the verification number management table in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the management side content storage state information in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the management side change log | history information in the content delivery system for describing the 1st Embodiment of this invention The figure which shows operation | movement in the case of browsing the various information for content delivery services in the content delivery system for describing the 1st Embodiment of this invention. The figure which shows schematic operation | movement flow of the list information in the content delivery system for demonstrating the 1st Embodiment of this invention, and cabinet information generation processing The figure which shows an example of the content information table in the content delivery system for describing the 1st Embodiment of this invention The figure which shows an example of the content list which can be disclosed in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the cabinet information in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows operation | movement in the case of purchasing the cabinet in the content delivery system for demonstrating the 1st Embodiment of this invention. The figure which shows operation | movement in the case of purchasing the cabinet in the content delivery system for demonstrating the 1st Embodiment of this invention. The figure which shows the operation | movement in the case of receiving the delivery of the content in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the operation | movement in the case of receiving the delivery of the content in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the operation | movement in the case of receiving the delivery of the content in the content delivery system for describing the 1st Embodiment of this invention The figure which shows operation | movement in the case of returning the content in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the example of a display of the rental page screen in the content delivery system for describing the 1st Embodiment of this invention The figure which shows the example of a display of the cabinet purchase screen in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows the example of a display of the screen at the time of the content delivery request | requirement in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the display screen of the browser at the time of distribution impossible in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the display screen at the time of the content return in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows an example of the display screen of the browser at the time of the verification failure in the content delivery system for demonstrating the 1st Embodiment of this invention The figure which shows the schematic flow of the content storage state report production | generation process in the content delivery system for demonstrating the 2nd Embodiment of this invention. The figure which shows the schematic flow of the content storage state report verification process in the content delivery system for describing the 2nd Embodiment of this invention

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Terminal device 2 ... Network 3 ... Portal server 4 ... Content database 5 ... Content delivery server 6 ... Cabinet management server 7 ... Billing server 11 ... Cabinet management client DESCRIPTION OF SYMBOLS 12 ... Content delivery client 13 ... Browser 14 ... Player 15 ... Wireless communication means 111 ... Information holding means 112 ... Storage state holding means 113 ... Information change means 114 ... Status report generation means 115 ... Status report output means 121 ... Status report input means 122 ... Storage status holding means 123 ... Status report verification means 124 ... Verification number management table

Claims (17)

A data discard recognition method for recognizing that electronic data held in a terminal device is discarded using a computer connected to a network,
A status management step of managing status information indicating a storage state of the electronic data in the terminal device for each terminal device as management-side status information;
Receiving a status report based on the status information from the terminal device, and
The status management step compares the status update step of updating the management-side status information based on the status report, the management-side status information, and the status information included in the status report, so that the electronic data is A data discarding recognition method including a status confirmation step for determining whether or not it has been discarded. A data discard recognition method according to claim 1,
The status information includes at least the identification information of the electronic data, data discard information indicating discard of the electronic data, and storage location information of the electronic data in the terminal device,
In the status check step, when the identification information and the storage location information of the electronic data included in the status report match the identification information and the storage location information included in the management-side status information, the data discarding A data discard recognition method that determines that information is valid. A data discard recognition method according to claim 2,
The status information includes a part of the content of the electronic data held in the terminal device,
In the status check step, the data discard information included in the status report indicates discard of the electronic data, and a part of the content of the electronic data included in the status report is included in the management-side status information. A data discard recognition method for determining that the electronic data has been discarded when it does not match a part of the content of the electronic data. A data discard recognition method according to claim 1,
The status report when the electronic data is stored in the terminal device includes the status information when the electronic data is stored,
The status report after discarding the electronic data in the terminal device includes discard presentation information obtained by performing a predetermined operation on at least part of the status information after discarding the electronic data,
In the status confirmation step, the discard presentation information included in the status report is compared with management side judgment information obtained by performing a predetermined calculation on at least a part of the management side status information, and when both match each other A data discard recognition method for determining that the electronic data has been discarded. A data discard recognition method according to any one of claims 1 to 4,
The electronic data is content distributed via the network,
The data discard recognition method, wherein the status information is content storage state information indicating a storage state of the content. A data destruction recognition computer that recognizes that electronic data held in a terminal device has been destroyed using a network,
A status management unit that manages status information indicating the storage state of the electronic data in the terminal device as management-side status information for each terminal device;
Receiving a status report based on the status information from the terminal device,
The status management unit compares the status update function for updating the management-side status information based on the status report, the management-side status information, and the status information included in the status report, so that the electronic data is A computer having a status confirmation function for determining whether or not it has been discarded. A computer for data destruction recognition according to claim 6,
The status information includes at least the identification information of the electronic data, data discard information indicating discard of the electronic data, and storage location information of the electronic data in the terminal device,
The status confirmation function is configured to discard the data when the identification information and the storage location information of the electronic data included in the status report match the identification information and the storage location information included in the management-side status information. A computer that determines that information is valid. A computer for data destruction recognition according to claim 7,
The status information includes a part of the content of the electronic data held in the terminal device,
In the status confirmation function, the data discard information included in the status report indicates discard of the electronic data, and a part of the content of the electronic data included in the status report is included in the management-side status information. A computer that determines that the electronic data has been discarded if it does not match a part of the content of the electronic data. A computer for data destruction recognition according to claim 6,
The status report when the electronic data is stored in the terminal device includes the status information when the electronic data is stored,
The status report after discarding the electronic data in the terminal device includes discard presentation information obtained by performing a predetermined operation on at least part of the status information after discarding the electronic data,
The status confirmation function compares the discard presentation information included in the status report with management judgment information obtained by performing a predetermined calculation on at least a part of the management status information, and the two match A computer that determines that the electronic data has been discarded. A computer for data destruction recognition according to any one of claims 6 to 9,
The electronic data is content distributed via the network,
The status information is a content storage state information indicating a storage state of the content. A terminal device that holds electronic data,
A status holding unit for storing status information indicating a storage state of the electronic data;
A status report generator for generating a status report based on the status information;
A status report output unit that outputs the status report generated by the status report generation unit;
A status change unit that changes a storage state of the electronic data including the destruction of the electronic data, and the status information includes identification information of the electronic data, data destruction information indicating the destruction of the electronic data, and the electronic A terminal device including at least data storage location information. The terminal device according to claim 11,
The status information is a terminal device including a part of the content of the electronic data. The terminal device according to claim 11,
The status report at the time of storing the electronic data includes the status information at the time of storing the electronic data,
The terminal device including the discard presentation information obtained by performing a predetermined calculation on at least a part of the status information after the electronic data is discarded, the status report after the electronic data is discarded. The terminal device according to any one of claims 11 to 13,
The electronic data is content distributed via the network,
The terminal information is content storage state information indicating the storage state of the content.   A data discard recognition program for executing each step in the data discard recognition method according to any one of claims 1 to 5 using a computer.   The program for implement | achieving the said status management part and the said receiving part in the computer for data destruction recognition of any one of Claim 6 thru | or 10.   The terminal program for implement | achieving the said status report production | generation part in the terminal device of any one of Claim 11 thru | or 14, the said status report output part, and the said status change part using a computer.

Images