JP7580972B2 - Information processing system, information processing device, server device, program, or method - Google Patents

Description

The technology disclosed in this application relates to an information processing system, an information processing device, a server device, a program, or a method.

In recent years, instead of owning products manufactured and sold by manufacturers, users' consumption trends are shifting toward a temporary consumption model in the form of services in which such products are used temporarily.

JP 2004-227513 A JP 2003-76891 A JP 2008-198032 A JP 2003-242032 A

Patent Document 1 relates to technology related to vehicle rental. Patent Document 2 relates to technology for eliminating risks related to sales. Patent Document 3 relates to technology for tokens of usage rights. Patent Document 4 relates to the circulation of usage rights. However, it is desirable to appropriately support the relationship between usage rights and ownership, etc. Therefore, various embodiments of the present invention provide an information processing system, an information processing device, a server device, a program, or a method to solve the above problems.

The system according to the first embodiment of the present invention comprises:
An acquisition unit that acquires information related to an authority to use a first object stored in association with a first related person;
an association storage unit that is capable of storing the first related party and information related to the authority to own the first object in association with each other based on the first related party and information related to the authority to use the first object;
A system comprising: Here, the "information related to the authority to use" may include the use authority information described later, and the "information related to the authority to use the first object" may include the use authority information associated with the information including or indicating the first object, or may include the use authority information including the information including or indicating the first object. Similarly, the "information related to the authority to own" may include the ownership authority information described later, and the "information related to the authority to own the first object" may include the ownership authority information associated with the information including or indicating the first object, or may include the ownership authority information including the information including or indicating the first object. Moreover, "based on the first related party and the information related to the authority to use the first object" may directly or indirectly use "the first related party and the information related to the authority to use the first object", and for example, as described later, may or may not be via the information related to the authority to exchange. Moreover, the first object may be a unique object that exists as a physical entity, may be a mass-produced object, or may be a specific type of object. In addition, the association storage unit may be capable of storing each of the above and below described information in association with each other, or may store each of the above and below described information in association with each other.

A system according to a second embodiment of the present invention includes:
The first object indicates an object of the same kind specified by the same rental amount,
The system of the first embodiment. Here, the same rental amount may be a type in which the first object is rented and the rental amount is the same in the type of business in which the first object is rented. As described later, for example, if it is a rental car, the rental fee may be the same, but is not limited to such an example.

A system according to a third embodiment of the present invention includes:
The association storage unit
The first party and information regarding the authority to exchange the first object can be stored in association with each other using information regarding the authority to use the first object and the first party;
The first party and information regarding the authority to own the first object can be stored in association with each other using information regarding the authority to exchange the first object with the first party.
The system according to the first or second embodiment. Here, similarly, the "information related to the authority to exchange" may include exchange authority information described later, and the "information related to the authority to exchange the first object" may include exchange authority information associated with information including or indicating the first object, or may include exchange authority information including information including or indicating the first object. Also,
The association storage unit
The second party and information related to the authority to use the second object may be used to store the second party and information related to the authority to exchange the second object in association with each other. Here, the second party may be the same as or different from the first party. Also, the second object may be the same as or different from the first object.
Moreover, the association storage unit
using information regarding the authority to exchange a third object with a third party,
The third party and information related to the authority to own the third object may be stored in association with each other. Here, the third party may be the same as or different from the first and/or second party. Furthermore, the third object may be the same as or different from the first and/or second object. Furthermore, when a process of storing the second party and information related to the authority to exchange the second object in association with each other and a process of storing the third party and information related to the authority to own the third object in association with each other are performed, the order of the processes may be either one.

A system according to a fourth embodiment of the present invention includes:
The association storage unit uses information related to the first related party and the authority to use a predetermined number of the first targets,
The first related person and information related to the authority to own the first object can be stored in association with each other.
A system according to any one of the first to third embodiments.

A system according to a fifth embodiment of the present invention includes:
The association storage unit uses information indicating an intention of the first related party to exchange information related to the authority to use the first object with information related to the authority to own the first object.
A system according to any one of the first to fourth embodiments.

A system according to a sixth embodiment of the present invention includes:
The association storage unit
The first party and the information on the authority to exchange the first object can be stored in association with each other using information indicating an intention of the first party to exchange information on the authority to use the first object and information on the authority to exchange the first object;
the first party, the information regarding the authority to exchange the first object, and the information regarding the authority to own the first object can be stored in association with each other using information indicating an intention of the first party to exchange information regarding the authority to exchange the first object and information regarding the authority to own the first object;
A system according to any one of the first to fifth embodiments.

A system according to a seventh embodiment of the present invention includes:
The information regarding the right to own the first object is stored in a security token.
A system according to any one of the first to sixth embodiments.

The system according to the eighth embodiment of the present invention comprises:
The one security token is capable of storing a plurality of pieces of information indicating an owner of the first object.
A system according to any one of the first to seventh embodiments.

A system according to a ninth embodiment of the present invention includes:
The one security token is capable of storing information indicating one authorized user who is using the first object.
A system according to any one of the first to eighth embodiments.

A system according to a tenth embodiment of the present invention comprises:
The information regarding the authority to use the first object can be stored in a security token in association with an expiration date during which the authority to use the first object can be exercised.
A system according to any one of the first to ninth embodiments.

A system according to an eleventh embodiment of the present invention includes:
When the information on the authority to exchange the first object is issued in exchange for information on the authority to use the first object, the information on the authority to use the first object is invalidated.
A system according to any one of the first to tenth embodiments.

A system according to a twelfth embodiment of the present invention comprises:
The information on the authority to use the first object is issued based on information on the owner of the first object.
A system according to any one of the first to eleventh embodiments.

A system according to a thirteenth embodiment of the present invention comprises:
When the information on the authority to own the first object is issued in exchange for information on the authority to use the first object, the information on the authority to use the first object is invalidated.
A system according to any one of the first to twelfth embodiments.

A system according to a fourteenth embodiment of the present invention comprises:
The association storage unit is capable of associating information indicating a contributor who has contributed in relation to the first object with information relating to the amount of contribution of the contributor to the first object and storing the information in a single security token.
A system according to any one of the first to thirteenth embodiments.

A system according to a fifteenth embodiment of the present invention comprises:
The related note will be issued when the dividend conditions for the one investor are satisfied.
The information indicating the one contributor and the information indicating the authority to use the first object can be stored in one security token in association with each other.
A system according to any one of the first to fourteenth embodiments.

A system according to a sixteenth embodiment of the present invention comprises:
The association storage unit is capable of storing information identifying an anonymous association that owns the first target that is the target of the investment in the one security token.
A system according to any one of the first to fifteenth embodiments.

A system according to a seventeenth embodiment of the present invention comprises:
The information regarding the authority to exchange the first object can be stored in a security token in association with an expiration date during which the authority to exchange the first object can be exercised.
A system according to any one of the first to sixteenth embodiments.

A system according to an eighteenth embodiment of the present invention comprises:
The first object indicates a particular vehicle type that will have the same rental price if the vehicle is rented;
A system according to any one of the first to seventeenth embodiments.

A system according to a nineteenth embodiment of the present invention comprises:
The association storage unit
The first party can be stored in association with information indicating the authority to own the first object by using information on the authority obtained by contributing to the first object and information on the authority to own the first object, the information being stored in association with the first party.
The system according to any one of the first to eighteenth embodiments. Here, the "information related to the authority obtained by investing" may include investment authority information described later, and the "information related to the authority obtained by investing in relation to the first target" may include investment authority information associated with information including or indicating the first target, or may include investment authority information including information including or indicating the first target.

