Information processing device, information processing method, storage medium and computer program product

Abstract

[Problem] To allow more appropriate confirmation of whether a data recording destination is a peer-to-peer type database or a storage unit other than a peer-to-peer type database. [Solution] An information processing apparatus is provided, the information processing apparatus comprising: a request unit that requests information about whether a data recording destination is a P2P database or a storage unit other than a P2P database for a plurality of different targets; and an output control unit that controls output of information obtained as a result of the request to a user.

Description

Technical Field

[0001] The present disclosure relates to an information processing device, an information processing method, and a program. Background Art

[0002] In recent years, services using peer-to-peer databases including blockchain data have been actively developed. By using services using peer-to-peer databases including blockchain data, it is possible to prevent falsification of data managed in the peer-to-peer database and ensure the authenticity of the data.

[0003] Patent document 1 discloses a file sharing system that can provide advantages of both peer-to-peer type and client-server (C / S) type. By using this system, a user can easily determine in which folder (storage unit) each data is stored in the peer-to-peer type or the C / S type.

[0004] Reference List

[0005] Patent Literature

[0006] Patent Document 1: JP 2006-11693 A Summary of the invention

[0007] Technical issues

[0008] However, using the technology of Patent Document 1, etc., the user himself cannot confirm the authenticity of the information about the registration destination of the data (hereinafter, for the purpose of description, also referred to as "registration destination information") provided from the system. Therefore, although there is a possibility that the registration destination information provided from the system may be forged, the user has to trust the registration destination information provided from the system.

[0009] Therefore, the present disclosure is proposed in view of the above situation, and the present disclosure provides a new and improved information processing device, information processing method and program that can more appropriately confirm whether the registration destination of data is a peer-to-peer type database or a storage unit other than the peer-to-peer type database.

[0010] Solution to the problem

[0011] According to the present disclosure, an information processing device is provided, which includes: a request unit, configured to request information about whether the registration destination of data is a P2P database or a storage unit other than the P2P database for multiple targets different from each other; and an output control unit, configured to control the output of information obtained as a result of the request to a user.

[0012] In addition, according to the present disclosure, there is provided an information processing method executed by a computer, the method comprising: requesting information about whether the registration destination of data is a P2P database or a storage unit other than the P2P database for multiple targets different from each other; and controlling the output of information obtained as a result of the request to a user.

[0013] Furthermore, according to the present disclosure, there is provided a program that causes a computer to realize: requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; and controlling output of information obtained as a result of the request to a user.

[0014] Advantageous Effects of the Invention

[0015] According to the present disclosure as described above, it is possible to more appropriately confirm whether the registration destination of data is a peer-to-peer type database or a storage unit other than the peer-to-peer type database.

[0016] Note that the above effects are not necessarily limitative. Together with or in place of the above effects, any of the effects described in this specification or other effects that can be understood from this specification can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 2 is a diagram illustrating an overview of blockchain data as one type of peer-to-peer database.

[0018] Figure 2 2 is a diagram illustrating an overview of blockchain data as one type of peer-to-peer database.

[0019] Figure 3 2 is a diagram illustrating an overview of blockchain data as one type of peer-to-peer database.

[0020] Figure 4 is a diagram illustrating a configuration example of an information processing system according to the present embodiment.

[0021] Figure 5 : is a block diagram showing a functional configuration example of the client device 100 according to the present embodiment.

[0022] Figure 6 : is a block diagram showing a functional configuration example of the server device 200 according to the present embodiment.

[0023] Figure 7 : is a block diagram showing a functional configuration example of the node device 300 according to the present embodiment.

[0024] Figure 8 : is a block diagram showing a functional configuration example of the storage device 400 according to the present embodiment.

[0025] Fig. 9 is a sequence diagram showing an example of the flow of processing performed by each device regarding providing data to a user and registering destination information.

[0026] Fig.10 is a diagram showing an example of a UI indicating registration destination information of data.

[0027] Fig.11 is a diagram showing an example of a UI indicating registration destination information of data.

[0028] Fig.12 is a diagram showing an example of a UI indicating registration destination information of data.

[0029] Fig.13 : is a diagram showing an example of a UI indicating registration destination information of data.

[0030] Fig.14 is a diagram showing an example of a UI indicating registration destination information of data.

[0031] Fig.15 is a diagram showing an example of a UI indicating registration destination information of data.

[0032] Fig.16 is a diagram showing an example of a UI indicating registration destination information of data.

[0033] Fig.17 is a diagram showing an example of a UI indicating registration destination information of data.

[0034] Fig.18 is a diagram showing an example of a UI indicating registration destination information of data.

[0035] Fig.19 is a diagram showing an example of a UI indicating registration destination information of data.

[0036] Fig. 20 is a diagram showing an example of a UI indicating registration destination information of data.

[0037] Fig.21 : is a diagram showing an example of a UI indicating registration destination information of data.

[0038] Fig. 22 is a diagram showing an example of a UI to be used to confirm registration destination information about data for a second target.

[0039] Fig.23 : is a diagram showing an example of a UI indicating history information about additional recording of data.

[0040] Fig.24 321 is a diagram showing an example of a UI to be used for registering data in the P2P database 321 .

[0041] Fig.25 321 is a diagram showing an example of a UI to be used for registering data in the P2P database 321 .

[0042] Fig.26 is a diagram showing an example of a UI indicating that data cannot be deleted.

[0043] Fig. 27 is a diagram showing an example of a UI indicating that data cannot be deleted.

[0044] Fig.28 3 is a diagram showing an example of a UI indicating that registration of data in the P2P database 321 is being performed.

[0045] Fig.29 3 is a diagram showing an example of a UI indicating that registration of data in the P2P database 321 is being performed.

[0046] Fig.30 3 is a diagram showing an example of a UI indicating that registration of data in the P2P database 321 is being performed.

[0047] Fig.31 is a diagram showing an example of a UI indicating that registration of data in the storage device 400 is being performed.

[0048] Fig.32 is a diagram showing an example of a UI indicating that registration of data in the storage device 400 is being performed.

[0049] Fig.33 1 is a block diagram showing a hardware configuration example of the information processing device 900 that realizes the client device 100 , the server device 200 , the node device 300 , or the storage device 400 according to the present embodiment. DETAILED DESCRIPTION

[0050] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that, in this specification and the drawings, the same reference numerals are used to denote structural elements that have substantially the same function and structure, and repeated explanation of these structural elements is omitted.

[0051] Note that the description will be provided in the following order.

[0052] 1. Overview of Peer-to-Peer Database

[0053] 2. Implementation Method

[0054] 2.1. Summary

[0055] 2.2. System Configuration Example

[0056] 2.3. Functional Configuration Example of Client Device 100

[0057] 2.4. Functional Configuration Example of Server Device 200

[0058] 2.5. Functional Configuration Example of Node Device 300

[0059] 2.6. Functional Configuration Example of Storage Device 400

[0060] 2.7. Processing Flow

[0061] 3. User Interface Example

[0062] 3.1. Example of UI indicating registration destination information of data

[0063] 3.2. Example of UI indicating confirmation result for second target

[0064] 3.3. Example of UI indicating history information about data addition

[0065] 3.4. Example of UI to be used to register data in the P2P database 321

[0066] 3.5. Example of UI indicating that data cannot be deleted

[0067] 3.6. Example of UI indicating that data registration in the P2P database 321 is being performed

[0068] 4. Hardware Configuration Example

[0069] 5. Conclusion

[0070] <1. Overview of Peer-to-Peer Database>

[0071] Before describing the embodiments of the present disclosure, first, an overview of a peer database will be described.

[0072] In the information processing system according to the present embodiment, a distributed peer-to-peer database distributed in a peer-to-peer network is utilized. Note that there is also a case where a peer-to-peer network is referred to as a peer-to-peer distributed file system. In the following description, there is a case where a peer-to-peer network is represented as a "P2P network", and a peer-to-peer database will be represented as a "P2P database". Examples of P2P databases may include blockchain data distributed in a P2P network. Therefore, first, an outline of a blockchain system will be described as an example.

