Movable property collateral management device, movable property collateral management system, and movable property collateral management method

Abstract

To provide a personal property security management device, a personal property security management system and a personal property security management method which facilitate post-installation of a security management function in security management of a personal property, and integrate the security management of the personal property.SOLUTION: A personal property security management system has a plurality of device management servers 201-1 to 201-N, and one security management server 202. The security management server 202 registers a token for security management in association with each piece of personal property identification information and registers a financial institution ID for identifying a loan source in association with each piece of the personal property identification information, and if the personal property identification information received from the device management servers is not registered, newly issues a token for security registration and registers the newly registered token in association with the personal property identification information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a personal property collateral management device, a personal property collateral management system, and a personal property collateral management method. [Background technology]

[0002] Generally, one method of corporate financing is asset-backed financing, in which loans are secured by movable assets such as machinery and equipment owned by the company. In this way, financial institutions secure the movable assets as collateral and reduce the risk of non-recovery.

[0003] In this case, a system for managing the movable property that has been used as collateral is required, and for example, a method has been proposed for monitoring the movable property as collateral to detect any abnormalities in the movable property (Patent Document 1).Furthermore, a system has been proposed for supporting the business of movable property-secured loans, in which the status of the movable property is grasped and managed, and changes to the content of the collateral and the execution of security rights are indicated in real time for the movable property (Patent Document 2). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-38735 [Patent Document 2] Japanese Patent Application Laid-Open No. 2011-100291 Summary of the Invention [Problem to be solved by the invention]

[0005] In the above-mentioned Patent Documents 1 and 2, when trying to implement a security management function in a device management server, which is an existing IoT management service, there is a problem in that it is difficult to add the security management function retroactively.

[0006] Furthermore, if multiple IoT management services exist, there will be multiple device management servers to manage them, which means that financial institutions will not be able to centralize and use collateral management functions.

[0007] The present invention has been made in consideration of the above background, and aims to provide a movable property collateral management device, a movable property collateral management system, and a movable property collateral management method that allow for easy retrofitting of collateral management functions in the management of movable property collateral, and that enable centralized management of movable property collateral. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the above-mentioned objectives, one embodiment of the present invention is a movable property collateral management device that communicates with one or more movable property management devices that register movable property identification information specific to the movable property to be managed as collateral, and manages the movable property that is the subject of a loan from a lender, and is characterized by comprising: a collateral registration unit that links and registers the collateral registration information assigned to each movable property identification information; a collateral management unit that links and registers financial institution information that identifies the lender to each movable property identification information registered in the collateral registration unit; a collateral registration and issuance unit that receives the movable property identification information specific to the movable property from the movable property management device, and generates and issues new collateral registration information if the received movable property identification information does not exist in either the collateral registration unit or the collateral management unit; and a registration unit that links the received movable property identification information with the collateral registration information issued by the collateral registration and issuance unit and registers it in the collateral management unit.

[0009] Another embodiment of the present invention is a movable property collateral management system having one or more movable property management devices and a movable property collateral management device that manages the collateral of movable property that is the subject of loans from loan sources through communication with each movable property management device, wherein each movable property management device has a movable property management unit that registers movable property identification information specific to the movable property to be managed as collateral, and the movable property collateral management device has a collateral registration unit that registers collateral registration information assigned to each movable property identification information in association with the movable property identification information, a collateral management unit that registers financial institution information identifying the loan source in association with each movable property identification information registered in the collateral registration unit, a collateral registration and issuance unit that receives movable property identification information specific to the movable property to be registered in the movable property management unit from the movable property management device and generates and issues new collateral registration information if the received movable property identification information does not exist in either the collateral registration unit or the collateral management unit, and a registration unit that links the received movable property identification information with the collateral registration information issued by the collateral registration and issuance unit and registers it in the collateral management unit.

[0010] Furthermore, another embodiment of the present invention is a movable property collateral management method for a system having one or more movable property management devices and a movable property collateral management device that manages the collateral of movable property that is the subject of loans from loan sources by communicating with each movable property management device, wherein each movable property management device registers movable property identification information specific to the movable property to be collateral managed in a first memory, and the movable property collateral management device has a second memory that links and registers collateral registration information assigned to each movable property identification information, and links and registers financial institution information that identifies the loan source for each movable property identification information, and the movable property collateral management device includes a first step of receiving movable property identification information specific to the movable property to be registered in the first memory from the movable property management device, and generating and issuing new collateral registration information if the received movable property identification information does not exist in the second memory, and a second step of linking and registering the received movable property identification information with the collateral registration information issued in the first step in the second memory. [Effects of the Invention]

