Sharing system, sharing method, maintenance node, generation node, and program

The sharing system uses blockchain channels to efficiently and securely share resource construction or failure information with customers, addressing communication challenges and ensuring transparency.

JP7578891B2Active Publication Date: 2024-11-07NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023500132
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-02-16
Publication Date
2024-11-07
Estimated Expiration
2041-02-16

AI Technical Summary

Technical Problem

Existing systems face challenges in efficiently sharing information on resource construction or failures with customers, leading to potential burdens in communication and coordination among different parties involved in service provision.

Method used

A sharing system utilizing blockchain technology to create operation and provision channels for sharing operation data and providing information on resource construction failures, involving a maintenance node with monitoring and updating units, and a providing node for customer notification.

Benefits of technology

Facilitates easy and secure sharing of construction work or failure information to customers, ensuring transparency and tamper-resistance through blockchain mechanisms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578891000001
    Figure 0007578891000001
  • Figure 0007578891000002
    Figure 0007578891000002
  • Figure 0007578891000003
    Figure 0007578891000003
Patent Text Reader

Abstract

A sharing system 1 comprises: a blockchain operation channel CP in which a plurality of nodes share operation data P including information about construction and failure of resources used in services provided to customers; a blockchain provision channel CV in which a plurality of nodes share provision data V used to provide customers with information about prescribed construction and failure of resources; a maintenance node 4 which is provided with a monitoring unit 42 that participates in the operation channel CP and the provision channel CV and monitors for construction and failure of resources, and an update unit 44 that, upon detecting an update of a construction or failure status relating to the provision channel CV in which the update unit 44 participates, updates the provision data V with the detected construction or failure status; and a provision node 6 which is provided with a notification unit 61 that participates in the provision channel CV, refers to the provision data V, and notifies customers of the updated construction or failure status.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a sharing system, a sharing method, a maintenance node, a generation node, and a program. [Background technology]

[0002] Distributed ledger technologies such as blockchain are known (Non-Patent Document 1). Blockchain is a technology in which multiple computers constituting a distributed network each have a ledger that records transaction history, ensuring tamper-resistance and transparency of transactions.

[0003] There is a system that reduces the cost of adding new services when coordinating services provided to customers (Patent Document 1). The configuration information of the coordinated service providing system constructed by the construction system is input to a configuration information management client. After confirming that the registration of the configuration information has been completed, the configuration information management client notifies the maintenance system.

[0004] There is open source integrated monitoring software for centralized monitoring of servers, networks, and applications (Non-Patent Document 2). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2018-206050 A [Non-patent literature]

[0006] [Non-Patent Document 1] osonoi, "Introduction to Blockchain / Hyperledger Fabric", [online], November 10, 2020, [Retrieved February 8, 2021], Internet〈URL:https: / / speakerdeck.com / osonoi / hyperledger-fabric-ru-men-bian-750c5a73-67d6-4ee3-9378-81d624c5e48e?slide=13〉 [Non-Patent Document 2] Assist, "Zabbix open source integrated monitoring tool", [online], November 10, 2020, [Retrieved February 8, 2021], Internet〈URL:https: / / www.ashisuto.co.jp / product / category / system-management / zabbix / 〉 Summary of the Invention [Problem to be solved by the invention]

[0007] Resources used for services provided to customers are subject to appropriate construction and are monitored for occurrence of failures. Information about construction or failures on these resources is shared with the parties providing the service as appropriate. Information about construction or failures should also be provided appropriately to customers who use the service. Since different customers are affected by each construction or failure, providing information about construction or failures can be a burden.

[0008] The present invention has been made in consideration of the above circumstances, and an object of the present invention is to provide a technique that can easily provide information about construction or malfunctions to customers who use a service. [Means for solving the problem]

[0009] A sharing system of one embodiment of the present invention includes a blockchain operation channel that shares operation data including information on construction faults of resources used in a service provided to a customer among multiple nodes, a blockchain provision channel that shares among multiple nodes provision data used to provide information on specified construction faults for the resources to the customer, a maintenance node that participates in the operation channel and the provision channel and has a monitoring unit that monitors construction faults of the resources, an update unit that, when it detects an update to the status of a construction fault for the provision channel it participates in, updates the detected status of the construction fault to the provision data, and a provision node that participates in the provision channel and has a notification unit that refers to the provision data and notifies the customer of the status of the construction fault after the update.