[0073] like Figure 1 As shown, blockchain data is data including a plurality of blocks like a chain. In each block, one or two or more target data may be stored as a transaction (trade).

[0074] Blockchain data includes values ​​such as a hash value of the previous block and a random number. The hash value of the previous block is information for determining whether a block is a "correct block" that correctly continues from the previous block. The random number is information for preventing fraud in authentication using hashes, and forgery is prevented by using random numbers. Examples of random numbers may include, for example, a character string, a numeric string, data indicating a combination of a character string and a numeric string, and the like.

[0075] In addition, in the blockchain data, fraud is prevented by using an electronic signature using an encryption key provided to the data of each transaction. In addition, the data of each transaction is made public and shared throughout the P2P network. Note that the data of each transaction can be encrypted using an encryption key.

[0076] Figure 2 is a diagram showing aspects of registering target data by user A in a blockchain system. User A provides an electronic signature generated using a private key of user A to the target data to be registered in the blockchain data. Then, user A broadcasts a transaction including the target data provided with the electronic signature on the P2P network. In this way, it is guaranteed that the owner of the target data is user A.

[0077] Figure 3 is a diagram showing aspects of transmitting target data from user A to user B in a blockchain system. User A places user B's public key in a transaction by providing an electronic signature generated using user A's private key to the transaction. In this way, the target data is indicated to be transmitted from user A to user B. In addition, user B can obtain user A's public key from user A to obtain the target data provided with the electronic signature or encrypted when the target data is traded.

[0078] In addition, in the blockchain system, other target data can be placed in the blockchain data by utilizing, for example, side chain technology.

[0079] <2. Implementation Method>

[0080] The outline of the P2P database has been described above. Subsequently, embodiments of the present disclosure will be described.

[0081] (2.1. Summary)

[0082] First, an outline of an embodiment of the present disclosure will be described.

[0083] As mentioned above, in recent years, services using P2P databases including blockchain data have been actively developed. In addition, the authenticity of data managed by the P2P database can be guaranteed.

[0084] However, it is considered that due to processing performance (such as, for example, processing speed), storage capacity, operational constraints, etc., storage units other than P2P databases (such as, for example, databases, etc., including relational databases. Hereinafter, for descriptive purposes, also referred to as "other storage units") as well as P2P databases are also used to construct an information processing system.

[0085] When a P2P database and other storage units are used together in an information processing system, since the reliability (or authenticity) of registered data between the P2P database and other storage units is different, there are cases where users need to identify whether the registration destination of data is the P2P database or other storage units.

[0086] Here, using the technology of Patent Document 1, etc., the user can easily determine in which folder (storage unit) each data is stored in the peer-to-peer type or C / S type. However, using the technology of Patent Document 1, etc., the user himself cannot confirm the authenticity of the registration destination information of the data provided from the system. Therefore, although there is a possibility that the registration destination information provided from the system may be forged, the user has to trust the registration destination information provided from the system.

[0087] Therefore, in view of the above situation, the author of the disclosure has created a technology according to the disclosure. According to the disclosure, information about whether the registration destination of data is a P2P database or other storage unit can be requested for multiple targets different from each other, and the information obtained due to the request can be output to the user. In this way, the user himself can confirm the authenticity of the registration destination information of the data provided from the system. In other words, the disclosure makes it possible to more appropriately confirm whether the registration destination of data is a P2P database or other storage unit. The disclosure will be described in detail below.

[0088] (2.2. System Configuration Example)

[0089] The above has described the outline of the present embodiment. Figure 4 A configuration example of an information processing system according to the present embodiment is described.

[0090] like Figure 4 As shown, the information processing system according to the present embodiment includes a client device 100, a server device 200, a plurality of node devices 300 (in the figure, node devices 300a to 300d), and a storage device 400. In addition, the plurality of node devices 300 are respectively connected to a P2P network 500. In addition, the client device 100 is connected to the server device 200 via a network 600a, the server device 200 is connected to the node device 300a via a network 600b, and the server device 200 is connected to the storage device 400 via a network 600c.

[0091] Note that the configuration of the information processing system according to the present embodiment is not limited to Figure 4 For example, the number of each device constituting the information processing system may be changed appropriately. In addition, the server device 200 may be connected to a node device 300 other than the node device 300a.

[0092] Although the content of services that can be provided by the information processing system is not particularly limited, in this specification, the case where the information processing system provides management services such as student academic performance records (e.g., records of test results, total credits earned, qualifications obtained, etc.) and student activity records (e.g., records of club activities, student physical activities, attendance, etc.) to various educational institutions (such as, for example, nurseries, kindergartens, elementary schools, junior high schools, high schools, universities, graduate schools, cram schools, preparatory schools, and schools for obtaining qualifications) (hereinafter, for descriptive purposes, referred to as "academic performance and activity record service") will be considered as an example. That is, users who utilize the information processing system include teachers belonging to various educational institutions, etc., but are not limited to these. For example, users who utilize the information processing system may include students themselves, parents of students, any company that attempts to utilize students' academic performance records, etc.

[0093] It is assumed that, in the information processing system according to the present embodiment, data of higher importance requiring authenticity assurance is managed at the P2P database provided at the node device 300 , while other data is managed at the storage device 400 .

[0094] (Client Device 100)

[0095] The client device 100 is an information processing device to be used by a user who receives provision of academic performance and activity record services. For example, the user can obtain data on academic performance records or activity records of students registered in the P2P database or storage device 400 via the server device 200 by performing an input operation on the client device 100, and also identify whether the registration destination of the data is the P2P database or the storage device 400.

[0096] More specifically, in the case where the user performs an input operation on the client device 100 to request desired data, the client device 100 sends a request signal for requesting the data to the server device 200. The request signal is also a signal for requesting registration destination information about whether the registration destination of the data is a P2P database or a storage device 400. The server device 200, which has received the request signal, obtains the target data from the P2P database or the storage device 400 provided to the node device 300, and provides the data together with the registration destination information to the client device 100. The client device 100 provides the data and the registration destination information to the user via an output unit (such as, for example, a display device such as a display, a sound output device such as a speaker, a light source device such as a lamp, and a tactile presentation device such as an actuator), which serves as a user interface (hereinafter, for description purposes, also referred to as "UI"). In this way, the user can not only obtain the desired data, but also identify the registration destination information of the acquisition source of the data.

[0097] Furthermore, in the present embodiment, the user himself can confirm the authenticity of the registration destination information of the data provided from the server device 200. For example, the client device 100 requests the registration destination information for a target different from the above by the user performing a predetermined input operation.

[0098] Here, the "target" to which the client device 100 requests registration destination information indicates a node device 300 connected to the P2P network 500, a predetermined device that can access the node device 300 (such as, for example, a predetermined server device), predetermined software (such as, for example, a predetermined application programming interface (API)), etc.

[0099] That is, in the above, although the client device 100 requests the registration destination information for the node device 300a via the server device 200 (it can be understood that the target for requesting the registration destination information is the server device 200), through the subsequent input operation performed by the user, the client device 100 requests the registration destination information for a node device 300 different from the previous device (or a server device 200 different from the previous device). In this way, even in the case where the registration destination information previously provided to the client device 100 has been forged, the user can recognize the occurrence of forgery based on the registration destination information provided from the different target.

[0100] Hereinafter, a target for which the client device 100 requests registration of destination information via the server device 200 is defined as a “first target”, and a target different from the previous target for which the client device 100 subsequently requests registration of destination information is defined as a “second target”. Note that the target for which the client device 100 requests registration of destination information is not limited to the above example.