[0011] According to the present invention, it is easy to retrofit a security management function in security management of movable property, and it is possible to centralize security management of movable property. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is an explanatory diagram illustrating the mechanism of a personal property collateral management system according to one embodiment of the present invention. [Figure 2] 1 is a configuration diagram showing the hardware configuration of a personal property collateral management system according to one embodiment of the present invention. [Figure 3A] 1 is a block diagram showing the functional configuration of an equipment management server of a personal property security management system according to one embodiment of the present invention. [Figure 3B] 1 is a block diagram showing the functional configuration of a collateral management server of a personal property collateral management system according to one embodiment of the present invention. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of a table of a personal property collateral management system according to one embodiment of the present invention. [Figure 5] FIG. 1 is an explanatory diagram illustrating an example of a sequence related to collateral registration in a personal property collateral management system according to one embodiment of the present invention. [Figure 6A] 10 is a flowchart illustrating an example of operations related to security registration in a personal property security management system according to one embodiment of the present invention. [Figure 6B] 10 is a flowchart illustrating another example of the operation related to security registration in the personal property security management system according to one embodiment of the present invention. [Figure 7A] FIG. 1 is an explanatory diagram illustrating an example of a sequence related to collateral monitoring in a personal property collateral management system according to one embodiment of the present invention. [Figure 7B] FIG. 10 is an explanatory diagram illustrating another example of a sequence relating to collateral monitoring in a personal property collateral management system according to one embodiment of the present invention. [Figure 8] FIG. 1 is an explanatory diagram illustrating an example of a sequence relating to security preservation in a personal property security management system according to one embodiment of the present invention. [Figure 9]FIG. 10 is an explanatory diagram illustrating an example of a sequence for releasing a security in a personal property security management system according to one embodiment of the present invention. [Figure 10] FIG. 10 is an explanatory diagram illustrating an example of a sequence relating to collateral transfer in a personal property collateral management system according to one embodiment of the present invention. [Figure 11A] 10 is a flowchart illustrating an example of the operation related to the transfer of collateral in a personal property collateral management system according to one embodiment of the present invention. [Figure 11B] 10 is a flowchart illustrating another example of the operation related to the transfer of collateral in the personal property collateral management system according to one embodiment of the present invention. [Figure 12] FIG. 1 is an explanatory diagram illustrating an example of a sequence relating to the transfer of ownership in a personal property collateral management system according to one embodiment of the present invention. [Figure 13] 10 is a flowchart illustrating an example of the operation related to the transfer of ownership in a personal property collateral management system according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the following description and drawings are merely examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Furthermore, unless otherwise specified, each component may be singular or plural.

[0014] In the following description, identical or similar components may be assigned the same reference numerals, and redundant description may be omitted. Furthermore, in the following description, various types of information may be described using expressions such as "information" and "table," but the various types of information may be expressed using data structures other than these. Furthermore, expressions such as "identification information," "identifier," "name," "ID," and "number" may be used to describe identification information, but these are interchangeable. Furthermore, in the following description, "table" will be abbreviated as "TBL."

[0015] First, an overview of this embodiment will be described with reference to Fig. 1. Fig. 1 is an explanatory diagram illustrating the mechanism of the movable property security management system according to this embodiment.

[0016] 1, the movable property collateral management system of this embodiment is composed of a device management server group 201 (device management servers 201-1 to 201-N, which are movable property management devices) that manage one or more movable properties (e.g., devices), and one collateral management server 202 that corresponds to the movable property collateral management device. Here, device management servers 201-1 to 201-N correspond to, for example, equipment leasing companies or businesses, and collateral management server 202 corresponds to, for example, financial institutions or businesses, but the parties that make up the movable property collateral management system are not limited to these.

[0017] Each equipment management server 201-1 to 201-N (N is a natural number) does not have a collateral management function implemented, but rather multiple different equipment management servers 201-1 to 201-N are connected to a single collateral management server 202 via a network, and the collateral management of each equipment management server 201-1 to 201-N is entrusted to that single collateral management server 202, thereby realizing centralized collateral management.

[0018] As a result, the addition of the security management function is handled by a system separate from each equipment management server 201-1 to 201-N, i.e., the security management server 202. Therefore, even if the number of equipment management servers or the number of devices subject to security management increases, the security management server 202 simply absorbs the processing of adding devices to the devices subject to security management, making it easy to share security management.

[0019] As a representative example, an external device management client terminal (hereinafter referred to as "device management client") 204 is connected to device management server 201-1 via a network, and other movable devices DV1 to DVM (M is a natural number) are also connected via the network. To simplify the following explanation, each device management server has a similar configuration and is therefore designated by the same reference numerals as in FIG. 1.

[0020] The device management client 204 executes processes such as registering devices to be managed and transferring ownership of devices between the device management client 204 and the device management server 201-1 in response to operations by an operator.

[0021] In addition, an external collateral management client terminal (hereinafter referred to as "collateral management client") 203 is connected to the collateral management server 202. The collateral management client 203 executes the processes required for collateral management between the collateral management server 202 and the collateral management server 202 in response to an operator's operation.

[0022] Next, the configuration of this embodiment will be described. Fig. 2 is a configuration diagram showing the hardware configuration of the movable property collateral management system according to this embodiment, Fig. 3A is a block diagram showing the functional configuration of the device management server of the movable property collateral management system according to this embodiment, Fig. 3B is a block diagram showing the functional configuration of the collateral management server of the movable property collateral management system according to this embodiment, and Fig. 4 is an explanatory diagram explaining an example of a table of the movable property collateral management system according to this embodiment.

[0023] First, the hardware configuration of this embodiment will be described using Fig. 2. Since each device in the device management server group 201 has a similar hardware configuration, and the security management server 202 also has a similar configuration, the device management server 201-1 will be used as a representative example for the description.

[0024] As shown in Figure 2, the equipment management server 201-1 is generally composed of a CPU 301 that controls the entire device, a memory 302 that stores programs such as the processing according to this embodiment (flowchart described below) executed by the CPU 301 and stores various data that is being executed, a keyboard 307, a pointing device 308, an input I / F 303 that transmits input operations from the keyboard 307 and pointing device 308 to the inside, a communication I / F 304 that is connected to the network NW and controls communication with the security management server 202, an auxiliary storage device 305 that is a memory that registers and stores and manages various data and TBLs, a display 309 that displays various information and data, an output I / F 306 that sends display data from the inside to the display 309, and a bus 310 that is connected to each unit within the device and controls communication of data, signals, etc. within the device.

