JP4860648B2 - Receivable management system, receivable management method and receivable management program - Google Patents

Description

  The present invention relates to a debt management system that includes a debtor device managed by a debtor and a credit management device managed by a creditor, and manages a credit exchanged between the credit management devices.

  In recent years, settlement processing has been carried out using electronic bond information that represents credit and debt relationships as electronic information. In addition, as a model for realizing payment processing using electronic bond information, creditor certification that continues to manage electronic bond information with the debtor's credit management device and proves that it is a creditor with the financial institution's credit management device There has been proposed a model for executing credit transfer by managing information and distributing creditor certification information between credit management devices on the financial institution side.

  For example, Patent Document 1 discloses a method for efficiently authenticating the owner of protected data that is circulated by using a token that is information that identifies the owner of the protected data that should be prevented from being used multiple times. ing.

  There is also a technique in which the credit management device on the side of the credit transferer simply transfers the creditor certification information corresponding to the credit to be transferred to the credit management device on the side of the credit transferee (see Non-Patent Document 1, for example). ).

Japanese Patent Application Laid-Open No. 2001-126009 Masayuki Terada, Kurano Hanadate, Kan Fujimura, Jun Sekine, “General Purpose Originality Guarantee System for Electronic Rights Distribution Boards”, Transactions of Information Processing Society of Japan, June 13, 2001, Vol. 42 no. 8 p. 2017-2029

  However, while the technology of Patent Document 1 described above makes it easy for the debtor to identify the creditor, the creditor assigner is responsible for the electronic claim information corresponding to the creditor certification information to the debtor each time the claim is assigned. There is a problem that it takes time to request an update and a cost for notifying the update request of the electronic bond information.

  In addition, the technology of Non-Patent Document 1 described above does not incur costs for renewal requests, but renewal of creditors accompanying the transfer of receivables is not reflected in the electronic receivable information, making it difficult for the debtors to identify the creditors. There is a problem.

  Accordingly, the present invention has been made to solve the above-described problems of the prior art, and a specific cost of the creditor by the debtor, and an electronic claim information update request notification imposed on the creditor in association with the credit transfer. An object of the present invention is to provide a claim management system, a claim management method, and a claim management program capable of adjusting the cost required for the payment according to the purpose of electronic bond distribution.

  In order to solve the above-described problems and achieve the object, the invention according to claim 1 includes a debtor device managed by a debtor and a credit management device managed by a creditor, A receivable management system for managing receivables exchanged between devices, wherein the receivable management device is information uniquely associated with receivable information on receivables held by the obligor device, and a new receivable Creditor certification that includes at least the creditor renewal request frequency, which indicates how often the creditor requests the creditor to renew the creditor, and the number of times the credit is assigned to be renewed every time the receivable is transferred between credit management devices Along with information, a receivable assignment accepting means for receiving a receivable assignment message for notifying the assignment of receivables from a receivable management device which is a management source of the receivable wish to be assigned, and a debt received by the receivable assignment accepting means On the condition that the transfer message has not been tampered with, it verifies whether the creditor certification information received together with the claim transfer message was created by the obligor of the claim to be transferred, The creditor certification information verification means for verifying whether the creditor information is uniquely associated with the creditor information on the creditor, and the creditor certification information created by the debtor by the creditor certification information verification means. And the claim included in the creditor certification information received together with the claim assignment message by the claim assignment acceptance means when it is verified that it is uniquely associated with the claim information about the claim for assignment. Creditor assignment frequency updating means for updating the number of assignments, and a creditor who received the credit assignment frequency updated by the credit assignment frequency update means together with the credit assignment message The credit transfer number determination means for determining whether or not the creditor renewal request frequency included in the clear information has been reached, and the credit transfer number of times has reached the creditor renewal request frequency by the credit transfer number determination means If judged, the creditor update request means for transmitting an update request message for requesting the creditor to be updated to the debtor device, and the credit transfer count is determined by the credit transfer count determination means. If it is not determined that the frequency has been reached, the credit transfer count updated by the credit transfer count updating means, the creditor renewal request frequency, and the self-identifier to become a new creditor are included. The creditor certification information is stored, and when the credit transfer number determination means determines that the credit transfer number has reached the creditor update request frequency, the update request received from the debtor device is received. Creditor certification information storage means for storing creditor certification information included in the solicitation response message, and the debtor device receives an update request message for requesting creditor update from the credit management device. Received from the claim management device, update request verification means for verifying whether or not the origin of creditor certification information included in the update request message is self, on condition that the update request message has not been tampered with If the update request verification means verifies that the creditor certification information included in the renewal request message is self, the creditor certificate information contained in the receivable information corresponding to the creditor certification information included in the renewal request message The creditor identifier is updated to the creditor identifier of a new creditor that is the sender of the update request message, and the update processing means for updating the number of times the credit is transferred, and the credit management device that is the sender of the update request message An update request response means for transmitting an update request response message including creditor certification information including at least the creditor identifier updated by the update processing means and the number of times of credit transfer. To do.

  Further, in the invention according to claim 2, in the above invention, the debtor device is characterized by a debt identifier for identifying a claim managed by itself, a creditor identifier for identifying a creditor, and a debtor for identifying a debtor. Claim information generating means for generating claim information including information relating to a claim and a debtor relationship concluded between the creditor and the debtor, and claim information for storing the claim information generated by the claim information generation means A storage means, a creditor update request frequency setting means for setting a creditor update request frequency indicating a frequency of requesting a new creditor to update the creditor, and a claim information generated by the claim information generating means A creditor identifier that uniquely identifies a creditor, a debtor identifier that identifies a debtor, and a creditor update request frequency set by the creditor update request frequency setting means. Creditor certification information generating means for generating creditor certification information including the creditor certification information issuing means for issuing creditor certification information generated by the creditor certification information generating means to the credit management device. It is characterized by having.

  According to a third aspect of the present invention, in the above invention, when the debtor device receives a debt settlement request presenting the creditor certification information from the credit management device, the creditor included in the creditor certification information The debt settlement date in the claim information corresponding to the identifier is confirmed. If the debt settlement date is exceeded, the debt is fulfilled, and the debt information stored in the claim information storage means is It is further characterized by having a debt fulfillment means for deleting information on claims that have been fulfilled.

  According to a fourth aspect of the present invention, in the above invention, the creditor update request frequency setting means transmits an update request message requesting the creditor to update the creditor together with the creditor update request frequency. Is set to the required creditor identifier for which the creditor certification information is issued, and the creditor certification information issuing means is set together with the creditor certification information for the notification required creditor identifier set by the creditor update request frequency setting means. The credit transfer acceptance means receives the creditor certification information and the notice required creditor identifier set by the creditor march request frequency setting means together with the credit transfer message, and the creditor renewal request If the identifier of the creditor who receives the claim and becomes a new creditor matches the required creditor identifier received together with the claim transfer message, the means And transmits an update request message for requesting the update of the creditor against location.

  According to a fifth aspect of the present invention, in the above invention, the creditor update request frequency setting means requests the creditor to update the creditor from the new creditor together with the creditor update request frequency. The creditor certification information issuing means sets the reference date set by the creditor update request frequency setting means to the credit management device together with the creditor certification information. The credit transfer assignment receiving means receives the creditor certification information and the reference date that requires transmission of the update request message requesting the creditor update together with the credit transfer message, and the creditor update requesting means When the date of receipt of the credit transfer message is after the reference date received together with the credit transfer message, an update request message requesting the creditor device to be updated is transmitted to the debtor device.

  According to a sixth aspect of the present invention, in the above invention, the creditor update request frequency setting means sets a creditor update request frequency for each user identifier that identifies a user of a credit management device that can be a credit transfer destination. The creditor certification information issuing means issues creditor update request frequency set for each user identifier by the creditor certification information and the creditor update request frequency setting means to the credit management device, and the creditor assignment acceptance means Receives the creditor certification information and the creditor update request frequency set for each user identifier by the creditor update request frequency setting means together with the credit transfer message, and the creditor update request means receives the credit transfer request message together with the credit transfer message. The creditor reassignment count associated with the user identifier in the creditor renewal request frequency received together with the receivable assignment message is And judging whether or not reached the required frequency.

  Further, in the invention according to claim 7, in the above invention, the creditor update request frequency setting means is associated with the number of days from the date of receipt of the credit assignment message to the date of debt settlement included in the claim information. Each creditor renewal request frequency is set, and the creditor certification information issuing means associates the creditor renewal request frequency setting means with the creditor renewal request frequency setting means in association with the creditor certification information and the number of days from the date of receipt of the loan assignment message to the debt settlement date. The creditor update request frequency is issued to each creditor renewal request device, and the creditor assignment acceptance means updates the creditor in association with the creditor certification information and the number of days from the date of receipt of the creditor assignment message to the debt settlement date. Each creditor renewal request frequency set by the request frequency setting means is received together with a claim transfer message, and the creditor update request means receives the number of receivable transfers received together with the claim transfer message. In the creditor renewal request frequency received together with the credit transfer message, it is determined whether or not the creditor renewal request frequency associated with the number of days from the date of receipt of the credit transfer message to the debt settlement date is reached. It is characterized by.

  According to an eighth aspect of the present invention, in the above invention, the creditor renewal request frequency setting means updates the number of receivable assignments for each user identifier that identifies a user of a receivable management apparatus that can be a remittance destination of the receivable. The creditor certification information issuing means transmits the creditor certification information and the update count condition set for each user identifier by the creditor update request frequency setting means to the credit management device, The transfer acceptance means receives the creditor certification information and the update count condition set for each user identifier by the creditor update request frequency setting means together with the credit transfer message, and the credit transfer count update means receives the credit transfer message. The number of receivable assignments received together with the renewal is also updated according to the update number condition received together with the receivable assignment message.

  Further, in the invention according to claim 9, in the above invention, the creditor update request frequency setting means is associated with the number of days from the date of receipt of the claim assignment message to the date of debt settlement included in the claim information. The creditor certificate information issuing means issues the creditor certification information and the update frequency condition set by the creditor update request frequency setting means to the credit management device. The credit transfer assignment receiving means receives creditor certification information and each creditor update request frequency set by the creditor update request frequency setting means together with a credit transfer message, and the credit transfer number update means The number of times of receivable assignment received together with the message is updated according to the update number condition received together with the same receivable assignment message.

  In the invention according to claim 10, in the above invention, the creditor certification information is included in the creditor certification information before the division in each creditor certification information divided in accordance with the division of the credit. It is characterized by including the creditor renewal request frequency and the number of times of credit transfer.

  Further, the invention according to claim 11 is exchanged between claims management devices in a claims management system comprising a debtor device managed by a debtor and a claims management device managed by a creditor. A claim management method for managing a claim, wherein the claim management device is information uniquely associated with claim information on a claim held by the debtor device, from a new creditor to a debtor. The creditor wishes to transfer, along with the creditor renewal request frequency indicating the frequency of creditor renewal request and the creditor certification information including at least the number of receivable transfers assigned each time the receivable is transferred between credit management devices A claim assignment acceptance step for receiving a claim assignment message for notifying the assignment of a claim from a claim management device that is a management source of the claim, and a claim assignment received by the claim assignment acceptance step On the condition that the message has not been tampered with, verify whether the creditor certification information received together with the claim transfer message was created by the obligor of the claim to be transferred and A creditor certification information verification step for verifying whether or not the creditor identification information is uniquely associated with the creditor information, and the creditor certification information created by the debtor through the creditor certification information verification step. And when it is verified that the information is uniquely associated with the claim information of the claim to be assigned, the assignment of the claim included in the creditor certification information received together with the claim assignment message in the claim assignment acceptance step The number of times of receivable transfer that updates the number of times of renewal, and the number of times of receivable transfer that is updated by the step of renewing the number of times of receivable transfer The credit transfer number determination step for determining whether or not the creditor renewal request frequency included in the received creditor certification information has been reached, and the credit transfer number of times reaches the creditor renewal request frequency by the credit transfer number determination step. If it is determined that the creditor has been transferred, an update request message for requesting the update of the creditor is transmitted to the creditor device, and the creditor transfer count is determined by the creditor transfer count determination step. If it is not determined that the creditor renewal request frequency has been reached, the number of receivable assignments updated by the receivable assignment number renewal step, the creditor renewal request frequency, and the new creditor's own identifier If the creditor certification information including the above is stored, and it is determined that the creditor assignment frequency has reached the creditor renewal request frequency by the creditor assignment frequency determination step A creditor certification information storage step for storing creditor certification information included in the update request response message received from the debtor device, the debtor device from the credit management device to the creditor When an update request message requesting an update is received, it is verified whether or not the creditor certification information source included in the update request message is self, provided that the update request message has not been tampered with. Included in the update request message if the update request verification step and the update request verification step verify that the creditor certification information included in the update request message received from the claim management device is the self The creditor identifier in the credit information corresponding to the creditor certification information to be updated is updated to the creditor identifier of the new creditor who is the sender of the update request message, and the number of times the credit is transferred is updated And an update request response message including creditor certification information including at least the creditor identifier and the number of times of credit transfer updated by the update processing step with respect to the claim management device that is the transmission source of the update request message. And an update request response step for transmitting.

  The invention according to claim 12 is exchanged between the claim management devices in the claim management system including the debtor device managed by the debtor and the claim management device managed by the creditor. A credit management program for causing a computer as a credit management device to execute processing related to the management of credits, wherein the computer as the credit management device is uniquely associated with credit information about the credit held by the debtor device Information that is a creditor renewal request frequency that indicates how often a new creditor requests the creditor to renew the creditor, and a credit that is renewed every time the credit is transferred between credit management devices Receivable assignment message for notifying the transfer of receivables from the receivable management device that manages the receivables desired to be transferred along with creditor certification information including at least the number of transfers The creditor credential received together with the claim assignment message is the obligor of the claim that you wish to assign, provided that the credit assignment acceptance procedure received and the claim assignment message received through the claim assignment acceptance procedure have not been tampered with. The creditor certification information verification procedure for verifying whether the creditor information is uniquely associated with the credit information about the transfer-requested claim and the creditor certificate If it is verified by the information verification procedure that the creditor certification information was created by the debtor and is uniquely associated with the claim information for the claim to be transferred, the credit transfer A procedure for renewing the number of receivables transferred to update the number of receivables included in the creditor certification information received together with the receivable assignment message by the acceptance procedure; A reassignment frequency determination procedure for determining whether or not the renewed reassignment frequency has reached a creditor renewal request frequency included in the creditor certification information received together with the receivable assignment message; and If the procedure determines that the number of receivables has reached the creditor renewal request frequency, a creditor renewal request that sends an update request message to the debtor device to request renewal of the creditor And if the number of receivable assignments is not determined to have reached the creditor renewal request frequency by the receivable assignment number determination procedure, the receivable assignment number updated by the receivable assignment number updating means, Creditor certification information including the frequency of creditor renewal request and its own identifier to become a new creditor is stored in the storage unit, and the number of receivable transfers is determined by the creditor renewal request by the procedure for determining the number of receivables transferred If it is determined that the frequency has been reached, a creditor certification information storage procedure for storing creditor certification information included in the update request response message received from the debtor device in the storage unit is executed. It is characterized by that.

  The invention according to claim 13 is exchanged between claims management devices in a claims management system comprising a debtor device managed by a debtor and a claims management device managed by a creditor. A credit management program for causing a computer as a debtor device to execute processing relating to the management of credits, wherein the computer as the debtor device receives an update request message requesting the creditor to be updated from the credit management device The update request verification procedure for verifying whether or not the origin of the creditor certification information included in the update request message is self, on the condition that the update request message has not been tampered with, If the creditor certification information included in the received update request message is verified by the update request verification procedure as being the source of the creditor certification information, the update request message Updating the creditor identifier in the credit information corresponding to the included creditor certification information to the creditor identifier of the new creditor that is the sender of the update request message, and updating the number of times the credit is transferred; Update for transmitting an update request response message including creditor certification information including at least the creditor identifier updated by the update processing procedure and the number of times of credit transfer to the credit management device that is the transmission source of the update request message And a request response procedure.

  According to the present invention, creditor certification information proving creditors is distributed among creditors, and the number of receivable assignments updated as the creditor certification information is distributed reaches the creditor renewal request frequency. The creditor's renewal request is notified to the obligor, so the obligor's specific cost of the creditor and the cost required for the electronic receivable information renewal request imposed on the creditor when the receivable is assigned It is possible to adjust according to the purpose of electronic bond distribution.

  In addition, according to the present invention, since the debtor sets the renewal request frequency for notifying the creditor's renewal and issues it to the creditor together with the creditor certification information, the debtor has an opportunity to grasp the change of the creditor. It can be set independently.

  Further, according to the present invention, when a debt settlement request presenting creditor certification information is received from the credit management device, the debt settlement date in the credit information corresponding to the creditor identifier included in the creditor certification information is confirmed. If the debt settlement date has been exceeded, the debt will be fulfilled and the information on the debt that fulfilled the debt will be deleted from the claim information. Can be implemented and digested.

  In addition, according to the present invention, the obligor apparatus specifies the obligor for which the obligor is required to notify the obligor who is required to transmit an update request message requesting the obligor to renew the obligor, together with the frequency of the obligor renewal request. The identifier is set, and the mandatory creditor identifier notified together with the creditor certification information is issued to the credit management device. The credit management device receives the creditor certification information and the mandatory creditor identifier notified together with the credit transfer message, and receives the credit. If the new creditor's own creditor identifier matches the mandatory notification creditor identifier received with the credit transfer message, an update request message requesting the creditor device to update the creditor is sent. Therefore, it is possible for the debtor to arbitrarily select a creditor who is required to send an update request message along with the transfer of the claim.

  In addition, according to the present invention, the debtor device sets the reference date when it is necessary to send an update request message requesting the creditor to be renewed from the new creditor to the debtor together with the frequency of the creditor update request. Set and issue the base date together with the creditor certification information to the credit management device. The credit management device sets the base date when the creditor certification information and the update request message requesting the creditor update are required. If the receipt date of the receivable transfer message is after the reference date received with the receivable transfer message, an update request message requesting the renewal of the creditor is sent to the debtor device. It is possible for the debtor side to arbitrarily set a reference date for transmitting an update request message from a new creditor along with the transfer.

  Further, according to the present invention, the debtor device sets the creditor update request frequency for each user identifier that identifies a user of the credit management device that can be a transferee of the credit, and sets it for each creditor certification information and user identifier. The creditor renewal request frequency sent to the receivable management device is received, and the receivable management device receives the creditor renewal request frequency set for each creditor certification information and user identifier together with the receivable transfer message and receives it together with the receivable transfer message It is determined whether the number of receivables transferred has reached the creditor renewal request frequency associated with the user identifier in the creditor renewal request frequency received together with the receivable assignment message. It is possible to manage receivables according to creditors.

  According to the present invention, the debtor device sets each creditor renewal request frequency in association with the number of days from the date of receipt of the claim assignment message to the debt settlement date included in the claim information, and the creditor certification information And the creditor renewal request frequency set in correspondence with the number of days from the date of receipt of the receivable assignment message to the due date of the debt settlement to the receivable management device. The receivable management device receives the creditor certification information and the receivable assignment message. The creditor renewal request received when the creditor renewal request frequency set in association with the number of days from the date to the debt settlement date is received together with the receivable assignment message, and the number of receivable assignments received together with the receivable assignment message is received together with the receivable assignment message Since it is determined whether or not the frequency of the creditor renewal request associated with the number of days from the receipt date of the receivable assignment message to the debt settlement date has been reached, the debtor side determines the debt settlement date. It is possible to carry out the management of the corresponding receivables.

  Further, according to the present invention, for example, the creditor renewal condition of the number of times of receivable assignment renewed with the assignment of the receivable (for example, the number of times of addition of the current number of receivable assignments, etc.) Therefore, it is possible to speed up the transmission of the update request notification from the creditor according to the transfer destination of the credit.

  In addition, according to the present invention, the renewal condition of the number of times of receivable assignment that is renewed with the assignment of receivables (for example, the number of times of addition of the current number of receivable assignments, etc.) Since it changes according to the number of days, it is possible to speed up the transmission of the update request notification from the creditor according to the number of days from the transfer date of the bond to the debt settlement date.

  Further, according to the present invention, each creditor certification information divided according to the split of credits includes the creditor renewal request frequency and the number of times of credit transfer included in the creditor certification information before the split. Therefore, it is possible to maintain a function of transmitting an update request message from a new creditor without requiring any special processing according to the split of the credit.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out a claim management system, a claim management method, and a claim management program according to the present invention will be described in detail with reference to the accompanying drawings. In addition, below, after describing Example 1 as one embodiment of the claim management system according to the present invention, another example will be described as another embodiment included in the present invention.