[0101] Here, the “registration destination information” according to the present embodiment is “information about whether the registration destination of the target data is a P2P database or the storage device 400”. Furthermore, the “registration destination information” (that is, “information about whether the registration destination of the target data is a P2P database or the storage device 400”) can be interpreted as including the concept of “information about whether the registration destination of the target data is a P2P database” or “information about whether the registration destination of the target data is the storage device 400”. Furthermore, in the case where there are multiple P2P databases in the information processing system (for example, in the case where there are multiple P2P networks 500), the “registration destination information” can be interpreted as including the concept of “information about which P2P database (or P2P network 500) is the registration destination of the target data”.

[0102] Here, the content of the registration destination information to be requested for the first target may be the same as or different from the content of the registration destination information to be requested for the second target. For example, the registration destination information to be requested for the first target may be "information about whether the registration destination of the target data is a P2P database or the storage device 400", while the registration destination information to be requested for the second target may be "information about whether the registration destination of the target data is a P2P database (whether the target data is actually registered in the P2P database)".

[0103] In addition, although it has been described above that the request for registration of destination information for the first target or the second target is performed based on an input operation performed by a user, the request method is not necessarily limited to this. More specifically, the request for registration of destination information for the first target or the second target may be performed based on a trigger other than an input operation performed by a user or may be performed automatically (or autonomously). For example, the request for registration of destination information for the first target may be performed by triggering a process performed by software running on the client device 100. In addition, in the case where the registration of destination information is provided from the first target, the client device 100 may automatically (or autonomously) request registration of destination information for the second target.

[0104] In addition, regarding “request to register destination information”, the request signal transmitted from the client device 100 does not necessarily include information indicating that the registration destination information is requested. For example, if the client device 100 acquires the registration destination information from the server device 200 as a result of the client device 100 transmitting a certain signal to the server device 200, it can be interpreted that “request to register destination information” is being executed.

[0105] Here, although it is basically assumed that the user who uses the client device 100 is an individual, the user is not limited thereto. For example, the user includes any organization or any group (such as, for example, a company, an association, and a circle).

[0106] Note that the type of the client device 100 is not particularly limited. For example, the client device 100 may be any device such as a general-purpose computer, a personal computer (PC), and a tablet PC. In addition, the processing content of the above-mentioned client device 100 may be changed appropriately.

[0107] (Server Device 200)

[0108] The server device 200 is an information processing device that provides various functions to the client device 100 in the academic performance and activity record service. For example, in the case where the server device 200 receives a request signal from the client device 100, the server device 200 identifies the requested content by analyzing the request signal, and acquires data on the student's academic performance record or activity record by sending a request signal for requesting target data to the node device 300 or the storage device 400 based on the requested content. Then, the server device 200 sends the registration destination information of the data to the client device 100 together with the data.

[0109] Note that the processing content of the server device 200 is not limited to the above. For example, the server device 200 may acquire data by sending a request signal to both the node device 300 and the storage device 400 without analyzing the request signal received from the client device 100. In addition, the server device 200 may also acquire data from the node device 300 or the storage device 400 without receiving a request signal from the client device 100, and provide the data to the client device 100. In addition, in a similar manner to the client device 100, the type of the server device 200 is not particularly limited.

[0110] (Node device 300)

[0111] Node device 300 is an information processing device connected to P2P network 500 and saves a P2P database. In the P2P database provided at node device 300, data on students' academic performance records, activity records, etc. are registered. Note that the contents of the data registered in the P2P database are not limited to these.

[0112] Then, the node device 300 acquires data from the P2P database and registers the data in the P2P database. Regarding acquiring data, in the case where the node device 300 receives a request signal from the server device 200, the node device 300 acquires the data specified by the request signal from the P2P database and provides the data to the server device 200. In addition, regarding registering data, in the case where the node device 300 receives a request signal regarding registering data from the server device 200, the node device 300 registers the data included in the request signal in the P2P database. Note that the case where the node device 300 acquires data from the P2P database and the case where the node device 300 registers the data in the P2P database are not limited to the above case. For example, the node device 300 may also acquire data from the P2P database and may provide the data to the server device 200 when the node device 300 does not receive a request signal from the server device 200.

[0113] Note that, in the case where the node device 300 registers data in the P2P database, acquires data from the P2P database, etc., the node device 300 basically uses a predetermined program provided at the P2P database and to be executed on the P2P database (hereinafter, for the purpose of description, referred to as a "P2P database program"). By using the P2P database program, for example, various processes are implemented according to predetermined rules. In addition, by the P2P database program provided at the P2P database, the risk of the program being fraudulently modified is reduced.

[0114] Although the P2P database program is a chain code in Hyperledger, the P2P database program is not limited thereto. For example, the P2P database program may indicate a smart contract. Note that the node device 300 may use a program other than the P2P database program when appropriate to obtain data from the P2P database and register the data in the P2P database. In addition, similar to the client device 100, the type of the node device 300 is not particularly limited.

[0115] In addition, although in the present embodiment, a description will be provided assuming that a plurality of node devices 300 have the same function, each node device 300 may have functions different from each other. For example, a node device 300 that approves registration of data in a P2P database (such as, for example, an endorsement node), a node device 300 that instructs each node device 300 to perform registration after approval (such as, for example, a sorting node), and a node device 300 that registers data in a P2P database (such as, for example, a submission node) may also be provided.

[0116] (Storage device 400)

[0117] The storage device 400 is a predetermined storage device used together with the P2P database in the information processing system according to the present embodiment. More specifically, the storage device 400 can store various data provided to the client device 100 via the server device 200. The data to be stored in the storage device 400 is, for example, data about the student's academic performance record, activity record, etc. Note that the content of the data to be stored in the storage device 400 is not limited to these. In the case where the storage device 400 receives a request signal from the server device 200, the storage device 400 obtains the data specified by the request signal and provides the data to the server device 200. Note that the processing content of the storage device 400 is not limited to the above. For example, in the case where the storage device 400 does not receive a request signal from the server device 200, the storage device 400 can also provide arbitrary data to the server device 200. In addition, in a similar manner to the client device 100, the type of the storage device 400 is not particularly limited.

[0118] (P2P Network 500)

[0119] The P2P network 500 is a network on which a P2P database is distributed. As described above, each node device 300 can update the P2P database by connecting to the P2P network 500 while maintaining consistency with the P2P databases stored by other node devices 300.

[0120] Note that there is no particular limitation on the type of the P2P network 500. For example, the P2P network 500 may be one of a consortium type operated by a plurality of organizations, a private type operated by a single organization, and a public type with no particular limitation on participants.

[0121] Note that there is no particular limitation on the communication scheme, line type, etc. to be used in the P2P network 500. For example, the P2P network 500 may be implemented with a leased line network such as an Internet Protocol-Virtual Private Network (IP-VPN). In addition, the P2P network 500 may be implemented with a public network such as the Internet, a telephone network, a satellite communication network, various local area networks (LANs) including Ethernet (registered trademark), a wide area network (WAN), etc. In addition, the P2P network 500 may be implemented with a wireless communication network such as Wi-Fi (registered trademark) or Bluetooth (registered trademark).

[0122] (Network 600)

[0123] The network 600 is a network connecting between the client device 100 and the server device 200, the server device 200 and the node device 300, and the server device 200 and the storage device 400. Note that, in a similar manner to the P2P network 500, there is no particular limitation on the communication scheme, the type of line, etc. to be used at the network 600.

[0124] The configuration example of the information processing system according to the present embodiment has been described above. Figure 4 The above configuration described is only an example, and the configuration of the information processing system according to the present embodiment is not limited to the example. For example, all or part of the functions of the client device 100 may be provided at the server device 200. For example, software that provides all or part of the functions of the client device 100 may be executed on the server device 200. In addition, conversely, all or part of the functions of the server device 200 may be provided at the client device 100. The configuration of the information processing system according to the present embodiment can be flexibly changed according to the specifications and operations.

[0125] (2.3. Functional Configuration Example of Client Device 100)

[0126] In the above description, an example of the configuration of the information processing system according to the present embodiment has been explained. Figure 5 A functional configuration example of the client device 100 is described.

[0127] like Figure 5 As shown, the client device 100 includes a control unit 110 , an input unit 120 , an output unit 130 , a storage unit 140 , and a communication unit 150 .

