Computer, method, and program for supporting information sharing

Abstract

To provide a computer that supports information sharing, which solves a problem that even if an information registrant generates shared information suitable for an information user, when the information is used for a purpose not intended by the information registrant, the information does not fully reflect the purpose of use of the information user, and is insufficient as shared information.SOLUTION: A computer having a processor and a storage, in which the processor stores, in the storage, shared information registered by an information registrant and a sharing purpose related to the shared information, where the shared information is registered information registered by the information registrant or information generated by processing the registered information in accordance with the sharing purpose, stores, in the storage, the purpose of use of the registration information of the information user, acquires an information sharing gap by comparing at least the shared information or the sharing purpose with use purpose in order to share information with the information user, and generates, on the basis of the information sharing gap, supplemental information and shares the shared information and the supplemental information with the information user.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a disaster response support technology for supporting infrastructure restoration, evacuation guidance, etc., when a disaster occurs. [Background technology]

[0002] One example of a technology for controlling information sharing is described in Patent Publication No. 2021-111406 (Patent Document 1).

[0003] Patent document 1 describes a method in which a user assigns priorities to each profile to be used only within a community such as business, social, or video game, and then selects and associates profiles for each friend or associate.The system then integrates and customizes the three highest-priority profiles from the associated profiles to generate a profile for each individual friend or associate. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-111406 Summary of the Invention [Problem to be solved by the invention]

[0005] In the method described in Patent Document 1, registered information is customized from multiple pieces of registered information including profiles, etc., to generate shared information suited to the information user. However, if the information user uses the shared information for another community, for example, and the information is used for a purpose that is difficult to identify from the information user's attributes and is not intended by the information registrant, the information does not fully reflect the information user's intended use, and is not sufficient as shared information. [Means for solving the problem]

[0006] In order to solve at least one of the above problems, one aspect of the present invention realizes the following method.

[0007] That is, the computer that supports information sharing according to the present invention is a computer having a processor and a storage that stores an information sharing program, and the processor that executes the information sharing program: (1) stores in the storage first shared information registered by a first information registrant and a first sharing purpose related to the first shared information, wherein the first shared information is the first registered information registered by the first information registrant or information generated by processing the first registered information in accordance with the first sharing purpose; (2) stores in the storage a first purpose of use of the first registered information related to a first information user; and (3) in order to share information with the first information user: (3a) obtains a first information sharing gap by comparing at least the first shared information or the first sharing purpose with the first use purpose; (3b) generates first supplementary information based on the first information sharing gap; and (3c) shares the first shared information and the first supplementary information with the first information user.

[0008] Other problems and solutions disclosed in the present application will be made clear in the section of embodiments of the invention and the drawings. [Effects of the Invention]

[0009] According to one aspect of the present invention, it is possible to generate information to be shared by taking into consideration not only the sharing purpose of the information registrant but also the usage purpose of the information user with whom the information is shared. Problems, configurations, and effects other than those described above will become clear from the description of the following embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a conceptual diagram of an information sharing system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram illustrating an example of a configuration of an information sharing system according to an embodiment of the present invention. [Figure 3A]FIG. 2 is an explanatory diagram illustrating an example of a sharing purpose database held by the information sharing system according to the embodiment of the present invention. [Figure 3B] FIG. 2 is an explanatory diagram illustrating an example of a sharing purpose database held by the information sharing system according to the embodiment of the present invention. [Figure 4A] FIG. 2 is an explanatory diagram illustrating an example of a registration information database held by the information sharing system according to the embodiment of the present invention. [Figure 4B] FIG. 2 is an explanatory diagram illustrating an example of a registration information database held by the information sharing system according to the embodiment of the present invention. [Figure 4C] FIG. 2 is an explanatory diagram illustrating an example of a registration information database held by the information sharing system according to the embodiment of the present invention. [Figure 4D] FIG. 2 is an explanatory diagram illustrating an example of a registration information database held by the information sharing system according to the embodiment of the present invention. [Figure 4E] FIG. 2 is an explanatory diagram illustrating an example of a registration information database held by the information sharing system according to the embodiment of the present invention. [Figure 5A] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 5B] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 5C] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 5D] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 5E] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 5F] FIG. 2 is an explanatory diagram illustrating an example of a shared information database held by the information sharing system according to the embodiment of the present invention. [Figure 6A] FIG. 2 is an explanatory diagram illustrating an example of a purpose of use database held by the information sharing system according to the embodiment of the present invention. [Figure 6B]FIG. 2 is an explanatory diagram illustrating an example of a purpose of use database held by the information sharing system according to the embodiment of the present invention. [Figure 7A] FIG. 2 is an explanatory diagram illustrating an example of a supplementary information database held by the information sharing system according to the embodiment of the present invention. [Figure 7B] FIG. 2 is an explanatory diagram illustrating an example of a supplementary information database held by the information sharing system according to the embodiment of the present invention. [Figure 7C] FIG. 2 is an explanatory diagram illustrating an example of a supplementary information database held by the information sharing system according to the embodiment of the present invention. [Figure 8A] 10 is a flowchart illustrating an example of a process in which the information sharing system according to the embodiment of the present invention generates shared information and supplemental information and shares the information. [Figure 8B] 10 is a flowchart illustrating an example of a process in which the information sharing system according to the embodiment of the present invention generates shared information and supplemental information and shares the information. [Figure 9] FIG. 10 is an explanatory diagram illustrating an example of a screen displayed by the information sharing system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0012] The information sharing system and method according to the present invention are a system and method for generating shared information that can be shared by multiple information registrants, for example by removing sensitive information from the information registered by multiple information registrants, and generating supplemental information that is consistent with the intended use of the information, for use in disaster response, such as when infrastructure operators restore infrastructure or when local governments provide evacuation guidance to residents in the event of a disaster. Here, the shared information is generated based on the registered information registered by others and the intended use of the information. Furthermore, the supplemental information is generated by extracting an information sharing gap (gap) between the shared information and the intended use registered by the information user, acquiring additional information to eliminate the information sharing gap, and generating supplemental information to fill the information sharing gap based on the information. Sharing this shared information and supplemental information with the information user reduces the information sharing gap (gap) when the information user uses the information. Here, the additional information is acquired by acquiring the registered information if it is included in the registered information, or by inquiring about the information registrant to acquire new information, or by inquiring about other information registrants to acquire alternative information (alternative information). Finally, based on the access management information about the information user, it is determined whether the information user is allowed to access the shared information and supplementary information. [Example]

[0013] This embodiment shows an example of effective information sharing in the event of a disaster, when information users such as infrastructure operators who restore infrastructure or local governments who provide evacuation guidance use information shared by others to respond to the disaster.

[0014] The details of this embodiment will be described with reference to Figures 1 to 9. However, the present invention is not limited to this embodiment, and can be applied to any situation in which information is shared.

[0015] Before describing the details of the embodiment, an overview of the embodiment will be first described with reference to Fig. 1. In the embodiment, when an information user such as an infrastructure operator uses registered information from others to carry out disaster response such as infrastructure restoration in the event of a disaster, the information user generates shared information that can be shared by using the registered information from others as is or by processing the registered information, such as by deleting sensitive information, and generates supplementary information so as not to deviate from the information user's intended use, thereby enabling effective information sharing.

[0016] FIG. 1 is a conceptual diagram of an information sharing system according to an embodiment of the present invention.

[0017] Specifically, Fig. 1 is composed of an information registrant 111 that registers disaster-related information, an information user 121 such as an infrastructure operator that responds to disasters, and an information sharing system 200 that supports information sharing from the information registrant 111 to the information user 112. Here, the information registrant 111 registers various disaster-related information at the time of a disaster as registered information 101, and at that time registers the purpose of information sharing as sharing purpose 102. The information registrant 111 also registers access management information 105 for information sharing. Meanwhile, the information user 112 registers the purpose of using the registered information 101 as usage purpose 104, in order to carry out disaster response such as infrastructure recovery at the time of a disaster.

[0018] The information sharing system 200 includes an information receiving and collecting unit 211, a shared information generating unit 212, a supplementary information generating unit 213, an information sharing unit 214, a sharing purpose database 221, a registration information database 222, a shared information database 223, a usage purpose database 224, and a supplementary information database 225.

[0019] The information reception / collection unit 211 receives information from the information registrant 111 and the information user 112, stores the registration information 101 in the registration information database 222, stores the sharing purpose 102 in the sharing purpose database 221, and stores the usage purpose 104 and access management information 105 in the usage purpose database 224. The shared information generation unit 212 processes the registration information 101 so that it does not deviate from the sharing purpose 102, and stores it in the shared information database 223 as shared information 103.