[0010] A sharing method of one embodiment of the present invention involves sharing operation data including information on construction faults of resources used in a service provided to a customer among multiple nodes, sharing a blockchain operation channel and provision data used to provide information on specified construction faults for the resource to the customer among multiple nodes, a maintenance node participating in the blockchain provision channel monitors construction faults of the resource, and when the maintenance node detects an update to the status of a construction fault for the provision channel in which it participates, it updates the detected status of the construction fault to the provision data, and the provision node participating in the provision channel refers to the provision data and notifies the customer of the updated status of the construction fault.

[0011] A maintenance node of one embodiment of the present invention is equipped with a blockchain operation channel that shares operation data including information on construction faults of resources used in services provided to customers among multiple nodes, and provision data that is used to provide information on specific construction faults for the resources to the customers among multiple nodes.The maintenance node participates in the blockchain provision channel and monitors construction faults of the resources, and an update unit that, when it detects an update to the status of a construction fault related to the provision channel it participates in, updates the detected status of the construction fault to the provision data.

[0012] A generating node of one embodiment of the present invention includes a generating unit that generates a blockchain provision channel that shares provision data related to the other construction breakdown information when other construction breakdown information is registered in operation data including information on a construction breakdown of a resource used in a service provided to a customer, and a request unit that requests a maintenance node participating in the blockchain operation channel that shares the operation data with other nodes to join the provision channel and requests the information on the other construction breakdown in the operation data to be registered in the provision data.

[0013] One aspect of the present invention is a program for causing a computer to function as the above-mentioned maintenance node or generation node. Effect of the Invention

[0014] According to the present invention, a technique can be provided that can easily provide information about construction or malfunctions to customers who use the service. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram illustrating a system configuration of a shared system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram for explaining an outline of the processing of the shared system. [Diagram 3]FIG. 3 is a diagram illustrating an example of a data structure of the operation data. [Figure 4] FIG. 4 is a diagram for explaining the sequence of a shared system (part 1). [Diagram 5] FIG. 5 is a diagram for explaining the sequence of the shared system (part 2). [Figure 6] FIG. 6 is a diagram for explaining an example of operation data registered in the sequence shown in FIG. 4-5 (part 1). [Figure 7] FIG. 7 is a diagram for explaining an example of operation data registered in the sequence shown in FIG. 4-5 (part 2). [Figure 8] FIG. 8 is a diagram for explaining an example of operation data registered in the sequence shown in FIG. 4-5 (part 3). [Figure 9] FIG. 9 is a diagram illustrating functional blocks of the maintenance node. [Figure 10] FIG. 10 is a flowchart illustrating the processing of the maintenance node. [Figure 11] FIG. 11 is a diagram illustrating the functional blocks of the generation node. [Figure 12] FIG. 12 is a diagram for explaining the hardware configuration of a computer used in each node. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the description of the drawings, the same parts are given the same reference numerals and the description will be omitted.

[0017] (Shared System) 1, information on construction or malfunction of resources used in services provided to customers is shared among resource managers and the like, and is provided to the customers. "Construction or malfunction" may be referred to as "construction malfunction."

[0018] In the sharing system 1, the scope of sharing information about resources is set using the Hyperledger Fabric function of the blockchain. In the example shown in Fig. 1, the sharing system 1 includes an operation channel CP, a first providing channel CV1 and a second providing channel CV2, a construction node 2, a management node 3, a maintenance node 4, a generation node 5, a first providing node 6a and a second providing node 6b.

[0019] The operation channel CP, the first provision channel CV1, and the second provision channel CV2 are channels in which the scope of data sharing is set using the blockchain's Hyperledger Fabric function. Data in the channel is shared between nodes participating in the channel.

[0020] The operation channel CP is used to provide services to customers. The operation channel CP shares operation data P, including information on construction failures of resources used in the services provided to customers, among multiple nodes. In the operation channel CP, the operation data P is shared among service providing nodes. In the example shown in Figure 1, the construction node 2, management node 3 and maintenance node 4 participate in the operation channel CP and share the operation data P.