[0025] The security management server 202 has a similar configuration, and the communication I / F 304 is connected to the network NW and controls communication with each of the device management servers 201-1 to 201-N.

[0026] The security management client 203 and the device management client 204 shown in Fig. 1 have the same hardware configuration as that shown in Fig. 2. The security management client 203 and the security management server 202 are connected via a network, and similarly, the device management client 204 and the device management server are connected via a network.

[0027] Each of the above-mentioned networks may be a wired communication network or a wireless communication network, and the Internet or a dedicated line may be selected as appropriate.

[0028] Next, the device management server 201-1 will be described with reference to Fig. 3A. As shown in Fig. 3A, the device management server 201-1 includes a processing unit 401A having a security registration token acquisition unit 403, a device management data inquiry unit 404, a device shutdown intermediary unit 405, a device ownership transfer unit 406, etc., and a storage unit 402A having device management data 407 including a device management TBL 408, etc.

[0029] Here, the processing unit 401A has a function of performing processing according to a program stored in the memory 302 by the CPU 301. The storage unit 402A has a function of the auxiliary storage device 305.

[0030] In the processing unit 401A, the security registration token acquisition unit 403 is responsible for registering the security target device, and the device management data inquiry unit 404 is responsible for monitoring the security target device. The device shutdown intermediary unit 405 is responsible for maintaining the security target device, and the device ownership transfer unit 406 is responsible for transferring the ownership of the security target device. This processing unit 401A executes processing in cooperation with each unit of the security management server 202.

[0031] 4(a), the equipment management TBL 408 is configured to register and store, as a set, an equipment-owning company ID that identifies the company that owns the equipment, location information that indicates the location of the equipment, a location acquisition time that indicates the time when the location information was acquired, and the current value of the equipment (collateral), linked to an equipment ID assigned to each piece of equipment to be secured. Note that each piece of data in the equipment management TBL 408 is also monitoring data.

[0032] For example, the device ID "M111111" is paired with the device owner company ID "X", location information "139°xx', 35°xx'", location acquisition time "2023 / 11 / 11 11:11:11", and present value "13,500,000 yen".

[0033] Next, the security management server 202 will be described with reference to Fig. 3B. As shown in Fig. 3B, the security management server 202 includes a processing unit 401B having a security registration token issuing unit 410, a security monitoring unit 411, a security maintenance unit 412, a security registration unit 413, a security release unit 414, a security registration confirmation unit 415, a security interest transfer token issuing unit 416, an equipment security interest transfer unit 417, etc., and a memory unit 402B having security management data 418 including a security registration token TBL 419, a security interest transfer token TBL 420, and a security management TBL 421, etc.

[0034] Here, the processing unit 401B has a function of performing processing according to a program stored in the memory 302 by the CPU 301. The storage unit 402B has a function of the auxiliary storage device 305.

[0035] In the processing unit 401B, the collateral registration token issuing unit 410 is responsible for issuing a collateral registration token (for example, randomly generated character string data) which is collateral registration information for registering a pledged device as collateral, the collateral monitoring unit 411 is responsible for monitoring the pledged device, the collateral preservation unit 412 is responsible for preserving the pledged device, and the collateral registration unit 413 is responsible for registering the pledged device as collateral.

[0036] The security release unit 414 is responsible for processing to release the security of the secured device, and the security registration confirmation unit 415 is responsible for processing to confirm the security status of the secured device. The security interest transfer token issuance unit 416 is responsible for processing to issue a security interest transfer token (e.g., randomly generated character string data) that is security interest transfer information for the secured device, and the device security interest transfer unit 417 is responsible for processing to transfer the security interest of the secured device. This processing unit 401B executes processing in cooperation with each unit of the device management servers 201-1 to 201-N. Note that each device management server 201-1 to 201-N is assigned a unique device management ID, and the processing unit 401B executes processing in cooperation with the device management server determined by the device management ID. For example, the device management IDs of the device management servers 201-1 to 201-N are assigned as S001 to S00N.

[0037] Furthermore, the security registration token TBL 419 is configured to register and store a security registration token, which will be described later, as a set linked to the device management ID and the device ID registered in the device management TBL 408, as shown in FIG. 4(b), for example.

[0038] For example, the device management ID "S001" and device ID "M111111" are paired with the security registration token "T-4035-9924-1032." Here, the device management ID and device ID serve as personal property identification information.

[0039] The security interest transfer token TBL420 is configured to register and store a security interest transfer token, which will be described later, as a set linked to the device management ID and the device ID registered in the device management TBL408, as shown in Figure 4(c), for example.

[0040] For example, the device management ID "S001" and the device ID "M111119" are paired with the security interest transfer token "T-1025-6307-0770."

[0041] The security management TBL 421 is configured to register and store a device management ID and a financial institution ID for identifying a financial institution in association with the device ID registered in the device management TBL 408, as shown in FIG. 4(d), for example.

[0042] For example, the device management ID "S001" and the device ID "M111113" are paired with the financial institution ID "A."