[0020] Depending on the sharing purpose 102, the shared information generation unit 212 may generate the registered information 101 as the shared information 103 without processing it (i.e., the registered information is used as is), or may generate the shared information 103 by performing any processing on the registered information 101. Processing is mainly intended to delete sensitive information, and while there are no specific limitations on the method, typical examples include summarization, thinning, and statistical processing. Summarization, for example, is the deletion of details of information, and may include, for example, approximating or rounding numerical values, and deleting details such as street names and block numbers from addresses. Statistical processing, for example, includes aggregation and averaging.

[0021] The supplemental information generating unit 213 compares the shared information 103 with the intended use 104, extracts the information sharing gap (divergence) as an information sharing gap, and acquires additional information to eliminate the information sharing gap.

[0022] The additional information is acquired by acquiring it from a part of the registered information 101, by inquiring of the information registrant 111 and acquiring it as new registered information, or by inquiring of another information registrant 111 that holds information similar to and capable of substituting the registered information 101 (alternative information) and acquiring the alternative information as new registered information. Here, the supplemental information generation unit 213 generates supplemental information 106 for filling the information sharing gap based on the information sharing gap and the additional information.

[0023] Thereafter, the information sharing unit 214 determines whether the information user 112 can access the shared information 103 and the supplementary information 106 based on the supplementary information 106 and the access management information 105, and if both or either one of them is accessible, displays the accessible information to the information user 112 on the input / output device 232.

[0024] FIG. 2 is a block diagram showing an example of the configuration of an information sharing system 200 according to an embodiment of the present invention.

[0025] The information sharing system 200 includes a central control unit 230, a main memory unit 210, an auxiliary memory unit 220, a communication unit 231, and an input / output unit 232. These are interconnected by a bus.

[0026] The auxiliary storage device 220 stores a shared purpose database 221 , a registration information database 222 , a shared information database 223 , a use purpose database 224 , and a supplementary information database 225 .

[0027] The main memory device 210 stores programs. The information reception / collection unit 211, the shared information generation unit 212, the supplemental information generation unit 213, and the information sharing unit 214 are programs. Hereinafter, when an entity is described as "XX unit," it means that the central control device 230 reads each program from the auxiliary memory device 220, loads it into the main memory device 210, and then realizes the function of each program (described in detail later).

[0028] The central control device 230 is an example of a processor, and another example is a GPU (Graphics Processing Unit), but other semiconductor devices may be used as long as they are the main body that executes predetermined processing.

[0029] The information sharing system 200 is a system that supports the sharing of disaster information registered by an information registrant 111 via an input / output device 232 with information users 121 who are engaged in disaster response, such as infrastructure restoration, via the input / output device 232, in the event of a disaster.

[0030] The information registration system 250 is a system owned by the information registrant 111, and instead of the information registrant 111 registering disaster-related information in the input / output device 232 of the information sharing system 200, the information registrant 111 may register the disaster-related information in an input / output device (not shown) of the information registration system 250, and the information sharing system 200 may receive and register the information via the communication line 240. The information usage system 251 is a system owned by the information user 112, and instead of the information user 112 obtaining shared information and supplemental information for disaster response from the input / output device 232 of the information sharing system 200, the information user 112 may transmit the shared information and supplemental information from the information sharing system 200 to the information usage system 251 via the communication line 240, and the information received by the information usage system 251 may be obtained from the input / output device (not shown) of the information usage system 251. Here, the information registration system 250 and the information usage system 251 are general-purpose computers, and communicate with the information sharing system 200 via the communication line 240.

[0031] The communication line 240 may be a LAN (Local Area Network), a dedicated line, a WAN (Wide Area Network), a power line network, a wireless network, a public line network, a mobile phone network, a satellite communication line, or any other network. When a public communication line such as a public line network is used, VPN (Virtual Private Network) technology may be used to conceal the contents of communication and create a pseudo-dedicated line.

[0032] Information sharing system 200 may be a subsystem of information registration system 250 or information usage system 251. Alternatively, information sharing system 200 may be a subsystem of a system that includes both information sharing system 200 and information registration system 250, or both information sharing system 200 and information usage system 251, or all of information sharing system 200, information registration system 250, and information usage system 251.

[0033] Here, the databases held by information sharing system 200 will be described in detail.

[0034] 3A to 4E and 6B show examples of databases that store information input by information registrant 111 from input / output device 232 of information sharing system 200. Note that instead of directly inputting this information to input / output device 232 of information sharing system 200, information registrant 111 may input this information to an input / output device of information registration system 250, and the information may then be received as data from information registration system 250 to information sharing system 200 via communication line 240. Here, particularly, FIG. 6B shows information entered by information registrant 111 while referring to shared information database 223 and supplemental information database 225. Note that this information may also be automatically set by information sharing system 200 based on the registered information.

[0035] 6A shows an example of a database that stores information input by information user 112 from input / output device 232 of information sharing system 200. Note that instead of directly inputting this information to input / output device 232 of information sharing system 200, the information user 112 may input the information to an input / output device of information usage system 251, and the information may be received as data from information usage system 251 to information sharing system 200 via communication line 240.

[0036] 5A to 5F and 7A to 7C are assumed to store information that is automatically registered by the information sharing system.

[0037] 3A and 3B are explanatory diagrams showing an example of the sharing purpose database 221 held by the information sharing system 200 according to the embodiment of the present invention.

[0038] The sharing purpose database 221 stores a registration information management table 300 (FIG. 3A) and a sharing purpose table 310 (FIG. 3B).

[0039] In the registration information management table 300 illustrated in FIG. 3A, data such as the ID and name of the registered information is stored in order to manage the type of disaster-related information (hereinafter referred to as registered information) registered by the information registrant 111.

[0040] The registration information management table 300 is made up of a registration information ID 301, a name 302, and a description 303. The registration information ID 301 is a key for identifying each record.

[0041] The registration information ID 301 is an identifier for uniquely identifying the registration information registered by the information registrant 111, and is assigned by the information sharing system 200. Note that the registration information ID 301 may be assigned by the information registration system 250 and received as data via the communication line 240. The name 302 indicates the name of the registration information. The description 303 indicates what kind of information the registration information is. The name 302 and the description 303 are both registered by the information registrant 111. Note that the information registration system 250 may analyze the registration information and automatically register the name 302 and the description 303.

[0042] Next, the sharing purpose table 310 illustrated in FIG. 3B stores data for managing the ID of the registered information registered by the information registrant 111, the purpose of sharing with others, and the ID of the shared information generated based on the ID.

[0043] The sharing purpose table 310 is made up of a sharing purpose ID 311, a sharing purpose 312, a format 313, a registration information ID 314, and a sharing information ID 315. The sharing purpose ID 311 is a key for identifying each record.

[0044] The sharing purpose ID 311 is an identifier for uniquely identifying a sharing purpose indicating the purpose for which the information registrant 111 shares registered information with others, and is assigned by the information sharing system 200. Note that the sharing purpose ID 311 may be an ID assigned by the information registration system 250 and received as data via the communication line 240. The sharing purpose 312 indicates the purpose for sharing the registered information registered by the information registrant 111. The format 313 indicates the format of the data that the information registrant 111 desires to share in the information sharing, such as data aggregated by city, ward, town, or village or raw data before aggregation. The registered information ID 314 indicates the identifier of the registered registered information. The shared information ID 315 indicates an identifier for identifying shared information generated by processing the registered information indicated by the registered information ID 314 in accordance with the sharing purpose 312 and the format 313.

[0045] 4A, 4B, 4C, 4D, and 4E are explanatory diagrams showing examples of the registration information database 222 held by the information sharing system 200 according to the embodiment of the present invention.

[0046] The registration information database 222 stores an RI0010 table 400 (FIG. 4A), an RI0020 table 410 (FIG. 4B), an RI0030 table 420 (FIG. 4C), an RI0021 table 430 (FIG. 4D), and an RI0031 table 440 (FIG. 4E).

[0047] Here, the above table names "RI0010" to "RI0031" correspond to the values of the registration information ID 301 in the registration information management table 300. For example, the RI0010 table 400 shown in FIG. 4A shows an example of the contents of the registration information identified by the value "RI0010" of the registration information ID 301. The same applies to the other tables in the registration information database 222.

[0048] In the RI0010 table 400 illustrated in FIG. 4A, data on remaining gasoline at gas stations, which indicates how much gasoline remains at each gas station at the time of a disaster, is stored among the registered information registered by the information registrant 111.

[0049] The RI0010 table 400 is made up of a base ID 401, a name 402, an address 403, a remaining amount of gasoline 404, and an update 405. The base ID 401 is the key for identifying each record.

[0050] The base ID 401 is an identifier for uniquely identifying a gas station, and is assigned by the information registrant 111 or the information registration system 250, or is a number that was already assigned at the time the information registrant 111 or the information registration system 250 obtained the information. The name 402 indicates the name of the gas station. The address 403 indicates the address of the gas station. The remaining gasoline amount 404 indicates the amount of gasoline remaining at the gas station. The update 405 indicates the date this record was updated. The update 405 may also include the hour, minute, second, etc.