[Outline and Features of Claim Management System (Example 1)]
First, the outline and characteristics of the claim management system according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram for explaining the outline and features of the claim management system according to the first embodiment.

  The claim management system according to the first embodiment is summarized to manage the claims exchanged between the claim management devices, but it facilitates the identification of the creditors by the debtors, and to the creditors along with the assignment of the claims. The main feature is that it is possible to reduce the cost required for notification of an update request for imposed electronic bond information.

  The main features will be described in detail. The credit management system according to the first embodiment is, for example, as shown in FIG. 1, a debtor device managed by a debtor and a credit managed by the current owner of the claim. It includes a management device A and a credit management device B managed by a person who wishes to transfer the credit. A person who wishes to assign a claim becomes an official creditor by assigning creditor certification information from the current owner of the claim.

  In the system as described above, when the debtor device concludes a claim liability relationship with the claim management device A, the debtor device generates and stores the claim information for the claim, and the creditor certificate uniquely associated with the claim information. Information is issued to the creditor management apparatus A in advance.

  Upon receipt of the transfer request message including the transfer request claim ID for identifying the transfer request claim from the claim management device B, the claim management device A confirms that the transfer request message has not been tampered with, Along with the creditor certification information corresponding to the ID, a transfer message for notifying the transfer of the bond is transmitted to the bond management apparatus B (see (1) in FIG. 1).

  The creditor certification information transmitted together with the transfer message is information uniquely associated with the credit information of the credit held by the debtor device. The creditor ID for identifying the creditor, the debtor ID from the new creditor Transfer notification frequency (for example, “5”) indicating the frequency of requesting the creditor to update the creditor, and the number of hops subtracted each time the bond is transferred between the bond management devices (equivalent to the transfer notification frequency) “5” as an initial value. For example, when the current value is “1”, it indicates that it has already been transferred four times).

  When the credit management device A transmits the transfer message to the credit management device B, the creditor ID for identifying the creditor included in the creditor certification information is “UID1” indicating the current owner of the credit. Is updated to “UID2”, which is a person who wishes to transfer the receivable.

  Moreover, the claim management apparatus A invalidates the creditor certification information transmitted to the claim management apparatus B at the time of transmission of the claim assignment message (see (2) in FIG. 1).

  When the credit management device B receives the transfer message from the credit management device A (see (3) in FIG. 1), the creditor certification information received together with the transfer message is transferred on condition that the transfer message is not falsified. And whether or not it is created by the debtor who wishes to be receivable, and whether or not it is uniquely associated with the receivable information on the receivable wished to be transferred (( 4)).

  When it is verified that the creditor management device B is created by the creditor and the creditor certification information is uniquely associated with the claim information about the transferable claim Then, “1” is subtracted from the number of hops included in the creditor certification information received together with the transfer message (see (5) in FIG. 1).

  After subtracting the number of hops, the bond management device B confirms whether or not the number of hops after the subtraction is “hop count = 0” (that is, confirms whether or not the transfer notification frequency has been reached). Then, it is determined whether or not the creditor device is requested to update the creditor (see (6) in FIG. 1).

  When it is confirmed that “the number of hops = 0” (when the arrival of the transfer notification frequency is confirmed), the claim management apparatus B requests the creditor renewal information to request the creditor renewal. Is sent to the debtor device (see (7) in FIG. 1).

  For this reason, the claim management system according to the first embodiment, as described in the main feature described above, is a specific cost of the creditor by the debtor, and a request for updating the electronic credit information imposed on the creditor when the creditor is assigned. The cost required for notification can be adjusted according to the purpose of electronic bond distribution.

  Hereinafter, a process after the claim information change request message is transmitted from the claim management apparatus B to the debtor apparatus will be briefly described.

  When the debtor device receives the claim information change request message from the claim management device B, the originator of the creditor certification information included in the claim information change request message is provided on the condition that the claim information change request message has not been tampered with. Verify whether you are self. If it is verified that the origin of the creditor certification information included in the claim information change request message received from the claim management device B is self, the credit information change is made in the creditor ID of the claim information The creditor ID in the credit information uniquely corresponding to the creditor certification information included in the request message is updated to a new creditor that is the transmission source of the claim information change request message (for example, “UID1” → “UID2”) And the hop count is reset (for example, reset from “0” to an initial value “5”) (see (8) in FIG. 1).

  Then, the debtor device sends the updated creditor ID (for example, “UID2”) and the reset hop count (for example, “5” to the credit management device B that is the transmission source of the claim information change request message. ")" Is sent to the creditor information change request response message including creditor certification information including at least (see (9) in FIG. 1).

  Upon receipt of the claim information change request response message from the debtor device, the claim management device B receives the creditor certification information contained in the claim information change request response message on the condition that the claim information change request response message has not been tampered with. Store (see (10) in FIG. 1).

[Structure of Claim Management System (Example 1)]
Next, the structure of the claim management system according to the first embodiment will be described with reference to FIGS. FIG. 2 is a block diagram illustrating the configuration of the bond management system according to the first embodiment. FIG. 3 is a block diagram illustrating the configuration of the debtor apparatus according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of bond information according to the first embodiment. FIG. 5 is a block diagram illustrating a configuration of a credit management device managed by the current owner of the credit according to the first embodiment. FIG. 6 is a diagram illustrating a configuration example of creditor certification information according to the first embodiment. FIG. 7 is a block diagram illustrating a configuration of a credit management apparatus managed by a person who wants to transfer a credit according to the first embodiment.

  As shown in FIG. 2, the claim management system according to the first embodiment is managed by the debtor device 100 managed by the debtor, the claim management device 200 managed by the current owner of the claim, and the claimee. The debtor device 100, the bond management device 200, and the bond management device 300 are connected to each other in a communicable state via the network 1. The network 1 corresponds to the Internet, a dedicated line, a LAN, and the like.

  As an initial state, the debtor device 100 manages the debtor ID (UID0), the public key (Pk0) and the private key (Sk0) corresponding to the debtor ID (UID0), and the bond information (X), and the device address Assume that (A0) is assigned.

  The credit management device 200 includes creditor ID (UID1), public key (Pk1) and private key (Sk1) corresponding to creditor ID (UID1), and creditor certification information (C) uniquely corresponding to credit information (X). T) is managed and a device address (A1) is assigned.