[0128] (Control Unit 110)

[0129] The control unit 110 is a functional component that comprehensively controls the overall processing performed by the client device 100. For example, the control unit 110 can control the start and stop of the output unit 130, the communication unit 150, etc. using a control signal. Note that the control content of the control unit 110 is not limited to these. For example, the control unit 110 can control the processing generally performed at various servers, general-purpose computers, PCs, tablet PCs, etc.

[0130] In addition, if Figure 5 As shown, the control unit 110 includes a request unit 111 and an output control unit 112 .

[0131] (Request unit 111)

[0132] The request unit 111 is a functional component that performs various requests to external devices including acquisition, registration, confirmation as to whether data is registered, etc. Figure 5 As shown, the request unit 111 includes a first request unit 111 a and a second request unit 111 b .

[0133] (First Requesting Unit 111a)

[0134] The first request unit 111a is a functional component that performs various requests for the first target including acquisition of data, registration, confirmation as to whether the data is registered, etc. More specifically, in the case where the user performs an input operation for requesting acquisition of desired data using the input unit 120, the first request unit 111a generates a request signal for requesting acquisition of data based on the input operation, and transmits the signal to the server device 200 via the communication unit 150. In this way, the first request unit 111a can realize acquisition of desired data from the node device 300 or the storage device 400, and acquisition of registration destination information of the data.

[0135] In addition, in the case where the user performs an input operation for requesting registration of desired data using the input unit 120, the first request unit 111a generates a request signal for requesting registration of data, and transmits the signal to the server device 200 via the communication unit 150. In this way, the first request unit 111a can realize registration of desired data in the node device 300 or the storage device 400. Here, although the user cannot basically delete, correct, etc. the data registered in the P2P database, the user can add an additional record to the data registered in the P2P database (for example, an additional record indicating deletion or correction of data can be added). The first request unit 111a can realize the addition of an additional record by generating a request signal for requesting addition of an additional record to the data registered in the P2P database and transmitting the signal to the server device 200 via the communication unit 150.

[0136] (Second Requesting Unit 111b)

[0137] The second request unit 111b is a functional component that performs various requests for the second target including acquisition of data, registration, confirmation as to whether the data is registered, etc. More specifically, in a case where the user who has confirmed the registration destination information obtained as a result of the request for the first target performs an input operation for requesting the registration destination information of the desired data using the input unit 120, the second request unit 111b generates a request signal for requesting the registration destination information, and transmits the signal to the second target via the communication unit 150. In this way, the user himself can confirm the authenticity of the registration destination information of the data provided from the server device 200.

[0138] (Output Control Unit 112)

[0139] The output control unit 112 is a functional component that controls the output of data obtained due to the request made by the first request unit 111a or the second request unit 111b to the user (in other words, the output control unit 112 controls the provision of a UI). More specifically, the output control unit 112 controls the output of the user's desired data obtained due to the request made by the first request unit 111a and the registration destination information of the data, or controls the output of the registration destination information obtained due to the request made by the second request unit 111b. In this case, in the case where the acquisition of the registration destination information fails (or in the case where the registration destination of the data is unknown), the output control unit 112 can control the output of information indicating that the acquisition failed or the registration destination is unknown.

[0140] The output control unit 112 controls the output of the registered destination information and the like by controlling a display device such as a display, a sound output device such as a speaker, a light source device such as a lamp, a tactile presentation device such as an actuator, and the like provided at the output unit 130. A specific example of the UI implemented by the output control unit 112 will be described later. Note that, as described above, the server device 200 can control the provision of the UI by the output control unit 112 provided at the server device 200.

[0141] (Input unit 120)

[0142] The input unit 120 is a functional component that receives user input. For example, the input unit 120 includes input devices such as a mouse, a keyboard, a touch panel, a button, a switch, and a microphone, and the user can perform input operations for acquiring desired data or requesting registration, etc. by using these input devices. Note that the input device provided at the input unit 120 is not particularly limited.

[0143] (Output unit 130)

[0144] The output unit 130 is a functional component that outputs data obtained due to a request made by the first request unit 111a or the second request unit 111b to the user by being controlled by the output control unit 112 (in other words, the output unit 130 provides a UI). For example, the output unit 130 includes a display device such as a display, a sound output device such as a speaker, a light source device such as a lamp, a tactile presentation device such as an actuator, and the like, and outputs data requested by the user or registration destination information of the data, and the like based on the control of the output control unit 112. Note that the output device provided at the output unit 130 is not limited to these.

[0145] (Storage unit 140)

[0146] The storage unit 140 is a functional component that stores various data. For example, the storage unit 140 stores data obtained due to a request made by the first request unit 111a or the second request unit 111b, registration destination information of the data, etc., or stores programs, parameters, etc. to be used by various functional components of the client device 100. Note that the data stored in the storage unit 140 is not limited to these.

[0147] (Communication unit 150)

[0148] The communication unit 150 is a functional component that controls various communications with external devices. For example, the communication unit 150 sends the request signal generated by the first request unit 111a to the server device 200, and receives a response signal including the data specified by the request signal, the registration destination information of the data, etc. In addition, the communication unit 150 sends the request signal generated by the second request unit 111b to the second target (or an external device that can perform communication with the second target, etc.), and receives a response signal including the registration destination information of the data specified by the request signal, etc. Note that the data to be transmitted by the communication unit 150 and the case where the communication unit 150 performs communication are not limited to these.

[0149] The functional configuration example of the client device 100 has been described above. Figure 5 The above-described functional configuration is merely an example, and the functional configuration example of the client device 100 is not limited to this example. For example, the client device 100 does not necessarily have to include Figure 5 In addition, the functional configuration of the client device 100 can be flexibly changed according to the specifications and operations.

[0150] (2.4. Functional Configuration Example of Server Device 200)

[0151] In the above description, the functional configuration example of the client device 100 has been described. Figure 6 A functional configuration example of the server device 200 is described.

[0152] like Figure 6 As shown, the server device 200 includes a control unit 210 , a storage unit 220 , and a communication unit 230 .

[0153] (Control Unit 210)

[0154] The control unit 210 is a functional component that comprehensively controls the overall processing performed by the server device 200. For example, the control unit 210 can use a control signal to control the start and stop of an output unit (not shown), a communication unit 230, etc. In addition, in the present embodiment, the control unit 210 implements the acquisition of data, etc. from the node device 300 or the storage device 400 by providing an access control unit 211. In addition, the control unit 210 provides a response signal including data acquired from the node device 300 or the storage device 400 and a response signal including registration destination information of the data to the client device 100 via the communication unit 230. Note that the control content of the control unit 210 is not limited to these. For example, the control unit 210 can control processing that is generally performed at various types of servers, general-purpose computers, PCs, tablet PCs, etc.

[0155] (Access Control Unit 211)

[0156] The access control unit 211 is a functional component that controls access to the node device 300 or the storage device 400, and includes a P2P database access control unit 211a and a storage access control unit 211b. In addition, when the server device 200 receives a request signal from the client device 100, the access control unit 211 identifies the requested content by analyzing the request signal. Then, in the case where it is necessary to obtain data from the P2P database, etc., the access control unit 211 uses the P2P database access control unit 211a to achieve access to the P2P database. In addition, in the case where it is necessary to obtain data from the storage device 400, etc., the access control unit 211 uses the storage access control unit 211b to achieve access to the storage device 400. Note that the P2P database access control unit 211a and the storage access control unit 211b set at the access control unit 211 can be integrated to be implemented as one functional component.

[0157] (P2P database access control unit 211a)