[0051] Next, in the RI0020 table 410 illustrated in FIG. 4B, among the registered information registered by the information registrant 111, data on drawing information of underground buried objects is stored, which indicates the location of underground buried objects that have a significant impact on the lives of residents, such as water supply and sewage, electricity, gas, and communications.

[0052] The RI0020 table 410 is composed of an underground buried area ID 411, an object 412, a document type 413, a name 414, an area 415, a document link 416, and an update 417. The keys for identifying each record are the underground buried area ID 411, the object 412, and the document type 413.

[0053] The underground buried area ID 411 is an identifier for uniquely identifying the area in which underground buried objects are managed. It is assigned by the information registrant 111 or the information registration system 250, or it is a number that was already assigned at the time the information registrant 111 or the information registration system 250 obtained the information. The object 412 indicates the type of underground buried object, i.e., water supply and sewerage, electricity, gas, or communications, which have a significant impact on the lives of residents. The document type 413 indicates the type of drawing used to manage the location of the underground buried object. The name 414 indicates the name used to manage the underground buried object. The area 415 indicates the address of the underground buried object's location. The document link 416 indicates the address where the drawing of the underground buried object is electronically managed. The update 417 indicates the date this record was updated. The update 417 may also include the hour, minute, second, etc.

[0054] Next, in the RI0030 table 420 illustrated in FIG. 4C, data on fire occurrence status indicating the occurrence, spread, and extinguishing of a fire that has a serious impact on the safety of residents is stored from among the registered information registered by the information registrant 111.

[0055] The RI0030 table 420 is composed of a fire situation ID 421, a mesh ID 422, an address 423, a fire situation 424, an outbreak confirmation 425, a fire extinguishing confirmation 426, and an update 427. The keys for identifying each record are the fire situation ID 421 and the mesh ID 422.

[0056] The fire situation ID 421 is an identifier for uniquely identifying a fire that occurred at the time of the disaster, and is assigned by the information registrant 111 or the information registration system 250, or is a number that was already assigned at the time the information registrant 111 or the information registration system 250 obtained the information. The mesh ID 422 is a regional mesh ID that is generally used to uniquely identify a region, and indicates the location to which the fire outbreak situation of the fire situation ID 421 relates. The regional mesh may be any general mesh, such as a 500m mesh or a 250m mesh.

[0057] Address 423 indicates the address of the regional mesh with mesh ID 422. Fire status 424 indicates the latest status of the fire with fire status ID 421 in the regional mesh with mesh ID 422. Occurrence confirmation 425 indicates the date on which the fire with fire status ID 421 was confirmed in the regional mesh with mesh ID 422. Fire suppression confirmation 426 indicates the date on which the fire with fire status ID 421 was confirmed to have been suppressed in the regional mesh with mesh ID 422. Update 427 indicates the date on which this record was updated. The date of occurrence confirmation 425, fire suppression confirmation 426, and update 427 may all include the hour, minute, second, etc.

[0058] Next, the RI0021 table 430 illustrated in Fig. 4D shows additional information that has been added to the registered information registered by the information registrant 111 to eliminate the information sharing gap with the intended use 104 of the information user 112. In the example of Fig. 4D, data on diagram information of underground buried objects is stored, which indicates the locations of underground buried objects that have a significant impact on the lives of residents, such as water supply and sewage, electricity, gas, and communications.

[0059] The RI0021 table 430 is composed of an underground buried area ID 431, an object 432, a document type 433, a name 434, an area 435, a document link 436, and an update 437. The keys for identifying each record are the underground buried area ID 431, the object 432, and the document type 433.

[0060] The configuration of the RI0021 table 430 is the same as the drawing information of the underground buried object shown in the RI0020 table 410. That is, the underground buried area ID 431, object 432, document type 433, name 434, area 435, document link 436, and update 437 are the same items as the underground buried area ID 411, object 412, document type 413, name 414, area 415, document link 416, and update 417 shown in Fig. 4B, respectively, and therefore detailed explanations will be omitted.

[0061] Next, the RI0031 table 440 illustrated in Fig. 4E shows additional information registered as alternative information to the shared information, that is, the fire outbreak situation, in order to eliminate the information sharing gap with the information user 112's purpose of use 104, among the registered information registered by the information registrant 111. In the example of Fig. 4E, data on fire estimation information showing estimated information on the occurrence, spread, and extinguishing of a fire that has a serious impact on the safety of residents is stored.

[0062] The RI0031 table 440 is composed of a fire estimation ID 441, a mesh ID 442, an address 443, a fire estimation 444, an outbreak estimation 445, a fire extinguishing estimation 446, and an update 447. The keys for identifying each record are the fire estimation ID 441 and the mesh ID 442.

[0063] The fire estimation ID 441 is an identifier for uniquely identifying a fire estimated to have occurred at the time of the disaster, and is assigned by the information registrant 111 or the information registration system 250, or is a number that was already assigned at the time the information registrant 111 or the information registration system 250 obtained the information. The mesh ID 442 is a regional mesh ID that is generally used to uniquely identify a region, and indicates the location of the fire estimated to have occurred and identified by the fire estimation ID 441. The regional mesh may be any general mesh, such as a 500m mesh or a 250m mesh.

[0064] Address 443 indicates the address of the regional mesh with mesh ID 442. Fire estimate 444 indicates the latest estimated status of the fire with fire estimate ID 441 in the regional mesh with mesh ID 442. Estimated occurrence 445 indicates the date on which the fire with fire estimate ID 441 is estimated to occur in mesh ID 442. Estimated fire suppression 446 indicates the date on which the fire with fire estimate ID 441 is estimated to be suppressed in the regional mesh with mesh ID 442. Update 447 indicates the date on which this record was updated based on the estimate. The date of estimated occurrence 445, estimated fire suppression 446, and update 447 may all include the hour, minute, second, etc.

[0065] 4A to 4E, each table in the registration information database 222 may include identification information (such as the name) of the information registrant 111 who registered the information. In the example shown in FIGS. 4A to 4E, the RI0020 table 410 and the RI0021 table 430 were registered by the same information registrant 111, and the RI0030 table 420 and the RI0031 table 440 were registered by different information registrants 111.

[0066] Furthermore, the registration information database 222 of this embodiment stores information on remaining gasoline at gas stations, information indicating the status (e.g., location) of underground buried objects, information indicating the occurrence of a fire, etc. These are examples of information that are considered necessary for activities such as rescue and restoration in response to a disaster such as an earthquake, and may include at least one of information indicating the location of resources, information indicating the status of facilities, information indicating the status of a disaster (e.g., landslide, flooding, traffic obstruction, etc.), etc.

[0067] Furthermore, in this embodiment, the registration and sharing of information assuming disaster response is described as an example, but the present invention is not limited to disasters and can be applied to the registration and sharing of any information.

[0068] 5A, 5B, 5C, 5D, 5E, and 5F are explanatory diagrams showing examples of the shared information database 223 held by the information sharing system 200 according to the embodiment of the present invention.

[0069] In the shared information database 223, an SI0010 table 500 (FIG. 5A), an SI0020 table 510 (FIG. 5B), and an SI0030 table 520 (FIG. 5C) are stored.

[0070] Here, the above table names "SI0010" to "SI0030" correspond to the values of the shared information ID 315 in the shared purpose table 310. For example, the SI0010 table 500 shown in Fig. 5A shows an example of the contents of the shared information identified by the value "SI0010" of the shared information ID 315. The same applies to the other tables in the shared information database 223.

[0071] In the SI0010 table 500 illustrated in FIG. 5A, data on remaining gasoline at gas stations, which indicates how much gasoline remains at gas stations in each city, ward, town, or village at the time of a disaster, is stored among the shared information generated based on the registration information of the information registrant 111 and the purpose of sharing.

[0072] The SI0010 table 500 is made up of a city / ward / town / village ID 501, a name 502, the number of gas station locations 503, a remaining amount of gasoline 504, and an update 505. The city / ward / town / village ID 501 is the key for identifying each record.

[0073] The city / ward / town / village ID 501 is an identifier such as a city / ward / town / village code that is generally used to uniquely identify a city / ward / town / village. The name 502 indicates the name of the city / ward / town / village. The number of gas station locations 503 indicates the number of gas station locations that have remaining gasoline in the city / ward / town / village. Note that the number of gas station locations 503 may indicate the number of all gas station locations regardless of whether there is remaining gasoline, or may indicate the number of each location together with, for example, "number of locations with remaining gasoline / total number of gas station locations."

[0074] The remaining gasoline amount 504 indicates the total amount of gasoline remaining at gas stations in a city, ward, town, or village. The remaining gasoline amount 504 may also be displayed as both the capacity and the total amount remaining, such as "total remaining gasoline amount / total capacity of all gas station locations." Update 505 indicates the date this record was updated. Update 505 may also include the hour, minute, second, etc.