A system according to a twentieth embodiment of the present invention comprises:
The association storage unit
The first party can be stored in association with information indicating the authority to use the first object by using information on the authority obtained by contributing to the first object and information on the authority to use the first object, the information being stored in association with the first party,
20. A system according to any one of the first to nineteenth embodiments.

A system according to a twenty-first embodiment of the present invention comprises:
The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to own the first object and the object of value, the information being stored in association with the first party.
A system according to any one of the first to twentieth embodiments.

A system according to a twenty-second embodiment of the present invention comprises:
The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to use the first object, which is stored in association with the first party, and the object of value.
A system according to any one of the first to twenty-first embodiments.

A system according to a twenty-third embodiment of the present invention comprises:
The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to exchange the first object stored in association with the first party and the object of value.
A system according to any one of the first to twenty-second embodiments.

A system according to a twenty-fourth embodiment of the present invention comprises:
The association storage unit
The first party and the object of value can be stored in association with each other using information on the authority obtained by contributing in relation to the first object, which is stored in association with the first party, and the object of value.
A system according to any one of the first to twenty-third embodiments.

A method according to a twenty-fifth embodiment of the present invention includes:
The system,
An acquisition step of acquiring information related to an authority to use a first object stored in association with a first related person;
an association storage step for storing the first related party and information related to the authority to own the first object in association with each other based on information related to the authority to use the first object;
How to do it.

A method according to a twenty-sixth embodiment of the present invention includes:
The system comprises a memory.
The method of the twenty-fifth embodiment.

A program according to a twenty-seventh embodiment of the present invention,
The system,
An acquisition means for acquiring information related to an authority to use a first object stored in association with a first related person;
an association storage means for storing the first related party and information related to the authority to own the first object in association with each other based on information related to the authority of the first related party and the authority to use the first object;
A program to function as a

A program according to a twenty-eighth embodiment of the present invention,
The system comprises a memory.
A program according to the twenty-seventh embodiment.

One embodiment of the present invention can appropriately support the relationship between usage and ownership.

FIG. 1 is a block diagram showing the configuration of a system according to an embodiment. FIG. 2 is a block diagram showing a configuration of a system according to an embodiment. FIG. 3 is a block diagram illustrating the functions of a system according to an embodiment. FIG. 4 is a diagram showing the data structure of the system according to one embodiment. FIG. 5 is a diagram showing the data structure of the system according to one embodiment. FIG. 6 is a diagram showing the data structure of the system according to one embodiment. FIG. 7 is a diagram showing the data structure of the system according to one embodiment. FIG. 8 is a block diagram showing a configuration of a system according to an embodiment. FIG. 9 is a diagram showing a flow of a system according to an embodiment. FIG. 10 is a diagram showing a flow of a system according to an embodiment. FIG. 11 is a diagram showing a flow of a system according to an embodiment. FIG. 12 is a diagram showing a flow of a system according to an embodiment. FIG. 13 is a diagram showing a flow of a system according to an embodiment. FIG. 14 is a diagram showing a flow of a system according to an embodiment. FIG. 15 is a diagram showing a flow of a system according to an embodiment.

1. Components of the information processing device 10 The system according to the present invention uses an information processing device. An example system may use one or more information processing devices. The multiple information processing devices may be information processing devices owned or used by the same organization, or may be information processing devices installed in different locations owned or used by different organizations. The information processing device may be a centralized one or may enable distributed processing. In the case of multiple information processing devices, various computing systems such as terminal devices, servers, and clouds may be mixed. The information processing device may be a general-purpose information processing device or a dedicated information processing device. The information processing device may be various information processing devices such as a workstation, a notebook computer, a desktop computer, a tower type, and a laptop type. The terminal device may be a portable terminal device, and may be various information processing devices such as a smartphone, a PDA, a mobile phone, and a wearable computer. In the present application, the term "system" may refer to a single information processing device or may be composed of multiple information processing devices.

Here, an example of an information processing device including basic functions is described, but the information processing device used in the system according to the present invention is not limited to the information processing device described below, and various types of information processing devices may be used, such as those with some functions enhanced or those with some functions omitted. Also, when the system is composed of multiple information processing devices, each information processing device may have the same functions or different functions.

As shown in FIG. 1, the information processing device 10 may include a calculation device and a storage device. The calculation device and the storage device may be connected by a bus. The information processing device may also include a communication device that enables communication with the outside. The communication device may be connectable to a network. The information processing device 10 may also include an input device and a display device.

The bus has the function of transmitting information between devices. The bus may have the function of transmitting information between a computing device, a storage device, an input device, a display device, and a communication device.

A storage device is a device that has the function of recording information. The storage device may be either an external memory or an internal memory, and may be either a main storage device or an auxiliary storage device. It may also be a magnetic disk (hard disk), an optical disk, a magnetic tape, a semiconductor memory, etc. The information processing device may also have a storage device connected via a network, or a storage device on the cloud connected via a network.

The arithmetic device has a calculation function. An example of the arithmetic device is a processor. This may be a CPU or an MPU. It may also have a graphics processing unit, a digital signal processor, etc. The arithmetic device may be a device that has the function of executing program instructions.

Note that in the block diagram of FIG. 1, registers, L1 caches, L2 caches, and the like, which store information in locations physically close to the arithmetic unit, may be included within the arithmetic unit, but in computer architecture design, the storage device may include these as devices that record information. In short, it is sufficient that the arithmetic unit, storage device, and bus are configured to cooperate to execute information processing.

The storage device may include a program for executing instructions related to the present invention. It may also appropriately record data required for executing instructions related to the present invention. The storage device may also include a database.

In addition, the above describes a case where the arithmetic unit is executed based on a program stored in a storage device, but as one form of combination of the above bus, arithmetic unit and storage device, the information processing related to the present system may be realized by a programmable logic device that can change the hardware circuitry itself, or a dedicated circuit in which the information processing to be executed is predetermined.

An input device is used to input information, but may also have other functions. Examples of input devices include a keyboard, a mouse, a touch panel, or a pen-type pointing device.

A display device has a function of displaying information. Examples include liquid crystal displays, plasma displays, and organic electroluminescence displays, but in short, any device that can display information will do. A display device may also include an input device, such as a touch panel, as part of the device.

The network, together with the communication device, has the function of transmitting information. That is, the network has the function of transmitting information held by an information processing device to another information processing device (not shown) via the network, and/or enabling information held by another information processing device to be obtained via the network. The communication device may be of any connection type, such as USB, IEEE 1394, Ethernet (registered trademark), PCI, SCSI, etc. The network may be either wired or wireless, and may use optical fiber, coaxial cable, etc.

2. Overview of the System of an Embodiment Next, an example of a system using the above-mentioned information processing device will be described with reference to FIG. 2. The example system may include a management system 010. The management system 010 may be connectable to an administrator terminal 011 so as to be able to manage the target. In this figure, the management system 010 is directly connected to the administrator terminal 011, but may be connected via a network 000 or the like. The management system is also an example of a system, and may be composed of one or more information processing devices as described above, some or all of which may be server devices, or some or all of which may be clouds. The management system may be connectable to related party terminals 01, 02, and 03 handled by related parties A to C defined below in the present application documents. Here, three examples of related party terminals are shown, but there may be two, four or more. The management system may distinguish and manage each managed object using an ID that can distinguish each managed object defined below. For example, in the case where there is ID01 for managed object A and ID02 for managed object B, there may be related persons A to C for managed object A and related persons B to D for managed object B. Here, related persons B and C overlap for managed object A and managed object B, but such overlap may or may not exist.

3. Functions of the System According to an Embodiment Next, functions of the system according to an embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing a specific example of functions of the system according to an embodiment. The system according to an embodiment may have all the functions described below, or may have some of the functions.