[0043] The processing of this embodiment will be described below. First, collateral registration of this embodiment will be described using Figures 5, 6A, and 6B. Figure 5 is an explanatory diagram illustrating an example of a sequence related to collateral registration in the movable property collateral management system of this embodiment, Figure 6A is a flowchart illustrating an example of operation related to collateral registration in the movable property collateral management system of this embodiment, and Figure 6B is a flowchart illustrating another example of operation related to collateral registration in the movable property collateral management system of this embodiment. In the following description, as in the example shown in Figure 1, the device management client will be referred to as 204, the collateral management server will be referred to as 202, the collateral management client will be referred to as 203, the device management server will be referred to as 201-1, and the device will be referred to as DV1.

[0044] First, the sequence of security registration will be described with reference to Fig. 5. In security registration, in step S501, the device management client 204, which has logged in with the device-owning company ID, transmits a security registration token issuance command to the device management server 201-1 in response to an operator operation.

[0045] Next, in step S502, the security registration token acquisition unit 403 of the equipment management server 201-1 acquires the equipment ID paired with the equipment-owning company ID from the equipment management TBL 408 (equipment management data 407) stored in the memory unit 402A, and transmits the pair of equipment management ID and equipment ID to the security management server 202.

[0046] Furthermore, in step S503, the collateral registration token issuing unit 410 of the collateral management server 202 attempts to generate and store a collateral registration token (see Figure 6A described below), and if the collateral registration token is generated and stored, it returns a set of the device management ID, device ID, and collateral registration token to the device management server 201-1.

[0047] Then, in step S504, the security registration token acquisition unit 403 of the device management server returns the received set of device management ID, device ID, and security registration token to the device management client 204.

[0048] Next, in step S505, the device management client 204 that has logged in with the device-owning company ID displays a set of the device management ID, the device ID, and the security registration token.

[0049] Furthermore, in step S506, when the security management client 203 that has logged in with the financial institution ID inputs a set of the device management ID, device ID, and security registration token, it transmits the set to the security management server 202.

[0050] Then, in step S507, the security registration unit 413 of the security management server 202 checks whether the security registration token matches and links the device with the financial institution (see FIG. 6B, which will be described later).

[0051] Here, the "generation and storage of a security registration token" in step S503 described above will be specifically explained using Figure 6A. The processing here is executed by a program (memory 302) of the security management server 202. In the following explanation, the security registration token is generated by the security registration token issuing unit 410, the security confirmation for each table is performed by the security registration confirmation unit 415, and the security registration in each table is performed by the security registration unit 413.

[0052] First, when a pair of a device management ID and a device ID is received from the device management server 202-1, the registered record in the security registration token TBL 419 is referenced (step S601), and it is confirmed whether the received pair is registered (stored) (step S602). As a result, if the pair is registered (YES route in step S602), this process ends.

[0053] On the other hand, if the pair has not yet been registered (NO route in step S602), the registered records in the security management TBL 421 are further referenced (step S603) to check whether the received pair has been registered (stored) (step S604). As a result, if the pair has been registered (YES route in step S604), this process ends.

[0054] If the pair has not yet been registered (NO route in step S604), the security registration token issuing unit 410 generates a security registration token (step S605). A new pair is generated as a record by combining the device management ID and device ID received in step S601 with the security registration token generated in step S605 (step S606).

[0055] Then, the set of the device management ID, device ID, and security registration token generated in step S606 is inserted as a new record into the security registration token TBL 419 and stored (registered) (step S607). In this way, this process ends.

[0056] For example, if a pair of device management ID "S001" and device ID "M111111" is received, this pair is already registered in the security registration token TBL 419, as shown in Figure 4(b), and therefore this processing ends. On the other hand, if a pair of device management ID "S001" and device ID "M111113" is received, as is clear from Figures 4(b) and 4(d), there is no registration in the security registration token TBL 419, but registration in the security management TBL 421 can be confirmed, and therefore this processing ends here.

[0057] In addition, if a pair of device management ID "S001" and device ID "M111112" is received and has not been registered in the security registration token TBL419 or the security management TBL421, a new record is registered in the security registration token TBL419 in step S607.

[0058] In this way, it is possible to ensure exclusivity so that only one of the security registration token and the security registration exists.

[0059] 6B, the "linking of the device with the financial institution" in step S507 will be specifically described. The processing here is also executed by the program (memory 302) of the security management server 202. Here too, the security registration token is generated by the security registration token issuing unit 410, the security registration confirmation unit 415 is responsible for security confirmation for each table, and the security registration unit 413 is responsible for security registration in each table.

[0060] It is assumed that the security management client 203 has received a set of the device management ID, device ID, and security registration token from the device management client 204 in advance after step S505 as shown in FIG.

[0061] In the security management server 202, when a set of device management ID, device ID, and security registration token is input from the security management client 203 (step S611), the security registration token TBL 419 is referenced to check whether the input set exists in the record (step S612).

[0062] If the input set does not match a set (record) in the security registration token TBL419 (NO route in step S613), this process ends; on the other hand, if there is a match (YES route in step S613), the record of the matching set is deleted (step S614).

[0063] If the record cannot be deleted (NO route in step S615), the process ends with the deletion having failed, whereas if the record can be deleted (YES route in step S615), the deletion is successful and the input set is linked to the financial institution ID and inserted as a new record in the collateral management TBL 421, where it is stored (registered) (step S616).