[0075] Next, in the SI0020 table 510 illustrated in Figure 5B, data on drawing information of underground buried objects, which is shared information generated based on the registration information of the information registrant 111 and the purpose of sharing, is stored, and which indicates the location of underground buried objects that have a significant impact on the lives of residents, such as water supply and sewage, electricity, gas, and communications.

[0076] The SI0020 table 510 is composed of an underground buried area ID 511, an object 512, a document type 513, a name 514, an area 515, a document link 516, and an update 517. The keys for identifying each record are the underground buried area ID 511, the object 512, and the document type 513.

[0077] The configuration of the SI0020 table 510 is the same as the underground buried object drawing information of the RI0020 table 410 and the RI0021 table 430. That is, the underground buried area ID 511, object 512, document type 513, name 514, area 515, document link 516, and update 517 are the same items as, for example, the underground buried area ID 411, object 412, document type 413, name 414, area 415, document link 416, and update 417 shown in FIG. 4B, respectively, and therefore detailed explanations thereof will be omitted.

[0078] Next, in the SI0030 table 520 illustrated in FIG. 5C, data on the occurrence of a fire, which has a serious impact on the safety of residents, and the spread and extinguishing of the fire, is stored among the shared information generated based on the registration information of the information registrant 111 and the purpose of sharing.

[0079] The SI0030 table 520 is composed of a fire situation ID 521, a mesh ID 522, an address 523, a fire situation 524, an outbreak confirmation 525, a fire extinguishing confirmation 526, and an update 527. The keys for identifying each record are the fire situation ID 521 and the mesh ID 522.

[0080] The configuration of the SI0030 table 520 is the same as the fire outbreak status of the RI0030 table 420. That is, the fire situation ID 521, mesh ID 522, address 523, fire situation 524, outbreak confirmation 525, fire extinguishing confirmation 526, and update 527 are the same items as the fire situation ID 421, mesh ID 422, address 423, fire situation 424, outbreak confirmation 425, fire extinguishing confirmation 426, and update 427 shown in Fig. 4C, respectively, and therefore detailed description thereof will be omitted.

[0081] Note that Figure 5A shows an example of shared information generated by aggregating registered information, and Figures 5B and 5C show examples of shared information generated from the registered information itself without processing. However, these are just examples of shared information, and shared information can be generated from each piece of registered information either without processing or by processing it in any way (for example, by aggregating, averaging, summarizing, thinning, etc.).

[0082] For example, Fig. 5D shows shared information created by summarizing remaining gasoline 404 as "0-19KL" for the RI0010 table, which shows gas station remaining gasoline information, among the registered information. Similarly to SI0010, Fig. 5E shows shared information created by tallying the remaining gasoline by city, ward, town, or village, and then dividing the totaled remaining gasoline by the number of households in the city, ward, town, or village to obtain an average value. Fig. 5F shows shared information created by thinning out addresses 403.

[0083] For example, in SI0011 table 530 shown in FIG. 5D, base location ID 531, name 532, address 533, and update 535 are respectively the same as base location ID 401, name 402, address 403, and update 405 in RI0010 table 400 shown in FIG. 4A. A summarized value of remaining gasoline amount 404 is stored in remaining gasoline amount 534. For example, if the value of remaining gasoline amount 404 is "24 KL (kiloliters)," this is replaced with a numerical value with a predetermined range, and a summarized value of "20-30 KL" is stored as remaining gasoline amount 534.

[0084] In SI0012 table 540 shown in Fig. 5E, city / ward / town / village ID 541, name 542, number of gas station locations 543, and update 545 are respectively the same as city / ward / town / village ID 501, name 502, number of gas station locations 503, and update 545 in SI0010 table 500 shown in Fig. 5A. And, remaining gasoline per household 544 stores the value obtained by dividing the value of remaining gasoline 504 by the number of households in the city / ward / town / village (i.e., the average remaining gasoline per household).

[0085] In the SI0013 table 550 shown in Fig. 5F, the location ID 551, name 552, remaining gasoline amount 553, and update 554 are the same as the location ID 401, name 402, remaining gasoline amount 404, and update 405 in the RI0010 table 400 shown in Fig. 4A. The address 403 in the RI0010 table 400 has been deleted (i.e., thinned out) in the SI0013 table 550.

[0086] 6A and 6B are explanatory diagrams showing an example of the intended use database 224 held by the information sharing system 200 according to the embodiment of the present invention.

[0087] The purpose of use database 224 stores a purpose of use table 600 (FIG. 6A) and an access management information table 610 (FIG. 6B).

[0088] The purpose of use table 600 illustrated in FIG. 6A stores data for managing the purpose of use registered by the information user 112 for the shared information, the ID of the supplementary information generated based on the purpose of use, and the ID of the registered information on which the supplementary information is generated.

[0089] The purpose of use table 600 is made up of a purpose of use ID 601, a purpose of use 602, a format 603, a registered information ID 604, an additional information ID 605, and a supplemental information ID 606. The purpose of use ID 601 is the key for identifying each record.

[0090] The purpose of use ID 601 is an identifier for uniquely identifying the purpose of use of the information user 112 for the information shared from others, and is assigned by the information sharing system 200. Note that the purpose of use ID 601 here may be an ID assigned by the information use system 251 and received as data via the communication line 240. The purpose of use 602 indicates how the information user 112 will use the information shared from others. The format 603 indicates the format of the data the information user 112 wishes to use when using the information, such as data aggregated by city, ward, town, or village, or raw data before aggregation, etc.

[0091] The registered information ID 604 is an identifier of the registered information registered by the information registrant 111, and indicates the information that forms the basis of the shared information used by the information consumer 112. The additional information ID 605 is an identifier of the registered information that is additionally registered by the information registrant 111 in order to eliminate the information sharing gap extracted from the shared information generated from the registered information of the registered information ID 604, and the intended use 602 and format 603. The supplemental information ID 606 indicates an identifier for identifying the supplemental information generated by processing the registered information of the additional information ID 605 in accordance with the intended use 602 and format 603.

[0092] Next, the access management information table 610 illustrated in Figure 6B stores a user ID indicating the information user 112 and data regarding the shared information and supplementary information that the information user 112 can access (i.e., data indicating that the information user 112 can access the shared information generated from the sharing purpose ID, the shared information of the shared information ID, and the supplementary information of the supplementary information ID).

[0093] The access management information table 610 is made up of a user ID 611, a sharing purpose ID 612, a shared information ID 613, and a supplementary information ID 614. The user ID 611 is used as a key to identify each record.

[0094] The user ID 611 is an identifier for uniquely identifying the information user 112 and is assigned by the information sharing system 200. Note that the user ID 611 here may be an identifier assigned by the information use system 251 and received as data via the communication line 240. The sharing purpose ID 612 is an identifier for uniquely identifying the sharing purpose registered by the information user 112 and is assigned by the information sharing system 200. The shared information ID 613 is an identifier for uniquely identifying shared information that can be accessed by the information user 112 with the user ID 611, among the shared information generated by the information sharing system 200, and is assigned by the information sharing system 200. The supplemental information ID 614 is an identifier for uniquely identifying supplemental information that can be accessed by the information user 112 with the user ID 611, among the supplemental information generated by the information sharing system 200, and is assigned by the information sharing system 200.

[0095] 7A, 7B, and 7C are explanatory diagrams showing examples of the supplementary information database 225 held by the information sharing system 200 according to the embodiment of the present invention.

[0096] In the supplemental information database 225, an SI0010-1 table 700 (FIG. 7A), an SI0020-1 table 710 (FIG. 7B), and an SI0030-1 table 720 (FIG. 7C) are stored.

[0097] Here, the above table names "SI0010-1" to "SI0030-1" correspond to the values of the supplementary information ID 606 in the intended use table 600. For example, the SI0010-1 table 700 shown in FIG. 7A shows an example of the contents of the shared information identified by the value "SI0010-1" of the supplementary information ID 606. The same applies to the other tables in the supplementary information database 225.

[0098] In the SI0010-1 table 700 illustrated in FIG. 7A, data on remaining gasoline at gas stations, which is one of the supplementary information used by the information user 112, is stored, and indicates how much gasoline remains at each gas station at the time of a disaster.

[0099] The SI0010-1 table 700 is composed of a location ID 701, a name 702, an address 703, a remaining amount of gasoline 704, and an update 705. The key for identifying each record is the location ID 701. The configuration of the SI0010-1 table 700 is the same as the gas station remaining amount information in the RI0010 table 400. In other words, the location ID 701, the name 702, the address 703, the remaining amount of gasoline 704, and the update 705 correspond to the location ID 401, the name 402, the address 403, the remaining amount of gasoline 404, and the update 405 shown in FIG. 4A, respectively.