[0021] The operation data P includes, for example, customer resource data and construction malfunction data. The customer resource data associates a customer identifier with an identifier of a resource used in a service provided to the customer. The construction malfunction data associates a construction or malfunction identifier for a resource with an identifier of the resource and a construction or malfunction state. The operation data P is formed using a blockchain mechanism, and therefore ensures the tamper-resistance and transparency of transactions.

[0022] The construction node 2 registers customer information and contract information regarding service contracts with customers in the operation data P. When providing a service to a customer, the management node 3 registers information about the service and information about the resources to be allocated for the service in the operation data P. The maintenance node 4 registers information about scheduled construction work for resources used in providing a service to a customer, or information about the occurrence of a fault detected during resource monitoring, in the operation data P.

[0023] The first provision channel CV1 and the second provision channel CV2 are used to provide information on construction failures to customers. The first provision channel CV1 and the second provision channel CV2 share, among multiple nodes, provision data V used to provide information on specific construction failures for resources to customers. The first provision channel CV1 and the second provision channel CV2 share information on different construction failures. The first provision channel CV1 and the second provision channel CV2 are each formed using a blockchain mechanism, thereby ensuring tamper-resistance or transparency of transactions.

[0024] In the first provision channel CV1, the first provision data V1 is shared between the maintenance node 4 and the first provision node 6a. The maintenance node 4 also participates in the operation channel CP, and registers information on construction malfunctions in the operation data P, and registers information on construction malfunctions related to the first provision channel CV1 in the first provision data V1. The first provision node 6a notifies the customer terminal 9a related to the construction malfunction of the information on the construction malfunction shared in the first provision channel CV1.

[0025] The second provision data V2 is shared between the maintenance node 4 and the second provision node 6b in the second provision channel CV2. The maintenance node 4 also participates in the operation channel CP, and registers information on construction malfunctions in the operation data P, and registers information on construction malfunctions related to the second provision channel CV2 in the second provision data V2. The second provision node 6b notifies the customer terminal 9b related to the construction malfunction of the information on the construction malfunction shared in the second provision channel CV2.

[0026] The first provided data V1 and the second provided data V2 each associate a state of the construction breakdown with a specific construction breakdown identifier, and an identifier of a customer related to the resource that is the subject of the construction breakdown. The first provided data V1 and the second provided data V2 each have information on different construction breakdown identifiers. The first provided data V1 and the second provided data V2 are formed using a blockchain mechanism, and therefore ensure the tamper-resistance or transparency of transactions.

[0027] When a new construction breakdown is registered in the operation channel CP, the generation node 5 generates a provision channel CV for providing information about the construction breakdown to customers. A provision channel CV is generated for each construction breakdown registered in the operation channel. A construction breakdown is one construction or one breakdown counted in the shared system 1, and is identified by one identifier until the construction or breakdown is completed. The provision data V shared in the provision channel CV corresponds, as information about the construction breakdown, to the identifier of a specific construction breakdown, the state of the construction breakdown, and the identifier of a customer related to the resource or service that is the subject of the construction breakdown.

[0028] 1, the shared system 1 includes one operation channel CP and two provision channels CV1 and CV2, but is not limited to this. The shared system 1 may include one or more operation channels CP and a provision channel CV for each construction or failure that occurs in a resource.

[0029] 1, a case will be described in which the maintenance node 4 participates in both the first provision channel CV1 and the second provision channel CV2, but this is not limiting. The shared system may include multiple maintenance nodes 4, one maintenance node participating in the first provision channel CV1, and another maintenance node participating in the second provision channel CV2.

[0030] When the first providing channel CV1 and the second providing channel CV2 are not particularly distinguished, they may be simply referred to as providing channel CV. When the first providing node 6a and the second providing node 6b are not particularly distinguished, they may be simply referred to as providing node 6. When the first providing data V1 and the second providing data V2 are not particularly distinguished, they may be simply referred to as providing data V.

[0031] An overview of the processing in the shared system 1 will be described with reference to Fig. 2. Fig. 2 shows (1) processing for registering new customer information and contract information to the operation channel CP, (2) processing for registering construction malfunction information for resources to the operation channel CP, (3) processing for generating a provision channel CV that provides the registered construction malfunction information to customers, and (4) processing for notifying customers of the construction malfunction information shared in the provision channel CV.