The creditor certification information (T) includes a credit ID (XID) for identifying the uniquely associated credit information, and a frequency at which a new creditor requests the creditor to update the creditor. Notification frequency F (for example, “5” when renewal transfer is requested for the fifth time), and the hop count H (transfer notification frequency The initial value is “5”, which is the same value. For example, if the current value is “1”, it indicates that it has already been transferred four times), and the debtor ID (UID0) for identifying the debtor ), A creditor ID (UID1) for identifying the creditor, and at least a signature SIG ₀ (XID, UID0, F) with a secret key (Sk0) for XID, UID0, F.

  The credit management device 300 manages the creditor ID (UID2), the public key (Pk2) and the secret key (Sk2) corresponding to the creditor ID (UID2), and is assigned the device address (A2). To do.

  As the creditor certification information (T) described above, there are various character strings, CSV (Comma Separated Value) format, XML (Extensible Markup Language) format, HTML (Hyper Text Markup Language) format, binary format, etc. Information described using a description format can be adopted, and information included in the creditor certification information (T) in order to detect falsification of the creditor certification information (T) includes, for example, a debtor and a credit An electronic signature by a creditor or a public key certificate issued to a creditor or debtor can be adopted.

  The above device address is information for uniquely identifying each of the debtor device 100, the claim management device 200, and the claim management device 300 on the network. For example, an IPv6 (Internet Protocol Version 6) address, a host name, or the like Can be used.

  As shown in FIG. 3, the debtor device 100 managed by the debtor includes a communication unit 110, a storage unit 120, and a control unit 130. The communication unit 110 controls communication related to various information exchanged between the bond management apparatus 200 and the bond management apparatus 300. The communication unit 110 can also encrypt the exchanged information using SSL (Secure Socket Layer) or the like as necessary.

  The storage unit 120 is a storage unit that stores data and programs necessary for various processes performed by the control unit 130, and is particularly configured to store bond information 121 as closely related to the present invention. The bond information 121 corresponds to “bond information” described in the claims.

  The credit information 121 is information generated by the credit information generation unit 131 described later as information related to the credit and debt relationship concluded between the creditor and the debtor, and specifically, as illustrated in FIG. “Debt ID (XID)” for specifying the receivable X, “Payment amount” and “Payment date” for the debt, “Debt ID (UID0)” for specifying the debtor, and the creditor “Creditor ID (UID1)” is stored.

  In addition to the above-described information, additional information such as transfer restriction special contract, interest rate, debtor's financial status, transaction history between the debtor and creditor may be included in the claim information 121.

  The control unit 130 is a processing unit that has a predetermined control program, a program that defines various processing procedures, and an internal memory for storing necessary data, and executes various processes using these, and is particularly suitable for the present invention. The closely related items include a credit information generation unit 131, a creditor certification information generation unit 132, an update processing unit 133, and a response message transmission unit 134.

  The claim information generation unit 131 corresponds to the “claim information generation means” described in the claims, and the creditor proof information generation unit 132 also sets the “creditor update request frequency setting” described in the claims. Corresponding to “means”, “creditor certification information generating means”, and “creditor certification information issuing means”, the update processing unit 133 is also “update request verification means” and “update processing means” described in the claims. The response message transmission unit 134 corresponds to “update request response means” described in the claims.

  The receivable information generating unit 131 is a processing unit that generates receivable information relating to a receivable-liability relationship concluded between the creditor and the obligor when the receivable-liability relationship is concluded, and the generated receivable information is stored in the storage unit 120. Stored as bond information 121.

  The creditor certification information generation unit 132 is a processing unit that uniquely generates creditor certification information issued to the creditor in association with the credit information generated by the credit information generation unit 131. Specifically, the creditor certification information generation unit 132 sets a transfer notification frequency that represents the frequency with which a new creditor is requested to update the creditor.

  Next, the creditor certification information generation unit 132 uniquely associates with the credit information generated by the credit information generation unit 131, and identifies a creditor ID for identifying the creditor, a debtor ID for identifying the debtor, And creditor certification information including the transfer request frequency. Then, the creditor proof information generation unit 132 issues creditor proof information to the credit management device 200 managed by the creditor who has concluded the credit liability relationship via the communication unit 110.

  The update processing unit 133 is a processing unit that receives a credit information change request message requesting creditor update, verifies creditor certification information included in the credit information change request message, and updates the credit information.