[0100] Next, in the SI0020-1 table 710 shown in FIG. 7B, among the supplementary information used by the information user 112, data indicating the location of underground buried objects that have a significant impact on the lives of residents, such as water supply and sewerage, electricity, gas, and communications, is stored, and among these, in particular, data indicating test drilling result reports and underground buried object completion confirmation books from when each infrastructure operator, such as water supply and sewerage, electricity, gas, and communications, has excavated in the past for facility maintenance, etc., is stored, separate from the facility drawings of the shared information.

[0101] The SI0020-1 table 710 is composed of an underground buried area ID 711, an object 712, a document type 713, a name 714, an area 715, a document link 716, and an update 717. The keys for identifying each record are the underground buried area ID 711, the object 712, and the document type 713.

[0102] The configuration of SI0020-1 table 710 is the same as the underground buried object drawing information of RI0020 table 410, RI0021 table 430, and SI0020 table 510. That is, underground buried area ID 711, object 712, document type 713, name 714, area 715, document link 716, and update 717 correspond to underground buried area ID 431, object 432, document type 433, name 434, area 435, document link 436, and update 437 shown in Fig. 4D, respectively.

[0103] Next, in the SI0030-1 table 720 illustrated in FIG. 7C, data on fire estimation information indicating estimated information is stored as alternative information to the fire occurrence situation indicating the occurrence, spread, and extinguishing of a fire that has a serious impact on the safety of residents, among the supplementary information used by the information user 112.

[0104] The SI0030-1 table 720 is composed of a fire estimation ID 721, a mesh ID 722, an address 723, a fire estimation 724, an outbreak estimation 725, a fire extinguishing estimation 726, and an update 727. The keys for identifying each record are the fire estimation ID 721 and the mesh ID 722.

[0105] The configuration of SI0030-1 table 720 is the same as the fire estimation information in RI0031 table 440. That is, fire estimation ID 721, mesh ID 722, address 723, fire estimation 724, outbreak estimation 725, fire suppression estimation 726, and update 727 correspond to fire estimation ID 441, mesh ID 442, address 443, fire estimation 444, outbreak estimation 445, fire suppression estimation 446, and update 447 shown in FIG. 4E, respectively.

[0106] 8A and 8B are flowcharts showing an example of a process in which the information sharing system 200 according to the embodiment of the present invention generates shared information and supplemental information and shares the information.

[0107] In step S800, the central control unit 230 starts the processing flow, and then the process proceeds to step S801.

[0108] In process S801, the information receiving and collecting unit 211 receives the registration information and sharing purpose registered by the information registrant 111 via the input / output device 232. The information receiving and collecting unit 211 stores the ID, name, etc. of the registration information and the sharing purpose in the registration information management table 300 and the sharing purpose table 310 of the sharing purpose database 221, respectively. The information receiving and collecting unit 211 also stores details of the registration information in the registration information database 222.

[0109] Furthermore, here, the information receiving and collecting unit 211 receives, from the information registrant 111, a user ID that identifies the information user 112 who is permitted to access the shared information generated in the information sharing system 200 based on the sharing purpose for each sharing purpose. Then, the information receiving and collecting unit 211 stores information indicating that the information user 112 is permitted to access the shared information in the access management information table 610 of the usage purpose database 224. Specifically, the information receiving and collecting unit 211 stores the received user ID in user ID 611, and stores the ID of the shared information generated based on the received sharing purpose in sharing purpose ID 612 corresponding to the user ID.

[0110] In process S802, the shared information generation unit 212 generates shared information from the sharing purpose stored in the shared purpose table 310 of the sharing purpose database 221 and the registration information stored in the registration information database 222, and stores the generated shared information in the shared information database 223. At this time, the shared information generation unit 212 searches for the corresponding table name in the registration information database 222 for each sharing purpose ID 311 using the registration information ID 314 as a key, and processes the configuration of the corresponding table, which is the registration information, so that it matches the format 313, to generate the shared information.

[0111] For example, for the shared purpose ID 311 "SO0010" shown in Fig. 3B, the table for the corresponding registered information ID 314 "RI0010" is searched for by table name in the registered information database 222, and the RI0010 table 400 in Fig. 4A is obtained. Here, since the format 313 is "number of locations with remaining gasoline for each city, ward, town, or village, and total amount," the shared information generation unit 212 aggregates the addresses 403 in the RI0010 table 400 for each city, ward, town, or village, determines the number of location IDs 401 in the aggregated RI0010 table 400 for each city, ward, town, or village as the number of locations, and calculates the sum of the remaining gasoline amounts 404 as the total amount of remaining gasoline.

[0112] The shared information generation unit 212 assigns a shared information ID "SI0010" to the shared information thus generated and stores it in shared information ID 315, and also generates SI0010 table 500 in the shared information database 223 to store the above shared information. When storing the information, the name of the city, ward, town, or village to be counted is stored in name 502, the number of counted locations is stored in number of gas station locations 503, the total amount is stored in remaining gasoline amount 504, and the date of generation process is stored in update 505. The shared information generation unit 212 also separately obtains a city, ward, town, or village code that is commonly used to uniquely identify a city, ward, town, or village from an external system, matches it with name 502, and stores the corresponding city, ward, town, or village code in city, ward, town, or village ID 501.

[0113] Furthermore, in this case, the user ID 611 and the sharing purpose ID 612 in the access management information table 610 of the usage purpose database 224 are set to indicate that the information user 112 can access the shared information generated from the sharing purpose, and further, to clarify that the information user 112 can also access the shared information specifically generated in process S802, the shared information ID indicating the shared information generated in process S802 is stored in the shared information ID 613 of the same record.

[0114] In step S 803 , the information receiving and collecting unit 211 receives the purpose of use registered by the information user 112 via the input / output device 232 and stores it in the purpose of use table 600 of the purpose of use database 224 .

[0115] In process S804, the supplemental information generation unit 213 extracts an information sharing gap based on the shared information database 223 and the usage purpose table 600 of the usage purpose database 224. For example, the supplemental information generation unit 213 searches for the table of the registration information ID 604 "RI0010" by table name in the registration information database 222 for the usage purpose ID 601 "UO002" in the usage purpose table 600, and acquires the RI0010 table 400 of FIG. 4A. Furthermore, the supplemental information generation unit 213 searches for the registration information ID 314 in the shared purpose table 310 of the shared purpose database 221 using the registration information ID 604 "RI0010" as a key, identifies the shared information ID 315 "SI0010" of the corresponding record, and identifies the corresponding SI0010 table 500 in the shared information database 223.

[0116] 5A, the SI0010 table 500 stores the number of gas station locations and remaining gasoline amounts tallied by city, ward, town, or village. This format has a gap with "Address of gas station, remaining amount, in XXX city, XXX prefecture" in format 603 of the usage purpose table 600, so the supplemental information generation unit 213 extracts this as an information sharing gap. Note that the supplemental information generation unit 213 may also extract the information sharing gap by comparing format 603 ("Address of gas station, remaining amount, in XXX city, XXX prefecture" in the above example) with format 313 of the shared purpose table 310 ("Number of gas station locations with remaining amount, total amount, in each city, ward, town, or village" in the above example).

[0117] In process S805, the supplemental information generation unit 213 determines whether or not there is an information sharing gap extracted in process S804. If an information sharing gap has been extracted, it is determined that there is a gap (process S805: Yes), and the process proceeds to process S806. If no information sharing gap has been extracted, it is determined that there is no gap (process S805: No), and the process proceeds to process S812.

[0118] In process S806, the supplemental information generation unit 213, in order to acquire additional information for eliminating the information sharing gap, first determines whether the registration information database 222 contains additional information (i.e., information that will eliminate the information sharing gap when added to the shared information 103). For example, for a record with usage purpose ID 601 "UO002" in the usage purpose table 600 of the usage purpose database 224, the format 603 is "Address and remaining amount of gas station in XXX city, XXX prefecture," and the registration information ID 604 is "RI0010," so the table name in the registration information database 222 is searched for using the registration information ID 604 "RI0010" as a key, and the RI0010 table 400 is acquired.

[0119] Here, since the RI0010 table 400 and the format of the format 603 "Address of gas station, remaining amount, in XXX city, XXX prefecture" match, it is determined that there is no information sharing gap between the two, and that the registration information database 222 contains additional information (Process S806: Yes). Thus, if the registration information contains additional information, the process proceeds to Process S810. On the other hand, if the registration information does not contain additional information (Process S806: No), the process proceeds to Process S807.

[0120] In process S807, the supplemental information generation unit 213 requests the information registrant 111 to register additional information to eliminate the information sharing gap in order to acquire additional information to eliminate the information sharing gap. For example, for a record with the usage purpose ID 601 "UO003" in the usage purpose table 600 of the usage purpose database 224, the format 603 is "facility drawings of underground buried objects in AAA town, XXX city, XXX prefecture, test excavation result report, and underground buried property completion confirmation book." In response to this, assuming that an information sharing gap with the shared information has been extracted, the supplemental information generation unit 213 requests the information registrant 111 to register the additional information "test excavation result report, underground buried property completion confirmation book."