In addition, in the following, the functions are described separately for ease of understanding, but in terms of implementation, there is no need for each function to be implemented individually for each unit, and multiple functions may be implemented by one implementation unit, one function may be implemented by multiple implementation units, or multiple functions may be implemented by multiple implementation units in units different from the unit. For example, when multiple information processing devices constituting a system according to one embodiment have the following multiple functions, one information processing device may have one or more functions exclusively, or one information processing device may have each part of one or more functions.

3.1. Authority Management Unit 31
The authority management section has a function of storing and managing various information issued by an authority issuing section, which will be described later.

The authority management unit may store and manage information related to owned authority (sometimes referred to as "ownership authority information" in the present application). In addition, within the system according to one embodiment, a person who has the authority to own an object may be referred to as an "owner."

Similarly, the authority management unit may store and manage information related to the authority to use (sometimes referred to as "usage authority information" in the present application documents). Also, within the system of one embodiment, a person who has the authority to use an object may be referred to as a "user."

Similarly, the authority management unit may store and manage information related to the authority to be exchanged (sometimes referred to as "exchange authority information" in the present application). Also, within the system according to one embodiment, a person who has the authority to request acquisition of ownership of an object may be referred to as an "exchange authority holder."

Similarly, the authority management unit may store and manage information related to the authority to receive dividends through investment (sometimes referred to as "investment authority information" in the present application documents). Furthermore, within a system according to one embodiment, a person who has the authority to invest in a target and receive dividends may be referred to as an "investment right holder." Note that in the present application documents, an investment right holder is referred to as an investment right holder in the sense that the person has the right to receive dividends, and does not mean a person who has the right to make an investment.

In addition, in this application document, "rights information" is sometimes used as a higher concept than ownership rights information, use rights information, exchange rights information, and investment rights information. Furthermore, a person who has a relationship with the subject, such as an owner, use rights holder, exchange rights holder, or investment rights holder, is sometimes used as a higher concept than "related person." Furthermore, the subject of the rights information is sometimes called a "managed object." The managed object may be various things. The managed object may be a tangible object or an intangible object. Furthermore, the managed object may be movable property or real estate. Furthermore, movable property may be a specified movable property or an unspecified object.

The ownership authority information may be stored and managed in the authority management unit in association with an ID related to the ownership authority information, information indicating the ownership authority, information indicating one or more owners, and/or information indicating the managed object that is the subject of the ownership. For example, the ownership authority information may include an ID related to the ownership authority information, information indicating the ownership authority, information indicating one or more owners, and/or information indicating the managed object that is the subject of the ownership. The ownership authority information may also be associated with information related to the managed object, such as including information related to the managed object. For example, if the managed object is a vehicle, the information related to the managed object may be the manufacturer of the managed vehicle, the manufacturing date of the managed vehicle, options attached to the managed vehicle, information related to accidents and repairs for the managed object, and/or the date of the next vehicle inspection for the managed object. The ownership authority information being associated with the information related to the managed object has the advantage of making it easy to access the information about the managed object.

Similarly, the usage authority information may be stored and managed in the authority management unit in association with an ID related to the usage authority information, information indicating the authority to use, information indicating one authorized user, the expiration date during which the authority to use is valid, information indicating the person who issues the usage authority information, and/or information indicating the managed object that is the subject of use. For example, the usage authority information may include an ID related to the usage authority information, information indicating the authority to use, information indicating one authorized user, information indicating the person who issues the usage authority information, and/or information indicating the managed object that is the subject of use. Note that the information indicating the person who issues the usage authority here may actually be the one who grants the usage authority, or may be the one who permits the issuance of the authority.

Similarly, the exchange authority information may be stored and managed in the authority management unit in association with an ID related to the exchange authority information, information indicating the authority to exchange, information indicating one exchange authorized party, the expiration date for which the authority to exchange is valid, information indicating the person who issues the exchange authority information, and/or information indicating the managed object that is the subject of the exchange. For example, the exchange authority information may include an ID related to the exchange authority information, information indicating the authority to exchange, information indicating one exchange authorized party, the expiration date for which the authority to exchange is valid, and/or information indicating the managed object that is the subject of the exchange.

Similarly, the investment authority information may be stored and managed in the authority management unit in association with an ID related to the investment authority information, information indicating the authority to invest and receive dividends, information indicating one investor, information related to the investment amount, and/or information indicating the target of the investment. For example, the investment authority information may include an ID related to the investment authority information, information indicating the authority to invest and receive dividends, information indicating one investor, information related to the investment amount, and/or information indicating the target of the investment. Here, the information indicating the target of the investment may be a specific person or a specific organization, or may be a managed object held by a specific person or organization. As there is a specific person or organization, the target of the investment may be one or more as long as it can be specified. For example, it may be an entity that holds a managed object such as a specific corporation, association, or partnership (such as an anonymous partnership), or it may be the managed object itself, or it may be both. For example, the investor forms an anonymous partnership, and one or more specific managed objects held by the anonymous partnership may be the target of the investment. In this case, the information indicating the target of the investment may only include information identifying the anonymous partnership, or may include information identifying the anonymous partnership and information identifying the specific assets held by the anonymous partnership. Furthermore, the information regarding the investment amount may be the investment amount or the investment rate.

The authority management unit may store and manage the authority information in various data formats. In addition, the authority management unit may store some or all of the ownership authority information, usage authority information, exchange authority information, and contribution authority information in the same data structure or in different data structures.

For example, the authority management unit may store and manage each piece of authority information using a predetermined data structure. For example, the data structure may be in the form of a token. The token may not be a security token, and may be a security token. If the token is protected by security, it has a tamper-proof function. In particular, when a token having a tamper-proof function stores information related to authority, the reliability of the retention of such information related to authority is improved, and there is an advantage that the highly valuable information of authority can be safely stored. For example, a security token of a blockchain may be used as the token. That is, in this case, the ownership authority information, the usage authority information, the exchange authority information, and the contribution authority information may each be a security token or may include a security token. In this way, each piece of authority information using a security token may be called an ownership token, a usage authority token, an exchange authority token, and a contribution authority token. In this case, there is an advantage that transparency can be achieved while preventing tampering, and the trust of the parties involved can be improved. In this application document, the blockchain may be Ethereum.

The authority management unit may store the ownership authority information, for example, as shown in FIG. 4. The ownership authority information may include an authority ID that can distinguish a security token, an ownership indicating an authority type, one or more owners who own a specific vehicle as a related party, information indicating a specific vehicle as a managed object, and vehicle-related information for the specific vehicle. In this way, the ownership authority information as one security token may be associated with one physical managed object, and there is an advantage that information about the one physical managed object can be safely stored. Note that, for example, when a blockchain security token is used, the one or more owners may use MultiSig to realize management of multiple owners. On the other hand, for example, when a token that is not a security token is used in a blockchain, the one or more owners may use ERC721. In addition, the ownership authority information may include a user who rented the specific vehicle as a lessee only when the specific vehicle is being rented, that is, from the start of the rental to the end of the rental, and the scheduled end time of the rental at the start of the rental. In this case, there is an advantage that the current renter of the vehicle can be identified by accessing the security token for one specific vehicle. As described above, the vehicle-related information has the advantage that information about a specific vehicle can be accessed by including the information. The authority ID may be set for each type of authority, or may be set as an ID as a security token regardless of the type of authority.