Specifically, the update processing unit 133 uses the creditor certification information (T), a random number (R3) arbitrarily generated by the credit management device 300, and a signature using a secret key (Sk3) managed by the credit management device 300. When a claim information change request message including SIG ₃ (T, R3) is received from the claim management apparatus 300, the signature SIG ₃ (T, R3) is verified using the public key (Pk3), and the claim information change request message is received. Make sure that it has not been tampered with. When it is confirmed that the bond information change request message has not been tampered with, the update processing unit 133 uses the public key (Pk0) to sign the signature SIG ₀ (XID, UID0, F) are verified, and it is confirmed that the creator of the creditor certification information (T) included in the claim information change request message is self.

  If the update processing unit 133 can confirm that the creditor certification information (T) included in the claim information change request message received from the claim management apparatus 300 is self, The creditor ID in the creditor information (X) uniquely corresponding to the creditor certification information (T) included in the creditor information change request message is changed in the creditor ID of the stored creditor information 121. Substitute the creditor ID of the new creditor who is the sender of the request message (for example, update from “UID1” to “UID2”) and set the value of the hop count H to the same value as the transfer notification frequency F Reset (for example, reset from “0” to “5”).

  The response message transmission unit 134 is a processing unit that transmits a bond information change request response message to the bond management apparatus 300 that is the transmission destination of the bond information change request message.

Specifically, when the update processing unit 133 finishes updating the bond information (X), the response message transmission unit 134 updates the creditor ID (for example, “UID2”) and the reset hop count H ( For example, a creditor information change request response message including creditor certification information (T) including at least “5”), an arbitrary random number (R3), and a signature SIG ₃ (T, R3) Is transmitted to the claim management apparatus 300 which is the transmission source.

  As shown in FIG. 5, the claim management apparatus 200 managed by the current owner of the claim is configured to include a communication unit 210, a storage unit 220, and a control unit 230. The communication unit 210 controls communication related to various information exchanged between the debtor device 100 and the bond management device 300. Note that the communication unit 210 can also encrypt exchanged information using SSL (Secure Socket Layer) or the like as necessary.

  The storage unit 220 is a storage unit that stores data and programs necessary for various processes performed by the control unit 230. In particular, the storage unit 220 is configured to store creditor certification information 221 that is closely related to the present invention. The creditor certification information 221 corresponds to “creditor certification information” described in the claims.

  The creditor certification information 221 is information that is received and stored from the debtor when the creditor debt relationship is concluded as information for certifying the creditor's identity. Specifically, as illustrated in FIG. Obligor certification information (T), obligor ID (UID0) for identifying the obligor, obligor ID (UID1) for identifying the obligor, and requesting a new obligor to update the obligor Transfer notification frequency F representing the frequency (for example, 5), the number of hops H subtracted each time a bond is transferred between bond management devices ("5", which is the same value as the transfer notification frequency, is set as an initial value, for example, If the current value is “1”, it indicates that it has already been transferred four times).

  The control unit 230 is a processing unit that has a predetermined control program, a program that defines various processing procedures, and an internal memory for storing required data, and executes various processes using these, and is particularly suitable for the present invention. As closely related, a transfer request message receiving unit 231, a creditor certification information invalidating unit 232, and a creditor certification information transmitting unit 233 are provided.

The assignment request message receiving unit 231 is a processing unit that receives an assignment request message for requesting assignment of a claim from the claim management apparatus 300 managed by a claim assignee. The assignment request message includes a claim ID (for example, XID) of a claim that is desired to be transferred, a creditor ID (UID2) of a manager of the claim management apparatus 300 that is a request for transfer of the claim, and a claim management that is the transfer request source. The device address (A2) of the device 300, a random number (R1) arbitrarily generated by the bond management device 300, and a signature SIG ₂ (XID, UID2, A2, R1) with a secret key (Sk2) managed by the creditor management device 300 )It is included.

When the transfer request message receiving unit 231 receives the transfer request message from the bond management device 300, the transfer request message receiving unit 231 verifies the signature SIG ₂ (XID, UID2, A2, R1) included in the transfer request message using the public key (Pk2). Confirm that the transfer request message has not been tampered with.

  If it can be confirmed that the transfer request message has not been tampered with, the transfer request message receiving unit 231 records the device address (A2) included in the transfer request message as the destination of the creditor certification information.

  Next, the assignment request message receiving unit 231 reads the creditor certification information corresponding to the claim ID (XID) included in the assignment request message from the storage unit 220, and obtains the creditor ID in the read creditor certification information. Update to creditor ID included in transfer request message (update from UID1 to UID2).

  The creditor certification information invalidation unit 232 is a processing unit that invalidates creditor certification information to be sent in response to a claim assignment request in the storage unit 220, and the creditor read from the storage unit 220 by the transfer request message receiving unit 231. When the update of the person ID is completed, the record corresponding to the bond ID (XID) included in the transfer request message is invalidated in the storage unit 220.

  In addition, when it becomes necessary to identify the current creditor on the debtor side, the current creditor is identified by using a record corresponding to the invalidated claim in the creditor management device of the original creditor as a trail. be able to. For example, the current creditor can be specified by following the distribution route of the creditor certification information from the device address recorded as the destination of the creditor certification information.

The creditor certification information transmission unit 233 is a processing unit that transmits creditor certification information in response to a claim assignment request. The creditor certification information (T) in which the creditor ID is updated by the assignment request message reception unit 231; and A transfer message including a signature SIG ₁ (T, R1) with the secret key (Sk1) and notifying the transfer of the receivable is transmitted with the device address (A2) recorded by the transfer request message receiving unit 231 as the destination.

  As shown in FIG. 7, the claim management apparatus 300 managed by a person who wants to assign a claim includes a communication unit 310, a storage unit 320, and a control unit 330. The communication unit 310 controls communication related to various information exchanged between the debtor device 100 and the bond management device 200. The communication unit 310 can also encrypt the exchanged information using SSL (Secure Socket Layer) or the like as necessary.

  The storage unit 320 is a storage unit that stores data and programs necessary for various processes performed by the control unit 330. In particular, the storage unit 320 is configured to store creditor certification information 321 that is closely related to the present invention. The creditor certification information 321 corresponds to “creditor certification information” described in the claims.

  The creditor certification information 321 is creditor certification information stored by a creditor certification information storage unit 337 described later.

  The control unit 330 is a processing unit that has a predetermined control program, a program that defines various processing procedures, and an internal memory for storing required data, and executes various processes using these, and is particularly suitable for the present invention. As closely related, a transfer request message transmission unit 331, a creditor certification information verification unit 332, a hop number subtraction unit 333, an update request determination unit 334, an update request message transmission unit 335, an update request response A telegram receiving unit 336 and a creditor certification information storage unit 337 are provided.

  The transfer request message transmission unit 331 corresponds to the “credit transfer request unit” described in the claims, and the creditor certification information verification unit 332 includes the “credit transfer acceptance unit” described in the claims and Corresponding to the “creditor certification information verification means”, the hop number subtraction unit 333 corresponds to the “credit receivable number updating means” described in the claims, and the update request determination unit 334 is also equivalent to the claims. The update request message transmission unit 335 corresponds to the “creditor update request unit” described in the claims, and the creditor certification information storage unit 337 This also corresponds to “creditor certification information storage means” described in the claims.

  The assignment request message transmission unit 331 is a processing unit that transmits an assignment request message requesting assignment of a claim to the claim management apparatus 200 managed by the current owner of the claim.

Specifically, the transfer request message transmission unit 331 first generates an arbitrary random number (R1). Then, a claim ID (for example, XID), a creditor ID (UID2), a device address (A2), an arbitrarily generated random number (R1), and a signature SIG ₂ (XID, A transfer request message including UID2, A2, R1) is transmitted to the claim management apparatus 200.

  The creditor certification information verification unit 332 is a processing unit that verifies the transfer message received from the credit management device 200.

Specifically, when the creditor certification information verification unit 332 receives the transfer message from the bond management device 200, it verifies the signature SIG ₁ (T, R1) included in the transfer message using the public key (Pk1). Confirm that the transfer message has not been tampered with.