[0121] Here, in extracting information sharing gaps, the supplemental information generation unit 213 searches the registered information ID 314 of the shared purpose table 310 of the shared purpose database 221 using the registered information ID 604 "RI0020" as a key, and identifies the shared information ID 315 "SI0020" of the corresponding record. The supplemental information generation unit 213 searches the table name of the shared information database 223 using this "SI0020" as a key, identifies the SI0020 table 510, and acquires the document type 513 "equipment drawing." The supplemental information generation unit 213 also searches the table name of the registered information database 222 using the registered information ID 604 "RI0020" as a key, identifies the RI0020 table 410, and acquires the document type 413 "equipment drawing." Since both document type 513 "Equipment Drawing" and document type 413 "Equipment Drawing" are in a different format from the "Exploratory Drilling Result Report / Underground Buried Property Completion Confirmation Book," the supplementary information generation unit 213 extracts this as an information sharing gap.

[0122] In process S808, if the information registrant 111 has no problem with registering the additional information requested in process S807 (in the example of process S807, the additional information is "Test Excavation Result Report / Underground Buried Property Completion Confirmation Book") (process S808: Yes), the supplemental information generation unit 213 accepts this and the process proceeds to process S810. On the other hand, if there is a problem with registering the additional information (process S808: No), the supplemental information generation unit 213 accepts this and the process proceeds to process S809.

[0123] For example, if the information registrant 111 who registered the information in the RI0020 table 410 also possesses the test drilling result report and underground buried property completion confirmation book, and is able to add and register it upon request, it is determined that there is no problem with the registration of the additional information (process S808: Yes).On the other hand, if the information registrant does not possess the test drilling result report and underground buried property completion confirmation book, or if they possess it but cannot disclose it, it is determined that there is a problem with the registration of the additional information (process S808: No).

[0124] In process S809, the supplemental information generation unit 213 requests other information registrants 111 (for example, information registrants 111 other than the information registrant 111 who registered the information in the RI0020 table 410) to register additional information to resolve the information sharing gap, in order to obtain additional information to resolve the information sharing gap. At this time, the supplemental information generation unit 213 may make the request to all information registrants 111, as in a broadcast, or may make the request only to specific information registrants 111. If each table in the registration information database 222 contains identification information of the information registrant 111 who registered the information, the identification information can be referenced to select the information registrant 111 to request registration of additional information.

[0125] For example, for a record with usage purpose ID 601 "UO006" in usage purpose table 600 of usage purpose database 224, format 603 is "Fire outbreak status for each mesh in HHH ward, ZZZ city, XXX prefecture, and neighboring cities and towns (ZZZ city)," and an information sharing gap with the shared information is extracted for this, so supplemental information generation unit 213 requests information registrant 111 to register additional information "Fire outbreak status in III town, JJJ town, HHH ward, ZZZ city, XXX prefecture," with the condition that registration of alternative information is also acceptable. Here, supplemental information generation unit 213 searches registration information ID 314 in shared purpose table 310 of shared purpose database 221 using registration information ID 604 "RI0030" as a key, and identifies shared information ID 315 "SI0030" of the corresponding record. Using this "SI0030" as a key, the table name in the shared information database 223 is searched for, and the SI0030 table 520 is identified.

[0126] Because the SI0030 table 520 differs from the format of "Fire outbreak status in III Town, JJJ Town, HHH Ward, ZZZ City, XXX Prefecture," the supplemental information generation unit 213 extracts this as an information sharing gap. As a result, if the information registrant 111 possesses the requested alternative information and there is no problem with registering it in the information sharing system 200 (Process S809: Yes), the supplemental information generation unit 213 accepts this fact and proceeds to Process S810. On the other hand, if there seems to be a problem with registering the alternative information, such as the information registrant 111 not possessing the alternative information or possessing the alternative information but being unable to disclose it (Process S809: No), the supplemental information generation unit 213 accepts this fact and proceeds to Process S812.

[0127] In process S810, the information receiving and collecting unit 211 receives the additional information registered by the information registrant 111 via the input / output device 232. The information receiving and collecting unit 211 stores the ID, name, etc. of the registered information in the registered information management table 300 of the sharing purpose database 221, and stores details of the registered information in the registered information database 222. In addition, the registered information ID of the registered information registered as additional information here is stored in the additional information 605 of the usage purpose table 600 of the usage purpose database 224.

[0128] For example, in the case of the additional information "Test Excavation Result Report / Underground Buried Property Completion Confirmation Book" shown in the example of process S807, the information reception and collection unit 211 adds the information relating to it as a new record to the registered information management table 300, stores it in the RI0021 table 430 of the registered information database 222 as drawing information of the underground buried object, and stores the registered information ID "RI0021" in the additional information 605 of the intended use table 600. Similarly, although omitted in Fig. 3A, the registered information ID 301 of the new record added to the registered information management table 300 will be "RI0021."

[0129] Also, for example, if the additional information shown in the example of process S809 is replacement information for "Fire outbreak status in III Town, JJJ Town, HHH Ward, ZZZ City, XXX Prefecture," the information reception and collection unit 211 adds the information therefor as a new record to the registration information management table 300, stores it as fire presumption information in the RI0031 table 440 of the registration information database 222, and stores the registration information ID "RI0031" in the additional information 605 of the usage purpose table 600. Similarly, although omitted in Fig. 3A, the registration information ID 301 of the new record added to the registration information management table 300 will be "RI0031."

[0130] Note that, since the additional information in process S805 is included in the original registration information (i.e., the source of the shared information to be added), it is not newly added or stored in the registration information management table 300 or the registration information database 222, but is only stored in the additional information 605 in the usage purpose table 600. For example, in the record for usage purpose ID "UO002", "RI0010" is stored as the registration information ID 604, and "RI0010" is also stored as the additional information ID 605.

[0131] In process S811, the supplemental information generation unit 213 generates supplemental information from the purpose of use stored in the purpose of use table 600 of the purpose of use database 224 and the additional information stored in the registration information database 222, and stores the generated supplemental information in the supplemental information database 225. In this case, for each purpose of use ID 601 in the purpose of use table 600, the corresponding table name in the registration information database 222 is searched for using the additional information ID 605 as a key, and the configuration of the corresponding table, which is the registered information as additional information, is processed to match the format 603 of the purpose of use table 600, thereby generating the supplemental information.

[0132] For example, for the intended use ID 601 "UO002" shown in Fig. 6A, the supplemental information generation unit 213 searches the table of additional information ID 605 "RI0010" by table name in the registration information database 222, and acquires the RI0010 table 400 in Fig. 4A. Here, since the format 603 is "Address and remaining amount of gas station in XXX city, XXX prefecture," the supplemental information generation unit 213 thins out other records so that the only address 403 in the RI0010 table 400 is XXX city, XXX prefecture.

[0133] The supplemental information generation unit 213 assigns a supplemental information ID "SI0010-1" to the supplemental information thus generated and stores it in the supplemental information ID 606, and also generates an SI0010-1 table in the supplemental information database 225 and stores the supplemental information. At this time, the supplemental information generation unit 213 stores the date of generation processing in update 705. Also, at this point, the supplemental information generation unit 213 receives information from the information registrant 111 indicating that access to the supplemental information is permitted for the user ID, and stores the user ID and supplemental information ID of the supplemental information in the user ID 611 and supplemental information ID 614, respectively, in the access management information table 610 of the intended use database 224.

[0134] In process S812, the information sharing unit 214 determines whether the information user 112 can access the shared information and supplemental information from the access management information table 610 in the intended use database 224. At this time, access is determined based on whether the values of the shared information ID 613 and supplemental information ID 614 indicating the shared information and supplemental information being judged are in the same record as the value of the user ID 611 indicating the information user 112 being judged. If access is possible, access is deemed to be permitted and the process proceeds to process S813, and if access is not possible, access is deemed to be denied and the process proceeds to process S814.

[0135] In step S813, the information sharing unit 214 displays the shared information and supplementary information on the input / output device 232 used by the information user 112, thereby sharing the information.

[0136] In step S814, the central processing unit 130 ends the processing flow.

[0137] In addition, in process S802, when generating shared information, if the previously generated shared information is incorrect due to an error in the registration information or the like, the information related to the incorrect shared information can be deleted from each database, or the information can be overwritten and updated to become the correct shared information.

[0138] Note that the steps up to step S802 may be executed before the information user 112 starts disaster response, and the steps from step S803 onwards may be executed when the information user 112 starts disaster response.

[0139] In step S803, the information user 112 may register a different purpose of use from the one initially registered at any time, and this registration may trigger the execution of steps S803 and subsequent steps.

[0140] When extracting information sharing gaps in process S804, the information stored in each database may be extracted using some or all of the 5W1H items (When, Where, Who, What, Why, and How). For this purpose, each database may hold data in the 5W1H format.