[0064] For example, when a set of device management ID "S002", device ID "M222222", and collateral registration token "T8515-0745-6283" is input, it can be confirmed that it matches the registration record in the collateral registration token TBL 419 shown in Figure 4(b). In this case, the record in the collateral registration token TBL 419 is deleted, and a set of device management ID "S002", device ID "M222222", and financial institution ID "A" linked to it is registered as a new record in the collateral management TBL 421 as shown in Figure 4(d).

[0065] Here too, it is possible to ensure exclusivity so that only one of the security registration token and the security registration exists. In particular, even if step S507 is executed by multiple financial institutions at the same time, only the first financial institution to arrive can insert a record.

[0066] Furthermore, the collateral monitoring of this embodiment will be described with reference to Figures 7A and 7B. Figure 7A is an explanatory diagram illustrating an example of a sequence related to collateral monitoring in the personal property collateral management system according to this embodiment, and Figure 7B is an explanatory diagram illustrating another example of a sequence related to collateral monitoring in the personal property collateral management system according to this embodiment.

[0067] In the collateral monitoring sequence, in step S701 (see FIG. 7A), the collateral management client 203, which has logged in with a financial institution ID, inputs a pair of a device management ID and a device ID and transmits them to the collateral management server 202. Here, a query is made as to whether the status of device DVm (m is a natural number) is being monitored.

[0068] Next, in step S702, the collateral monitoring unit 411 of the collateral management server 202 confirms that a set of equipment management ID, equipment ID, and financial institution ID is stored in the collateral management TBL 421, and sends the equipment ID to the equipment management server 201-n (n is a natural number) of the equipment management ID.