The authority management unit may store the use authority information as shown in FIG. 5. The use authority information may include an authority ID that can distinguish security tokens, a use right indicating the type of authority, a user who has the use right as a related party, information indicating the type of vehicle as a managed object, an expiration date that is a period during which the use right can be used, a specific owner who issued the use right, and others. In this way, the use authority information as one security token may be associated with a specific type of managed object, and there is an advantage that information about such a specific type of managed object can be safely stored. When the use authority information has information indicating the type of vehicle as a managed object, the use right means the authority to use a specific type of vehicle, not a specific vehicle, as the use right, and there is an advantage that the scope of use can be expanded. In addition, since an expiration date is set, there is an advantage that the vehicle is not managed indefinitely, but is managed efficiently. In addition, there is an advantage that the issuer information makes it clear which owner the use right is for, and it is possible to determine the settlement of the fee for the use of the vehicle. The authority ID may be set for each type of authority, or may be set as an ID as a security token without distinguishing between types of authority.

The authority management unit may store the exchange authority information as shown in FIG. 6. The exchange authority information may include an authority ID that can distinguish security tokens, an exchange authority indicating the type of authority, an exchange authority holder who has the exchange authority as a related party, an expiration date when the authority to exchange is valid, information indicating the type of vehicle as the managed object, a specific owner who issued the exchange authority, and others. In this way, the exchange authority information as one security token may be associated with a specific type of managed object, and there is an advantage that information about such one specific type of managed object can be safely stored. When the exchange authority information has information indicating the type of vehicle as the managed object, the exchange authority means an authority that can be exchanged for ownership of a specific type of vehicle, not a specific vehicle, as the exchange authority, and there is an advantage that the scope of the exchange can be expanded. In addition, since an expiration date is set, there is an advantage that the management of the vehicle is not indefinite, and efficient management of the vehicle is possible. In addition, there is an advantage that the ownership holder for which the exchange authority is for is made clear by having the issuer information. The authority ID may be set for each authority type, or may be set as an ID as a security token without distinction of authority type.

The authority management unit may store the investment authority information as shown in FIG. 7. The investment authority information may include an authority ID that can distinguish security tokens, an investment right indicating an authority type, an investor who has the investment right as a related party, one or more vehicle IDs as information indicating the managed object, dividend conditions for the investment right, a specific owner who issued the investment right, and others. In this way, the investment authority information as one security token may be associated with one or more specific managed objects, and there is an advantage that information about such one or more specific managed objects can be safely stored. Although an example of one or more specific vehicles is shown as the managed object, it may be a specific type of vehicle. In addition, instead of the managed object, the investment may be information that specifies the assets held by a specific SPC. In this case, the target of the investment is not a rented vehicle but a specific asset held by the SPC, and there is an advantage that the present system can be used for assets other than vehicles. The authority ID may be set for each authority type, or may be set as an ID as a security token without distinguishing between authority types.

Although the above shows examples of each piece of authority information, the present invention is not limited to these. In particular, there may be multiple pieces of each piece of authority information. In other words, if there are multiple managed objects, there may be the same number of security tokens related to the owned authority information corresponding to each physical managed object. Furthermore, there may be as many security tokens related to the usage authority information as there are usage rights issued. Similarly, there may be as many security tokens related to the exchange authority information as there are exchange rights issued. There may be a security token related to the investment authority for each range of investment.

In addition, in the above, an example of storing authority information using a security token is shown, but the invention is not limited to such technical means. Authority information may be stored in a general database in combination with the above-mentioned security token or instead of the security token. In this case, a data structure for each piece of authority information may be used, such as a token for each piece of authority information, or the authority information may be managed in a general relational database or distributed processing database. When using such a database, the information may be mutually referenceable and may be mutually searchable. For example, for a certain managed object, it may be possible to search for the owner, user, investor, and exchange owner related to the managed object, and vice versa.

In addition, the authority management unit of the system according to one embodiment may indirectly store and manage each piece of authority information by storing the actual state of each piece of authority information in an information processing device outside the system according to one embodiment, and storing and managing only an ID associated with each piece of authority information and capable of accessing each piece of authority information.

Although the information related to the authority information has been described here, the authority management unit may store and manage other information in addition to the above.

The authority management unit may also be able to manage a specific security token from another information processing device by associating the ID of a security token that stores such ownership-related information from another information processing device.

The location where the authority management unit stores the information may be a storage technical means within the information processing device. Such storage technical means may be, for example, various storage means within the information processing device, such as a register, caches such as L1, L2, and L3, a hard disk, volatile memory such as DRAM or SRAM, non-volatile memory, or a hard disk drive.

3.2. Authority issuing unit 32
The authority issuing unit has a function of generating each of the authority information, such as ownership authority information, usage authority information, exchange authority information, and/or contribution authority information. Note that the process of issuing various authority information may include a process of generating various authority information.

The authority issuing unit may generate each of the authority information, such as ownership authority information, usage authority information, exchange authority information, and/or contribution authority information, when certain conditions are met.

For example, the authority issuing unit may generate ownership authority information when the owner acquires information indicating that the owner has begun ownership of the managed object. In other words, the specified condition may be that information indicating that ownership has begun has been acquired. The information indicating that ownership of the managed object has begun may be, for example, information indicating that the owner has purchased the managed object, that legal ownership procedures for the managed object have begun, that the legal ownership procedures have been completed, etc.

The authority issuing unit may also generate usage authority information when a usage right holder acquires a usage right. That is, the specified condition may be that information on acquiring the usage right of the managed object has been acquired. The information on acquiring the usage right of the managed object may be, for example, information on an investment right holder obtaining the usage right by satisfying a dividend condition, or information on an owner of the managed object issuing the usage right, etc.

The authority issuing unit may generate exchange authority information when the exchange authority holder acquires information on the acquisition of exchange authority for the managed object. That is, the predetermined condition may be that information on the acquisition of exchange authority for the managed object has been acquired. The information on the acquisition of exchange authority for the managed object may be, for example, information on the acquisition of exchange authority in exchange for a usage right, or information on the purchase of an exchange right. When the authority issuing unit issues exchange authority information in exchange for usage right information, it may perform processing to invalidate the usage right information for the exchanged usage right. This processing has the advantage of preventing a state in which usage rights are excessively generated. The processing to invalidate such usage right information may be processing to delete the usage right information itself, processing to include information indicating invalidity in the usage right information, or processing to hold such usage right information but make it inaccessible.

For example, the authority issuing unit may generate investment authority information when an investment right holder acquires information on the investment made in the managed object. In other words, the specified condition may be that the investment information has been acquired. The investment information on the managed object may be, for example, information that the investment right holder has invested in the managed object.

The generation of each piece of authority information, such as ownership authority information, usage authority information, exchange authority information, and/or investment authority information, may include a process of generating a new data structure to be used as each piece of authority information, or may include a process of overwriting or rewriting information in an already existing data structure that is used as each piece of authority information.

3.3 Exchange unit 33
The exchange unit has a function of exchanging at least one of the pieces of information that is authority information. The exchange unit may have a rule for the exchange and a function for determining the rule for the exchange. The exchange unit may exchange only if the rule for the exchange is satisfied.

The exchange unit may exchange authority information with another authority information, or may exchange one authority information and the other not authority information. The former may be, for example, an exchange of usage authority information and ownership authority information, an exchange of usage authority information and exchange authority information, an exchange of exchange authority information and ownership authority information, an exchange of contribution authority information and ownership authority information, an exchange of contribution authority information and usage authority information, etc. The latter may be an exchange of ownership authority information and a value, an exchange of usage authority information and a value, an exchange of exchange authority information and a value, an exchange of contribution authority information and a value, etc. The value may be, for example, cash, electronic money, virtual currency, or StableCoin. When a security token on the blockchain is used as the authority information and StableCoin is used as the value, there is an advantage that DVP settlement is possible without going through a specific intermediary organization.