[0158] The P2P database access control unit 211a is a functional component that implements access to the P2P database based on a request signal from the client device 100. More specifically, in the case where it is determined through analysis of the request signal from the client device 100 that data needs to be acquired from the P2P database P2P, the database access control unit 211a generates a new request signal for requesting acquisition of data, etc., based on the requested content, and transmits the request signal to the node device 300. In this way, the P2P database access control unit 211a implements acquisition of data, etc. from the P2P database or registration of data in the P2P database. Note that the above-mentioned processing of the P2P database access control unit 211a can be appropriately changed. For example, the P2P database access control unit 211a can transmit the request signal transmitted from the client device 100 to the node device 300 as it is without generating a new request signal. In addition, the P2P database access control unit 211a can also access the P2P database in the case where the server device 200 does not receive a request signal from the client device 100.

[0159] (Storage Access Control Unit 211b)

[0160] The storage access control unit 211b is a functional component that implements access to the storage device 400 based on a request signal from the client device 100. More specifically, in the case where it is determined through analysis of the request signal from the client device 100 that data needs to be acquired from the storage device 400, the storage access control unit 211b generates a new request signal for requesting acquisition of data, etc., based on the requested content, and transmits the request signal to the storage device 400. In this way, the storage access control unit 211b implements acquisition of data, etc. from the storage device 400 or registration of data in the storage device 400. Note that the above-mentioned processing of the storage access control unit 211b can be appropriately changed. For example, in a similar manner to the P2P database access control unit 211a, the storage access control unit 211b can transmit the request signal transmitted from the client device 100 to the storage device 400 as it is without generating a new request signal. In addition, the storage access control unit 211b can also access the storage device 400 in the case where the server device 200 does not receive a request signal from the client device 100.

[0161] (Storage unit 220)

[0162] The storage unit 220 is a functional component that stores various types of data. For example, the storage unit 220 stores a request signal from the client device 100, data acquired from the P2P database or the storage device 400, stores registration destination information of data, or stores programs, parameters, etc. to be used by various functional components of the server device 200. Note that the data stored in the storage unit 220 is not limited thereto.

[0163] (Communication unit 230)

[0164] The communication unit 230 is a functional component that controls various types of communications with external devices. For example, the communication unit 230 receives a request signal for requesting to obtain user desired data from the client device 100. Then, the communication unit 230 sends the request signal generated by the P2P database access control unit 211a to the node device 300, and receives a response signal including the data specified by the request signal, etc. In addition, the communication unit 230 sends the request signal generated by the storage access control unit 211b to the storage device 400, and receives a response signal including the data specified by the request signal, etc. Thereafter, the communication unit 230 sends a response signal including the data obtained from the node device 300 or the storage device 400 and the registration destination information to the client device 100. Note that the data transmitted by the communication unit 230 and the case where the communication unit 230 performs communication are not limited to this.

[0165] The functional configuration example of the server device 200 has been described above. Figure 6 The above-described functional configuration is merely an example, and the functional configuration example of the server device 200 is not limited to this example. For example, the server device 200 does not necessarily have to include Figure 6 In addition, the functional configuration of the server device 200 can be flexibly changed according to specifications and operations.

[0166] (2.5. Functional Configuration Example of Node Device 300)

[0167] In the above description, the functional configuration example of the server device 200 has been described. Figure 7 A functional configuration example of the node device 300 is described.

[0168] like Figure 7 As shown, the node device 300 includes a control unit 310 , a storage unit 320 and a communication unit 330 .

[0169] (Control Unit 310)

[0170] The control unit 310 is a functional component that comprehensively controls the overall processing performed by the node device 300. For example, the control unit 310 can use a control signal to control the start and stop of an output unit (not shown), a communication unit 330, etc. In addition, the control unit 310 controls the process of acquiring data from the P2P database 321 or the process of registering data in the P2P database 321 based on a request signal provided from the server device 200. In this case, the control unit 310 can control these types of processing (the process of acquiring data or the process of registering data) based on the user's access rights, etc. Note that the control content of the control unit 310 is not limited to these. For example, the control unit 310 can control the processing that is usually performed in various types of servers, general-purpose computers, PCs, tablet PCs, etc.

[0171] (Storage unit 320)

[0172] The storage unit 320 is a functional component that stores various types of data. For example, the storage unit 320 stores programs, parameters, etc. to be used by various functional components of the node device 300. Note that the contents of the data stored in the storage unit 320 are not limited to these. Figure 7 As shown, the storage unit 320 includes a P2P database 321 .

[0173] (P2P database 321)

[0174] The P2P database 321 is a database commonly maintained by each node device 300, and is, for example, blockchain data. As described above, in the P2P database 321, data of higher importance that requires authenticity assurance, such as students' academic performance records, activity records, etc., are registered. An electronic signature generated using an encryption key can be provided to various types of data to be registered in the P2P database 321, or the data can be encrypted using an encryption key. Note that the data to be registered in the P2P database 321 is not limited to this. For example, in the case of acquiring data from the P2P database 321 or performing a charge when registering data in the P2P database 321, data about assets owned by each user can be registered in the P2P database 321. As Figure 7 As shown, the P2P database 321 includes a P2P database program 322 .

[0175] (P2P database program 322)

[0176] The P2P database program 322 is a predetermined program provided at the P2P database 321 and to be executed on the P2P database 321. By using the P2P database program 322, various types of processing are implemented according to predetermined rules while maintaining consistency. Regarding the predetermined rules, for example, the P2P database program 322 can perform approval processing or charging processing based on predetermined rules by cooperating with other node devices 300 when registering data or acquiring data. In addition, by providing the P2P database program 322 at the P2P database 321, the risk of the program being fraudulently modified is reduced. Although the P2P database program 322 is a chain code of a hyperledger, the P2P database program 322 is not limited to this. For example, the P2P database program 322 can indicate a smart contract.

[0177] The P2P database program 322 can realize the overall processing to be performed for the P2P database 321. For example, the P2P database program 322 can realize the acquisition processing of various data, the registration processing of various data, etc. to be performed by accessing the P2P database 321. Note that the processing to be realized by the P2P database program 322 is not limited to the above. There is no particular limitation on the development language of the P2P database program 322, the number of P2P database programs 322 set on the P2P database 321, etc.

[0178] (Communication unit 330)

[0179] The communication unit 330 is a functional component that controls various types of communications with external devices. For example, the communication unit 330 receives a request signal from the server device 200, and transmits data acquired based on the request signal to the server device 200. In addition, the communication unit 330 transmits / receives data to be used for updating the P2P database 321 and the like (such as data to be used for establishing consensus) when communicating with other node devices 300. Note that the data to be transmitted by the communication unit 330 and the case where the communication unit 330 performs communication are not limited to this.

[0180] The functional configuration example of the node device 300 has been described above. Figure 7 The above-described functional configuration is merely an example, and the functional configuration example of the node device 300 is not limited to this example. For example, the node device 300 does not necessarily have to include Figure 7 In addition, the functional configuration of the node device 300 can be flexibly changed according to specifications and operations.

[0181] (2.6. Functional Configuration Example of Storage Device 400)

[0182] In the above description, the functional configuration example of the node device 300 has been described. Figure 8A functional configuration example of the storage device 400 is described.

[0183] like Figure 8 As shown, refer to Figure 8 The storage device 400 includes a control unit 410 , a storage unit 420 , and a communication unit 430 .

[0184] (Control Unit 410)

[0185] The control unit 410 is a functional component that comprehensively controls the overall processing performed by the storage device 400. For example, the control unit 410 can control the start and stop of the output unit (not shown), the communication unit 430, etc. using a control signal. In addition, the control unit 410 controls the acquisition processing of data from the storage unit 420 or the registration processing of data in the storage unit 420 based on the request signal provided from the server device 200. Note that the control content of the control unit 410 is not limited thereto. For example, the control unit 410 can control the processing generally performed in various types of servers, general-purpose computers, PCs, tablet PCs, etc.

[0186] (Storage unit 420)

[0187] The storage unit 420 is a functional component that stores various types of data. For example, as described above, the storage unit 420 stores data that does not require authenticity assurance (or does not require high authenticity) in student academic performance records, activity records, etc. In addition, the storage unit 420 stores programs, parameters, etc. to be used by various functional components of the storage device 400. Note that the content of the data stored in the storage unit 420 is not limited thereto.