[0032] When a customer newly signs up for a service, in step S1 the construction node 2 issues a transaction to register the customer information and contract information in the operation channel CP. The customer information and contract information are registered in operation data P. The operation data P in which the customer information and contract information are registered is loosely synchronized between the nodes participating in the operation channel CP.

[0033] In step S2, the management node 3 updates the service information to be provided to the customer according to the contract information registered in step S1, and further allocates resources for providing the service to the customer. The management node 3 issues a transaction to register the service information and resource information in the operation channel CP. The service information and resource information are registered in operation data P. The operation data P in which the service information and resource information are registered is loosely synchronized between the nodes participating in the operation channel CP.

[0034] In step S3, the maintenance node 4 monitors the resources allocated for the services provided to the customer. When the maintenance node 4 detects a construction failure for the resource, it issues a transaction to register in the operation channel CP according to the detected construction failure information. The construction failure information is registered in the operation data P. The operation data P in which the construction failure information is registered is loosely synchronized between the nodes participating in the operation channel CP.

[0035] When the generating node 5 detects that new construction malfunction information has been registered in the operation data P, the generating node 5 searches for an identifier of a customer related to the construction malfunction in step S4. In step S5, the generating node 5 generates a provision channel CV for providing the construction malfunction information to the customer searched for in step S4.

[0036] In step S6, the generation node 5 requests the maintenance node 4 and the provider node 6 to participate in the provision channel CV generated in step S5. In step S6, the generation node 5 requests the maintenance node 4 to register information about the construction failure that triggered the search for the customer identifier in step S4 in the provision channel CV. The maintenance node 4 acquires construction failure information about the provision channel CV and information about the customer to whom the resource targeted by the construction failure is assigned from the operation channel CP. The maintenance node 4 issues a transaction to register the acquired construction failure information and customer information in the provision channel CV. In addition, when the construction failure information about the provision channel CV is updated in the operation channel CP, the maintenance node 4 issues a transaction to register the updated information in the provision channel CV. The updated construction failure information is registered in the provision channel CV. The provision data V in which the construction failure information is registered is loosely synchronized between the nodes participating in the provision channel CV.

[0037] The provider node 6 monitors the provided data V of the provided channel CV, and when the data of the provided data V is updated, in step S7, provides the updated data to the customer.

[0038] The providing node 6 refers to the provided data V and notifies the customer of the updated status of the construction malfunction. The providing node 6 refers to the provided data V and identifies contact information such as an email address of the customer. The providing node 6 notifies the identified contact information of the status of the construction malfunction updated in the provided data V. The providing node 6 may selectively provide data, for example, by providing the updated data to the customer if the updated data satisfies a specified condition, and not providing the data to the customer if the condition is not satisfied.

[0039] An example of operation data P shared through the operation channel CP will be described with reference to Fig. 3. The operation data P includes customer information, contract information, service information, service resource information, resource information, construction breakdown information, construction breakdown-resource information, customer-resource information, etc. The data structure shown in Fig. 3 is an example and is not limited thereto.

[0040] The customer information uses the customer's identifier (ID) as a key to associate information such as the customer's name, the identifier of the service used, contact information, etc. The contract information uses the customer's identifier and the service identifier as keys to associate information such as the start date of use, etc.

[0041] The service information uses the service identifier as a key to associate the service name with the identifier of the resource used. The service-resource information uses the service identifier and the resource identifier as keys to associate information such as the start date of use. The resource information uses the resource identifier as a key to associate the resource name, etc.

[0042] Construction breakdown information associates the construction breakdown name, occurrence date, recovery date, response history, information on resources affected by the construction breakdown, and service information, with the construction breakdown identifier as a key.Construction breakdown-resource information associates update dates, etc., with the construction breakdown identifier and resource identifier as keys.Customer-resource information associates construction breakdown information, with the customer identifier and resource identifier as keys.

[0043] The processing of the shared system 1 will be described with reference to Figures 4 and 5. An example of data registered in the operation data P will be described in Figures 6 to 8, but the data is not limited to this. For example, when a customer applies for an existing service or when existing resources are allocated, information on a service that the customer has applied for in advance or information on resources allocated to the customer may be registered in the service information, resource information, etc. Also, in Figures 6 to 8, construction failure information is described as failure information, and the description focuses on failures out of construction and failures.