[0069] Then, in step S703, the equipment management data inquiry unit 404 of the equipment management server 201-n acquires the monitoring data of the equipment ID stored in the equipment management TBL 408 (such as the equipment's GPS location information, the time of location acquisition, and the current value) and returns it to the security management server 202.

[0070] In the following step S704, the security monitoring unit 411 of the security management server 202 returns the received monitoring data to the security management client 203. As a result, in step S705, the security management client 203 that has logged in with the financial institution ID displays the monitoring data.

[0071] In this way, collateral monitoring becomes possible.

[0072] Regarding abnormality detection, as shown in FIG. 7B, first, in step S706, the collateral monitoring unit 411 of the collateral management server 202 periodically (for example, at a set time every day) transmits the device ID for the pair of device management ID and device ID stored in the collateral management TBL 421 to the device management server 201-n of the device management ID.

[0073] Then, in step S707, the equipment management data inquiry unit 404 of the equipment management server 201-n acquires the monitoring data of the equipment ID stored in the equipment management TBL 408 (such as the equipment's GPS location information, the time of location acquisition, and the current value) and returns it to the security management server 202.

[0074] Furthermore, in step S708, if the collateral monitoring unit 411 of the collateral management server 202 detects an abnormality in the received monitoring data, it notifies the collateral management client 203, which has logged in with the financial institution ID, of the combination of the equipment management ID, the equipment ID, and the monitoring data in which the abnormality was detected, for the financial institution ID that is paired with the equipment management ID and the equipment ID in the collateral management TBL 421.

[0075] Here, examples of detecting anomalies for each monitoring data include detecting an anomaly for GPS location information if the location is outside Japan, detecting an anomaly for the location acquisition time if it is before a certain period of time, and detecting an anomaly for the present value if it is below a certain amount.

[0076] Then, in step S709, the collateral management client 203 that has logged in with the financial institution ID displays the notified set of device management ID, device ID, and monitoring data in which an abnormality was detected.

[0077] In this way, regular monitoring of collateral makes it possible to detect abnormalities in a timely manner and without delay.

[0078] Furthermore, the security preservation and security release of this embodiment will be explained using Figures 8 and 9. Figure 8 is an explanatory diagram illustrating an example of a sequence related to security preservation in the personal property security management system according to this embodiment, and Figure 9 is an explanatory diagram illustrating an example of a sequence related to security release in the personal property security management system according to one embodiment of the invention.

[0079] First, the collateral maintenance will be explained using Fig. 8. First, in step S801, the collateral management client 203, which has logged in with a financial institution ID, inputs a set of a device management ID and a device ID and transmits it to the collateral management server 202. Next, in step S802, the collateral maintenance unit 412 of the collateral management server 202 confirms that the set of the device management ID, device ID, and financial institution ID is stored in the collateral management TBL 421, and transmits the device ID to the device management server 201-n of the device management ID.

[0080] Then, in step S803, the device shutdown intermediary unit 405 of the device management server 201-n transmits an operation shutdown command to the device DVm of the device ID. In the following step S804, the device DVm of the device ID receives the operation shutdown command and shuts down.

[0081] In this way, it is possible to stop the operation of the equipment (collateral) for the purpose of preserving the collateral.

[0082] Next, the release of security will be explained using Figure 9. First, in step S901, the security management client 203, which has logged in with a financial institution ID, inputs a set of a device management ID and a device ID and transmits it to the security management server 202. In the following step S902, the security release unit 414 of the security management server 202 deletes the record of the set of the device management ID, device ID, and financial institution ID from the security management TBL 421.

[0083] In this way, for example, it is possible to release the collateral once the money has been collected from the business through a loan.

[0084] Furthermore, the collateral transfer of this embodiment will be described using Figures 10, 11A, and 11B. Figure 10 is an explanatory diagram illustrating an example of a sequence related to collateral transfer in the personal property collateral management system of this embodiment, Figure 11A is a flowchart illustrating an example of operation related to collateral transfer in the personal property collateral management system of this embodiment, and Figure 11B is a flowchart illustrating another example of operation related to collateral transfer in the personal property collateral management system of this embodiment.

[0085] In the sequence, first, in step S1001, the security management client 203 that has logged in with a financial institution ID (for example, "A") inputs a pair of a device management ID and a device ID and transmits them to the security management server 202.

[0086] In the next step S1002, the security interest transfer token issuing unit 416 of the security management server 202 attempts to generate and store a security interest transfer token based on the processing in Fig. 11A, which will be described later. If the security interest transfer token issuing unit 416 is able to generate and store the security interest transfer token, it returns a set of the device management ID, device ID, and security interest transfer token to the security management client 203.

[0087] Then, in step S1003, the collateral management client 203 that has logged in with the financial institution ID "A" displays a set of the device management ID, the device ID, and the security interest transfer token. In the following step S1004, the collateral management client 203 that has logged in with the financial institution ID (for example, "B") inputs a set of the device management ID, the device ID, and the security interest transfer token and transmits it to the collateral management server 202.

[0088] Then, in step S1005, the equipment security interest transfer unit 417 of the security management server 202 confirms whether the security interest transfer token matches and changes the link between the equipment and the financial institution based on the processing of FIG. 11B described below.

[0089] Next, the processing of step S1002 described above will be explained using Fig. 11A. Here, the main processing is the generation and storage of a security interest transfer token by the security interest transfer token issuing unit 416 of the security management server 202.

[0090] First, when a set of device management ID, device ID, and financial institution ID is input from the security management client 203 (step S1101), the security management TBL 421 shown in Fig. 4(d) is referenced to check whether there is a matching set (step S1102). As a result, if a match is not confirmed (NO route in step S1103), this process ends.

[0091] On the other hand, if a match is confirmed (YES route in step S1103), a further reference is made to the security transfer token TBL420 shown in Figure 4(c) (step S1104), and it is confirmed whether a pair matching the input pair exists (step S1105).

[0092] If a match is confirmed (YES route in step S1105), the process ends. On the other hand, if a match is not confirmed (NO route in step S1105), a security interest transfer token is generated (step S1106). In the example of Figure 4(c), the pair of device management ID "S001" and device ID "M111119" and the pair of device management ID "S002" and device ID "M222228" exist, so this process ends. On the other hand, if the pair of device management ID "S003" and device ID "M333336" does not exist, a security interest transfer token will be generated.

[0093] In this way, the pair of the input pair and the security interest transfer token generated in step S1106 is inserted as a new record into the security interest transfer token TBL420 shown in Figure 4(c) and stored (registered) (step S1107).

[0094] 11B, the processing of step S1005 will be described. Here, the equipment security interest transfer unit 417 of the security management server 202 checks whether the security interest transfer token matches and changes the association between the equipment and the financial institution.

[0095] First, when a set of a device management ID, a device ID, and a security interest transfer token is input from the security management client 203 (step S1111), the security interest transfer token TBL 420 is referenced to check whether there is a matching set (step S1112). If a match is not confirmed (NO route in step S1113), this process ends.

[0096] For example, if a set of device management ID "S005", device ID "M666669" and security interest transfer token "T-3033-2107-1230" is input and that set does not exist in security interest transfer token TBL420, this process will end.

[0097] On the other hand, if a match is confirmed (YES route in step S1113), the record of the matching set is deleted (step S1114) from security interest transfer token TBL 420. As a result, if the record deletion fails (NO route in step S1115), this process ends.

[0098] For example, if a set of device management ID "S001", device ID "M111119" and security right transfer token "T-1025-6307-0770" is entered, a record exists in security right transfer token TBL420 as shown in Figure 4(c), so that set will be deleted.

[0099] On the other hand, if the record deletion is successful (YES route in step S1115), the financial institution ID of the record corresponding to the input set in the security management TBL 421 is updated (step S1116).

[0100] In this way, the security transfer token allows for exclusivity in updating security registrations.

[0101] Furthermore, by executing step S1116 after step S1115 is successful, even if step S1005 is executed by multiple financial institutions at the same time, it is possible to ensure that step S1116 is executed only by the first financial institution to arrive.

[0102] Furthermore, the transfer of ownership in this embodiment will be described with reference to Figures 12 and 13. Figure 12 is an explanatory diagram illustrating an example of a sequence related to the transfer of ownership in the personal property collateral management system according to this embodiment, and Figure 13 is a flowchart illustrating an example of the operation related to the transfer of ownership in the personal property collateral management system according to this embodiment.

[0103] In the sequence for transferring ownership, first, in step S1201, the device management client 204, which has logged in with the device-owning company ID, transmits the device ID and the device-owning company ID of the ownership transfer destination to the device management server 201-n. In the following step S1202, the device ownership transfer unit 406 of the device management server 201-n transmits a pair of the device management ID and the device ID to the security management server 202.

[0104] Then, in step S1203, the security registration confirmation unit 415 of the security management server 202 attempts to confirm whether security is registered and delete the security registration token based on the processing of Figure 13 described below, and returns the security registration confirmation result to the equipment management server 201-n.

[0105] Next, in step S1204, if the received security registration confirmation result is "no security registration," the device ownership transfer unit 406 of the device management server 201-n updates the device owning company ID paired with the device ID in the device management TBL 408 to the device owning company ID of the ownership transfer destination. As a result, the procedure for changing ownership to another company is completed.

[0106] Next, the above-mentioned step S1203 will be explained using Fig. 13. Here, the explanation will focus on the confirmation of the existence of a security registration by the security registration confirmation unit 415 of the security management server 202, and the deletion of the security registration token.

[0107] First, when a pair of device management ID and device ID is input to the device management server 201-n (device ownership transfer unit 406) (step S1301), the security registration token TBL419 is referenced to check whether the pair exists there (step S1302).

[0108] If it is confirmed that a matching pair exists (YES route in step S1303), the record of the matching pair is deleted from the security registration token TBL 419 (step S1304). If the deletion is not possible (NO route in step S1305), the deletion is deemed to have failed, and the security registration confirmation result is notified to the device management server 201-n as "security registration exists," which indicates the existence of security ownership (step S1309). By receiving this notification, the device management server 201-n can display the fact that security registration exists on the device management client 204.

[0109] On the other hand, if the deletion is successful in step S1305 (YES route), the deletion is deemed to have been successful, and the result of the security registration confirmation is notified to the device management server 201-n as "no security registration" (step S1306).

[0110] Also, if it is confirmed in step S1303 that no matching pair exists (NO route in step S1303), the collateral management TBL 421 is referenced to check whether a record of the pair entered in step S1301 exists there (step S1307).

[0111] If it is confirmed that a matching pair exists (YES route in step S1308), the security registration confirmation result is notified to the device management server 201-n as "security registration exists" (step S1309). On the other hand, if it is confirmed that a matching pair does not exist (NO route in step S1308), the security registration confirmation result is notified to the device management server 201-n as "no security registration", which indicates that there is no security ownership (step S1306). By receiving this notification, the device management server 201-n can display "no security registration" on the device management client 204.

[0112] In this way, it is possible to ensure exclusivity, that is, there can only be one of either the security registration token or the security registration.

[0113] Furthermore, by executing step S1302 after step S1301, and further by determining whether or not a security registration has been made depending on whether the deletion in step S1304 has been successful or not, it is possible to ensure that step S1203 is not executed simultaneously with step S507.

[0114] As explained above, according to this embodiment, in the security management of movable property, it is possible to realize the security management of movable property with a single security management server, regardless of the number of connected device management servers that manage devices, and regardless of the number of devices managed by each device management server. This makes it easy to add functions such as additional registration of movable property to be managed as security, monitoring, preservation, release, and transfer of security rights and ownership, and it is possible to centralize the security management of movable property using the security management server, rather than distributing it.

[0115] In the above-described embodiment, the collateral for asset-backed loans was equipment (e.g., machinery, facilities, vehicles, etc.), but since the collateral can be any asset that can be relatively easily valued and transferred, it can also be applied to inventory owned by commercial enterprises and retailers, intangible assets such as intellectual property rights such as patents, trademarks, and copyrights, account revenue rights based on accounts receivable and contracts, equipment leasing agreements, etc.

[0116] The mechanisms of the above-described embodiments can be used by companies and organizations to track and manage various types of assets. For example, they can be applied to managing IT assets, office furniture and equipment, fixed assets, etc. They can also be applied to tracking and managing inventory. This enables efficient inventory management and flexibility in industries such as retail, manufacturing, and logistics.

[0117] It can also be used to manage and evaluate assets under lease agreements. For example, it can track contract terms and deadlines for leasing office equipment or vehicles. It can also be applied to tracking assets and resources related to corporate projects. For example, it can manage the equipment and materials needed for construction or manufacturing projects.

[0118] In addition, in the above-described embodiment, security management is performed using tokens, but the present invention is not limited to tokens as long as the security is guaranteed in the same manner as a token, the security cannot be rewritten, and the security can be generated as a unique piece of identification information for security registration and security right transfer.

[0119] Furthermore, the above-described configurations, functional units, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC card, an SD card, a DVD, or other recording media.

[0120] Furthermore, the above-described layout of the various functional units, processing units, and storage units of the information collection system 10 is merely an example. The layout of the various functional units, processing units, and storage units can be changed to an optimal layout in terms of the performance, processing efficiency, communication efficiency, etc. of the hardware and software provided in these devices.

[0121] Furthermore, the configuration (schema, etc.) of the storage unit that stores the various types of data described above can be flexibly changed from the viewpoint of efficient use of resources, improved processing efficiency, improved access efficiency, improved search efficiency, and the like. [Explanation of symbols]

[0122] 201-1 to 201-N Device management server 202 Collateral Management Server 203 Collateral Management Clients 204 Device Management Client 301 CPU 302 memory 303 Input I / F 304 Communication I / F 305 Auxiliary storage device 306 Output I / F 307 Keyboard 308 Pointing Device 309 Display 401A, 401B Processing section 402A,402B Storage section 403 Collateral Registration Token Acquisition Department 404 Equipment Management Data Inquiry Unit 405 Equipment Shutdown Intermediary Department 406 Equipment Ownership Transfer Department 407 Equipment Management Data 408 Equipment management TBL 410 Collateral Registration Token Issuance Department 411 Collateral Monitoring Department 412 Collateral Preservation Department 413 Collateral Registration Department 414 Security Release Department 415 Collateral Registration Verification Department 416 Collateral Transfer Token Issuance Department 417 Equipment Security Interest Transfer Division 418 Collateral Management Data 419 Collateral Registration Token TBL 420 Collateral Transfer Token Transfer TBL 421 Collateral Management TBL

Claims

1. A movable property collateral management device that manages the collateral of movable property that is the subject of a loan from a loan source by communicating with one or more movable property management devices that register movable property identification information unique to the movable property to be managed as collateral, a security registration unit that links and registers security registration information assigned to each of the movable property identification information; a security management unit that links and registers financial institution information that identifies a loan source for each movable property identification information registered in the security registration unit; a security registration issuing unit that receives personal property identification information specific to the personal property from the personal property management device, and generates and issues new security registration information if the received personal property identification information does not exist in either the security registration unit or the security management unit; a registration unit that links the received movable property identification information with the security registration information issued by the security registration and issuance unit and registers the linked information in the security management unit; A movable property security management device comprising:

2. In the movable property collateral management device described in claim 1, the registration unit accepts a set of movable property identification information and collateral registration information specific to the movable property from the movable property management device, and if a set matching the accepted set exists in the collateral registration unit, deletes the matching set from the collateral registration unit and registers the accepted set in the collateral management unit by linking it to information about the financial institution that provided the loan.

3. In the movable property collateral management device described in claim 1, each movable property management device registers monitoring data for movable property, and further comprises a monitoring unit that is connected to an external client, receives movable property identification information specific to the movable property from the client, and refers to the collateral management unit to obtain and monitor the monitoring data from the movable property management device if a pair of the received movable property identification information and financial institution information exists.

4. In the movable property collateral management device described in claim 1, each movable property management device registers monitoring data for movable property, and further comprises a monitoring unit that acquires and monitors the monitoring data from the movable property management device based on each movable property identification information registered in the collateral management unit at predetermined intervals.

5. The movable property collateral management device described in claim 1 further comprises a collateral preservation unit that is connected to an external client, receives movable property identification information specific to the movable property from the client, and, if the received movable property identification information exists, refers to the collateral management unit and, if so, performs preservation of the movable property corresponding to the movable property identification information to the movable property management device.

6. The movable property collateral management device of claim 1 further comprises a collateral release unit that is connected to an external client, receives movable property identification information specific to the movable property from the client, and, if the received movable property identification information exists, refers to the collateral management unit and deletes the movable property identification information from the collateral management unit to release the movable property collateral.

7. 2. The movable property security management device according to claim 1, wherein the security registration information is randomly generated character string data.

8. The movable property collateral management device described in claim 1 further comprises a security right transfer registration unit that links and registers security right transfer information that identifies the movable property to which the security right is to be transferred for each movable property identification information registered in the security registration unit, and a security right transfer information issuing unit that is connected to an external client and receives from the client a set of movable property identification information and financial institution information specific to the movable property, and generates and issues new security right transfer information if the received set exists in the security management unit but does not exist in the security right transfer registration unit, wherein the movable property collateral management device is characterized in that the security right transfer registration unit registers the issued security right transfer information by linking it to the received set.

9. 9. The movable property security management device according to claim 8, wherein the security interest transfer information is character string data that is randomly generated.

10. In the movable property collateral management device described in claim 8, the registration unit is connected to another external client, accepts a set of movable property identification information and financial institution information specific to the movable property from the other client, and if a set matching the accepted set exists in the security right transfer registration unit, deletes the matching set and registers it in the security management unit by linking it to the accepted set and the financial institution information of the lender.

11. The movable property collateral management device of claim 1 is characterized in that it has a collateral registration confirmation unit that receives movable property identification information specific to the movable property from the movable property management device, and if the received movable property identification information exists in the collateral registration unit, deletes the received movable property identification information from the collateral registration unit and notifies the movable property management device of a no-collateral registration, which indicates that there is no collateral ownership, and on the other hand, if the received movable property identification information does not exist in the collateral registration unit and the received movable property identification information exists in the collateral management unit, notifies the movable property management device of a yes-collateral registration, which indicates that there is a collateral ownership.

12. A movable property collateral management system having one or more movable property management devices and a movable property collateral management device that manages collateral for movable property that is the subject of a loan from a loan source through communication with each of the movable property management devices, Each of the movable property management devices is A movable property management unit is provided for registering movable property identification information specific to the movable property to be managed as collateral, The movable property security management device a security registration unit that links and registers security registration information assigned to each of the movable property identification information; a security management unit that links and registers financial institution information that identifies a loan source for each movable property identification information registered in the security registration unit; a security registration and issuance unit that receives from the security management device the security identification information specific to the security to be registered in the security management unit, and generates and issues new security registration information if the received security identification information does not exist in either the security registration unit or the security management unit; a registration unit that links the received movable property identification information with the security registration information issued by the security registration and issuance unit and registers the linked information in the security management unit; A movable property collateral management system comprising:

13. A movable property collateral management method for a system having one or more movable property management devices and a movable property collateral management device that manages the collateral of movable property that is the subject of a loan from a loan source through communication with each of the movable property management devices, comprising: Each of the movable property management devices registers movable property identification information specific to the movable property being managed as collateral in a first memory, and the movable property collateral management device has a second memory that links and registers collateral registration information assigned to each of the movable property identification information, and links and registers financial institution information identifying a lender to each of the movable property identification information, a first step in the movable property security management device of receiving, from the movable property management device, movable property identification information specific to the movable property to be registered in the first memory, and generating and issuing new security registration information if the received movable property identification information does not exist in the second memory; a second step of linking the received personal property identification information with the security registration information issued in the first step and registering them in the second memory; A movable property collateral management method comprising:

Images