[0188] (Communication unit 430)

[0189] The communication unit 430 is a functional component that controls various types of communications with external devices. For example, the communication unit 430 receives a request signal from the server device 200 and sends data acquired based on the request signal to the server device 200. Note that the data to be transmitted by the communication unit 430 and the case where the communication unit 430 performs communication are not limited thereto.

[0190] The functional configuration example of the storage device 400 has been described above. Figure 8 The above-described functional configuration is merely an example, and the functional configuration example of the storage device 400 is not limited to this example. For example, the storage device 400 does not necessarily have to include Figure 8 In addition, the functional configuration of the storage device 400 can be flexibly changed according to specifications and operations.

[0191] (2.7. Processing Flow)

[0192] In the above description, the functional configuration example of the storage device 400 has been described. Fig. 9 Describe the processing flow of each device. Fig. 9 is a sequence diagram showing an example of the flow of processing performed by each device regarding providing data to a user and registering destination information.

[0193] exist Fig. 9 In step S1000, the user determines the data to be requested and performs a predetermined input operation on the input unit 120 of the client device 100. In step S1004, the first request unit 111a generates a request signal for requesting acquisition of data based on the input and transmits the signal to the server device 200 via the communication unit 150.

[0194] In step S1008, the access control unit 211 of the server device 200 identifies the requested content by analyzing the request signal. In step S1012, the P2P database access control unit 211a or the storage access control unit 211b generates a new request signal based on the requested content, and the P2P database access control unit 211a sends the signal to the node device 300a, and the storage access control unit 211b sends the signal to the storage device 400, respectively.

[0195] In step S1016, the control unit 310 of the node device 300a acquires the data specified by the request signal from the P2P database 321, or the control unit 410 of the storage device 400 acquires the data specified by the request signal from the storage unit 420. Then, in step S1020, the communication unit 330 of the node device 300a or the communication unit 430 of the storage device 400 transmits a response signal including the acquired data to the server device 200.

[0196] In step S1024, the communication unit 230 of the server device 200 transmits a response signal including the data from the node device 300a or the storage device 400 and the registration destination information of the data to the client device 100. In step S1028, the output control unit 112 of the client device 100 controls the output of the output unit 130 based on the response signal from the server device 200.

[0197] In step S1032, the user has received data outputted from the output unit 130 to determine that the authenticity of the registration destination information needs to be confirmed, and a predetermined input operation is performed on the input unit 120. In step S1036, the second request unit 111b generates a request signal for requesting acquisition of the registration destination information of the data based on the input operation, and transmits the signal to the second target (in this example, the second target is the node device 300b) via the communication unit 150.

[0198] In step S1040, the control unit 310 of the node device 300b confirms whether the data specified by the request signal is registered in the P2P database 321. In step S1044, the communication unit 330 of the node device 300b transmits a response signal including registration destination information of the data (information on whether the data is registered in the P2P database 321) to the client device 100.

[0199] In step S1048 , the output control unit 112 of the client device 100 controls the output of the output unit 130 based on the response signal from the node device 300 b to complete a series of processes.

[0200] Notice, Fig. 9 The individual steps in the sequence diagram of the embodiment do not necessarily have to be processed in chronological order in the order described. That is, the individual steps in the sequence diagram may be processed in an order different from the order described, or may be processed in parallel.

[0201] <3. User interface example>

[0202] The processing flow of each device has been described above. Subsequently, an example of a UI according to the present disclosure will be described.

[0203] (3.1. Example of UI indicating registration destination information of data)

[0204] First, refer to Figures 10 to 21 An example of a UI indicating whether the registration destination of data is the P2P database 321 or the storage device 400 is described. As described above, the output control unit 112 of the client device 100 can control the output of the data included in the response signal based on the registration destination information included in the response signal from the server device 200, and Figures 10 to 21 A display example of a display (output unit 130) is shown as an example of a UI, and the output of the display is controlled by the output control unit 112. Note that, as described above, the output control unit 112 can control a sound output device such as a speaker, a light source device such as a lamp, a tactile presentation device such as an actuator, and the like in addition to a display device such as a display.

[0205] First, if Fig.10 As shown, the output control unit 112 can perform control so that the file registered in the P2P database 321 (in the figure, the file 10) among the files (data) displayed as a list at the display is displayed in a recessed state as if the file is embedded in the screen.

[0206] In addition, if Fig.11As shown, the output control unit 112 can perform control so that among the files (data) displayed as a list at the display, the file registered in the P2P database 321 (in the figure, file 11) is displayed with a texture different from other files (files registered in the storage device 400).

[0207] In addition, if Fig.12 As shown, the output control unit 112 can perform control so that the character string registered in the P2P database 321 (in the figure, file 12) among the character strings (data) displayed as a list at the display is displayed in a state where a predetermined icon (in the figure, a check box icon 12 with a check mark) is set.

[0208] In addition, if Fig.13 As shown, the output control unit 112 can perform control so that the character strings (in the figure, file 13) registered in the P2P database 321 among the character strings (data) displayed as a list at the display are displayed in a recessed state as if the character strings are embedded in the screen.

[0209] In addition, if Fig.14 As shown, the output control unit 112 can perform control so that the character strings registered in the P2P database 321 among the character strings (data) displayed as a list at the display are displayed in a state where a predetermined icon (in the figure, a check box icon 14 with a check mark) is set.

[0210] The user can intuitively recognize the data registered in the P2P database 321 using the above-mentioned UI.

[0211] Subsequently, an example of a UI indicating data registered in the storage device 400 (other storage unit) will be described. Fig.15 As shown, the output control unit 112 can perform control so that a file registered in the storage device 400 (in the figure, file 15) among the files (data) displayed as a list on the display is displayed in a state where a predetermined mark (in the figure, a mark indicating a crack) is set.

[0212] In addition, if Fig.16 As shown, the output control unit 112 may perform control so that files registered in the storage device 400 among the files (data) displayed as a list at the display are displayed in a state provided with a predetermined icon (in the figure, the icon 16 with a question mark).

[0213] In addition, if Fig.17 As shown in , the output control unit 112 can perform control so that the character strings stored in the storage device 400 among the character strings (data) displayed as a list at the display are displayed in a state provided with a predetermined icon (in the figure, the icon 17 with a question mark).

[0214] The user can intuitively recognize the data registered in the storage device 400 using the above-described UI.

[0215] In addition, if Fig.18 As shown, an area 18 for data registered in the P2P database 321 and an area 19 for data registered in the storage device 400 may be provided at the display, and the output control unit 112 may control output so that data is displayed in the corresponding areas.

[0216] In addition, if Fig.19 As shown, a tab 20 for data registered in the P2P database 321 and a tab 21 for data registered in the storage device 400 may be set on the display, and the output control unit 112 may control output so that the data is displayed in the corresponding tabs.

[0217] In addition, you can set the display Fig. 20 A window for data registered in the P2P database 321 and Fig. 20 4 is a window for data registered in the storage device 400 shown in B in FIG. 1 , and the output control unit 112 can control the output so that the data is displayed in the corresponding window.

[0218] In addition, in the case where the client device 100 includes a plurality of displays, the following may be set: Fig.21 A display for data registered in the P2P database 321 and Fig.21 4 is a display for data registered in the storage device 400, and the output control unit 112 can control the output so that the data is displayed in the corresponding display.

[0219] (3.2. Example of UI indicating confirmation result for second target)

[0220] As described above, the user can confirm the authenticity of the registration destination information of the data for the second target after the registration destination information of the data is provided from the server device 200. Therefore, subsequently, an example of a UI indicating the confirmation result of the registration destination information provided from the second target will be described.