[0044] First, in step S101, the construction node 2 acquires application information from the customer terminal 9. In step S102, the construction node 2 updates the operation data P of the operation channel CP with the application information acquired in step S101. In accordance with the update of the operation channel CP in step S102, the operation data P of the management node 3 and the maintenance node 4 are also synchronized in steps S103 and S104.

[0045] At this time, the data shown in Fig. 6 is registered in the operation data P. In the example shown in Fig. 6, the customer identifier, the customer name, contact information, etc. are registered in the customer information. The customer identifier, the identifier of the service for which the customer has subscribed, etc. are registered in the contract information. Furthermore, the identifier of the service for which the customer has subscribed, the service name, etc. are registered in the service table information.

[0046] In step S105, the management node 3 allocates resources and updates the operation channel CP in accordance with the application information synchronized in step S103. In accordance with the update of the operation channel CP in step S105, the operation data P of the construction node 2 and the maintenance node 4 are also synchronized in steps S106 and S107.

[0047] At this time, the data shown in Fig. 7 is registered in the operation data P. In the example shown in Fig. 7, compared to the example shown in Fig. 6, the identifiers of resources allocated to the service subscribed by the customer and the like are registered in the service-resource information. The identifiers of the customer and the identifiers of the resources allocated to the customer and the like are registered in the customer-resource information. Furthermore, the identifiers of the resources, the resource names, and the like are registered in the resource information.

[0048] In step S108, the maintenance node 4 starts monitoring the resources used in the service. As shown in step S109, the maintenance node 4 detects a failure of the resource from an alarm or the like issued by the resource. As shown in step S110, the maintenance node 4 may also detect the occurrence of construction work on the resource.

[0049] When the maintenance node 4 detects construction or a failure, it updates the operation channel CP in step S111. In accordance with the update of the operation channel CP in step S111, the operation data P of the construction node 2 and the management node 3 are also synchronized in steps S112 and S113.

[0050] At this time, the data shown in Fig. 8 is registered in the operation data P. In the example shown in Fig. 8, compared to the example shown in Fig. 7, the identifiers of resources allocated to the service subscribed by the customer and the like are registered in the failure information. The identifiers of the customer, the identifiers of the resources allocated to the customer, the identifiers of the failures related to the resources, and the like are registered in the customer-resource information. Furthermore, the identifiers of the resources, the resource names, and the like are registered in the resource information.

[0051] In step S151, the generating node 5 refers to the operation channel CP to acquire new construction breakdown information. In step S152, the generating node 5 refers to the operation channel CP to acquire the identifier of the customer related to the new construction breakdown acquired in step S151. In step S151, the new construction breakdown is identified as a breakdown with identifier "0001". In step S152, for the breakdown identifier "0001" identified in step S151, the identifier "0001" of the customer to which the affected service identifier "0001" and the affected resource identifier "0001" are assigned in the breakdown information is identified.

[0052] In step S153, the generation node 5 generates a provision channel CV. The generated provision channel is used to provide the information on the failure identified in step S151 to the customer identified in step S152.

[0053] In step S154, the generating node 5 receives a notification that generation of the provision channel CV has been completed. In step S155, the generating node 5 transmits a request to the maintenance node 4 to join the provision channel CV. In step S156, the maintenance node 4 joins the provision channel CV. In step S157, the generating node 5 transmits a request to the providing node 6 to join the provision channel CV. In step S158, the providing node 6 joins the provision channel CV.

[0054] In step S159, the generation node 5 instructs the maintenance node 4 to register the customer information and construction malfunction information in the provision channel CV. The information registered here is the construction malfunction acquired in step S151 and the information about the customer acquired in step S152. The information that the maintenance node 4 registers in the provision channel CV is information required when notifying the status of the construction malfunction, such as the notification destination, or information that may be provided to the customer, such as the construction malfunction status. In step S160, the maintenance node 4 registers the customer information and the construction malfunction information in the provision channel CV. In accordance with the update of the provision channel CV in step S160, the operation data P of the construction node 2 and the maintenance node 4 are also synchronized in step S161.