If it can be confirmed that the transfer message has not been tampered with, the creditor certification information verification unit 332 uses the public key (Pk0) to sign the signature SIG ₀ (XID, UID0, F) is verified, and the creator of the creditor certification information (T) is the debtor (UID0) of the debtor device 100, and the creditor certification information (T) is transferred to the credit management device 200. It is confirmed whether or not it corresponds to the desired bond ID (XID).

  The hop number subtraction unit 333 is a processing unit that subtracts the hop number H in the creditor certification information included in the transfer message received from the bond management device 200.

  Specifically, the hop number subtracting unit 333 creates the creditor proof information (T) from the debtor device 100 (UID0), and the creditor proof information (T) is sent to the credit management device 200. On the other hand, when the creditor certification information verification unit 332 confirms that the creditor ID (XID) is desired to be assigned, the value of the hop count H included in the creditor certification information (T) is set. Subtract "1".

  The update request determination unit 334 is a processing unit that determines whether or not to request the creditor device 100 to update the creditor based on the value of the hop number H subtracted by the hop number subtraction unit 333.

  Specifically, the update request determination unit 334 confirms whether or not the value of the hop number H subtracted by the hop number subtraction unit 333 is “0” (the transfer notification included in the creditor certification information (T)). It is determined whether or not the obligor device 100 is requested to update the creditor by checking the frequency F (for example, reaching the frequency “5”).

  When it is confirmed that the value of the hop count H is “0” (when the arrival at the transfer notification frequency F can be confirmed), the update request determination unit 334 sends the creditor device 100 a creditor. The update request message transmission unit 335 is requested to transmit a bond information change request message. On the other hand, when it is not possible to confirm that the value of the hop number H is “0” (when it is not possible to confirm the arrival at the transfer notification frequency F), the update request determination unit 334 causes the hop number subtraction unit 333. The creditor certification information storage unit 337 is requested to store the creditor certification information (T) from which the value of the hop number H is subtracted.

  The update request message transmission unit 335 is a processing unit that transmits a bond information change request message for requesting the creditor device 100 to update the creditor.

Specifically, when the update request determining unit 334 requests the obligor device 100 to transmit a bond information change request message to the obligor device 100, the update request message transmitting unit 335 first generates an arbitrary random number (R3). Generate. Then, the update request message transmission unit 335 sends a signature SIG ₃ (T, R3) to the debtor device 100 using the creditor certification information (T), an arbitrarily generated random number (R3), and a secret key (Sk3). Send a claim information change request message containing.

  The update request response message receiving unit 336 is a processing unit that receives a bond information change request response message from the debtor device 100.

Specifically, the update request response message receiving unit 336 sends a bond information change request response message including the creditor certification information (T), the random number (R3), and the signature SIG ₃ (T, R3) from the debtor device 100. When received, the signature SIG ₃ (T, R3) is verified using the public key (Pk3) to confirm that the bond information change request response message has not been tampered with.

  When it can be confirmed that the bond information change request response message has not been tampered with, the update request response message reception unit 336 stores the creditor certification information (T) included in the bond information change request response message. The creditor certification information storage unit 337 is requested.

  The creditor certification information storage unit 337 is a processing unit that stores creditor certification information (T) in the storage unit 320.

  Specifically, the creditor certification information storage unit 337 is requested from the update request determination unit 334 to store the creditor certification information (T) obtained by subtracting the hop number H from the hop number subtraction unit 333. The creditor certification information (T) is stored in the storage unit 320.

  Further, when the creditor certification information storage unit 337 is requested by the update request response message receiving unit 336 to store the creditor certification information (T) included in the credit information change request response message, the creditor certification information is received. (T) is stored in the storage unit 320.

  The debtor device 100, the claim management device 200, and the claim management device 300 are known personal computers, workstations, mobile phones, PHS terminals, mobile communication terminals, PDAs, IC cards, RFIDs, automatic teller machines, etc. This information processing apparatus can be realized by mounting the above-described functions, and a magnetic medium such as a hard disk is used as a storage unit provided in the debtor apparatus 100, the bond management apparatus 200, and the bond management apparatus 300, respectively. It is also possible to mount a nonvolatile storage medium such as a flash memory.

[Processing by Claim Management System (Example 1)]
Then, the process by the credit management system based on Example 1 is demonstrated using FIG. 8 and FIG. FIG. 8 is a diagram illustrating a flow of processing by the bond management system according to the first embodiment. FIG. 9 is a diagram illustrating a processing outline of the credit management system according to the first embodiment.

As shown in FIG. 8, the receivable management device 300 includes a receivable ID (eg, XID), a creditor ID (UID2), a device address (A2), an arbitrarily generated random number (R1), a secret A transfer request message including the signature SIG ₂ (XID, UID2, A2, R1) with the key (Sk2) is transmitted to the bond management apparatus 200 (see step S801, for example, (2) or (13) in FIG. 9).

Upon receipt of the transfer request message from the bond management device 300 (step S802), the bond management device 200 uses the public key (Pk2) to obtain the signature SIG ₂ (XID, UID2, A2, R1) included in the transfer request message. It verifies and confirms that the transfer request message has not been falsified (for example, see (3) or (14) in FIG. 9).

  If it can be confirmed that the transfer request message has not been tampered with, the bond management device 200 records the device address (A2) included in the transfer request message as the destination of the creditor certification information (for example, FIG. 9). (See (4) or (15)).

  Next, the claim management apparatus 200 reads creditor certification information corresponding to the claim ID (XID) included in the assignment request message from the storage unit 220, and assigns the creditor ID in the read creditor certification information to the assignment request. Update to the creditor ID included in the message (update from UID1 to UID2) (for example, see (5) or (16) in FIG. 9).

  Upon completion of the update of the creditor ID, the claim management apparatus 200 invalidates the record corresponding to the claim ID (XID) included in the assignment request message in the storage unit 220 (step S803 in FIG. 8, for example, FIG. 9). (Refer to (6) or (17)).

The credit management device 200 includes a creditor certification information (T) with an updated creditor ID and a signature SIG ₁ (T, R1) with a secret key (Sk1), and a transfer message for notifying the transfer of the credit, The device address (A2) recorded by the transfer request message receiving unit 231 is transmitted as a destination (step S804, for example, refer to (7) or (18) in FIG. 9).

Upon receipt of the transfer message from the bond management device 200 (step S805), the bond management device 300 verifies the signature SIG ₁ (T, R1) included in the transfer message using the public key (Pk1), and the transfer message is If it is confirmed that the message has not been tampered with and that the transfer message has not been tampered with, the signature SIG ₀ (XID, UID0, F) is verified, and the creator of the creditor certification information (T) is the debtor (UID0) of the debtor device 100, and the creditor certification information (T) is transferred to the credit management device 200. It is confirmed whether or not it corresponds to the desired bond ID (XID) (see step S806, for example, (8) or (19) in FIG. 9).

  The credit management device 300 has created the creditor certification information (T) from the debtor device 100 (UID0), and the creditor certification information (T) has requested transfer to the credit management device 200. When the creditor certification information verification unit 332 confirms that the creditor ID (XID) corresponds to the creditor ID (XID), “1” is subtracted from the value of the hop count H included in the creditor certification information (T) ( Step S807, for example, see (9) or (20) in FIG.

  The credit management device 300 confirms whether or not the value of the subtracted hop count H is “0” (reach the transfer notification frequency F (eg, “5”) included in the creditor certification information (T)). In step S808, for example, refer to (10) or (21) in FIG. 9).

When it is confirmed that the value of the number of hops H is “0” (when the arrival of the transfer notification frequency F can be confirmed), the credit management device 300 sends the creditor device 100 to the creditor device 100. Based on the creditor certification information (T), an arbitrarily generated random number (R3), and a secret key (Sk3) in order to determine that an update is required and to request the creditor device 100 to update the creditor. A bond information change request message including the signature SIG ₃ (T, R3) is transmitted (see step S809, for example, (23) in FIG. 9).

The obligor apparatus 100 has a signature SIG ₃ (T, T), a creditor certification information (T), a random number (R3) arbitrarily generated by the bond management apparatus 300, and a private key (Sk3) managed by the bond management apparatus 300. When a claim information change request message including R3) is received from the claim management apparatus 300 (step S810), the signature SIG ₃ (T, R3) is verified using the public key (Pk3), and the claim information change request message is falsified. In the case where it is confirmed that the receivable information change request message has not been tampered with, it is possible to use the public key (Pk0) to sign the signature SIG ₀ ( XID, UID0, F) are verified and it is confirmed that the creditor certification information (T) included in the bond information change request message is self. (Step S811, for example, see (24) in FIG. 9).

  The debtor apparatus 100 is stored in the storage unit 120 when it can be confirmed that the creditor certification information (T) included in the claim information change request message received from the claim management apparatus 300 is self. The creditor ID in the credit information (X) that uniquely corresponds to the creditor certification information (T) included in the credit information change request message among the creditor IDs of the credit information 121 that has been received, and the credit information change request message (“UID1” → “UID2”) (see step S812, for example, (25) in FIG. 9), and the value of the number of hops H is changed. Reset to the same value as the transfer notification frequency F (“0” → “5”) (step S813, for example, refer to (26) in FIG. 9).

Then, the debtor apparatus 100 includes creditor certification information (T) including at least the updated creditor ID (“UID2”) and the reset hop count H (“5”), an arbitrary random number (R3), And a claim information change request response message including the signature SIG ₃ (T, R3) is transmitted to the claim management apparatus 300 that is the sender of the claim information change request message (step S814, for example, ( 27)).

When the bond management device 300 receives a bond information change request response message including the creditor certification information (T), the random number (R3), and the signature SIG ₃ (T, R3) from the debtor device 100 (step S815), it is disclosed. The signature SIG ₃ (T, R3) is verified using the key (Pk3), and it is confirmed that the bond information change request response message has not been tampered (for example, see (28) in FIG. 9). If it can be confirmed that the request response message has not been tampered with, the creditor certification information (T) included in the claim information change request response message is stored in the storage unit 320 (step S816, for example, ( 29)).