The exchange unit may also perform processing to invalidate the exchanged authority information. For example, when the exchange unit issues ownership authority information in exchange for usage authority information, it may perform processing to invalidate the usage authority information for the exchanged usage rights. Such processing has the advantage of preventing a state in which usage rights are excessively generated. Similarly, when the exchange unit issues exchange authority information in exchange for usage authority information, it may perform processing to invalidate the usage authority information for the exchanged usage rights. The processing to invalidate such usage authority information may involve processing to delete the usage authority information itself, processing to include information in the usage authority information indicating that it is invalid, or processing to retain such usage authority information but make it inaccessible.

In addition, in the present application, "exchange" refers to exchanging the rights held by the related parties when a predetermined rule is satisfied, and may be realized by various means in terms of information processing. For example, in the case of an exchange between usage authority information and ownership authority information, the owner in the ownership authority information may be rewritten with the user in the original usage authority information to indicate that the user in the original usage authority information has acquired ownership of the managed object in the original ownership authority information, and the user in the usage authority information may be rewritten with the owner in the original ownership authority information to indicate that the owner in the original ownership authority information has acquired the right to use the managed object in the original usage authority information. Although rewriting is described here, the usage authority information and the ownership authority information may each be newly generated. In addition, the same processing may be performed for the exchange of other authority information. In the exchange with a value object, the holder of each value object may be similarly replaced with the related party in each of the above-mentioned authority information.

The rules for exchange may be determined uniformly within the system according to one embodiment, may be determined in advance for each managed object, or may be determined dynamically in the market section described below.

The rules for the exchange may use, for example, the number of pieces of authority information or the intention of the person having authority over the authority information. For example, when exchanging usage authority information and ownership authority information, a predetermined number of usage authority tokens and information indicating the intention of the user to exchange the predetermined number of usage authority tokens for an ownership token may be used as conditions for the exchange, and when the rules for the exchange of such conditions are satisfied, the usage authority information and the ownership authority information may be exchanged.

Similarly, when exchanging usage right information and exchange right information, a predetermined number of usage right tokens and information indicating the user's intention to exchange the predetermined number of usage right tokens for an exchange right token may be used as conditions for the exchange, and when the rules for exchanging such conditions are satisfied, the usage right information and exchange right information may be exchanged.

Similarly, when exchanging exchange authority information with ownership authority information, a predetermined number of exchange authority tokens and information indicating the exchange authority holder's intention to exchange the predetermined number of exchange authority tokens for an ownership token may be used as conditions for the exchange, and when the rules for exchanging such conditions are satisfied, the exchange authority information may be exchanged with the ownership authority information.

The same may also be true when exchanging investment authority information and ownership authority information, and when exchanging investment authority information and usage authority information.

3.4. Market providing section 34
The market provider has a function of managing the rules of exchange used by the exchange.

The market providing unit may have a function to support rules determined as exchange rules by a person who wishes to exchange authority information. For example, a person who has a usage rights token may be able to set an exchange rule for exchanging a predetermined number of usage rights tokens for an ownership token for a certain managed object. More specifically, the person may be able to set an exchange rule for exchanging a predetermined number of usage rights tokens for a certain type of vehicle for an ownership token for a vehicle of that type of vehicle.

The rule for such an exchange may be that there is an intention to exchange. For example, when exchanging a usage rights token and an ownership token, information indicating an intention to exchange the usage rights token held by the usage rights holder associated with the usage rights token for the ownership token may be used. In addition to the intention held by the usage rights holder, information indicating an intention to exchange the ownership token held by the ownership holder for the usage rights token may be used. As described below, the market providing unit is of a sales condition registration type and a matching type. In the sales condition registration type, the registration process may correspond to an intention to exchange, and the registrant may exchange without requesting information indicating an intention to exchange, or may exchange after explicitly requesting information indicating an intention. The information indicating an intention may include a signature on the security token.

4. The system according to one embodiment is an example applied to a vehicle. A manufacturer that manufactures a vehicle generally desires to make a profit by manufacturing and selling the vehicle. On the other hand, the social situation is shifting from a user who uses the vehicle by purchasing it and then owning it to a consumption type using the vehicle such as car sharing. In such a situation, manufacturers are also responding by car sharing, etc., but there is a need to off-balance because the balance sheet deteriorates if they hold too many assets. On the other hand, a vehicle user may use the vehicle in a consumption type while developing a desire to own it depending on the use, so a system is needed to support ownership by realizing the desire to own from such a consumption type. Therefore, in the system according to one embodiment described below, in consideration of such issues, the system mainly supports the use of the usage right token as a system, while also supporting the ownership token that supports the desire to own that arises in response to such use, and supports the bridge from these usage right tokens to the ownership token as a system. In addition, the system according to one embodiment described below also includes a configuration that supports the investor as a system from the viewpoint of further supporting such ownership. Furthermore, by using usage rights tokens as dividends to such investors, it is possible to encourage usage among investors who support ownership, thereby promoting usage itself while increasing the opportunities for investors themselves to stimulate their desire to own through usage.

FIG. 8 shows a configuration of a system according to an embodiment. The system according to an embodiment may be composed of a management system. Such a management system may be connected to an owner A terminal 001A, an owner B terminal 001B, an investor A terminal 002A, an investor B terminal 002B, an exchange right holder A terminal 003A, an exchange right holder B terminal 003B, a user right holder A terminal 004A, and a user right holder B terminal 004B via a network 000. Each terminal may access the management system and each token described below. The system according to this embodiment will explain an example of using an ownership token, a usage right token, an investment right token, and an exchange right token using a blockchain security token, but other data structures and other databases may be used. These tokens may be processed by functions such as the authority management unit, the authority issuing unit, the exchange unit, and/or the market provision unit described above. The functions of the authority management unit, the authority issuing unit, the exchange unit, and/or the market providing unit may be executed only in the management system, or may be executed only in each terminal, or may be executed both in the management system and each terminal. Executing in each terminal means, for example, that the authority management unit included in the software installed and executable in the owner A terminal can execute the function of the authority management unit for tokens such as ownership tokens, and the authority issuing unit included in such software can execute the function of the authority issuing unit for tokens such as usage right tokens, and the authority management unit included in the software installed and executable in the user B terminal can execute the function of the authority management unit for tokens such as ownership tokens, and the authority issuing unit included in such software can execute the function of the authority issuing unit for tokens such as usage right tokens, etc. In this way, the software installed in each terminal may execute the functions of the authority management unit, the authority issuing unit, the exchange unit, and/or the market providing unit, etc. Furthermore, the software installed in each of these terminals may use authentication by the parties using each terminal, and the tokens that can be accessed or used may be identified through authentication by the parties using each terminal. For example, to execute an exchange using an ownership token, a usage right token, an exchange right token, or an investment right token, authentication of the owner, usage right holder, exchange right holder, and investment right holder may be required, respectively. Similarly, when using a usage right token to use a vehicle or when paying dividends to an investment right holder, authentication of each usage right holder and investment right holder may be required. Processing may be performed only if these authentications are properly processed. Such authentication may be performed by a signature in each token. Furthermore, these functions may be performed, for example, by a smart contract itself that handles blockchain security tokens, such as an asset manager or sharing manager described below, or software that can be connected to such a smart contract.

Figure 9 illustrates the procedures for issuing ownership rights and registering vehicle numbers. When a manufacturer produces and sells a vehicle, it is necessary to register the number, so we will explain how to set the owner, including this process.

First, vehicle model registration 01 is a step in which a manufacturer registers a new vehicle model that is to be manufactured and sold in the system according to one embodiment. The vehicle model may be an ID. The vehicle model may or may not include minor variations. Such an ID may be registered in a database in the management unit.