[0221] For example, when the user presses the Fig.12 In the case of the check box icon 12 shown in FIG. Fig. 22A pop-up window 22 shown in A in FIG. 1 is displayed on the display. Then, in the case where the user presses (clicks) a confirmation button 23 included in the pop-up window 22, the second request unit 111b confirms the registration destination information of the data for the second target, and the output control unit 112 controls the output so that a character string 24 of the confirmation result is displayed in the pop-up window 22 (in this example, information indicating that the data has been registered in the P2P database 321 is displayed together with the confirmation time). Through this UI, the user can easily confirm the authenticity of the registration destination information of the data.

[0222] (3.3. Example of UI indicating history information about additional recording of data)

[0223] As described above, although the user cannot basically delete, correct, etc. the data registered in the P2P database 321, the user can add an additional entry to the data registered in the P2P database 321 (for example, the user can add an additional entry indicating that the data has been deleted or corrected). Therefore, subsequently, an example of a UI indicating historical information about adding an additional entry to data (hereinafter, also simply referred to as "historical information") will be described.

[0224] For example, if a user Fig.23 The user selects a file whose history information the user desires to confirm from among the plurality of files (data) displayed as a list as shown in A in FIG. For example, the user selects a file whose history information the user desires to confirm by pressing (clicking) the file or continuously pressing (long pressing) the file for a certain period of time equal to or greater than a predetermined period of time. In this way, as Fig.23 As shown in B in FIG. 1 , the output control unit 112 controls the output so that the historical information about the file is displayed. Fig.23 In the example of B in , files are displayed for each version, with the newer versions appearing first. That is, in Fig.23 In B, file 25a is the latest version of the file, and file 25d is the oldest version of the file.

[0225] In this way, since the user can intuitively recognize whether the version of each file is old or new, the user can more easily confirm the history information of the file. Note that the UI indicating the history information is not limited to Fig.23 For example, each version of the file can be displayed in a line horizontally or vertically. In addition, a predetermined method (such as, for example, highlighting and a different font) can be used to indicate the part where the postscript is added.

[0226] (3.4. Example of UI to be used to register data in P2P database 321)

[0227] As described above, the user can register desired data in the P2P database 321 by performing an input operation for requesting registration of data using the input unit 120. Therefore, subsequently, an example of a UI to be used for registering data in the P2P database will be described.

[0228] For example, suppose Fig.24 As shown, an area 26 for data registered in the P2P database 321 and an area 27 for data registered in the storage device 400 are provided on the display, and files (data) are displayed in the corresponding areas. Then, the user can register the file in the P2P database 321 by dragging and dropping the file displayed in the area 27 to the area 26.

[0229] In addition, if Fig.25 As shown, the user can register a file in the P2P database 321 by selecting a character string 28 registered in the storage device 400 (in the figure, the selected portion is highlighted) and continuously pressing (long pressing) the selected portion for a certain period of time equal to or greater than a predetermined period of time.

[0230] Through the above-described UI, the user can more easily register data in the P2P database 321. Note that the UI to be used for registering data in the P2P database 321 is not limited to the above-described example.

[0231] (3.5. Example of a UI indicating that data cannot be deleted)

[0232] Subsequently, an example of a UI indicating that data cannot be deleted because it is registered in the P2P database 321 will be described.

[0233] For example, Fig.26 As shown, files 29 (data) registered in the P2P database 321, an area 31 showing files 30 (data) registered in the storage device 400, and a deletion area 32 for designating a file to be deleted are displayed on the display.

[0234] Furthermore, it is assumed that the user attempts to delete the file 29 registered in the P2P database 321 by dragging and dropping the file 29 to the deletion area 32. In this case, a display may be provided in which a rejection symbol 33 indicating that the file cannot be deleted is provided at the file 29 every time when the file 29 is about to be dragged to the deletion area 32, and further, in the case where the file 29 is dropped to the deletion area 32, the file 29 is forcibly returned to the original position in the area 31. Note that in the case where the user drags and drops the file 30 registered in the storage device 400 to the deletion area 32, the file 30 is appropriately deleted.

[0235] In addition, if Fig. 27As shown, when a user selects a character string 34 registered in a P2P database 321 (in the drawing, the selected portion is highlighted) and attempts to delete (or rewrite) the selected portion, an alarm message 35 may be displayed. In this example, an alarm message 35 "Cannot rewrite because this line is written to the P2P database" is displayed.

[0236] Through the above UI, the user can more easily recognize that the data that the user is trying to delete cannot be deleted because the data is registered in the P2P database 321. In this way, according to the present disclosure, the user can be made aware that he needs to be more careful in registering data in the P2P database 321. Note that the UI indicating that data cannot be deleted is not limited to the above example.

[0237] (3.6. Example of UI indicating that registration of data in P2P database 321 is being performed)

[0238] Subsequently, an example of a UI indicating that registration of data in the P2P database 321 is being performed will be described.

[0239] For example, Fig.28 As shown, a data editing area 36, ​​a save button 37, and a save draft button 38 are displayed on the display. Here, the save button 37 is a button pressed when the user registers the data edited in the editing area 36 in the P2P database 321, and the save draft button 38 is a button pressed when the user registers the data being edited in the storage device 400.

[0240] In the case where the user presses the save button 37, Fig.29 As shown, a message 39 indicating that data is being saved in the P2P database 321 (in this example, a message 39 of "data is being saved in the P2P database...") and a loading icon 40 reminding the user of the P2P database 321 (in this example, a loading icon 40 reminding the user of the blockchain through a plurality of consecutive blocks) are displayed. Note that Fig.30 The animation 41 shown may be displayed instead of the loading icon 40 (in this example, the animation 41 that reminds the user of the blockchain through a plurality of consecutive blocks is displayed).

[0241] In addition, Fig.28 In the case where the user presses the save draft button 38, as shown in FIG. Fig.31 As shown, a message 42 indicating that data is being saved in the storage device 400 (in this example, a message 42 of "data is being saved in the database...") and a loading icon 43 (a typical loading icon) that does not remind the user of the P2P database 321 are displayed. Fig.32The animation 44 (typical animation) shown not to alert the user of the P2P database 321 may be displayed instead of the loading icon 43 .

[0242] Through the above-described UI, the user can more easily recognize that data is being registered in the P2P database 321 or the storage device 400. Note that the UI indicating that data registration is being performed is not limited to the above-described example.

[0243] <4. Hardware Configuration Example>

[0244] An example of a UI of the present disclosure has been described above. Fig.33 Describes a hardware configuration example of each device.

[0245] Fig.33 1 is a block diagram showing a hardware configuration example of the client device 100, the server device 200, the node device 300, or the storage device 400. These devices may be composed of Fig.33 The information processing device 900 shown is used for implementation.

[0246] The information processing apparatus 900 includes, for example, an MPU 901, a ROM 902, a RAM 903, a recording medium 904, an input / output interface 905, an operation input device 906, a display device 907, and a communication interface 908. Furthermore, in the information processing apparatus 900, for example, the respective components are connected to a bus 909 as a data transmission path.

[0247] The MPU 901 includes one or two or more processors having an arithmetic circuit such as an MPU, various types of processing circuits, and the like, and functions as the control unit 110 of the client device 100, the control unit 210 of the server device 200, the control unit 310 of the node device 300, or the control unit 410 of the storage device 400. Note that the control unit 110 of the client device 100, the control unit 210 of the server device 200, the control unit 310 of the node device 300, or the control unit 410 of the storage device 400 may include a dedicated (or general-purpose) circuit (such as, for example, a processor different from the MPU 901) that can implement the above-mentioned various types of processing.

[0248] The ROM 902 stores control data such as programs to be used by the MPU 901, operation parameters, and the like. The RAM 903 temporarily stores programs to be executed by the MPU 901 and the like, for example.

[0249] The recording medium 904 is used as the storage unit 140 of the client device 100, the storage unit 220 of the server device 200, the storage unit 320 of the node device 300, or the storage unit 420 of the storage device 400, and stores various types of data such as data related to information processing according to the present embodiment and various types of programs. Here, examples of the recording medium 904 may include, for example, a magnetic recording medium such as a hard disk and a non-volatile memory such as a flash memory. In addition, the recording medium 904 may be detachable from the information processing device 900.