[0055] In step S162, when the maintenance node 4 detects an update of the customer information and the construction malfunction information, the maintenance node 4 registers the updated information in the provision channel CV. In accordance with the update of the provision channel CV in step S162, the provision data V of the provision node 6 is also synchronized in step S163.

[0056] In step S164, the provider node 6 notifies the customer terminal 9 of the status of the construction malfunction in accordance with the provided data V synchronized with other nodes belonging to the provided channel CV. The timing at which the provider node 6 notifies the customer terminal 9 may be set in the provided data V and the operation data P, or may be specified by the generating node 5. Although not shown in FIG. 5, after synchronizing the provided channel CV in step S161, the provider node 6 may notify the customer terminal 9 of the status of the construction malfunction. Furthermore, when the provider node 6 receives an inquiry from the customer terminal 9, it may notify the customer terminal 9 of the status of the construction malfunction.

[0057] In step S165, the provider node 6 receives an inquiry about the status of the construction malfunction from the customer terminal 9. In step S166, the provider node 6 transmits to the customer terminal 9 the status of the construction malfunction registered in the provision channel CV.

[0058] (Conservation node) The maintenance node 4 will be described with reference to Fig. 9. The maintenance node 4 participates in the operation channel CP and the provision channel CV.

[0059] The maintenance node 4 includes operation data P, first provided data V1, and second provided data V2, and functional units including a control unit 41, a monitoring unit 42, a registration unit 43, and an update unit 44. Each piece of data is stored in a memory 902 or a storage 903. Each function is implemented in a CPU 901.

[0060] The operation data P, the first provided data V1, and the second provided data V2 are shared with other nodes via the operation channel CP, the first provided channel CV1, and the second provided channel CV2, respectively.

[0061] The control unit 41 synchronizes the operation data P, the first provided data V1, and the second provided data V2 with other nodes. When the control unit 41 receives a transaction regarding these data, it processes the transaction and synchronizes these data.

[0062] The monitoring unit 42 monitors construction failures of resources. The monitoring unit 42 monitors resources used for services provided to customers, and detects construction or failures that have occurred in the resources.

[0063] When the monitoring unit 42 detects a new construction failure, the registration unit 43 registers information about the construction failure in the operation data P. The registration unit 43 assigns an identifier to the new construction or failure, and issues a transaction to update the construction failure information in the operation data P of each node participating in the operation channel CP. The registration unit 43 updates the operation data P held in the maintenance node.

[0064] When the update unit 44 detects an update to the state of a construction failure related to a provision channel CV in which the maintenance node 4 participates, it updates the detected state of the construction failure to the operation data P and the provision data V. The maintenance node 4 searches for the presence or absence of an update to the state of the construction failure for resources related to each provision channel CV in which it participates.

[0065] The maintenance node 4 belongs to both the first provision channel CV1 and the second provision channel CV2. When the update unit 44 detects an update of the state of a construction failure related to the first provision channel CV1 out of the first provision channel CV1 and the second provision channel CV2, the update unit 44 issues a transaction to update the first provision data V1 of each node participating in the first provision channel CV1. The update unit 44 updates the operation data held in the maintenance node 4.

[0066] When the update unit 44 detects an update to the state of a construction breakdown not related to the provision channel CV in which the maintenance node 4 participates, the update unit 44 issues a transaction to update the operation data P. The update unit 44 updates the operation data P held in the maintenance node 4.

[0067] The processing by the maintenance node 4 will now be described with reference to FIG.

[0068] In step S201, the maintenance node 4 monitors construction or failure of a resource.

[0069] In step S202, when new construction or a fault is detected, the process proceeds to step S203. In step S203, the new construction fault is registered in the operation data P.

[0070] In step S202, when an update of the construction or malfunction status is detected, the process proceeds to step S204. In step S204, the updated construction or malfunction status is registered in the operation data P and the provided data V.

[0071] The maintenance node 4 participates in both the operation channel CP and the provision channel CV. The maintenance node 4 registers the information registered in the operation channel in the necessary provision channel CV. Only the information necessary for notification to the customer is registered in the provision channel CV. The provision node 6 participating in that provision channel CV can appropriately notify the information necessary for notification to the customer.