Next, in application 02 and payment 03, a vehicle may be sold to an SPC (special purpose company), leasing company, or the like on a sales site that is associated with a system according to one embodiment and displays vehicle sales information. Although the following description mainly uses an SPC, the organization that owns the vehicle may be any entity. A system according to one embodiment may acquire order information obtained from such a sales site. Then, in response to such an order, when an SPC or the like purchases a vehicle and makes a payment, a system according to one embodiment may issue an ownership token.

Next, in vehicle registration 04, legal procedures for using the vehicle may be carried out. For example, a purchaser such as an SPC may register the number at a transportation bureau. Here, the information related to the number obtained for a specific vehicle may be stored in the ownership token described above. In this case, the ownership token may store the number itself, including a Japanese character string, or may store hashed information obtained by hashing the number using a specified hash function. In the latter case, since the number itself cannot be obtained from the ownership token, privacy can be respected, and at the same time, there is an advantage that a person related to the vehicle, such as an owner or a user, can, for example, take a picture of the number with a camera when using the vehicle, obtain the number, hash the number using the specified hash function described above, and verify the identity of the vehicle by comparing the hashed information with the ownership token described above.

The system according to one embodiment may be capable of processing registration failure response 05. This is processing for the case where the issued number is the same as that stored in a previously issued ownership token. In this case, since there is an error in one of them, it is necessary to check the information about the issued number and/or the previously issued ownership token. In this case, the information about the number in the previously issued ownership token may be the number itself, as described above, or the number hashed using a specified hash function, and it is sufficient if the information can be compared according to the stored information to check the past issuance status of the same number.

Figure 10 illustrates the procedure for creating and selling securities for a vehicle. This is the case where an SPC or other entity that has purchased a vehicle seeks investors by creating and selling securities.

First, registration 01 of the securities master may be performed. Here, an investment rights token may be generated based on the ownership token for the specific target vehicle. The system according to one embodiment may check the ownership token to see if an ownership token exists for the specific vehicle, if information indicating the owner is stored in the ownership token, and if the ownership token is linked to other securities.

Next, dividend condition registration 02 may be performed. Dividend conditions related to the investment may be associated with the investment token. The investment token may also store the dividend conditions. The dividend conditions may be, for example, a dividend in cash and/or a dividend of the right to use the vehicle associated with the investment token. The dividend in cash may specify a payment in StableCoin. The investment token may also store information indicating the vehicle that is the subject of the investment. The vehicle that is the subject of the investment may be a specific vehicle, a specific number of vehicles, or a specific model. In the case of a specific vehicle or a specific number of vehicles, the investment token may hold information that specifies the vehicle. In the case of a specific model, the investment token may store information that specifies the specific model.

Next, sales conditions registration 03 may be performed. Here, information regarding investment, including dividend conditions, etc., may be included in the investment solicitation.

Finally, application/settlement 04 may be performed. Here, when an application is made from an investor, an investment rights token is issued to the investor. In response to an application or cancellation of an application, the asset manager may deposit the investor's funds to the asset manager or return them to the investor from the deposit. In response to the issuance of the investment rights token, the asset manager may transfer money from the deposit to the SPC or securities company.

Next, FIG. 11 illustrates the procedures for registering and selling the right to use a prepaid card for a vehicle. An SPC or the like that holds ownership of the vehicle may make the above-mentioned investment to fund the purchase of the vehicle and/or issue the right to use the prepaid card.

First, registration of usage rights 01. Instead of issuing contribution rights tokens, the SPC etc. issues usage rights tokens. The system according to one embodiment generates one or more usage rights tokens. The one or more usage rights tokens may be directly or indirectly associated with the ownership token. The ownership rights token is associated with a specific vehicle using information related to a unique vehicle number, while the one or more usage rights tokens may be associated with a specific vehicle model, which is a higher-level concept of the specific vehicle. This is because if the usage rights token is associated with a specific vehicle in the same way as the ownership rights token, it becomes a usage right for the specific vehicle, and it is possible that it may be difficult to use the specific vehicle, for example, when a user who has purchased the usage rights moves. In addition, it is considered that there will be no inconvenience in use for some users as long as the vehicle is the same type, even if it is not a specific vehicle with the same number.

The range of specific vehicle models may be determined from various perspectives, but may be, for example, a range that would result in the same rental cost for vehicle rentals such as car sharing or rental cars. For example, minor changes due to differences in serial numbers or manufacturing dates usually result in the same rental price for vehicles, so the same vehicle model may be used. On the other hand, if a vehicle is equipped with specific options that are not easily removable and has a different rental cost set for renting the vehicle, the vehicle may be a different vehicle model. When vehicle models are set in this way, there is an advantage that information tailored to the site where the vehicle is rented can be stored in the usage rights token, making the terms of use clear.

In addition, in registration 01 of the usage rights, similar to the case of the contribution rights token, the system according to one embodiment may confirm that an ownership token exists for a specific vehicle, that information indicating the owner is stored in the ownership token, and that the ownership token is linked to other securities.

Next is sales condition registration 02. Here, the sales conditions for the usage right may be set, for example, the specific vehicle model mentioned above, the expiration date, the cost to purchase one usage right, the cost to purchase multiple usage rights, etc. Such a usage right may be a disposable type that cannot be used again once it has been used. In another embodiment, the usage right may be a type that can be used without conditions within a specified period, like a commuter pass.

Next is application/settlement 03. Here, the investor may be able to apply for or cancel the purchase of usage rights via the sales site. When an application is made by an investor, a usage rights token is issued to that investor. In response to an application or cancellation of an application, the asset manager may deposit the investor's funds to the asset manager or return them to the investor from the deposit. In response to the issuance of the usage rights token, the asset manager may transfer money from the deposit to the SPC.

Figure 12 illustrates the procedure for using a vehicle. As described above, an investor may be granted a usage right token as a dividend, and a usage right holder may purchase a usage right from an investor, which allows the user to use the usage right.

First, prior to use, in fee table registration 01, a usage fee table may be registered for each vehicle type described above. The system according to one embodiment may be provided with a usage fee table and may be able to specify a specific usage fee corresponding to the vehicle being used. Such usage fees may be set for each vehicle type. The range of vehicle types is as described above.

In reservation 02, a user may make a reservation for a specific vehicle type on a specific date in a vehicle rental system. A vehicle may be reserved from a vehicle rental system such as a car sharing site or a rental car, and the system according to an embodiment may provide such a vehicle rental system with a usage fee and the type and number of vehicles available for reservation associated with a schedule for which reservations can be made. At the time of this reservation, a check may be made as to whether the user has the right to use the vehicle.

More specifically, the system according to one embodiment may obtain, via the vehicle rental system, information identifying the user who wishes to reserve a vehicle, the type of vehicle the user wishes to reserve, and the planned use date (including the period of use) for the user's reservation, and compare it with the usage rights token. That is, the system may determine that a usage rights token exists that is associated with a user who matches the information identifying the user, that the usage rights token is for the vehicle type the user wishes to reserve, and that the planned use date and the end of the planned period for the user's reservation are within the validity period of the usage rights token, and may execute the reservation only if these conditions are met.

On the other hand, a vehicle may be reserved even if the user does not have the right to use the vehicle or does not use the right to use the vehicle. In this case, the reservation may be made without checking whether the user has the right to use the vehicle.

The vehicle rental system may be a part of the system according to an embodiment, or may be an external system that can simply be connected to the system according to an embodiment. The vehicle rental system may allow users to input information such as reservations and start of use from a homepage accessible on the Internet.

In use 03, the user starts using the reserved vehicle model on the reserved date and time. At the start of use, the user may input information about the start of use into the vehicle rental system described above, or may input information about the start of use into an IoT device at a location that can connect to the vehicle rental system and where the vehicle can actually be provided.