[0250] The input / output interface 905 connects, for example, an operation input device 906 and a display device 907. Here, examples of the input / output interface 905 may include, for example, a universal serial bus (USB) terminal, a digital visual interface (DVI) terminal, a high-definition multimedia interface (HDMI) (registered trademark) terminal, various types of processing circuits, and the like.

[0251] In addition, the operation input device 906 is provided on the information processing device 900, for example, and is connected to the input / output interface 905 inside the information processing device 900. Examples of the operation input device 906 may include, for example, a keyboard, a mouse, a keypad, a touch panel, a microphone, operation buttons, cursor keys, a rotary selector (e.g., a dial), a combination of these, etc. The operation input device 906 serves as the input unit 120 of the client device 100.

[0252] In addition, the display device 907 is provided on the information processing device 900, for example, and is connected to the input / output interface 905 inside the information processing device 900. Examples of the display device 907 may include, for example, a liquid crystal display, an organic electroluminescent (EL) display, etc. The display device 907 serves as the output unit 130 of the client device 100.

[0253] Note that it goes without saying that the input / output interface 905 can be connected to an external device such as an operation input device and an external display device outside the information processing device 900. Furthermore, the display device 907 may be a device that can perform display and allow user operation, such as a touch panel, for example.

[0254] The communication interface 908 is a communication device provided at the information processing device 900, and is used as the communication unit 150 of the client device 100, the communication unit 230 of the server device 200, the communication unit 330 of the node device 300, or the communication unit 430 of the storage device 400. In addition, the communication interface 908 may have a function of communicating with any external device such as a server in a wireless or wired manner, for example, via any network (or directly). Here, examples of the communication interface 908 may include, for example, a communication antenna and a radio frequency (RF) circuit (wireless communication), an IEEE802.15.1 port and a transmission / reception circuit (wireless communication), an IEEE802.11 port and a transmission / reception circuit (wireless communication), a local area network (LAN) terminal and a transmission / reception circuit (wired communication), etc.

[0255] Note that the hardware configuration of the information processing device 900 is not limited to Fig.33 For example, in the case where the information processing device 900 performs communication via a connected external communication device, the information processing device 900 does not include the communication interface 908. In addition, the communication interface 908 may have a configuration that enables communication using a plurality of communication schemes. In addition, the information processing device 900, for example, does not necessarily include the operation input device 906, the display device 907, etc. In addition, for example, Fig.33 Some or all of the components shown may be implemented using one or two or more integrated circuits (ICs).

[0256] <5. Conclusion>

[0257] As described above, according to the present disclosure, it is possible to request information (registration destination information) about whether the registration destination of data is the P2P database 321 or other storage unit (storage device 400) for multiple targets (first target and second target) different from each other, and provide the information obtained as a result of the request to the user. In this way, the user himself can confirm the authenticity of the registration destination information of the data provided from the system.

[0258] The preferred embodiments of the present disclosure have been described above with reference to the accompanying drawings, and the technical scope of the present disclosure is not limited to the above examples. Obviously, a person with ordinary knowledge in the technical field of the present disclosure can think of various changes and modifications within the scope of the technical concept described in the claims, and naturally understand that these changes and modifications belong to the technical scope of the present disclosure.

[0259] In addition, the effects described in this specification are merely illustrative or exemplary effects, not restrictive. That is, together with or in place of the above effects, the technology according to the present disclosure can achieve other effects that are obvious to those skilled in the art based on the description of this specification.

[0260] Furthermore, the present disclosure may also be configured as follows.

[0261] (1) An information processing device comprising:

[0262] a request unit configured to request information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; and

[0263] The output control unit is configured to control output of information obtained as a result of the request to a user.

[0264] (2) The information processing device according to (1),

[0265] Here, the request unit performs a request for a second target which is another target among the plurality of targets, based on information obtained due to a request for a first target which is one of the plurality of targets.

[0266] (3) The information processing device according to (2),

[0267] wherein the output control unit outputs information obtained due to the request for the first target to the user, and

[0268] The request unit then performs a request for the second target based on the user's operation.

[0269] (4) The information processing device according to any one of (1) to (3),

[0270] Here, when the registration destination of the data is the P2P database, the request unit requests additional history information on the data for at least one of the plurality of targets.

[0271] (5) The information processing device according to any one of (1) to (4),

[0272] Here, when the registration destination of the data is the P2P database, the output control unit outputs information indicating that the data cannot be deleted to the user.

[0273] (6) The information processing device according to any one of (1) to (5),

[0274] The request unit further requests, based on the operation of the user, at least one of the plurality of targets to register data in the P2P database.

[0275] (7) The information processing device according to (6),

[0276] The output control unit outputs information indicating that the data is being registered in the P2P database to the user during registration.

[0277] (8) The information processing device according to any one of (1) to (7),

[0278] The output control unit outputs the information obtained due to the request to the user in units of files or in units of data included in the files.

[0279] (9) The information processing device according to any one of (1) to (8),

[0280] Wherein, the P2P database is blockchain data.

[0281] (10) An information processing method executed by a computer, the information processing method comprising:

[0282] requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; and

[0283] Controls the output of information obtained as a result of the request to a user.

[0284] (11) A program for causing a computer to implement:

[0285] requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; and

[0286] Controls the output of information obtained as a result of the request to a user.

[0287] Reference numerals list

[0288] 100 client devices

[0289] 110 control unit

[0290] 111 Request Unit

[0291] 111a First request unit

[0292] 111b Second request unit

[0293] 112 Output Control Unit

[0294] 120 input units

[0295] 130 output units

[0296] 140 storage units

[0297] 150 communication units

[0298] 200 server devices

[0299] 210 control unit

[0300] 211 Access Control Unit

[0301] 211a P2P database access control unit

[0302] 211b storage access control unit

[0303] 220 storage units

[0304] 230 communication unit

[0305] 300-node device

[0306] 310 control unit

[0307] 320 storage units

[0308] 321P2P Database

[0309] 322P2P database program

[0310] 330 Communication Unit

[0311] 400 storage devices

[0312] 410 Control Unit

[0313] 420 storage units

[0314] 430 Communication Unit

[0315] 500P2P Network

[0316] 600 Network

Claims

1. An information processing device, comprising: a request unit configured to request information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; as well as An output control unit is configured to control output of information obtained due to the request to a user.

2. The information processing device according to claim 1, in, The request unit performs a request for a second target which is another target among the plurality of targets, based on information obtained as a result of a request for a first target which is one of the plurality of targets.

3. The information processing device according to claim 2, in, The output control unit outputs information obtained as a result of the request for the first target to the user, and The request unit then performs a request for the second target based on the user's operation.

4. The information processing device according to claim 1, in, In a case where the registration destination of the data is the P2P database, the request unit requests additional history information on the data for at least one of the plurality of targets.

5. The information processing device according to claim 1, in, In a case where the registration destination of the data is the P2P database, the output control unit outputs information indicating that the data cannot be deleted to the user.

6. The information processing device according to claim 1, in, The request unit further requests registration of data in the P2P database for at least one of the plurality of targets based on an operation of the user.

7. The information processing device according to claim 6, in, The output control unit outputs information indicating that the data is being registered in the P2P database to the user during registration.

8. The information processing device according to claim 1, in, The output control unit outputs information obtained due to the request to the user in units of files or in units of data included in the files.

9. The information processing device according to claim 1, in, The P2P database is blockchain data.

10. An information processing method executed by a computer, the information processing method comprising: requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; as well as Controls the output of information obtained as a result of the request to a user.

11. A storage medium having stored thereon a program which, when executed, causes a computer to: requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; and Controls the output of information obtained as a result of the request to a user.

12. A computer program product comprising a computer program / instructions, wherein: When the computer program / instructions are executed by a computer, the computer is caused to: requesting information about whether a registration destination of data is a P2P database or a storage unit other than the P2P database for a plurality of targets different from each other; as well as Controls the output of information obtained as a result of the request to a user.

Images