[0072] (provider node) The provider node 6 participates in a provider channel CV. As shown in FIG.

[0073] The notification unit 61 notifies the customer of the updated status of the construction malfunction with reference to the provided data V. The provision node 6 identifies contact information, such as the customer's email address, with reference to the provided data V. The notification unit 61 notifies the identified contact information of the status of the construction malfunction updated in the provided data V. The notification unit 61 may selectively provide data, for example, by providing the updated data to the customer if the updated data satisfies a predetermined condition, and not providing the data to the customer if the condition is not satisfied.

[0074] When the notification unit 61 receives an inquiry about the status of a construction malfunction from a customer, it notifies the customer of the status of the construction malfunction related to the customer by referring to the provided data V. The notification unit 61 identifies the provided data V having construction malfunction information related to the customer who made the inquiry, and returns the status of the construction malfunction to the customer by referring to the identified provided data.

[0075] Although not shown in Fig. 1, the provider node 6 includes a control unit that synchronizes the provider data V with other nodes. When the control unit receives a transaction regarding the data, the control unit processes the transaction and synchronizes the data.

[0076] (Generate node) The generation node 5 will be described with reference to FIG.

[0077] The generation node 5 includes new data 52 and the functional units of an acquisition unit 51, a generation unit 53, and a request unit 54. The data is stored in a memory 902 or a storage 903. Each function is implemented in a CPU 901.

[0078] The acquisition unit 51 acquires newly registered construction breakdown information and customer information related to the construction breakdown in the operation data P, and generates new data 52. The new data 52 includes the newly registered construction breakdown information and customer information related to the construction breakdown.

[0079] There are several methods for the acquisition unit 51 to generate new data 52. The acquisition unit 51 may acquire operation data P from any reliable node participating in the operation channel CP, and generate new data 52 from the acquired operation data P. The acquisition unit 51 may request any reliable node participating in the operation channel CP to acquire newly registered construction failure information and customer information related to the construction failure, and acquire the new data 52 generated by the request. In addition, when the generation node 5 participates in the operation channel CP, the new data 52 may be generated from the operation data P that the generation node 5 itself has.

[0080] When new construction failure information is registered in the operation data P, the generation unit 53 generates a blockchain provision channel CV for sharing provision data V related to the new construction failure information. For example, when a first provision channel CV1 already exists in the shared system 1, when new construction failure information is registered in the operation data P, the generation unit 53 generates a second provision channel CV2 for notifying the customer of the new construction failure information. In the second provision channel CV2, the second provision data V2 for notifying the customer of the new construction failure information is shared.

[0081] The request unit 54 requests the maintenance node 4 and the provider node 6 to participate in the provision channel generated by the generation unit 53. The request unit 54 requests the maintenance node 4 to register new construction failure information in the operation data P in the provision channel generated by the generation unit 53. When the generation unit 53 generates the second provision channel CV2, the request unit 54 requests the maintenance node 4 and the provider node to participate in the second provision channel CV2. The request unit 54 requests the maintenance node 4 to register information for notifying customers of construction failure information related to the second provision channel CV2 in the second provision data V2 of the second provision channel CV2.

[0082] The generating node 5 generates one provision channel CV for one construction breakdown. The generating node 5 registers, in the provision channel CV, information for notifying the customer related to the provision channel CV of the construction breakdown information.

[0083] The sharing system 1 can easily provide information on construction or malfunction related to a service to a customer who uses the service, out of the construction malfunction information shared by the operator who provides the service.

[0084] Each node in the present embodiment described above is, for example, a general-purpose computer system including a CPU (Central Processing Unit, processor) 901, a memory 902, a storage 903 (HDD: Hard Disk Drive, SSD: Solid State Drive), a communication device 904, an input device 905, and an output device 906. In this computer system, the CPU 901 executes a program loaded on the memory 902, thereby realizing each function of each node.

[0085] Each node may be implemented by one computer, or may be implemented by multiple computers, and each node may be a virtual machine implemented by a computer.

[0086] The programs of each node can be stored on a computer-readable recording medium such as a HDD, SSD, USB (Universal Serial Bus) memory, CD (Compact Disc), or DVD (Digital Versatile Disc), or can be distributed via a network.

[0087] The present invention is not limited to the above-described embodiment, and various modifications are possible within the scope of the present invention. [Explanation of symbols]