When a user uses a usage right, the system according to one embodiment obtains information identifying the user, information indicating the specific vehicle to be used, and the date of use (including the period of use) via the vehicle rental system, and compares it with the usage right token as described above. That is, it may be possible to start usage only if it is determined that a usage right token associated with a user matching the information identifying the user exists, that such usage right token is a usage right token for the vehicle type that the user wishes to reserve, and that the planned usage date and the end of the planned usage period for the user's reservation are within the validity period of the usage right token.

The current user may also be registered in the ownership token. For example, a system according to one embodiment may store information identifying the user using the vehicle in an ownership token associated with a particular vehicle being used. Similarly, the ownership token may store the period of use of the user using the vehicle. This allows information about the current vehicle user and the period of use to be obtained by accessing the ownership token.

When the user's use ends, the system according to one embodiment may invalidate the usage rights, assuming that the usage rights have been used. For example, information indicating that the usage rights token is invalid may be stored in the usage rights token, the usage rights token may be deleted, or access to the usage rights token may be disabled.

Next, in post-use settlement 04, a settlement process is performed for the amount of the usage right due to the use of the vehicle. In one embodiment, the system may perform separate processes for when the usage right is used and when the usage right is not used. Furthermore, when the usage right is used, the process may be different depending on whether the usage right issued by the owner who owns the vehicle is used or the usage right not issued by the owner who owns the vehicle is used.

First, when a usage right token issued by an owner of a vehicle is used, there is no need to accumulate sales information from such use. This is because the sales from the purchase of the usage right are obtained at the time the usage right token is issued. For example, in one embodiment, when a usage right token is used, if the information indicating the issuer stored in the usage right token matches the owner stored in the ownership token for the specific vehicle used when the usage right token is used, the system does not need to store the amount of sales from the use of the usage right in association with the owner.

On the other hand, when a usage right token is used, if the information indicating the issuer stored in the usage right token does not match the owner stored in the ownership token for the specific vehicle used when the usage right token is used, the owner may be able to claim the amount of the value of the usage right from the issuer of the usage right token. For example, the amount of the value of the usage right may be determined and stored as a charge to the issuer of the usage right in association with the owner of the vehicle. The amount of the value of the usage right may be calculated using a usage fee table related to the issuer. For example, the amount of the value of the usage right may be determined using the type of vehicle in the usage right token and the time period used in the usage fee table related to the issuer that issued the usage right token. This is an amount based on the purchase by the usage right owner, since the usage right owner who purchased the usage right token purchases the usage right based on the usage fee table related to the issuer that issued the usage right. If the amount of the value of the usage right is higher than the amount that would be charged if the owner were to rent the same vehicle on that date and time, the owner of the vehicle that rented the vehicle may be able to pay the difference to the usage right holder. For example, the owner of the vehicle that rented the vehicle may pay the difference to the usage right holder in StableCoin or the like. On the other hand, if the amount of the value of the usage right is lower than the amount that would be charged if the owner were to rent the same vehicle on that date and time, the owner of the vehicle that rented the vehicle may not be able to claim the difference from the usage right holder. This is because, from the perspective of the usage right holder, it means that the expenses will be different due to the fact that the owner happens to be different.

On the other hand, when the user does not use the usage right, the vehicle may be available for use by using various payment methods such as cash, credit card, electronic money, etc. In this case, the amount paid by such payment method may be added as sales information to the owner who owns the vehicle, and in this case or in other cases, the usage fee may be collected directly or indirectly from the user without going through the owner of another vehicle.

Figure 13 illustrates the procedure for dividends. As mentioned above, dividends to contributors can be cash and/or usage rights. Here, cash may or may not be paid in StableCoin.

First, in the case 01 where StableCoin is used and sales are generated from vehicle rentals such as car sharing or rental cars, the SharingManager collects sales information on such sales. This sales information may or may not be added to the sales information for each use of the vehicle, depending on the issuer of the usage rights token, as described below. The information added to the sales may be used to deposit a predetermined percentage of the sales to the asset manager according to the dividend conditions. Then, at the time of the predetermined dividend, a predetermined dividend may be paid to the investor who invested in the vehicle based on the deposited information. Here, the target of the dividend may be associated with the vehicle that is the target of the investment. For example, when multiple specific vehicles or vehicles of a specific type are the target of the investment, the dividend conditions may be applied to the corresponding sales of multiple specific vehicles or vehicles of a specific type, and the deposit to be paid may be determined. The asset manager may issue StableCoin or usage rights tokens to the investor based on the dividend conditions using the investment rights token. That is, the asset manager may issue StableCoin or usage rights tokens to the investment rights holders stored in the investment rights tokens associated with multiple specific vehicles or specific types of vehicles that are eligible for dividends, based on the dividend conditions stored in the investment rights tokens. In the case of StableCoin, it is sufficient to issue StableCoin to the investment rights holders, and in the case of usage rights tokens, information indicating the investment rights holders as usage rights holders may be stored in the usage rights token, and the type of vehicle related to the investment rights token, the expiration date of the usage rights token, etc. may be stored in the usage rights token.

In case 02 where StableCoin is not used, instead of issuing StableCoin, dividends may be paid by bank transfer, etc. If a usage rights token is issued, the same procedure as described above may be followed.

Figure 14 illustrates the procedures for a buying and selling market. A buying and selling market can be executed in various ways, but here we will explain two ways: a selling condition registration type 01 and a depth information type 02.

First, the sales condition registration type 01 may allow the sale of a usage right, an exchange right, and/or an ownership right according to the sales conditions determined and registered by the vehicle owner such as an SPC. For example, the usage right token, the exchange right token, and the ownership right token may be purchased with a value indicating a predetermined amount such as cash, StableCoin, a credit card, and/or electronic money. Note that when exchanging authority information or a token with a value, that is, when selling authority information or a token for a value, when information is acquired that a value has been obtained from, for example, A, the holder of such authority information or token may be set to A, and the sale may be made. In addition, the exchange right token and the ownership right token may be sold in exchange for a predetermined usage right token. Regarding the latter, for example, one exchange right token for a specific vehicle model may be exchangeable for a predetermined amount of usage right tokens for such a vehicle model. In this case, a user who has a predetermined amount of usage right tokens for one vehicle model may apply for purchase on a sales site to indicate a willingness to exchange the usage right tokens for an exchange right token for the vehicle model related to the usage right token, thereby storing information indicating the usage right holder in the exchange right token, and setting the user as the holder of the exchange right token. Similarly, one ownership right token for a specific vehicle may be exchangeable for a predetermined amount of usage right tokens for a vehicle model including the specific vehicle. In this case, a user who has a predetermined amount of usage right tokens for the same vehicle model as the vehicle related to the ownership right token may apply for purchase on a sales site to indicate a willingness to exchange the usage right tokens for an ownership right token for a specific vehicle model of the vehicle related to the usage right token, thereby storing information indicating the usage right holder in the usage right token, and setting the user as the holder of the usage right token. In addition to the amount of tokens, the condition for what can be exchanged may be an expiration date, a vehicle model, or the like.

In this way, a user with a usage rights token may develop a desire to own a certain type of vehicle by using that vehicle. If the user has a large number of usage rights tokens, there is an advantage in that the user can exchange the usage rights tokens for ownership tokens and become the owner, thereby satisfying the desire to own the vehicle. In particular, even if the investment rights holder of a vehicle originally invested in the vehicle, they often feel attached to the object of their investment, and by receiving the usage rights token as a dividend and actually using the vehicle using the usage rights token, they may further understand the vehicle in which they invested, and their attachment may increase, which may ultimately give rise to a desire to own it. Therefore, there is an advantage in that the investment rights holder can satisfy their desire to own by using the usage rights token to obtain an ownership token.