[Effects of Example 1]
As described above, according to the first embodiment, the receivable management device 300 transmits a transfer request message for requesting transfer of receivables to the receivable management device 200 that manages the receivables desired to be transferred. Transfer notification frequency F, which is information uniquely associated with the claim information about the claim held by the creditor device 100 and represents the frequency of requesting the creditor to update the creditor from the new creditor, and For notifying creditor assignment from the creditor management apparatus 200 which is the management source of the desired debt to be transferred, together with creditor certification information (T) including at least the number of hops H subtracted every time a claim is transferred between claims management apparatuses The creditor certification information (T) received together with the transfer message was created by the debtor of the claim to be transferred on condition that the transfer message was received and the received transfer message was not falsified. The creditor proof information (T) is created by the debtor by verifying whether it is uniquely associated with the claim information (X) of the transferable claim. If it is verified that the information is uniquely associated with the claim information (X) about the claim to be transferred, the creditor certification information (T) received together with the transfer message The value of the included hop count H is subtracted by “1”, and whether or not the subtracted hop count H has reached the transfer notification frequency F included in the creditor certification information (T) received together with the transfer message. If it is determined that the value of the hop count H has reached the transfer notification frequency F, a debt information change request message for requesting the creditor to be updated is sent to the debtor device 100. Since it is transmitted, the characteristics of the creditor by the debtor Cost, and with the claim assignment the cost of updating request notification of Electronic Monetary Information imposed on creditors, it can be adjusted according to the purpose of the Electronic Monetary distribution.

  Further, according to the first embodiment, it is determined whether or not it is necessary to transmit a credit information change request message for requesting creditor update by a simple method of subtracting the number of hops. Can be controlled to transmit.

  Further, according to the first embodiment, the receivable management apparatus 300 updates the request message including the creditor certification information received together with the transfer message in order to request the creditor to update when the transfer message has not been tampered with. Is transmitted to the debtor device 100, and the debtor device 100 identifies the creditor ID that identifies the creditor that it manages, the creditor ID that identifies the creditor, the debtor ID that identifies the debtor, and the claimant A transfer that represents the frequency of requesting renewal of creditors for new creditors by generating and storing receivable information (X) containing information related to claims and debts concluded between creditors and debtors Set up notification frequency F, uniquely associate with credit information (X), creditor ID to identify creditor, debtor ID to identify debtor, and creditor certification including transfer notification frequency F Generate information (T) and manage debts Is issued to the device 200, and when a receivable information change request message is received from the receivable management device 300, the receivable information change request message is received on the condition that the receivable information change request message has not been tampered with. Verifies whether or not the creditor certification information (T) included in the credit card is created by itself, and the creditor certification information (T) included in the credit information change request message received from the credit management device 300 is If verified as self, the creditor ID in the credit information (X) corresponding to the creditor certification information (T) included in the credit information change request message in the creditor ID of the credit information Is updated to a new creditor that is the sender of the claim information change request message, and the value of the hop count H is reset to the same value as the transfer notification frequency F, and the claim management device that is the sender of the claim information change request message 300 Since the creditor information change request response message including the creditor certification information (T) including at least the new creditor ID and the reset hop count is sent, the creditor's identity is ensured on the debtor side. Recognizing this, it is possible for the debtor to independently set an opportunity for grasping the change of the creditor.

  Further, according to the first embodiment, the credit management device 300, when it is not determined that the value of the hop count H has reached the transfer notification frequency F, the subtracted hop count H and the transfer notification. When the creditor certification information (T) including the frequency F and the new creditor's own identifier is stored, and it is determined that the value of the hop count H has reached the transfer notification frequency F Since the creditor certification information (T) received from the debtor device 100 as a claim information change request response message is stored, even if the credit is circulated between credit management devices, It is possible to maintain a function to reduce the cost required for notification of update of electronic bond information imposed on a person.

  Now, Example 1 has been described as an embodiment of the claim management system according to the present invention, but the present invention may be implemented in various different forms other than the above-described example. Therefore, other embodiments for carrying out the present invention will be described below.

(1) Debt information deletion after fulfillment of debt In the first embodiment, when a debt settlement request presenting creditor certification information is received from the credit management device, the debtor device is included in the creditor certification information. The debt settlement date in the debt information corresponding to the creditor identifier is confirmed, and if the debt settlement date is exceeded, the debt is fulfilled, and the debt that has been fulfilled from the stored debt information Information may be deleted. In other words, it is possible to fulfill and debts to creditors whose identity is surely recognized.

(2) Setting of creditors for which a creditor renewal request is required In addition to the transfer notification frequency F, the creditor device requests creditor renewal of the creditors in accordance with the transfer notification frequency F in the first embodiment. The creditor management device that has set the creditor that is required to send the change request message and receives the transfer message, if the creditor that is required to send the claim information change request message corresponds to itself, the debtor device The creditor may be requested to update the creditor. That is, it is possible for the debtor to arbitrarily select a creditor for whom transmission of a claim information change request message is indispensable with the transfer of the claim.

(3) Setting of the reference date that requires the creditor's renewal request In addition to the transfer notification frequency F, the obligor device sends a new creditor's creditor's If you set a reference date (for example, 5 days before the debt settlement date) that requires transmission of the receivable information change request message requesting renewal, and the receivable management device that received the transfer message, the transfer date of the transfer message will be the reference date If it is after that, the creditor device may be requested to update the creditor. That is, it is possible for the debtor side to arbitrarily set a reference date on which a claim information change request message needs to be transmitted along with the assignment of the claim.

(4) Set transfer notification frequency for each user who can be a transferee of receivables In the first embodiment, the obligor apparatus transfers each user identifier that identifies the user of the receivable management apparatus that can be the transferee of the receivables. The receivable management apparatus that sets the notification frequency F and receives the transfer message may determine whether or not the number of receivable transfers has reached the transfer notification frequency associated with its own user identifier. That is, it is possible for the debtor to manage the claim according to the creditor.