[0141] It should be noted that approval may be obtained from the information registrant 111 each time additional information is acquired in process S806. For example, if it is determined in process S806 that additional information is included in the registered information (process S806: Yes), the information reception and collection unit 211 may output information about the information user 112 requesting the additional information or information on the intended use of the information user 112 to the information registrant 111 who registered the registered information, and request approval for providing the additional information. Then, if approval is obtained, the information reception and collection unit 211 acquires the additional information (process S810), and the supplemental information generation unit 213 generates the supplemental information (process S811).

[0142] Generally, if the purpose of use does not match the purpose of sharing, additional information may not be provided. However, in particularly urgent cases, such as during a disaster, it will be possible to make an exceptional decision to approve the provision of additional information, which will contribute to a rapid disaster response.

[0143] In the process S807, the process S808, and the process S809, an inquiry may be made to the information registration system 250, and in this case, the information registrant 111 may not be involved, and the process may be automatically carried out between the systems.

[0144] In addition, in process S811, when generating supplementary information, if the previously generated supplementary information is incorrect due to an error in the additional information, etc., the information related to the erroneous supplementary information may be deleted from each database, or may be overwritten and updated to become the correct supplementary information.

[0145] 8A and 8B show processing blocks surrounded by dotted lines. Specifically, processing block 820 consisting of processing S801 and processing S802, processing block 821 consisting of processing S803, processing block 822 consisting of processing S804, processing block 823 consisting of processing S805 to processing S811, processing block 830 consisting of processing S806, processing block 831 consisting of processing S807 and processing S808, processing block 832 consisting of processing S809, and processing block 824 consisting of processing S812 and processing S813 are shown.

[0146] Next, information output by information sharing system 200 will be described with reference to FIG.

[0147] FIG. 9 is an explanatory diagram showing an example of a screen displayed by the information sharing system 200 according to the embodiment of the present invention.

[0148] Specifically, Figure 9 shows an example of a screen showing the process of generating shared information and supplementary information, which is used to output and display shared information and supplementary information from the input / output device 232 used by the information user 112 in process S813 of Figure 8.

[0149] This example screen may be referenced by the information registrant 111 or the system administrator of the information sharing system 200 to check the generation process when shared information or supplementary information is generated in process S802 or process S811, and may also be referenced by other users including the information registrant 111, information user 112, and system administrator at the timing of other processes.

[0150] The shared information / supplemental information generation process screen shown in FIG. 9 is made up of a shared information generation process 900 and a supplemental information generation process 910.

[0151] The shared information generation process 900 is made up of registration information 901 , a generation arrow 902 , and shared information 903 .

[0152] An explanation will be given based on the example described in process S802. For example, assume that the registration information 901 is the registration information with the registration information ID "RI0010." In this case, since the registration information is the registration information with the registration information ID 314 "RI0010" in the registration information management table 300 of the shared purpose database 221, the name 302 "Gas station remaining amount information" and the description 303 "Addresses and remaining amounts of gas stations nationwide" are obtained and displayed in the registration information 901. In addition, the table with the registration information ID 314 "RI0010" is searched for by table name in the registration information database 222, the RI0010 table 400 is identified, and the latest value "2023.9.19" in the update 405 is obtained and displayed in the registration information 901.

[0153] Next, for shared information 903, the shared purpose ID in shared purpose table 310 is searched for from registration information ID 314 "RI0010," and the format 313 of that record, "Number of gas station locations with remaining capacity, total amount," is obtained and displayed, and the shared information ID 315 of that record, "SI0010," is obtained and the table for "SI0010" is searched for by table name in shared information database 223. A link that can refer to the identified SI0010 table 500 is generated and displayed in shared information 903. Generation arrow 902 conceptually shows the process of generating shared information 903 from registration information 901.

[0154] Next, a supplemental information generation process 910 is made up of additional information 911 , a generation arrow 912 , and supplemental information 913 .

[0155] An explanation will be given based on the example described in process S811. For example, suppose the additional information 911 is the registration information with the registration information ID "RI0010." In this case, since the registration information is the registration information with the registration information ID 314 "RI0010" in the registration information management table 300 of the shared purpose database 221, the name 302 "Gas station remaining amount information" and the description 303 "Addresses and remaining amount of gas stations nationwide" are obtained and displayed in the additional information 911. In addition, the table with the registration information ID 314 "RI0010" is searched for by table name in the registration information database 222, the RI0010 table 400 is identified, and the latest value "2023.9.19" in the update 405 is obtained and displayed in the additional information 911.

[0156] Next, for the supplemental information 913, the registration information ID "RI0010" of the registration information 901 and the registration information ID "RI0010" of the additional information 911 are used to search the registration information ID 604 "RI0010" and the additional information ID 605 "RI0010" in the usage purpose table 600 of the usage purpose database 224, respectively, to identify a record that matches both. Then, the format 603 "Address of gas station, XXX city, XXX prefecture, remaining amount" of the record is obtained and displayed in the supplemental information 913, and the supplemental information ID 606 "SI0010-1" of the record is obtained and the table for "SI0010-1" is searched for by table name in the supplemental information database 225. A link that can refer to the identified SI0010-1 table 700 is generated and displayed in the supplemental information 913. A generation arrow 912 conceptually shows the process of generating the supplemental information 913 from the additional information 911.

[0157] The registration information 901 may indicate the name of the information registrant 111 who registered the registration information, thereby indicating whose information is the basis for the shared information. The additional information 911 may indicate the name of the information registrant 111 who registered the registration information that is the additional information, thereby indicating whose information is the basis for the supplementary information. For this purpose, the registration information database 222 may store the name of the information registrant 111.

[0158] Furthermore, the system according to the embodiment of the present invention may be configured as follows.

[0159] [1] A computer having a processor (e.g., a central control unit 230) and storage (e.g., a main memory 210 and an auxiliary memory 220) storing an information sharing program (e.g., a program for realizing an information reception / collection unit 211, a shared information generation unit 212, a supplementary information generation unit 213, and an information sharing unit 214), The processor that executed the information sharing program: (1) The storage stores first shared information registered by a first information registrant (e.g., information in the shared information database 223) and a first sharing purpose related to the first shared information (e.g., information in the sharing purpose database 221), where the first shared information is first registered information registered by the first information registrant (e.g., information in the registered information database 222) or information generated by processing the first registered information in accordance with the first sharing purpose; (2) storing in the storage a first purpose of use (e.g., information in the purpose of use database 224) of the first registration information relating to the first information user; (3) To share information with the first information users: (3a) obtaining a first information sharing gap by comparing at least the first shared information or the first sharing purpose with the first use purpose (e.g., step S804); (3b) generating first supplemental information based on the first information sharing gap (e.g., step S811); (3c) The first shared information and the first supplementary information are shared with the first information user (for example, step S813).

[0160] This allows information to be generated to be shared, taking into consideration not only the sharing purpose of the information registrant, but also the use purpose of the information user with whom the information is shared.

[0161] [2] The computer according to [1] above, the first shared information is information generated by processing the first registration information in accordance with the first sharing purpose, For the process of (3b), the processor that executed the information sharing program: (3bA) The first supplementary information is generated so as to include information from the first registration information that will eliminate the first information sharing gap by adding it to the first shared information (for example, processes S810 and S811 if process S806: Yes).

[0162] This makes it possible to generate information that eliminates information sharing gaps based on information that has already been registered.

[0163] [3] The computer according to [2] above, For the processing of (3bA), the processor that executed the information sharing program requests the provision of information from the first registration information that will eliminate the first information sharing gap by adding it to the first shared information, and if the request is approved, generates the first supplementary information (for example, processing S810, S811 if processing S806: Yes).

[0164] This means that, for example, when the present invention is applied to providing information during a disaster, it will be possible to make decisions such as approving the provision of additional information on an exceptional basis depending on the level of urgency, even if the use is outside of the original purpose, thereby contributing to rapid disaster response.

[0165] [4] The computer according to [1] above, For the process of (3b), the processor that executed the information sharing program: (3bB) requesting the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information (e.g., process S807); (3bC) The first supplemental information is generated based on the information registered in response to the request in (3bB) (for example, steps S810 and S811 in the case where step S808 returns Yes).

[0166] This makes it possible to generate information that eliminates information sharing gaps based on additional information provided by information registrants.

[0167] [5] The computer according to [1] above, For the process of (3b), the processor that executed the information sharing program: (3bD) requesting a second information registrant different from the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information (e.g., process S809); (3bE) The first supplemental information is generated based on the information registered in response to the request in (3bD) (for example, steps S810 and S811 in the case where step S809 returns Yes).

[0168] This makes it possible to generate information that bridges the information sharing gap based on alternative information provided by other information registrants, even if the original information registrant does not provide the necessary information.