[0088] 1. Shared Systems 2 Building Nodes 3 Management Node 4. Conservation Node 5. Generate Nodes 6 Provider Node 9 Customer terminal 41 Control section 42 Monitoring Department 43 Registration Department 44 Update section 51 Acquisition Department 52 New Data 53 Generation part 54 Request section 61 Notification Department 901 CPU 902 Memory 903 Storage 904 Communication equipment 905 Input Device 906 Output Device CP Operation Channel CV delivery channel P Operation Data V Provided Data

Claims

1. Using a blockchain operation channel, operation data including information on construction failures of resources used in a service provided to multiple customer terminals is shared among multiple nodes, A control unit that uses the provision channel of the blockchain to provide information on a predetermined construction failure for the resource to the multiple customer terminals, and shares the provision data including the state of the construction failure and identifiers of the multiple customer terminals related to the construction failure among multiple nodes; A monitoring unit that monitors construction failures of the resource; a maintenance node including an update unit that updates the provided data with the detected state of a construction failure when the monitoring unit detects an update of the state of a construction failure related to the provided data; a control unit that shares the provided data with a plurality of nodes using the provided channel; a provision node including a notification unit that refers to the provision data and notifies the plurality of customer terminals related to the construction fault of the state of the construction fault after updating; A shared system comprising:

2. An acquisition unit that acquires the operation data from a node that shares the operation data, and acquires information on new construction failures in the operation data; A generation unit that generates other provision data related to the new construction failure information; a generating node including a request unit that requests the maintenance node and the other providing nodes to share the other providing data among a plurality of nodes, and requests the maintenance node to register information on the new construction failure in the operation data in the other providing data; The sharing system of claim 1 further comprising:

3. When the notification unit of the provider node receives an inquiry about a state of a construction breakdown from one of the multiple customer terminals, the notification unit refers to the provided data and notifies the customer terminal that originated the inquiry about the state of the construction breakdown. The sharing system of claim 1 .

4. A maintenance node uses an operation channel of a blockchain to share among a plurality of nodes operation data including information on construction failures of resources used in a service provided to a plurality of customer terminals, and uses a provision channel of the blockchain to provide information on a specific construction failure for the resource to the plurality of customer terminals, and shares among the plurality of nodes provision data including the state of the construction failure and identifiers of the plurality of customer terminals related to the construction failure; a provider node shares the provided data among a plurality of nodes using the provided channel; The maintenance node monitors construction failures of the resource; When the maintenance node detects an update of a state of a construction failure related to the provided data, the maintenance node updates the state of the construction failure detected in the provided data; The provision node refers to the provision data and notifies the plurality of customer terminals related to the construction failure of the updated state of the construction failure. How to share.

5. Using a blockchain operation channel, operation data including information on construction failures of resources used in a service provided to multiple customer terminals is shared among multiple nodes, A control unit that uses the provision channel of the blockchain to provide information on a predetermined construction failure for the resource to the multiple customer terminals, and shares the provision data including the state of the construction failure and identifiers of the multiple customer terminals related to the construction failure among multiple nodes; A monitoring unit that monitors construction failures of the resource; an update unit that updates the provided data with the detected state of the construction failure when the monitoring unit detects an update of the state of the construction failure related to the provided data; Equipped with conservation nodes.

6. An acquisition unit that acquires operation data including information on construction failures of resources used in a service provided to a plurality of customer terminals from a node that shares the operation data, and acquires new construction failure information in the operation data; A generation unit that generates other provision data related to the new construction failure information; a request unit that requests a maintenance node that shares the operation data with other nodes to share the other provided data among a plurality of nodes and requests that information on the new construction failure in the operation data be registered in the other provided data; A generating node comprising:

7. A program for causing a computer to function as the maintenance node according to claim 5 or the generation node according to claim 6.

Citation Information

Patent Citations

  • Service cooperation device and service cooperation method

    JP2018206050A

  • Vehicle information processor, control method, and vehicle data provision system

    JP2019156148A

  • Construction management server, management system for construction data, program for construction management server

    JP2020095445A

  • Failure detection system

    JP2020107203A

  • Medical information management system and member device used in same

    WO2020049656A1