(5) Each transfer notification frequency is set in association with the number of days from the transfer message reception date to the debt settlement date. In the first embodiment, from the transfer message reception date to the debt settlement date included in the claim information. Each transfer notification frequency F is associated with the number of days (for example, if the debt settlement date is 5 days from the reception date, the frequency is set from “5” to “4”, and the debt settlement date is 4 days from the reception date. In some cases, the frequency is set from “4” to “3”, etc., and the receivable management device that receives the transfer notification has the number of receivable transfers as the number of days from the date of receipt of the receivable transfer message to the debt settlement date It may be determined whether or not the transfer notification frequency associated with is reached. That is, it is possible for the debtor to manage the receivable according to the debt settlement date.

(6) Set the update count condition for each user who can be the transferee of the receivable In addition, in the above embodiment, the renewal transfer count condition of the receivable transfer count updated with the transfer of the receivable (for example, The number of additions, etc.) may be changed for each creditor on the debtor side. As a result, the debtor can speed up the transmission of the update request notification from the creditor according to the transferee of the credit.

(7) An update count condition is set in association with the number of days from the date of receipt of the transfer message to the date of settlement of the debt. Further, according to the present invention, the update count condition of the number of receivable transfers updated with the transfer of the claim (for example, The number of times the receivables are transferred at the current time may be changed according to the number of days until the debt settlement date. As a result, the debtor can speed up the transmission of the update request notification from the creditor according to the number of days from the transfer date of the claim to the debt settlement date.

(8) Inheritance of creditor certification information before split of credit In addition, in Example 1 above, each creditor certification information divided according to the split of credit was included in the creditor certification information before split You may make it include the transfer notification frequency F and the hop number H, respectively. That is, it is possible to maintain the function of transmitting a bond information change request message from a new creditor without requiring special processing in accordance with the split of the bond.

(9) Counting the number of receivables transfer In the above embodiment, the value of the hop number H is calculated by subtracting the hop number H, which is set to the same value as the transfer notification frequency F, as the initial value every time the receivable transfer is performed. A case has been described in which it is determined whether or not the creditor device is requested to update the creditor by determining whether or not it is “0”. However, the present invention is not limited to this, and separately from the transfer notification frequency F, the number of times of receivable transfer is counted, and the number of transfer of receivables is updated every time a transfer notification is received. In comparison, it is determined whether or not the obligor device is requested to update the creditor by determining whether or not the number of receivables counted at this time exceeds the transfer notification frequency F. Also good.

  Also, in the debtor device, for example, when a multiple of 5 is set as the transfer notification frequency F, when the update request is received from the debtor device, the number of receivable transfers is updated with the same value as the current time. It may be. When the transfer notification frequency F is set as a multiple of 5, the number of receivable transfers needs to be gradually increased even after an update request, and this is to be addressed.

(10) System Configuration etc. The configuration of the claim management system shown in FIG. 2 is functionally conceptual. For example, as shown in FIG. It does not necessarily need to be physically configured as illustrated.

  Also, each component of the debtor device 100 shown in FIG. 3, the claim management device 200 shown in FIG. 5, and the claim management device 300 shown in FIG. 7 is functionally conceptual, and is not necessarily physically configured as shown. You don't need to be. That is, the specific form of distribution / integration of the devices shown in FIGS. 3, 5 and 7 is not limited to the illustrated one. For example, the update processing unit 133 and the response message transmission unit 134 shown in FIG. The transfer request message receiving unit 231 and the creditor proof information deleting unit 232 shown in FIG. 5 are integrated, and the creditor proof information verifying unit 332 and the hop number subtracting unit 333 shown in FIG. A part can be configured to be functionally or physically distributed / integrated in arbitrary units according to various loads or usage conditions.

  When the administrator of the claim management apparatus 200 shown in FIG. 5 desires to assign a claim, it has the same function as the claim management apparatus 300 described in the first embodiment, and the claim management shown in FIG. When the administrator of the apparatus 300 becomes the current owner of the bond, it has the same function as the bond management apparatus 200 described in the first embodiment.

(11) Claim Management Program In addition, the various processes (see FIGS. 8 and 9) of the claim management apparatus 300 described in the first embodiment are executed by using a computer system such as a personal computer or a workstation. It can be realized by executing with. Therefore, in the following, an example of a computer that executes a bond management program having the same function as the bond management apparatus 300 described in the first embodiment will be described with reference to FIG. FIG. 10 is a diagram illustrating a computer that executes a bond management program.

  As shown in the figure, a computer 400 as a bond management device is configured by connecting an input unit 410, an output unit 420, a communication control I / F unit 430, an HDD 440, a RAM 450, and a CPU 460 through a bus 500.

  Here, the input unit 410 receives input of various data from the user. The output unit 420 displays various information. The communication control I / F unit 430 controls exchange of various information. The HDD 440 stores information necessary for the CPU 460 to execute various processes. The RAM 450 temporarily stores various information. The CPU 460 executes various arithmetic processes.

  As shown in FIG. 10, the HDD 440 stores in advance a bond management program 441 that exhibits the same functions as the processing units of the bond management apparatus 300 shown in the first embodiment, and bond management data 442 in advance. It is remembered. Note that the bond management program 441 may be appropriately distributed and stored in a storage unit of another computer that is communicably connected via a network.

  Then, the CPU 460 reads this bond management program 441 from the HDD 440 and expands it in the RAM 450, whereby the bond management program 441 functions as a bond management process 451 as shown in FIG. Then, the bond management process 451 reads the bond management data 442 and the like from the HDD 440, expands it in the area allocated to itself in the RAM 450, and executes various processes based on the expanded data and the like. The bond management process 451 includes a control unit 330 (transfer request message transmission unit 331, creditor certification information verification unit 332, hop count subtraction unit 333, update request determination unit, and the like of the bond management apparatus 300 illustrated in FIG. 334, an update request message transmission unit 335, an update request response message reception unit 336, a creditor certification information storage unit 337), and the like.

  Note that the above-described bond management program 441 is not necessarily stored in the HDD 440 from the beginning. For example, a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, an IC inserted into the computer 400, and the like. Each program is stored in a “portable physical medium” such as a card, and “another computer (or server)” connected to the computer 400 via a public line, the Internet, a LAN, a WAN, or the like. The computer 400 may read and execute each program from these.

  Further, as with a computer that executes a program having the same function as the above-described bond management device 300, various processes (see FIGS. 8 and 9) of the debtor device 100 described in the first embodiment are as follows. This can be realized by executing a program prepared in advance on a computer system such as a personal computer or a workstation.

(12) Receivable Management Method The following receivable management method is realized by the receivable management system described in the first embodiment.

  That is, the claim management device 300 is information uniquely associated with the claim information (X) about the claim held by the debtor device 100, and the creditor updates the creditor from the new creditor to the debtor. It is the origin of the receivable wished to be transferred together with the creditor certification information (T) including at least the transfer notification frequency F representing the requested frequency and the number of hops H subtracted each time the bond is transferred between claims management devices. A receivable assignment acceptance step for receiving a assignment message for notifying the assignment of a receivable from the claim management apparatus 200 (see, for example, step S805 in FIG. 8), and the assignment message received by the claim assignment acceptance step is not falsified. On the condition that the creditor certification information (T) received together with the transfer message is verified by the debtor of the claim to be transferred. A creditor proof information verification step for verifying whether or not the credit information (X) for the transfer-requested credit is uniquely associated (see, for example, step S806 in FIG. 8), the creditor proof information When it is verified by the verification step that the creditor certification information (T) is created by the debtor and is uniquely associated with the claim information about the transferable claim, A credit transfer number update step of subtracting the hop number H included in the creditor certification information (T) received together with the transfer message by the credit transfer acceptance step (see, for example, step S807 in FIG. 8), and the credit transfer number update step Whether or not the hop count H subtracted by (1) has reached the transfer notification frequency F included in the creditor certification information (T) received together with the transfer message. A fixed credit transfer number determination step (see, for example, step S808 in FIG. 8), and when the transfer number determination step determines that the hop number H has reached the transfer notification frequency F, A creditor management method including a creditor update requesting step for transmitting a creditor information change request message for requesting an update to the debtor device 100 (see, for example, step S809 in FIG. 8) is realized.

  As described above, the claim management system, the claim management method, and the claim management program according to the present invention are useful for managing the claims exchanged between the claim management apparatuses, and in particular, the debtors are identified by the debtors. In addition to facilitating this, it is suitable for reducing the cost required for notification of an update request for electronic bond information imposed on a creditor when a bond is transferred.

It is a figure for demonstrating the outline | summary and the characteristic of the credit management system which concern on Example 1. FIG. It is a block diagram which shows the structure of the credit management system which concerns on Example 1. FIG. It is a block diagram which shows the structure of the debtor apparatus which concerns on Example 1. FIG. It is a figure which shows the structural example of the bond information which concerns on Example 1. FIG. It is a block diagram which shows the structure of the credit management apparatus managed by the current owner of the credit which concerns on Example 1. FIG. It is a figure which shows the structural example of the creditor certification | authentication information which concerns on Example 1. FIG. It is a block diagram which shows the structure of the credit management apparatus managed by the assignee of the credit which concerns on Example 1. FIG. It is a figure which shows the flow of the process by the credit management system which concerns on Example 1. FIG. It is a figure which shows the process outline | summary of the credit management system which concerns on Example 1. FIG. It is a figure which shows the computer which performs a debt management program.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network 100 Obligor apparatus 110 Communication part 120 Storage part 130 Control part 200 Claim management apparatus 210 Communication part 220 Storage part 230 Control part 300 Claim management apparatus 310 Communication part 320 Storage part 330 Control part 400 Computer (bond management apparatus)
410 Input unit 420 Output unit 430 Communication control I / F unit 440 HDD (Hard Disk Drive)
441 Claim Management Program 442 Claim Management Data 450 RAM (Random Access Memory)
451 Bond Management Process 460 CPU (Central Processing Unit)
500 buses

Claims (13)

A debt management system configured to include a debtor device managed by a debtor and a credit management device managed by a creditor, and managing a claim exchanged between the credit management devices,
The claim management device
Creditor renewal request frequency, which is information uniquely associated with the receivable information about the receivable held by the obligor device, and represents the frequency of requesting renewal of the creditor from the new creditor , And a creditor for notifying the transfer of credit from the credit management device that is the management source of the receivables desired to be transferred, together with creditor certification information that includes at least the number of credit transfers assigned each time a claim is transferred between credit management devices A receivable transfer acceptance means for receiving a transfer message;
Whether the creditor certification information received together with the claim assignment message was created by the debtor of the claim to be assigned, provided that the claim assignment message received by the claim assignment acceptance means has not been tampered with. A creditor certification information verification means for verifying whether or not the credit card information is uniquely associated with the claim information about the transferable claim,
When it is verified by the creditor proof information verification means that the creditor proof information is created by the debtor and is uniquely associated with the credit information about the claim to be transferred Receivable assignment number updating means for updating the receivable assignment number included in the creditor certification information received together with the receivable assignment message by the receivable assignment accepting means;
A receivable assignment number determining means for determining whether the receivable assignment number updated by the receivable assignment number updating means has reached a creditor renewal request frequency included in the creditor certification information received together with the receivable assignment message; ,
If the number of receivable assignments is determined to have reached the creditor renewal request frequency by the receivable assignment number determination means, an update request message for requesting renewal of the creditor is transmitted to the debtor device. Creditor renewal request means to
If it is not determined by the credit transfer number determination means that the number of credit transfer has reached the creditor update request frequency, the credit transfer number updated by the credit transfer number update means and the creditor update request When the creditor certification information including the frequency and the self-identifier of the new creditor is stored, and it is determined by the credit transfer number determination means that the number of credit transfer reaches the creditor renewal request frequency Creditor certification information storage means for storing creditor certification information included in the update request response message received from the debtor device,
With
The debtor device is:
If an update request message requesting creditor renewal is received from the credit management device, the creator of the creditor certification information included in the update request message is self-provided on the condition that the update request message has not been tampered with. Update request verification means for verifying whether or not
If the creditor certification information included in the update request message received from the credit management device is verified by the update request verification means as the source of the creditor certification information included in the update request message, the creditor certification information included in the update request message Updating the creditor identifier in the corresponding credit information to the creditor identifier of the new creditor that is the source of the update request message, and updating processing means for updating the number of times of credit transfer;
Update for transmitting an update request response message including creditor certification information including at least the creditor identifier updated by the update processing means and the number of times of credit transfer to the credit management device that is the transmission source of the update request message Request response means;
A debt management system characterized by comprising: The debtor device is:
Credit identifier that identifies the credits that it manages, creditor identifier that identifies the creditor, debtor identifier that identifies the debtor, and information related to the claims and debts concluded between the creditor and the debtor A bond information generating means for generating the included bond information;
Claim information storage means for storing the claim information generated by the claim information generation means;
A creditor renewal request frequency setting means for setting a creditor renewal request frequency indicating a frequency of requesting a new creditor to renew the creditor;
A creditor identifier that uniquely identifies a creditor, a debtor identifier that identifies a debtor, and a creditor update request frequency setting means that is uniquely associated with the claim information generated by the claim information generation means. Creditor certification information generating means for generating creditor certification information including the frequency of creditor renewal request,
Creditor certification information issuing means for issuing creditor certification information generated by the creditor certification information generating means to the credit management device;
The claim management system according to claim 1, further comprising:   When the debtor device receives a debt settlement request presenting the creditor certification information from the credit management device, the debtor device confirms the debt settlement date in the credit information corresponding to the creditor identifier included in the creditor certification information. In addition, when the debt settlement date has been exceeded, the debt fulfillment is performed, and the debt fulfillment means for deleting the debt information fulfilled from the debt information stored in the claim information storage means is further provided The claim management system according to claim 2. The creditor renewal request frequency setting means, together with the creditor renewal request frequency, provides a notification required creditor identifier that identifies a creditor that is required to send an update request message requesting the debtor to renew the creditor. Set,
The creditor proof information issuing means issues a notice required creditor identifier set by the creditor update request frequency setting means together with the creditor proof information to the credit management device,
The credit transfer acceptance means receives creditor certification information and a notification mandatory creditor identifier set by the creditor marching request frequency setting means together with a credit transfer message,
The creditor renewal request means assigns a claim to the debtor device when the identifier of the creditor to which the creditor is transferred and becomes a new creditor and the notification mandatory creditor identifier received together with the claim transfer message match. 3. The claim management system according to claim 2, wherein an update request message for requesting update of a person is transmitted. The creditor renewal request frequency setting means sets a reference date when an update request message for requesting renewal of a creditor is required from a new creditor to a debtor together with the creditor renewal request frequency. ,
The creditor certification information issuing means issues a reference date set by the creditor update request frequency setting means together with the creditor certification information to the credit management device.
The receivable assignment acceptance means receives the creditor certification information and a reference date that requires transmission of an update request message requesting renewal of the creditor together with the receivable assignment message,
The creditor update request means, if the date of receipt of the credit transfer message is after the reference date received together with the credit transfer message, an update request message requesting the creditor device to update the creditor. The credit management system according to claim 2, wherein the system is transmitted. The creditor update request frequency setting means sets a creditor update request frequency for each user identifier that identifies a user of a credit management device that can be a transferee of a credit,
The creditor certification information issuing means issues creditor certification information and the creditor update request frequency set for each user identifier by the creditor update request frequency setting means to the credit management device,
The credit transfer acceptance means receives creditor certification information and the creditor update request frequency set for each user identifier by the creditor update request frequency setting means together with the credit transfer message,
The creditor renewal request means is configured such that the number of receivable transfers received together with the receivable transfer message is a creditor renewal request frequency associated with the user identifier of the creditor renewal request frequency received together with the receivable transfer message. 3. The claim management system according to claim 2, wherein it is determined whether or not it has reached. The creditor update request frequency setting means sets each creditor update request frequency in association with the number of days from the date of receipt of the credit transfer message to the debt settlement date included in the claim information,
The creditor proof information issuing means associates each creditor renewal request frequency set by the creditor renewal request frequency setting means in association with the number of days from the date of receipt of the creditor proof information and the credit transfer message to the debt settlement date. Issued to the debt management device,
The credit transfer assignment accepting means assigns each creditor renewal request frequency set by the creditor renewal request frequency setting means in association with the creditor certification information and the number of days from the receipt date of the credit transfer message to the debt settlement date. Received with the message,
The creditor renewal request means is configured such that the number of receivable transfers received together with the receivable transfer message is the number of days from the date of receipt of the receivable transfer message to the date of settlement of the debt in the creditor renewal request frequency received together with the receivable transfer message. 3. The claim management system according to claim 2, wherein it is determined whether or not the associated creditor update request frequency has been reached. The creditor update request frequency setting means sets an update count condition of the credit transfer count for each user identifier that identifies a user of a credit management device that can be a transferee of a claim,
The creditor proof information issuing means transmits the creditor proof information and the update number condition set for each user identifier by the creditor update request frequency setting means to the credit management device,
The receivable assignment accepting unit receives the renewal number condition set for each user identifier by the creditor certification information and the creditor renewal request frequency setting unit together with a receivable assignment message,
3. The claim management system according to claim 2, wherein the claim transfer count updating means updates the claim transfer count received together with the claim transfer message in accordance with the update count conditions received together with the claim transfer message. . The creditor update request frequency setting means sets an update count condition for the number of credit transfers in association with the number of days from the date of receipt of the credit transfer message to the debt settlement date included in the claim information,
The creditor proof information issuing means issues creditor certification information and the update number condition set by the creditor update request frequency setting means to a credit management device,
The credit transfer acceptance means receives creditor certification information and each creditor update request frequency set by the creditor update request frequency setting means together with a credit transfer message,
3. The claim management system according to claim 2, wherein the claim transfer count updating means updates the claim transfer count received together with the claim transfer message in accordance with the update count conditions received together with the claim transfer message. .   The creditor certification information includes that each creditor certification information divided according to the split of credits includes the creditor renewal request frequency and the number of times of credit transfer included in the creditor certification information before the split. The claim management system according to claim 1, wherein: In a claim management system comprising a debtor device managed by a debtor and a claim management device managed by a creditor, a claim management method for managing claims exchanged between claim management devices ,
The claim management device
Creditor renewal request frequency, which is information uniquely associated with the receivable information about the receivable held by the obligor device, and represents the frequency of requesting renewal of the creditor from the new creditor , And a creditor for notifying the transfer of credit from the credit management device that is the management source of the receivables desired to be transferred, together with creditor certification information that includes at least the number of credit transfers assigned each time a claim is transferred between credit management devices A receivable transfer acceptance step for receiving the transfer message;
Whether the creditor certification information received together with the credit transfer message was created by the debtor of the credit to be transferred on condition that the credit transfer message received in the credit transfer acceptance step has not been falsified And a creditor certification information verification step for verifying whether or not the credit information is uniquely associated with the claim information about the transfer-requested claim,
When it is verified by the creditor certification information verification step that the creditor certification information is created by the debtor and is uniquely associated with the credit information about the claim to be transferred , A receivable assignment number update step for updating the receivable assignment number included in the creditor certification information received together with the receivable assignment message by the receivable assignment acceptance step;
Debt transfer count determination step for determining whether the credit transfer count updated in the credit transfer count update step has reached the creditor update request frequency included in the creditor certification information received together with the credit transfer message; ,
If it is determined by the credit transfer count determination step that the credit transfer count has reached the creditor renewal request frequency, an update request message for requesting creditor update is transmitted to the debtor device. A creditor renewal request step,
If it is not determined that the number of receivable assignments has reached the creditor renewal request frequency in the receivable assignment number determination step, the receivable assignment number updated by the receivable assignment number renewal step and the creditor renewal request When the creditor certification information including the frequency and the self-identifier of the new creditor is stored, and it is determined by the credit transfer number determination step that the credit transfer number has reached the creditor renewal request frequency Creditor certification information storage step for storing creditor certification information included in the update request response message received from the debtor device,
Including
The debtor device is:
If an update request message requesting creditor renewal is received from the credit management device, the creator of the creditor certification information included in the update request message is self-provided on the condition that the update request message has not been tampered with. An update request verification step for verifying whether or not
If the creditor certification information included in the update request message received from the credit management device is verified by the update request verification step as the creditor certification information included in the update request message, the creditor certification information included in the update request message An update processing step of updating the creditor identifier in the corresponding credit information to the creditor identifier of the new creditor that is the transmission source of the update request message, and updating the number of times of credit transfer;
Update for transmitting an update request response message including creditor certification information including at least the creditor identifier and the number of times of credit transfer updated by the update processing step to the claim management device that is the transmission source of the update request message A request response step;
The claim management method characterized by including. In a claim management system comprising a debtor device managed by a debtor and a claim management device managed by a creditor, processing related to the management of claims exchanged between the claim management devices is performed as a claim management device. A debt management program to be executed by a computer
In the computer as the bond management device,
Creditor renewal request frequency, which is information uniquely associated with the receivable information about the receivable held by the obligor device, and represents the frequency of requesting renewal of the creditor from the new creditor , And a creditor for notifying the transfer of credit from the credit management device that is the management source of the receivables desired to be transferred, together with creditor certification information that includes at least the number of credit transfers assigned each time a claim is transferred between credit management devices Receivable assignment acceptance procedure for receiving the assignment message,
Whether the creditor certification information received together with the claim assignment message was created by the debtor of the claim to be transferred on condition that the claim assignment message received by the procedure for accepting claims is not falsified. A creditor certification information verification procedure for verifying whether the credit card information is uniquely associated with the claim information for the transferable claim,
When it is verified that the creditor certification information is created by the debtor by the creditor certification information verification procedure and is uniquely associated with the credit information about the claim to be transferred , A receivable assignment number update procedure for updating the receivable assignment number included in the creditor certification information received together with the receivable assignment message by the receivable assignment acceptance procedure;
Claim transfer count determination procedure for determining whether the credit transfer count updated by the credit transfer count update procedure has reached the creditor update request frequency included in the creditor certification information received together with the claim transfer message; ,
If it is determined that the number of receivables has reached the creditor renewal request frequency according to the procedure for determining the number of receivables transferred, an update request message for requesting renewal of the creditor is transmitted to the debtor device. A creditor renewal request procedure
If it is not determined that the number of receivable assignments has reached the creditor renewal request frequency according to the receivable assignment number judging procedure, the receivable assignment number renewed by the receivable assignment number renewal means and the creditor renewal request The creditor certification information including the frequency and the self-identifier of the new creditor is stored in the storage unit, and it is determined that the number of claims transferred has reached the creditor renewal request frequency according to the procedure for determining the number of claims assigned. If the creditor certification information is stored in the storage unit creditor certification information included in the update request response message received from the debtor device,
A loan management program characterized by In a debt management system comprising a debtor device managed by a debtor and a credit management device managed by a creditor, the processing related to the management of the claims exchanged between the credit management devices as the debtor device A debt management program to be executed by a computer
In the computer as the debtor device,
If an update request message requesting creditor renewal is received from the credit management device, the creator of the creditor certification information included in the update request message is self-provided on the condition that the update request message has not been tampered with. Update request verification procedure for verifying whether or not
If the creditor certification information included in the update request message received from the credit management device is verified by the update request verification procedure to be the creditor certification information included in the update request message, the creditor certification information included in the update request message Update the creditor identifier in the corresponding credit information to the creditor identifier of the new creditor who is the sender of the update request message, and update processing procedure for updating the number of credits transferred,
Update for transmitting an update request response message including creditor certification information including at least the creditor identifier updated by the update processing procedure and the number of times of credit transfer to the credit management device that is the transmission source of the update request message Request response procedure;
A loan management program characterized by

Images