In addition, ownership tokens are owned by the vehicle, which can lead to issues such as management, but exchange rights tokens have the advantage that they can be exchanged for vehicle ownership tokens at any time without causing such management issues.

In the case of depth information type 02, each user, owner, and exchanger may determine the buying and selling conditions for the tokens they own, and exchange may be possible for those that meet the buying and selling conditions. For this reason, the system according to one embodiment may provide a token market in which user, owner, and exchanger can participate, and in such a market, it may be possible to search for and determine a buying and selling partner by matching the buying and selling conditions. Such buying and selling conditions may specify the relationship between each exchangeable token, such as a usage right token, an ownership right token, and an exchange right token, or the relationship between these tokens and the above-mentioned value item, such as StableCoin or cash. The system according to one embodiment may have a function to acquire information to be matched and a function to match such information. The information to be matched may be a managed object, and in the case of a vehicle, for example, it may be the vehicle model. It may also be specified by the expiration date or the number of usage rights.

Figure 15 is a flow diagram that briefly illustrates each of the steps described above. However, it is not necessary for each of the flows below to be performed in the order described below, nor is it necessary for all of the steps to be performed. In particular, the ownership token, usage rights token, contribution rights token, and exchange rights token may each be issued at an appropriate time, and it is not necessary for all of these tokens to be issued. These tokens are merely prerequisites for the exchange between tokens, and issued tokens may be exchanged when conditions are met.

The authority issuing unit generates an ownership token when certain conditions are met using information identifying the owner, information identifying the vehicle to be managed, etc. (Step 1).

The authority issuing unit generates an investment token for each of one or more investment holders who have made an investment in relation to the managed object, using information identifying the investment holder, information identifying the type of vehicle to be managed, information related to the investment, etc., when certain conditions are met (step 2).

When the dividend conditions for the investment right holder are met or when the authority issuing unit obtains information to purchase a usage right token, it generates a usage right token using information identifying the usage right holder, information identifying the type of vehicle to be managed, the expiration date, etc. (Step 3).

The authority issuing unit generates an exchange right token for the exchange right holder when certain conditions are met, using information identifying the exchange right holder, information identifying the type of vehicle to be managed, the expiration date, etc. (Step 4).

Then, the exchange unit exchanges between ownership tokens, contribution rights tokens, usage rights tokens, exchange rights tokens, items of value, etc. that satisfy predetermined rules (step 5).

The invention examples described in the examples of this application document are not limited to those described in this application document, and needless to say, can be applied to various examples within the scope of the technical concept.

The processes and procedures described in this application document may be realizable not only by those explicitly described in the embodiments, but also by software, hardware, or a combination of these. The processes and procedures described in this application document may be implemented as computer programs and executed by various computers. These computer programs may be stored in a storage medium. These programs may be stored in a non-transient or temporary storage medium.

REFERENCE SIGNS LIST 10 Information processing device 11 Arithmetic unit 12 Storage device 13 Input device 14 Display device 15 Bus 16 Communication device 000, 17 Network 01 to 03 Related party terminal 001 Owner's terminal 002 Contribution right holder terminal 003 Exchange right holder terminal 004 Use right holder terminal 010 Management system 011 Manager terminal

Claims (28)

An acquisition unit that acquires information related to an authority to use a first object stored in association with a first related person;
an association storage unit that is capable of storing the first related party and information related to the authority to own the first object in association with each other based on the first related party and information related to the authority to use the first object;
A system comprising: The first object indicates an unspecified object of the same kind specified by the same rental amount,
The system of claim 1 . The association storage unit
The first party and information regarding the authority to exchange the first object can be stored in association with each other using information regarding the authority to use the first object and the first party;
The first party and information regarding the authority to own the first object can be stored in association with each other using information regarding the authority to exchange the first object with the first party.
A system according to any one of claims 1 to 2. The association storage unit uses information related to the first related party and the authority to use a predetermined number of the first targets,
The first related person and information related to the authority to own the first object can be stored in association with each other.
A system according to any one of claims 1 to 3. The association storage unit uses information indicating an intention of the first related party to exchange information related to the authority to use the first object with information related to the authority to own the first object.
A system according to any one of claims 1 to 4. The association storage unit
The first party and the information on the authority to exchange the first object can be stored in association with each other using information indicating an intention of the first party to exchange information on the authority to use the first object and information on the authority to exchange the first object;
the first party, the information regarding the authority to exchange the first object, and the information regarding the authority to own the first object can be stored in association with each other using information indicating an intention of the first party to exchange information regarding the authority to exchange the first object and information regarding the authority to own the first object;
A system according to any one of claims 1 to 5. The information regarding the right to own the first object is stored in a security token.
A system according to any one of claims 1 to 6. The one security token is capable of storing a plurality of pieces of information indicating an owner of the first object.
The system of claim 7. The one security token is capable of storing information indicating one authorized user who is using the first object.
9. A system according to claim 7 or 8. The information regarding the authority to use the first object can be stored in a security token in association with an expiration date during which the authority to use the first object can be exercised.
A system according to any one of claims 1 to 9. When the information on the authority to exchange the first object is issued in exchange for information on the authority to use the first object, the information on the authority to use the first object is invalidated.
A system according to any one of claims 1 to 10. The information on the authority to use the first object is issued based on information on the owner of the first object.
A system according to any one of claims 1 to 11. When the information on the authority to own the first object is issued in exchange for information on the authority to use the first object, the information on the authority to use the first object is invalidated.
A system according to any preceding claim. The association storage unit is capable of associating information indicating a contributor who has contributed in relation to the first object with information relating to the amount of contribution of the contributor to the first object and storing the information in a single security token.
A system according to any one of claims 1 to 13. The related note will be issued when the dividend conditions for the one investor are satisfied.
The information indicating the one contributor and the information indicating the authority to use the first object can be associated with each other and stored in one security token.
The system of claim 14. The association storage unit is capable of storing information identifying an anonymous association that owns the first target that is the target of the investment in the one security token.
The system of claim 14. The information regarding the authority to exchange the first object can be stored in a security token in association with an expiration date during which the authority to exchange the first object can be exercised.
17. A system according to any preceding claim. The first object indicates a particular vehicle type that will have the same rental price if the vehicle is rented;
18. A system according to any preceding claim. The association storage unit
The first party can be stored in association with information indicating the authority to own the first object by using information on the authority obtained by contributing to the first object and information on the authority to own the first object, the information being stored in association with the first party.
19. A system according to any preceding claim. The association storage unit
The first party can be stored in association with information indicating the authority to use the first object by using information on the authority obtained by contributing to the first object and information on the authority to use the first object, the information being stored in association with the first party,
20. A system according to any preceding claim. The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to own the first object and the object of value, the information being stored in association with the first party.
21. A system according to any one of claims 1 to 20. The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to use the first object, which is stored in association with the first party, and the object of value.
22. A system according to any preceding claim. The association storage unit
The first party and the object of value can be stored in association with each other using information related to the authority to exchange the first object stored in association with the first party and the object of value.
23. A system according to any preceding claim. The association storage unit
The first party and the object of value can be stored in association with each other using information on the authority obtained by contributing in relation to the first object, which is stored in association with the first party, and the object of value.
24. A system according to any one of claims 1 to 23. The system,
An acquisition step of acquiring information related to an authority to use a first object stored in association with a first related person;
an association storage step for storing the first related party and information related to the authority to own the first object in association with each other based on information related to the authority to use the first object;
How to do it. The system comprises a memory.
26. The method of claim 25. The system,
An acquisition means for acquiring information related to an authority to use a first object stored in association with a first related person;
an association storage means for storing the first related party and information related to the authority to own the first object in association with each other based on information related to the authority of the first related party and the authority to use the first object;
A program to function as a The system comprises a memory.
28. The program according to claim 27.