[0169] [6] The computer according to [1] above, For the process of (3b), the processor that executed the information sharing program: (3bA) When the first shared information is information generated by processing the first registration information in accordance with the first sharing purpose, and when the first registration information includes information that will eliminate the first information sharing gap when added to the first shared information, generate the first supplemental information so that the first registration information includes information that will eliminate the first information sharing gap when added to the first shared information (e.g., processes S810 and S811 when process S806: Yes), (3bB) if the first registration information does not include information that will eliminate the first information sharing gap by adding it to the first shared information, request the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information (e.g., process S807); (3bC) Generate the first supplemental information based on the information registered in response to the request in (3bB) (for example, processes S810 and S811 in the case of Yes in process S808), (3bD) If information is not registered in response to the request of (3bB), request a second information registrant different from the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information (e.g., process S809); (3bE) The first supplemental information is generated based on the information registered in response to the request in (3bD) (for example, steps S810 and S811 in the case where step S809 returns Yes).

[0170] This makes it possible to obtain the necessary information to generate information that will eliminate the information sharing gap in each of the following cases: when the information necessary to eliminate the information sharing gap is included in the original registration information; when the information is not included in the original information but can be obtained from the original information registrant; and when the information cannot be obtained from the original information registrant but alternative information can be obtained from another information registrant.

[0171] [7] The computer according to [1] above, The first sharing purpose includes information indicating a sharing purpose of the information (e.g., sharing purpose 312) and information indicating a format of the information corresponding to the sharing purpose (e.g., format 313); The first purpose of use includes information indicating a purpose of use of the information (e.g., purpose of use 602) and information indicating a format of the information corresponding to the purpose of use (e.g., format 603), For the processing of (3a), the processor that executes the information sharing program obtains a first information sharing gap by comparing the format of information corresponding to the sharing purpose included in the first sharing purpose with the format of information corresponding to the use purpose included in the first use purpose.

[0172] This makes it possible to automatically identify whether there are any information sharing gaps.

[0173] [8] The computer according to [1] above, The storage stores access management information (e.g., an access management information table 224) that indicates which information users can access the generated information. For the processing of (3c), the processor that executed the information sharing program refers to the access management information, and if the first information user can access the first shared information and the first supplementary information (e.g., processing S812: Yes), shares the first shared information and the first supplementary information with the first information user.

[0174] This allows you to manage information users' access to the information you share depending on the information you share.

[0175] [9] The computer according to [1] above, the first registration information includes at least one of information indicating the location of resources (e.g., gasoline), information indicating the status of facilities (e.g., underground utilities), and information indicating the occurrence status of disasters (e.g., fires); The first sharing purpose and the first use purpose each include at least one of a purpose related to the creation of a disaster support plan and a purpose related to the implementation of the support plan.

[0176] This makes it possible to contribute to a rapid disaster response when the present invention is applied to providing information during a disaster, for example.

[0177]

[10] The computer according to [1] above, The processing includes at least one of summarizing, thinning, and statistical processing of the first registration information.

[0178] This allows appropriate shared information to be generated depending on the purpose of sharing.

[0179] It should be noted that the present invention is not limited to the above-described embodiment, and includes various modifications. For example, the above-described embodiment has been described in detail to provide a better understanding of the present invention, and the present invention is not necessarily limited to an embodiment having all of the configurations described.

[0180] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in storage devices such as nonvolatile semiconductor memory, hard disk drives, and solid-state drives (SSDs), or in computer-readable, non-transitory data storage media such as IC cards, SD cards, and DVDs.

[0181] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are interconnected. [Explanation of symbols]

[0182] 200 Information Sharing System 210 Main storage 211 Information Reception and Collection Department 212 Shared information generation section 213 Supplementary information generation section 214 Information Sharing Department 220 Auxiliary storage 221 Shared Purpose Database 222 Registration Information Database 223 Shared Information Database 224 Purpose of Use Database 225 Supplementary Information Database 230 Central Control Unit 231 Communication equipment 232 I / O device 240 communication lines 250 Information Registration System 251 Information Use System

Claims

1. A computer having a processor and a storage device storing an information sharing program, The processor that executed the information sharing program: (1) First shared information registered by a first information registrant and a first sharing purpose related to the first shared information are stored in the storage, and the first shared information is first registered information registered by the first information registrant or information generated by processing the first registered information in accordance with the first sharing purpose; (2) storing a first purpose of use of the first registration information related to the first information user in the storage; (3) To share information with the first information users: (3a) obtaining a first information sharing gap by comparing at least the first shared information or the first sharing purpose with the first use purpose; (3b) generating first supplemental information based on the first information sharing gap; (3c) sharing the first shared information and the first supplemental information with the first information user; calculator.

2. 2. The computer of claim 1, the first shared information is information generated by processing the first registration information in accordance with the first sharing purpose, For the process (3b), the processor that executed the information sharing program: (3bA) generating the first supplemental information so as to include information from the first registration information that, when added to the first shared information, eliminates the first information sharing gap; calculator.

3. 3. The computer of claim 2, For the process of (3bA), the processor that executes the information sharing program requests provision of information from the first registration information that will eliminate the first information sharing gap by being added to the first shared information, and if the request is approved, generates the first supplemental information. calculator.

4. 2. The computer of claim 1, For the process (3b), the processor that executed the information sharing program: (3bB) requesting the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information; (3bC) generating the first supplemental information based on information registered in response to the request of (3bB); calculator.

5. 2. The computer of claim 1, For the process (3b), the processor that executed the information sharing program: (3bD) requesting a second information registrant different from the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information; (3bE) generating the first supplemental information based on information registered in response to the request of (3bD); calculator.

6. 2. The computer of claim 1, For the process (3b), the processor that executed the information sharing program: (3bA) When the first shared information is information generated by processing the first registered information in accordance with the first sharing purpose, and when the first registered information includes information that will eliminate the first information sharing gap when added to the first shared information, generate the first supplemental information so that the first registered information includes information that will eliminate the first information sharing gap when added to the first shared information; (3bB) if the first registration information does not include information that will eliminate the first information sharing gap by adding it to the first shared information, requesting the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information; (3bC) generating the first supplemental information based on the information registered in response to the request of (3bB); (3bD) if no information is registered in response to the request of (3bB), request a second information registrant different from the first information registrant to register information that will eliminate the first information sharing gap by adding it to the first shared information; (3bE) generating the first supplemental information based on information registered in response to the request of (3bD); calculator.

7. 2. The computer of claim 1, The first sharing purpose includes information indicating a purpose for sharing information and information indicating a format of the information corresponding to the sharing purpose; the first purpose of use includes information indicating a purpose of use of the information and information indicating a format of the information corresponding to the purpose of use; For the process of (3a), the processor that executes the information sharing program acquires a first information sharing gap by comparing a format of information corresponding to the sharing purpose included in the first sharing purpose with a format of information corresponding to the use purpose included in the first use purpose. calculator.

8. 2. The computer of claim 1, the storage stores access management information indicating information users who can access the generated information; For the process of (3c), the processor that executed the information sharing program refers to the access management information, and if the first information user is able to access the first shared information and the first supplemental information, shares the first shared information and the first supplemental information with the first information user. calculator.

9. 2. The computer of claim 1, the first registration information includes at least one of information indicating the allocation of resources, information indicating the status of facilities, and information indicating the occurrence status of a disaster; The first sharing purpose and the first use purpose each include at least one of a purpose related to the creation of a disaster support plan and a purpose related to the implementation of the support plan, calculator.

10. 2. The computer of claim 1, The processing includes at least one of summarizing, thinning, and statistical processing of the first registration information. calculator.

11. A method executed by a computer having a processor and a storage device storing an information sharing program, comprising: The processor that executed the information sharing program: (1) a procedure for storing, in the storage, first shared information registered by a first information registrant and a first sharing purpose related to the first shared information; (2) storing in the storage a first purpose of use of the first registration information related to the first information user; (3) a step of sharing information with the first information user, In the above (1), the first shared information is the first registered information registered by the first information registrant, or information generated by processing the first registered information in accordance with the first sharing purpose, In the above (3), the processor that executes the information sharing program: (3a) obtaining a first information sharing gap by comparing at least the first shared information or the first sharing purpose with the first use purpose; (3b) generating first supplemental information based on the first information sharing gap; (3c) sharing the first shared information and the first supplemental information with the first information user; method.

12. A program for controlling a computer having a processor and a storage device storing an information sharing program, (1) a procedure for storing, in the storage, first shared information registered by a first information registrant and a first sharing purpose related to the first shared information; (2) storing in the storage a first purpose of use of the first registration information related to the first information user; (3) sharing information with the first information user; In the procedure (1), the first shared information is the first registered information registered by the first information registrant, or information generated by processing the first registered information in accordance with the first sharing purpose, In the step (3), the program: (3a) obtaining a first information sharing gap by comparing at least the first shared information or the first sharing purpose with the first use purpose; (3b) generating first supplemental information based on the first information sharing gap; (3c) causing the processor to execute the procedure of sharing the first shared information and the first supplemental information with the first information user; program.

Images