Information processing system, information processing method, and computer

Abstract

A first computer at a first site, a second computer at a second site, and a terminal connected to the first computer, the first computer holding personal management information including a user ID and a contact destination as personal information of a user of the terminal, generating personal time series information by appending a time to operation information of the terminal and the personal information, generating processed time series information by encrypting the personal information of the personal time series information and transmitting it to the second computer, the second computer receiving the processed time series information, generating search range information for the processed time series information based on search conditions for the processed time series information of the user of the first site and a message transmitted to the user of the first site, and transmitting it to the first computer, and the first computer determining the user by searching the personal time series information with the search conditions of the received search range information.

Description

[0001] This application claims priority to Japanese application filed on November 17, 2020, namely Special Application 2020-190785, the contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to a computer system for giving instructions to an individual without transferring personal information across multiple locations. Background Technology

[0003] In recent years, with the popularization of IoT (Internet of Things), services are emerging that collect operational data from various devices at aggregation points to perform device maintenance. IoT-based maintenance services are sometimes provided globally, and the aggregation point monitoring the devices may differ from the country or region where the device being maintained is located. Furthermore, sometimes it involves multiple companies or organizations collaborating to provide maintenance services, not just the same one.

[0004] On the other hand, in the borderless cyberspace such as the Internet, laws have been enacted in recent years to restrict the cross-border transfer of personal information in various countries and regions (e.g., the European GDPR (General Data Protection Regulation), the California Consumer Privacy Act (California Consumer Privacy Act), and China's Cybersecurity Law and Surveying and Mapping Law).

[0005] These restrictions mostly limit the transfer of personal information. Furthermore, GDPR and similar regulations mandate that entities clearly define and explain the intended use of personal information, and provide requests for updates and deletions. Additionally, in China, location information, such as GPS data, can only be processed by companies licensed in China.

[0006] To implement the aforementioned IoT-enabled maintenance services quickly and efficiently, it is preferable to issue direct instructions from the aggregation point of monitoring equipment and devices to the maintenance manager at the local service point where the maintenance service is to be implemented.

[0007] However, where cross-border transfer of personal information is restricted in the local area where maintenance services are provided, aggregation points cannot obtain personal information such as the contact information and destination of the local maintenance manager, making it difficult to issue direct instructions. Furthermore, when the company operating the aggregation point is different from the company responsible for maintenance, it is difficult to obtain personal information from the local database regarding maintenance operation data, such as who performed the product settings.

[0008] As a technology for notifying individuals in an environment where the flow of personal information is restricted, Patent Document 1 (Japanese Patent Application Laid-Open No. 2009-237975) is known. In Patent Document 1, Organization A maintains personal information and generates an anonymized identification key based on that personal information. Organization A transmits the anonymized identification key to a central authority, and both parties have obtained the anonymized identification key in advance. The disclosure allows Organization A to perform a search for personal information using the anonymized identification key in situations such as emergencies where the central authority needs to search for matching individuals, and then notifies the central authority of the search results. Summary of the Invention

[0009] The problem that the invention aims to solve

[0010] In the aforementioned example, Organization A needs to transmit anonymized key numbers to the central authority in advance based on personal information. If Patent Document 1 is applied to maintenance services provided globally using IoT as described above, anonymized key numbers need to be generated based on the maintenance manager. This requires the storage and management of a large amount of anonymized information on the central authority side, which presents problems in ensuring data capacity and reliable application.

[0011] In particular, when the aggregation site that monitors IoT information is different from the enterprise or organization that operates the local site that performs maintenance operations, it can sometimes be difficult to generate anonymized key numbers for each of the maintenance personnel at the local site and distribute them to the aggregation site.

[0012] Therefore, the present invention was made in view of the above-mentioned problems, and its purpose is to notify individuals at local locations of alarms and instructions from the aggregation point without transferring personal information of the local location where maintenance work is carried out.

[0013] Methods for solving problems

[0014] This invention is an information processing system comprising a first computer operating at a first location, a second computer operating at a second location, and a client terminal connected to the first computer. The first computer maintains personal management information, including a user's identifier and contact destination, as the user's personal information for using the client terminal. It obtains operation information from the client terminal, generates personal time-series information by appending the user's personal information and time to the operation information, performs specified confidentiality measures on the personal information in the personal time-series information to generate processed time-series information, and sends the processed time-series information to the second computer. The second computer generates search scope information based on search criteria for determining the processed time-series information of the user at the first location and a message transmitted to the user at the first location, and sends the search scope information to the first computer. Upon receiving the search scope information from the second computer, the first computer retrieves the personal time-series information containing the personal information using the search criteria in the search scope information to determine the user.

[0015] Invention Effects

[0016] Therefore, in this invention, the first location (local location) does not transfer personal information to the second location (aggregation location) across boundaries. The first computer at the local location can determine the user (individual) who provided the personal information based on the search criteria received from the aggregation location and transmit messages and instructions.

[0017] Details of at least one embodiment of the subject matter disclosed in this specification are set forth in the accompanying drawings and the following description. Other features, forms, and effects of the disclosed subject matter become clear from the following disclosure, drawings, and scope of patent protection claimed. Attached Figure Description

[0018] Figure 1 Embodiment 1 of the present invention is a block diagram illustrating the general outline of a maintenance service system.

[0019] Figure 2 Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of a maintenance service system.

[0020] Figure 3 Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of a web server at a local location.

[0021] Figure 4 Embodiment 1 of the present invention is a block diagram illustrating an example of a data collaboration structure at a local location.

[0022] Figure 5Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of an object-specific server at a local location.

[0023] Figure 6 Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of a database server at a local location.

[0024] Figure 7 Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of a data aggregation server for an aggregation point.

[0025] Figure 8 The first embodiment of the present invention is a block diagram illustrating an example of the structure of an object scope specification server for an aggregation point.

[0026] Figure 9 Embodiment 1 of the present invention is a block diagram illustrating an example of the structure of a database server for aggregation points.

[0027] Figure 10 Embodiment 1 of the present invention is a timing diagram illustrating an example of data collaboration processing performed in a maintenance service system.

[0028] Figure 11 Embodiment 1 of the present invention is a timing diagram illustrating an example of a personalized request processing performed in a maintenance service system.

[0029] Figure 12 Embodiment 1 of the present invention is a flowchart illustrating an example of data collaborative processing performed at a local location.

[0030] Figure 13 Embodiment 1 of the present invention is a flowchart illustrating an example of object-person identification processing performed at a local location.

[0031] Figure 14 Embodiment 1 of the present invention is a flowchart illustrating an example of object scope specification processing performed at an aggregation point.

[0032] Figure 15A The diagram illustrating Embodiment 1 of the present invention is an example of time-series data containing personal information of a local location.

[0033] Figure 15B The diagram illustrating Embodiment 1 of the present invention is an example of time-series data of a device at a local location.

[0034] Figure 15C The diagram illustrating Embodiment 1 of the present invention is an example of time-series data of completed processing at a local location.

[0035] Figure 15DThe diagram shown is an example of the retrieval range data of the aggregation point, illustrating Embodiment 1 of the present invention.

[0036] Figure 15E The first embodiment of the present invention is illustrated in a diagram showing an example of a personal information management table for a local location.

[0037] Figure 16 The diagram shown is an example of a management screen for a local location, illustrating Embodiment 1 of the present invention.

[0038] Figure 17 Embodiment 2 of the present invention is a block diagram illustrating the general outline of a maintenance service system.

[0039] Figure 18 Embodiment 3 of the present invention is a block diagram illustrating the general outline of a notification service system. Detailed Implementation

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

[0041] Example 1

[0042] Figure 1 Embodiment 1 of the present invention is a block diagram illustrating the general outline of a maintenance service system (or information processing system). The maintenance service system includes local locations A (102-A) to C (102-C) that perform maintenance on equipment 111 in different countries and regions, and an aggregation location 103 that collects information from each location and issues alarms, notifications, and other messages related to the maintenance of equipment 111.

[0043] Furthermore, without separately identifying local bases A (102-A) to C (102-C), the symbol "102" with the "-" omitted is used. The same applies to the symbols for other constituent elements. Additionally, an example is shown of prohibiting the cross-border transfer of personal information between each local base 102 and the aggregation base 103.

[0044] The maintenance personnel who perform maintenance on equipment 111 belong to their respective local locations 102. These maintenance personnel use client terminals 101 to register personal information and report maintenance work (work information) at their assigned local locations 102. Furthermore, each local location 102 is an information processing system or computer system operating on one or more computers.

[0045] The personal information of maintenance operators is stored in the personal information management database 611 at local location A (102-A). The structures of local locations B (102-B) and C (102-C) are the same as those of local location A (102-A), therefore, local location A (102-A) will be described below.

[0046] Maintenance operators use the application on client terminal 101 to report maintenance work and other business operations (work information). Local location 102 collects work information from client terminal 101 and registers it in a time-series database (DB in the figure, the same below) 612 containing personal information.

[0047] As described later, the time-series database 612 containing personal information includes personal information such as the maintenance operator's identifier and the identifier of the equipment 111 for which maintenance work was performed. At the local location 102, the data collaboration program 401 generates processed time-series data containing the personal information from the time-series database 612 at predetermined intervals and sends it to the aggregation location 103.

[0048] Furthermore, the data collaboration procedure 401 applies processing algorithms to personal information, including filtering and confidentiality (anonymization), which correspond to the restrictions imposed by laws and regulations on the local base 102. Additionally, the timing for the local base 102 to send processed time-series data is predetermined in the maintenance service system based on a request from the aggregation base 103 and a specified period.

[0049] Aggregation point 103 stores the processed time series data received from each local point 102 into the processed time series database 902. In addition, it stores the operation information of the equipment 111 collected from each local point 102 into the database of other data 904.

[0050] At aggregation point 103, data analysis program 2230 monitors operational information within database 904 of other data, and when it detects anomalies, signs of anomalies, or replacement periods for components, it notifies output device of equipment 111 that requires maintenance.

[0051] The administrators of aggregation site 103 use the object scope designation program 801 to notify the client terminal 101 of the maintenance operator responsible for the equipment 111 that needs maintenance of alarms, maintenance content and other messages. Therefore, the retrieval scope data is generated and the maintenance operator is assigned to each local site 102 and the maintenance content is notified.

[0052] Since the processing completion time series database 902 at local location 102 does not contain personal information (or it is confidential), aggregation location 103 can identify the equipment 111 to be maintained, but the responsible maintenance operator cannot be identified. Therefore, the object scope designation procedure 801 uses the identifier of equipment 111, the date and period of the operation as search criteria to generate search scope data that includes a message to notify the maintenance operator. The object scope designation procedure 801 entrusts local location 102 with the identification of the individual maintenance operator and the notification of the maintenance content.

[0053] Upon receiving the search scope data at the local location 102, the object individual determination procedure 501 retrieves the time-series database 612 containing personal information based on the search scope data to determine the maintenance operator, obtains the contact destination registered in the personal information management database 611, and sends the maintenance content to the client terminal 101.

[0054] As described above, in the maintenance service system of this embodiment, the system generates time-series work information with filtered or confidential personal information from the local location 102 as processed time-series data and sends it to the aggregation location 103, thereby avoiding restrictions on the cross-boundary transfer of personal information.

[0055] Then, at aggregation point 103, search criteria and search scope data for the maintenance content (message) associated with the individual, such as the identifier of the device 111 to be maintained, are generated, and the maintenance operator is assigned to local point 102 for confirmation and notification. Furthermore, the search criteria for determining the maintenance operator at local point 102 are not limited to the identifier of the device 111; they can also be determined by the date and time of the work, the work content, the serial number of the replaced part, etc.

[0056] While aggregation site 103 cannot refer to personal information, it can identify the maintenance operator responsible for maintaining the identifier of device 111 by having local site 102's object identification procedure 501 retrieve a time-series database 612 containing personal information. This eliminates the need for cross-border transfer of personal information and enables rapid maintenance services to be provided at local site 102 and aggregation site 103, which are located in different countries and regions.

[0057] <System Structure>

[0058] Figure 2 This is a block diagram illustrating an example of the structure of a maintenance service system. The example shown depicts an aggregation point 103, local point A (102-A), and local point B (102-B) connected via an inter-point network 206, and each local point 102, client terminal 101, and device 111 connected via network 204. Furthermore, network 204 may consist of the Internet, a wireless (or wired) network, or the like.

[0059] The following description assumes that local base A (102-A) and local base B (102-B) have the same structure, therefore local base A (102-A) will be described. Local base 102 includes a web server 211, a database server 212, a data collaboration server 213, and an object personalization server 214.

[0060] Web server 211 receives maintenance operator's personal information from client terminal 101 and registers it in database server 212. Web server 211 receives job information from client terminal 101 and registers it in database server 212. Web server 211 receives operation information from device 111 and registers it in database server 212. Additionally, device 111 is a machine or device that includes sensors and communication devices (not shown).

[0061] In client terminal 101, application 203 runs, appending the maintenance operator's personal ID and timestamp to the work information entered by the maintenance operator and sending it to local location 102. At the local location 102, the received work information is stored as time-series data containing personal information in database server 212. Alternatively, the appending of the maintenance operator's personal ID and timestamp can also be performed by a web server 211 or similar at local location 102.

[0062] Database server 212 stores maintenance operator's personal information, time-series data containing personal information, and time-series data of device 111. Data collaboration server 213 performs prescribed processing on the time-series data containing personal information to generate processed time-series data and sends it to aggregation point 103.

[0063] In addition, the data collaboration server 213 sends the operation information of the device 111 to the aggregation point 103. Furthermore, the timing of the data collaboration server 213 sending the operation information is based on predetermined conditions such as a fixed period and requests from the aggregation point 103.

[0064] The object-specific determination server 214, based on the search scope data received from the aggregation point 103, searches the time-series database 612 containing personal information to determine the maintenance operator, and notifies the client terminal 101 of the maintenance content contained in the search scope data.

[0065] Furthermore, the above example illustrates the use of a separate server for each function, but the functions of the server described above can also be implemented using a single computer. In this case, any computer comprising the following components is acceptable: a receiving unit that receives personal information, job information, and operational information and registers them in a database; a data management unit that manages the data registered from the receiving unit; a data collaboration unit that processes personal information based on job information (including time-series data containing personal information) to generate processed time-series data; and a target individual determination unit that receives search scope data from aggregation point 103, retrieves time-series data containing personal information to determine the maintenance operator, and notifies the operator of the maintenance requirements.

[0066] Aggregation site 103 includes data aggregation server 221, database server 222, analysis server 223, and object scope specification server 224.

[0067] Data aggregation server 221 receives processed time-series data and time-series data from device 111 and stores them in database server 222. Database server 222 manages the processed time-series data and time-series data from device 111.

[0068] The analysis server 223 analyzes the time-series data of device 111, determines the identifier of device 111 that needs maintenance and the maintenance content, and outputs the results. Alternatively, the maintenance content can be specified by the person in charge of the aggregation point 103 or others.

[0069] The object-specific determination server 214 generates search range data by adding the identifier and maintenance content (or message) of the determined device 111 to search conditions such as the search period, and sends it to the local base 102. In addition, the object-specific determination server 214 can also broadcast the search range data to each local base 102 when the local base 102 to which the device 111 with the identified identifier belongs is unknown.

[0070] Furthermore, while the above description illustrates an example of functional application within a separate server, the functions of the aforementioned server can also be implemented using a single computer. In this case, any computer comprising the following components is acceptable: a receiving unit that receives processed time-series data and time-series data of device 111 and registers it in a database; a data management unit that manages the data registered from the receiving unit; an analysis unit that determines the identifier of device 111 requiring maintenance and the maintenance content based on the time-series data of device 111; and an object scope designation unit that generates search scope data containing search criteria such as the identifier of device 111 and the maintenance content, and sends it to the local base 102.

[0071] <Web Server>

[0072] The structure of each server is described below. Figure 3 This is a block diagram illustrating an example of the structure of a web server 211 at a local location 102. The web server 211 is a computer that includes a processor 304, a memory 305, a storage device 302, an input / output device 306, and a communication interface 303.

[0073] The storage device 302 is composed of a non-volatile storage medium and stores a user information registration and acceptance program 311, a user information collection program 312, and a database access program 313. Each program is loaded into the memory 305 and then executed by the processor 304.

[0074] User information registration and acceptance procedure 311 receives the maintenance operator's personal information from the maintenance operator's client terminal 101 and registers it in the database server 212. User information collection procedure 312 receives the work information input by the maintenance operator from the application 203 on the client terminal 101 and stores it in the database server 212 as a time-series data containing personal information.

[0075] In addition, the user information collection program 312 receives operational information from the device 111 and stores it as time-series data of the device 111 in the database server 212. The database access program 313 receives access from the user information registration acceptance program 311 and the user information collection program 312, and performs access to the database server 212.

[0076] The input / output device 306 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 303 connects to the network 204 (or the inter-site network 206) to perform communication.

[0077] <Data Collaboration Server>

[0078] Figure 4 This is a block diagram illustrating an example of the structure of a data collaboration server 213 at a local base 102. The data collaboration server 213 is a computer including a processor 405, a memory 406, a storage device 403, an input / output device 407, and a communication interface 404.

[0079] Storage device 403 is composed of a non-volatile storage medium that stores data collaboration program 401, database access program 402, and configuration file 420. After data collaboration program 401 and database access program 402 are loaded into memory 406, they are executed by processor 405.

[0080] The data collaboration program 401 includes time series data collection function 411, filtering or confidentiality processing application function 412, personal information content determination function 413, processing time series data transmission permission function 414, and processing time series data transmission function 415.

[0081] Processor 405 executes processing according to the programs of each functional unit, thereby functioning as a functional unit that provides the specified functions. For example, processor 405 implements the time series data collection function 411 by executing processing according to the time series data collection program included in the data cooperation program 401. The same applies to other programs. Moreover, processor 405 also functions as a functional unit that provides the respective functions of the multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0082] The data collaboration program 401 processes various information pre-defined in the configuration file 420.

[0083] The time-series data collection function 411 reads time-series data containing personal information set in the acquisition target table 421 of the configuration file 420. The filtering or confidentiality processing application function 412 uses the application target algorithm 422 of the configuration file 420 to filter or confidentialize the personal information containing the time-series data. The application target algorithm 422 can be appropriately set to comply with the laws and regulations of the country and region where the local base 102 is located. Furthermore, the application target algorithm 422 can be appropriately changed according to amendments to laws and regulations.

[0084] The personal information determination function 413 uses the determination logic 423 of the setting file 420 to determine whether the processed time series data, which has been filtered or confidentialified, contains personal information. The determination logic 423 can be appropriately modified according to changes in the time series data containing personal information.

[0085] When the format or data type of the processed time series data generated by the data collaboration program 401 is a newly appearing data type that has not yet been sent, the processed time series data transmission permission function 414 notifies the data processor designated by the destination 424 of the confirmation responder in the configuration file 420 to inquire whether the processed time series data can be sent. Additionally, the processed time series data transmission permission function 414 will detect data types not registered in the sent data type database 616 (described later) as newly appearing data types.

[0086] The completed time series data transmission function 415 sends the completed time series data, which has been authorized by the data processor, to the aggregation point 103.

[0087] When database access program 402 receives a database access request from data collaboration program 401, it accesses database server 212.

[0088] The input / output device 407 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 404 is connected to the network 204 (or the inter-site network 206) to perform communication.

[0089] <Personalized Server for Target>

[0090] Figure 5 This is a block diagram illustrating an example of the structure of the object-specific determination server 214 at local base 102. The object-specific determination server 214 is a computer including a processor 504, a memory 505, a storage device 502, an input / output device 506, and a communication interface 503.

[0091] Storage device 502 is composed of a non-volatile storage medium and stores object personal determination program 501, database access program 507, and configuration file 520. Object personal determination program 501 and database access program 507 are executed by processor 504 after being loaded into memory 505.

[0092] The object identification procedure 501 includes an object scope specification information receiving function 511, an object scope matching personal information retrieval function 512, an object individual report output function 513, and a person in charge notification function 514.

[0093] The processor 504 executes processing according to the programs of each functional unit, thereby functioning as a functional unit that provides the prescribed functions. For example, the processor 504 executes processing according to the object scope conformity personal information retrieval program included in the object individual determination program 501 to implement the object scope conformity personal information retrieval function 512. The same applies to other programs. Moreover, the processor 504 also functions as a functional unit that provides the respective functions of the multiple processes executed by each program. The computer and computer system are devices and systems that include these functional units.

[0094] The object identification procedure 501 uses various information preset in the configuration file 520 for processing. This information includes details about the database to be searched and the detailed search criteria.

[0095] The object scope specification information receiving function 511 receives the search scope data received from the aggregation point 103 and passes it to the object scope matching personal information retrieval function 512. The object scope matching personal information retrieval function 512 retrieves data matching the search scope data from a time-series database containing personal information specified by the search destination database (and search details) 521 as defined by the configuration file 520.

[0096] When the scope of the object meets the requirements of the personal information retrieval function 512, and the retrieval results contained in the retrieval scope data are obtained from the time series database containing personal information, the personal information is obtained and the contact destination of the maintenance operator is obtained from the personal information management database.

[0097] The Object Personal Report Output Function 513 generates and outputs notifications, alerts, or reports for maintenance operators identified in the personal information management database. The Supervisor Notification Function 514, referring to the notification activation 522 in the configuration file 520, determines whether notifications have been authorized for the maintenance operator. If authorized, it sends the notification generated by the Object Personal Report Output Function 513 to the appropriate client terminal 101. Additionally, the Supervisor Notification Function 514 notifies the local branch office 102, including administrators, of the identified maintenance operators and the maintenance content (or alerts).

[0098] The input / output device 506 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 503 is connected to the network 204 (or the inter-site network 206) to perform communication.

[0099] As described above, the object personal identification server 214 can retrieve time-series data containing personal information that meets the retrieval scope data sent from the aggregation point 103 to identify the maintenance operator, obtain the contact destination of the object's maintenance operator from the personal information management data, and notify the client terminal 101 of the content indicated by the aggregation point 103.

[0100] <Database Server>

[0101] Figure 6 This is a block diagram illustrating an example of the structure of a database server 212 at a local location 102. The database server 212 is a computer that includes a processor 604, a memory 605, a storage device 602, an input / output device 606, and a communication interface 603.

[0102] The storage device 602 is composed of a non-volatile storage medium and stores a database access API execution program 601, a personal information management database 611, a time-series database containing personal information 612, a metadata database 613, a processed time-series database 614, a device time-series database 615, and a transmitted data type database 616.

[0103] The database access API executor 601 is executed by the processor 604 after being loaded into memory 605, and accepts access from other servers.

[0104] Personal Information Management Database 611 stores the personal information of maintenance workers belonging to local site 102. Figure 15E This is a diagram representing an example of a personal information management table 6110 stored in a personal information management database 611.

[0105] The Personal Information Management Table 6110 contains, in one record, the manID 6111 (identifier of the maintenance operator), the name 6112 (name), the phone number 6113 (TEL), and the email address 6114 (E-Mail).

[0106] The time-series database 612 containing personal information is time-series data in which maintenance operators' identifiers and timestamps are appended to the job information collected by the web server 211 from the client terminal 101. Figure 15A This is a diagram representing an example of time-series data 6120 containing personal information stored in a time-series database 612 containing personal information.

[0107] In the time-series data 6120 containing personal information, one data item is composed of the manID 6121, the storage maintenance operator's identifier, the time 6122 and time 6123, the machineID 6124, the storage device 111's identifier, and the operation 6125, the storage job content.

[0108] exist Figure 15A The example shows that the maintenance operator with manID6121="0001" performed operation 6125, which was a replacement operation for part P, at time6122="1592497249" for device 111 with machineID6124="AS0001".

[0109] The metadata database 613 stores information such as the information obtained when the job information was acquired. The processed time series data 6140 obtained by the data collaboration server 213 after processing personal information is stored in the processed time series database 614. Figure 15C This is a diagram representing an example of processed time series data 6140 stored in the processed time series database 614.

[0110] In the processed time series data 6140, one data item is composed of the machineID 6141 and 6143 of the identifier of the storage device 111, the time 6142 of the storage timestamp, and the operation 6144 of the storage job content.

[0111] exist Figure 15C The example illustrates data from a replacement operation of part P performed on device 111 with machineID 6124 = "AS0001" and time 6142 = "1592497249". The illustrated example shows how data collaboration server 213 filters manID 6121 as personal information.

[0112] The device time series database 615 is a time series of data that adds identifiers and timestamps to the operating information collected by the Web server 211 from the device 111. Figure 15B This is a diagram representing an example of device time series data 6150 stored in device time series database 615.

[0113] In the device time series data 6150, one data item is composed of the machineID 6151 of the identifier of the storage device 111, the time 6152 of the storage timestamp, the temperature 6153 of the storage temperature, and the pressure 6154 of the storage pressure.

[0114] The input / output device 606 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 603 connects to the inter-base network 206 to perform communication.

[0115] <Data Aggregation Server>

[0116] Figure 7 This is a block diagram illustrating an example of the structure of a data aggregation server 221 at aggregation point 103. The data aggregation server 221 is a computer including a processor 705, a memory 706, a storage device 703, an input / output device 707, and a communication interface 704.

[0117] The storage device 703 is composed of a non-volatile storage medium and stores a data aggregation program 701 and a database access program 702.

[0118] The data aggregation program 701 and the database access program 702 are executed by the processor 705 after being loaded into the memory 706. The data aggregation program 701 registers the processed time-series data 6140 received from the local location 102 into the processed time-series database 902 of the database server 222. Additionally, the data aggregation program 701 registers the device time-series data 6150 received from the local location 102 into the database 904 of other data on the database server 222.

[0119] Database access program 702 accesses database server 222 based on access requests from data aggregation program 701.

[0120] The input / output device 707 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 704 connects to the network 204 (or the inter-site network 206) to perform communication.

[0121] <Object scope specifies the server>

[0122] Figure 8 This is a block diagram illustrating an example of the structure of the object scope designation server 224 of aggregation point 103. The object scope designation server 224 is a computer including a processor 805, a memory 806, a storage device 803, an input / output device 807, and a communication interface 804.

[0123] The storage device 803 is composed of a non-volatile storage medium, storing an object scope specification program 801 and a database access program 802. The object scope specification program 801 and the database access program 802 are executed by the processor 805 after being loaded into the memory 806.

[0124] The object range specification procedure 801 includes an object range acceptance function 811, a data location confirmation function 812, and a search range data sending function 813.

[0125] The processor 805 executes processes according to the programs of each functional unit, thereby functioning as a functional unit that provides the specified functions. For example, the processor 805 executes processes according to the retrieval range data transmission program included in the object range specification program 801 to implement the retrieval range data transmission function 813. The same applies to other programs. Moreover, the processor 805 also functions as a functional unit that provides the respective functions of the multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0126] The object scope specifying procedure 801's object scope receiving function 811 can receive messages from the input / output device 807, such as the maintenance operator's search criteria and maintenance content for determining the equipment 111 to be maintained. The data location confirmation function 812 receives the search criteria from the object scope receiving function 811 and retrieves the processed time series database 902. Figure 9 The system determines whether there is data that matches the search criteria, and thus determines whether the search criteria are valid.

[0127] If the data sending function 813 of the object scope specification program 801 contains data matching the search criteria in the processed time series database 902, then in addition to the aforementioned accepted search criteria, it also receives maintenance content and messages for the maintenance operator from the input / output device 807. Furthermore, the maintenance content can also be set by the analysis server 223 based on the analysis results of the analysis server 223.

[0128] Then, the search range data sending function 813 sends the data with the message added to the search criteria as search range data to the local base 102. In addition, if the processed time series database 902 does not contain information such as local base A (102-A) and local base B (102-B), the search range data sending function 813 broadcasts the search range data to each local base 102. Figure 15D An example of a search range of data 6130 is shown.

[0129] The retrieval range data 6130 includes machineID 6131, which is an identifier for storage device 111; notification 6132, which is a storage notification method; opMsg 6133, which is a storage maintenance content; and dueDate 6134, which is a storage period.

[0130] In the illustrated example, the maintenance operator responsible for device 111 with machineID6131 = "AS0001" is instructed to perform maintenance work via "e-mail" as the notification method, with the content being "restart" and the deadline being "12:00 on June 21, 2020".

[0131] Database access program 802 accepts access requests from data location confirmation function 812 and accesses the processed time series database 902.

[0132] The input / output device 807 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 804 is connected to the network 204 (or the inter-site network 206) to perform communication.

[0133] <Database Server>

[0134] Figure 9 This is a block diagram illustrating an example of the structure of the database server 222 at aggregation point 103. The database server 222 is a computer including a processor 907, a memory 908, a storage device 905, an input / output device 909, and a communication interface 906.

[0135] The storage device 905 is composed of a non-volatile storage medium and stores a database 904 containing a database access API execution program 901, a processed time series database 902, a metadata database 903, and other data.

[0136] The database access API executor 901 is executed by the processor 907 after being loaded into memory 908, and accepts access from other servers.

[0137] The completed time series database 902 is constructed in the same way as the completed time series database 614 of the database server 212 at the local base 102, and stores... Figure 15C The processing completion time series data shown is 6140.

[0138] Metadatabase 903 stores the data required by aggregation point 103. Other data database 904 stores device time-series data 6150, etc., sent from local point 102.

[0139] The input / output device 909 consists of input devices such as a mouse, keyboard, or touch panel, and output devices such as a display and speakers. The communication interface 906 connects to the inter-base network 206 to perform communication.

[0140] Furthermore, regarding the analysis server 223, although its internal structure is not shown, it is configured similarly to the servers described above. It reads device time-series data 6150 from the database 904 containing other data, analyzes the operational information of device 111, extracts the identifier of device 111 requiring maintenance, and displays it on the output device of the input / output device. The analysis server 223 analyzes the device time-series data 6150 to detect anomalies and signs of anomalies. Moreover, the detection of anomalies or signs of anomalies in device 111 requiring maintenance can be performed using well-known or publicly known techniques, and therefore will not be described in detail.

[0141] <Details of the process>

[0142] Figure 10 This is a sequence diagram illustrating an example of data collaboration processing within a maintenance service system. The processing begins at a predetermined time with the data collaboration procedure 401 at local location 102, generating processed time-series data 6140 from a time-series database 612 containing personal information, which has undergone the prescribed processing of the personal information, and sending it to aggregation location 103.

[0143] In the data collaboration server 213, the data collaboration program 401 requests the database access program 402 to obtain time-series data 6120 containing personal information (S1). Furthermore, the scope of the requested data can be a scope specified by the data processor (or administrator) or a pre-defined scope.

[0144] Database access program 402 requests time-series data 6120 containing personal information within a specified range from database server 212 (S2). Database server 212 retrieves the time-series data 6120 containing the requested personal information from time-series database 612 containing personal information and responds to database access program 402 (S3). Database access program 402 then responds with the access result to data collaboration program 401 (S4).

[0145] The data collaboration program 401 uses a pre-defined application object algorithm 422 to filter or confidentialize the personal information in the time series data 6120 containing personal information, generating processed time series data 6140 (S5). The data collaboration program 401 uses a pre-defined judgment logic 423 to proceed to the next step if the processed time series data 6140 does not contain personal information, and to end the processing if it does contain personal information (S6).

[0146] In step S7, the data collaboration program 401 extracts the data type of the processed time series data 6140 that does not contain personal information, refers to the sent data type database 616, and if it is the first time sending this type, consults the data processor (or manager) via the input / output device 407 to see if it can be sent. The data type is determined, for example, by the items (or fields) contained in the processed time series data 6140 and the data format.

[0147] When the data processor grants permission to send via input / output device 407 (S8), the data collaboration program 401 sends the processed time series data 6140 to the data aggregation server 221 of aggregation point 103 (S9, S10).

[0148] In the data aggregation server 221, the processed time series data 6140 received by the data aggregation program 701 is stored in the processed time series database 902 of the database server 222 (S11).

[0149] Through the above processing, the data collaboration program 401 performs prescribed filtering or confidentiality on the time series data 6120 containing personal information within the specified range to generate processed time series data 6140, and sends it to the data aggregation server 221 of the aggregation point 103.

[0150] In the database server 222 of aggregation site 103, the processed time-series data 6140 sent from each local site 102 is stored in the processed time-series database 902. Additionally, as described above, operation information sent from device 111 is also sent to the data aggregation server 221 of aggregation site 103 at predetermined intervals, and the device time-series data, which serves as the database server 222, is stored in the database 904 of other data.

[0151] Figure 11 This is a sequence diagram illustrating an example of a personal identification request processing performed in a maintenance service system. This processing is executed when the object personal identification server 214 at local location 102 receives retrieval range data 6130 from aggregation location 103.

[0152] The object scope designation server 224 of aggregation point 103 sends the retrieval scope data 6130 to the object personal determination server 214 of local point 102 (S21), and the object personal determination server 214 returns the received response (S22).

[0153] The object-person identification procedure 501 of the object-person identification server 214 requests data (personal information) consistent with the retrieval scope data 6130 from the time series database 612 containing personal information via the database access procedure 507 (S23, S24).

[0154] Database server 212 responds to object personal identification procedure 501 via database access procedure 507 with personal information consistent with the search scope data 6130 (S25, S26). As for the search scope data 6130, for example, the identifier of device 111 (machine ID 6151) and the work content (operation 6144) is the replacement of part P, database server 212 outputs the maintenance operator's identifier, i.e., manID 6121, as personal information consistent with the search criteria.

[0155] The object identification procedure 501 uses the maintenance operator's identifier (manID 6121) obtained from the database server 212 as the search criteria, and consults the personal information management database 611 of the database server 212 via the database access procedure 507 to find the contact destination (e.g., email address) (S27, S28).

[0156] Database server 212 obtains the contact destination (E-Mail 6114) of the specified manID 6121 and responds to object personal identification procedure 501 via database access procedure 507 (S29, S30).

[0157] The object personalization procedure 501 sends the maintenance content (op Msg 6133) and due date (due Date 6134) contained in the search range data 6130 as a message to the obtained contact destination (S31). In addition, the object personalization procedure 501 reports to the data processor at the local location 102 to notify the maintenance operator responsible for the equipment 111.

[0158] Through the above processing, the object-person identification server 214 determines the personal information (man ID 6121) by retrieving the time-series database 612 containing the personal information using an identifier (machine ID 6131) associated with the personal information contained in the search scope data 6130. Then, by obtaining the contact destination corresponding to the personal information from the personal information management database 611, the object-person identification server 214 can notify the maintenance operator responsible for the equipment 111 of the maintenance content contained in the search scope data 6130.

[0159] Figure 12 This is a flowchart illustrating an example of data collaboration processing performed at a local location. The process represents... Figure 10 Details of the processing performed by the data collaboration server 213.

[0160] The data collaboration program 401 of the data collaboration server 213 requests data from the time series database 612 containing personal information of the database server 212, within the range specified above (S41).

[0161] The data collaboration program 401 determines whether data can be obtained from the time-series database 612 containing personal information within a specified time (S42). If data can be obtained, it proceeds to step S43; otherwise, it proceeds to step S51. In step S51, the data collaboration program 401 generates an error log and stores it in the storage device 403, ending the process.

[0162] In step S43, for the time series data 6120 containing personal information within a specified range obtained by the data collaboration program 401, the personal information in the time series data 6120 containing personal information is filtered or made confidential using a pre-set application object algorithm 422, and processed time series data 6140 is generated.

[0163] In step S44, for the time-series data 6120 containing personal information obtained by the data collaboration program 401, it is determined whether there is any data that has not been filtered or confidentialized. If there is unprocessed data, proceed to step S45. If all data has been filtered or confidentialized, proceed to step S46.

[0164] In step S45, after filtering or keeping the next data confidential, the data collaboration program 401 returns to step S44 and repeats the above process. In step S46, the data collaboration program 401 loads the pre-set judgment logic 423.

[0165] In step S47, the data collaboration program 401 determines whether there is any unprocessed data in the processed time series data 6140 that has not been processed for personal information verification. If there is unprocessed data, the process proceeds to step S52; otherwise, the process proceeds to step S48.

[0166] In step S52, the data collaboration program 401 verifies whether the processed time series data 6140 contains personal information. In step S53, the data collaboration program 401 determines whether the processed time series data 6140 contains personal information. If it does not contain personal information, it returns to step S47 and repeats the above process. If it contains personal information, it proceeds to step S56.

[0167] In step S48, since the processed time series data 6140 does not contain personal information, the data collaboration program 401 extracts the data type of the processed time series data 6140 that does not contain personal information, and determines whether it is a data type that has already been sent by referring to the sent data type database 616. If it is a data type that has already been sent, proceed to step S49; if it is a data type that is being sent for the first time, proceed to step S54.

[0168] In step S54, the data collaboration program 401 consults the data processor (or manager) via the input / output device 407 or the communication interface 404 to inquire whether the processed time series data 6140 can be sent. In step S55, it is determined whether permission to send has been input from the input / output device 407 or the communication interface 404. If permission is granted, proceed to step S49; otherwise, proceed to step S56.

[0169] In step S49, the data collaboration program 401 sends the processed time series data 6140, which does not contain personal information, to the aggregation point 103. In step S50, the data collaboration program 401 outputs the sending log and ends the processing.

[0170] In step S56, if the processed time series data 6140 contains personal information or if the transmission is rejected, the data collaboration program 401 outputs a transmission rejection log and ends the processing.

[0171] Figure 13 This is a flowchart illustrating an example of object-specific identification processing performed at a local location. This processing represents... Figure 11 The object shown details the processing performed by server 214.

[0172] The local location 102 object personal determination server 214 receives the retrieval range data 6130 from the aggregation location 103 object range specification server 224 and begins processing (S61).

[0173] The object-person determination procedure 501 of the object-person determination server 214 requests data (personal information) that is consistent with the retrieval scope data 6130 from the time series database 612 containing personal information (S62).

[0174] The subject-specific identification procedure 501 determines whether data can be obtained from the time-series database 612 containing personal information within a specified time (S63). If data can be obtained, the procedure proceeds to step S65; otherwise, it proceeds to step S64. In step S64, the subject-specific identification procedure 501 generates a log indicating an error occurred while obtaining the time-series database 612 containing personal information and stores it in the storage device 502, thus ending the process.

[0175] The object-person determination procedure 501 determines whether the response from the database server 212 contains personal information that matches the search scope data 6130 (S65). If matching personal information is included, the process proceeds to step S67; otherwise, it proceeds to step S66. In step S66, the object-person determination procedure 501 outputs a report indicating that no matching object exists and ends the process.

[0176] Next, the subject identification procedure 501 consults the personal information management database 611 for the contact destination corresponding to the personal information obtained from the database server 212 (S67). The subject identification procedure 501 determines whether the data can be obtained from the personal information management database 611 within a specified time (S68). If the data can be obtained, proceed to step S70; otherwise, proceed to step S69.

[0177] In step S69, the object personal determination procedure 501 generates a log of an error that occurred when obtaining data from the personal information management database 611 and stores it in the storage device 502, then proceeds to step S70.

[0178] In step S70, the object personal determination procedure 501 generates a notification to be sent to the contact destination obtained from the personal information management database 611. Additionally, if obtaining the contact destination fails, a notification indicating that obtaining the matching contact destination has failed is generated.

[0179] The object identification procedure 501 uses the maintenance content (op Msg 6133) and the due date (dueDate 6134) contained in the retrieval range data 6130 as a message to generate a notification to be sent to the obtained contact destination.

[0180] The object identification procedure 501 refers to the information in the notification validity 522 of the setting file 520 to determine whether the notification to the identified maintenance operator is valid (S71). If the notification is valid, the process proceeds to step S71; if the notification is invalid, the process ends.

[0181] The object identification procedure 501 sends the aforementioned generated notification (S72) to the maintenance operator who has identified the contact destination, and reports to the data processor at the local location 102 that the maintenance operator responsible for equipment 111 has been notified.

[0182] Figure 14 This is a flowchart illustrating an example of object scope designation processing performed at aggregation site 103. This processing begins based on input from the person in charge (or manager) operating the input / output device 807 in the object scope designation server 224 at aggregation site 103. Furthermore, the person in charge of the object scope designation server 224 obtains identifiers, etc., of the devices 111 requiring maintenance from the analysis results of the analysis server 223.

[0183] The object scope specification program 801 of the object scope specification server 224 receives the items of the retrieved object from the input / output device 807 (S71). The items of the retrieved object can also be selected from the items of the processed time series data 6140.

[0184] The object scope specification procedure 801 accepts the value of the item or the range of values ​​of the search object as the search criteria (S72). The object scope specification procedure 801 retrieves the processed time series database 902 of the database server 222 using the search criteria accepted in step S72.

[0185] When a response is received from database server 222, object scope specification program 801 determines whether there are any search results (processed time series data 6140) that meet the search criteria (S74). If there are search results, object scope specification program 801 proceeds to step S75; otherwise, it proceeds to step S78.

[0186] In step S78, the object range specification program 801 consults via the input / output device 807 whether to reset the search criteria. If the criteria are reset, the program returns to step S71 and repeats the above process. If not, the process ends.

[0187] In step S75, the object scope designation program 801 receives from the input / output device 807 a message (maintenance content) notifying the maintenance operator determined at the local location 102 based on the above search criteria. The message content may include, for example, the maintenance details and the deadline for the work.

[0188] In step S76, the object scope specification program 801 generates search scope data 6130 based on the received message under the above search conditions, and in step S77, the search scope data 6130 is sent to the local base 102.

[0189] Through the above processing, the object scope designation server 224 can generate retrieval scope data 6130 after verifying the retrieval conditions required to determine the maintenance operator using the processed time series database 902 which does not contain personal information, so that the local base 102 can perform the determination of the individual and the sending of the message.

[0190] <Management Screen>

[0191] Figure 16 This diagram illustrates an example of the management screen 1700 at local location 102. This management screen 1700, displayed on the monitor (output device) of the input / output device 407 constituting the data collaboration server 213, is a screen that inquires with the data processor whether processed time-series data 6140 of a new data type can be sent. The management screen 1700 is enabled by the processed time-series data transmission permission function 414 of the data collaboration program 401. Figure 12 The output of steps S54 and S55) is as follows.

[0192] The management screen 1700 includes: area 1710, which displays the process of generating processed time series data 6140 by performing prescribed processing on raw data 1740 read from time series database 612 containing personal information; area 1720, which displays the content of the processed time series data 6140; and pop-up window 1730, which determines whether the processed time series data 6140 can be sent.

[0193] In the illustrated example, it is shown that personal information in the raw data 1740 is filtered or made confidential by prescribed algorithms 1741 and 1742 to generate processed time-series data 6120 containing personal information, resulting in processed time-series data 6140. This processing corresponds to... Figure 12 Step S45.

[0194] Furthermore, it is shown that after processing the time series data 6140, decisions 1743 and 1744 are made, a process 1745 is implemented to grant permission for consultation transmission. Decision 1743 is, for example, Figure 12 Step S53, determining whether personal information is present, determines 1744. Figure 12 The determination of the data type of the first occurrence in step S48.

[0195] In pop-up window 1730, the data processors of data collaboration server 213 determine whether to send the processed time series data 6140 displayed in area 1720 based on its data type.

[0196] By granting permission to the data processor for the first occurrence of the data type, it can be confirmed that the processed time series data 6140 complies with the restrictions of the local location 102. Then, the permitted data type is registered in the sent-complete data type database of the database server 212, granting permission to send subsequent processed time series data 6140 of the same data type.

[0197] As described above, the maintenance service system of Embodiment 1 collects processed time-series data 6140 (which does not contain personal information) and time-series data of device 111 from multiple local locations 102 at aggregation location 103. First, the device 111 to be maintained is determined based on the time-series data (904) of device 111.

[0198] Next, aggregation point 103 generates search scope data 6130 based on the processing completion time series data 6140 containing the identifier of device 111, which includes search criteria and instructions or messages for identifying the maintenance operator responsible for maintaining device 111, and sends it to local point 102. Furthermore, if the processing completion time series data 6140 does not contain information identifying local point 102, aggregation point 103 broadcasts the search scope data 6130 to local point 102.

[0199] The local base 102, having received the search scope data 6130, searches the time-series database 612 containing personal information using the search criteria of the search scope data 6130, and determines the identifier (manID 6121) of the maintenance operator for the equipment 111. Furthermore, if the search results for the time-series database 612 containing personal information include multiple maintenance operator identifiers, the local base 102 can, for example, set the identifier of the maintenance operator with the most recent data as the responsible person.

[0200] Then, the local location 102 retrieves the contact destination corresponding to the maintenance operator's identifier from the personal information management database 611 and sends the instructions or messages contained in the search range data 6130 to the maintenance operator's client terminal 101.

[0201] In this way, the local location 102 of the maintenance service system can determine the maintenance operator who provided the personal information based on the search criteria (6130) received from the aggregation location 103 without transferring personal information to the aggregation location 103, and transmit messages and instructions to the client terminal 101.

[0202] Furthermore, in the above embodiment 1, an example of using an individual's identifier (manID 6121) as personal information stored in a time-series database 612 containing personal information and time-series data 6120 containing personal information is shown, but it is not limited to this, as long as it is information that can uniquely identify an individual.

[0203] Furthermore, in Embodiment 1 above, an example was shown using a telephone number (TEL 6113) and an email address (E-Mail 6114) as the contact destination stored in the personal information management table 6110 of the personal information management database 611, but this is not a limitation. For example, any information that can send messages to the client terminal 101 used by the maintenance operator, such as an identifier for an SNS (Social Network Service), is acceptable.

[0204] Example 2

[0205] Figure 17 Embodiment 2 of the present invention is a block diagram illustrating the general outline of a maintenance service system. In this embodiment, an example is shown where, instead of the aggregation point 103 of Embodiment 1 described above, a location 103-A of the equipment manufacturing company (hereinafter referred to as the corporate location) provides maintenance instructions to maintenance personnel at local maintenance operation companies' locations (hereinafter referred to as local locations) 102-1 to 102-3 that perform maintenance on the company's products operating in various countries (countries A to C). Furthermore, the structures of local locations 102 and corporate locations 103-A are the same as in Embodiment 1 described above.

[0206] At each local location 102 in each country, similarly to Embodiment 1 above, the operation information (equipment time series data) and processing completion time series data 6140 of the equipment 111 are sent to the enterprise location 103-A. Also similarly to Embodiment 1 above, maintenance personnel at each local location 102 register their personal information in the personal information management database 611.

[0207] In this embodiment, it is permissible for companies operating local locations 102 in different countries to be from different groups. That is, the items and tables in the time-series database 612 containing personal information are not limited to being the same, and it is envisioned that they are different in each local location 102.

[0208] Therefore, projects such as processed time series data 6140 generated from a time series database 612 containing personal information at a local location 102 may vary from local location 102 to local location 102 in different countries, but must contain the identifier of the device 111 being maintained.

[0209] At enterprise site 103-A, the identifier of the equipment 111 to be maintained is determined based on the equipment time series data collected from each local site 102. Based on the identifier of the equipment 111, retrieval range data 6130 for determining the maintenance operator is generated and sent to the local site 102.

[0210] At local locations 102 in various countries, the time-series database 612 containing personal information is searched using the search criteria of the received search scope data 6130 to obtain personal information (manID) consistent with the search criteria, and the contact destination is obtained from the personal information management database 611.

[0211] At local locations 102 in various countries, the items in the time series database 612 containing personal information may differ, but the search criteria for the search scope data 6130 are generated based on the processed time series database 902 of each country.

[0212] Therefore, even if the projects in the time series database 612 containing personal information in the local locations 102 of various countries are different, the enterprise location 103-A can generate search scope data 6130 regardless of the differences in the time series database 61 containing personal information in the local locations 102 of various countries.

[0213] As described above, even if the projects such as the time-series database 612 containing personal information and the processed time-series data 6140 differ between local locations 102, the enterprise location 103-A can still transmit instructions and messages to maintenance operators at local locations 102 in various countries without being limited by the differences in projects between local locations 102.

[0214] Example 3

[0215] Figure 18 This is a block diagram illustrating an outline of a notification service system, representing Embodiment 3 of the present invention. In this embodiment, an example is shown where the content of the maintenance service system of Embodiment 1 described above is applied to the notification service system. In this embodiment, an example is shown where an organization X, such as a government agency, notifies users of organizations A through C that provide various services of alerts, etc.

[0216] In this embodiment, an example is shown where organization A provides SNS (Social Network Service) at service location 102-a, organization B provides transportation services from public transportation agencies at service location 102-b, and organization C provides navigation and other map information at service location 102-c. The structure of service locations 102-a to 102-c is the same as that of local location 102 in Embodiment 1 above.

[0217] Users at each service location 102 register their personal information in the personal information management database 611 of the service location 102 via client terminal 101. Furthermore, the user in this embodiment is equivalent to the maintenance operator in Embodiment 1 described above.

[0218] Service point 102 obtains the operation information when using the service, adds a user identifier to the operation information, generates time-series data 6120 containing personal information, and stores it in a time-series database 612 containing personal information. Additionally, the time-series database 612 contains user attribute information such as age, gender, or place of residence.

[0219] Service point 102 generates processed time-series data 6140 from a time-series database 612 containing personal information and sends it to point X103-a operated by organization X. Furthermore, the processed time-series data 6140 implements prescribed confidentiality measures on the attribute information of the time-series database 612 containing personal information. For example, service point 102 may change age to age group or region to prefecture. Alternatively, attribute information can be sent to aggregation point 103 without confidentiality.

[0220] Location X103-a will store the completed time series data 6140 received from each service location 102 into the completed time series database 902.

[0221] When issuing alerts or other notifications, base station X103-a generates search scope data 6130 by setting search criteria and messages (alerts or notifications) based on the attribute information of the processed time series database 902. For example, the search criteria might be set to the region of County X and the age group of 20-40 years old; the message might be set to infectious disease countermeasures. At base station X (103-a), search scope data 6130 is generated to determine the users to whom the notifications are sent and then sent to each service base station 102.

[0222] At each service point 102, the time-series database 612 containing personal information is searched using the search criteria from the received search scope data 6130. Personal information (manID) matching the search criteria (attribute information) is obtained, and the contact destination is retrieved from the personal information management database 611. The service point 102 can then send a message to the client terminal 101 at the retrieved contact destination.

[0223] Thus, in this embodiment, the attribute information of users who transmit alarm messages to organizations such as government agencies X is included in the retrieval scope data 6130 and sent to the service point 102 that has a time series database 612 containing personal information.

[0224] At service point 102, personal information can be retrieved from personal information management database 611 by searching time series database 612 containing personal information using search criteria that include attribute information. The retrieved personal information can be used to search personal information management table 6110 to obtain the contact destination and send the message to client terminal 101.

[0225] As described above, in this embodiment, service point 102 can identify individuals and transmit alerts, instructions, and other messages based on search criteria received from point X (103-a) without transferring personal information to point X (103-a) side.

[0226] <Summary>

[0227] As described above, the information processing systems (maintenance service systems, notification service systems) of the above embodiments 1 to 3 can be configured as follows.

[0228] (1) An information processing system comprising: a first computer (data collaboration server 213, object personal determination server 214) operating at a first location (local location 102), a second computer (data aggregation server 221, analysis server 223, object scope designation server 224) operating at a second location (aggregation location 103), and a client terminal (101) connected to the first computer, wherein the first computer (213, 214) maintains personal management information (personal information management table 6110) including the user's identifier (manID 6111) and contact destination (E-Mail 6114) as personal information of the user (maintenance operator) using the client terminal (101), obtains the operation information of the client terminal (101), generates personal time series information (time series data 6120 including personal information) with the user's personal information (6111) and time attached to the operation information, and processes the personal time series information... The personal information (6121) in the column information (6120) is confidentialized in accordance with regulations to generate processed time series information (processed time series data 6140). The processed time series information (6140) is sent to the second computer. The second computer (221, 223, 224) receives the processed time series information (6140) from the first computer. Based on the search conditions for the processed time series information (6140) used to determine the user of the first location and the message transmitted to the user of the first location, the second computer generates search scope information (search scope data 6130). The search scope information (6130) is sent to the first computer. When the first computer receives the search scope information (6130) from the second computer, it searches for personal time series information (6120) containing the personal information (6121) using the search conditions of the search scope information (6130) to determine the user.

[0229] According to the above structure, local location 102 can determine the maintenance operator who provided personal information based on the search criteria (6130) received from aggregation location 103 without transferring personal information to aggregation location 103.

[0230] (2) The information processing system according to (1) above is characterized in that the first computer obtains the personal information (6121) of the determined user from the personal time series information (6120), obtains the contact destination of the user that matches the personal information (6121) from the personal management information (6110), and sends the message contained in the search scope information (6130) to the contact destination.

[0231] According to the above structure, local base 102 obtains the contact destination by retrieving the personal information management table 6110 using the determined personal information, thereby enabling it to send messages to the client terminal 101 of the maintenance operator (user).

[0232] (3) In the information processing system described in (1) above, the first computer collects the operation information of the equipment (111) operating at the first location and the identifier (machineID 6151) of the equipment (111) as equipment time-series information, and sends it to the second computer. This includes the identifier (6121) of the user who performed maintenance on the equipment (111) and the identifier of the equipment (111) being maintained as the operation information of the client terminal (101). The user's identifier is kept confidential as personal information (6121) to generate processed time-series information (6140). The second computer analyzes the equipment time-series information (6140) received from the first computer. 150) Identifier (6151) of the device (111) to be maintained is determined, search conditions are generated for retrieving the identifier (6151) of the determined device (111) from the processed time series information (6140) that does not contain the personal information (6121), maintenance content of the device (111) to be maintained is generated as a message (6133), and the search scope information (6130) is generated according to the search conditions and the message. The first computer retrieves personal time series information (6120) containing the personal information (6121) based on the search conditions of the search scope information (6130) received from the second computer to determine the device (111) of the user and the device to be maintained.

[0233] Based on the above structure, aggregation point 103 generates retrieval scope data 6130, which includes retrieval criteria and instructions or messages for identifying the maintenance operator responsible for maintaining device 111, from the processed time-series data 6140 containing the identifier of device 111, and sends it to local point 102. Upon receiving the retrieval scope data 6130, local point 102 can determine the identifier (manID 6121) of the maintenance operator for device 111 in the time-series database 612 containing personal information, using the retrieval criteria of the retrieval scope data 6130.

[0234] (4) The information processing system according to (3) above is characterized in that the first computer uses the search scope information (6130) containing the identifier (machineID6151) of the device (111) to search for personal time series information (6120) containing personal information (6121) to obtain personal information (6121), uses the personal information (6121) of the search result to obtain the contact destination from the personal information management information (6110), and sends the message contained in the search scope information (6110) to the contact destination (6114).

[0235] According to the above structure, the local base 102 obtains the contact destination corresponding to the maintenance operator's identifier from the personal information management database 611, and sends the instructions or messages contained in the search range data 6130 to the maintenance operator's client terminal 101.

[0236] (5) The information processing system according to (2) above is characterized in that the first computer generates the personal time series information (6120) by including the user's identifier (6121) and the user's attribute information, and generates the processed time series information by keeping the user's identifier as personal information (6121) confidential. The second computer generates retrieval scope information (6130) by specifying the object to which the message is sent through the attribute information. The first computer retrieves the personal time series information (6120) with the retrieval conditions of the retrieval scope information (6130) containing the attribute information to obtain personal information (6121) and determine the user who sent the message.

[0237] Based on the above structure, the attributes of users who transmit alarms and other messages to government agencies or other organizations X are used as search scope data 6130 and sent to service point 102 which has a time series database 612 containing personal information. As a result, service point 102 can obtain the contact destination from personal information management database 611 and send messages to the client terminal 101 of users with specific attribute information.

[0238] (6) The information processing system according to (1) above is characterized in that the first base (102) and the second base (103) belong to different countries or organizations, and the first computer consults whether it can be sent when the processed time sequence information (6140) being sent is a data type that appears for the first time.

[0239] Based on the above structure, when the processed time series data 6140 is a data type that appears for the first time, it can be confirmed that the processed time series data 6140 complies with the restrictions of the local base 102 by accepting the permission of the data processor.

[0240] Furthermore, the present invention is not limited to the embodiments described above, and includes various modifications. For example, the embodiments described above are detailed for the purpose of easily understanding and illustrating the present invention, and are not limited to having all the structures described. In addition, a part of the structure of one embodiment can be replaced with the structure of another embodiment, and it is also possible to add the structure of another embodiment to the structure of one embodiment. Furthermore, for a part of the structure of each embodiment, the addition, deletion, or replacement of other structures can be applied individually or in combination.

[0241] Furthermore, some or all of the aforementioned structures, functions, processing units, and processing units can be implemented in hardware, for example, through integrated circuit design. Alternatively, the aforementioned structures and functions can be implemented in software by a processor interpreting and executing programs that implement each function. The programs, tables, files, and other information implementing each function can be stored in recording devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.

[0242] Furthermore, the control lines and information lines shown are those deemed necessary for the description, and do not necessarily represent all control lines and information lines on the product. In fact, it can be assumed that almost all the structures are interconnected.

[0243] <Supplement>

[0244] The following are representative examples of viewpoints of the present invention that are not covered by the scope of the patent claim.

[0245] <16>

[0246] A storage medium storing a program for controlling a computer having a processor and memory, operating at a first location, the storage medium storing a program for causing the computer to perform the following steps: a personal management information retention step, retaining personal management information including a user's identifier and contact destination as personal information of a user using the client terminal; a personal time-series information generation step, obtaining operation information of the client terminal, generating personal time-series information with the user's personal information and time appended to the operation information; a completed time-series information transmission step, generating completed time-series information by pre-defined confidentiality of the personal information in the personal time-series information, and transmitting the completed time-series information to a second computer; a retrieval scope information receiving step, receiving retrieval scope information from the second computer; and a user determination step, in which the first computer retrieves the personal time-series information containing the personal information according to the retrieval criteria of the retrieval scope information to determine the user.

Claims

1. An information processing system having a first computer operated at a first site, a second computer operated at a second site, and a client terminal connected to the first computer, characterized by the first computer holding personal management information including an identifier of a user and a contact destination as personal information of a user who uses the client terminal, acquiring operation information of the client terminal, generating personal time series information to which personal information of the user and a time are added to the operation information, generating processed time series information by performing prescribed security processing on the personal information of the personal time series information, and transmitting the processed time series information to the second computer, the second computer receiving the processed time series information from the first computer, generating search range information from a search condition for determining the processed time series information of the user of the first site and a message to be delivered to the user of the first site, and transmitting the search range information to the first computer, the first computer determining the user by searching the personal time series information including the personal information with the search condition of the search range information received from the second computer, the first computer collecting operation information of equipment operated at the first site and an identifier of the equipment as equipment time series information, and transmitting to the second computer, the personal time series information including an identifier of a user who performed maintenance of the equipment and the identifier of the equipment as a maintenance target as the operation information of the client terminal, and the processed time series information generated by performing security processing on the identifier of the user as the personal information, the second computer determining the identifier of the equipment as a maintenance target by analyzing the equipment time series information received from the first computer, generating a search condition for searching the determined identifier of the equipment from the processed time series information not including the personal information, generating a maintenance content of the equipment as a maintenance target as the message to be delivered to the user of the first site, and generating the search range information from the search condition and the message, and the first computer determining the user and the equipment as a maintenance target by searching the personal time series information including the personal information with the search condition of the search range information received from the second computer.

2. The information processing system according to claim 1, characterized by the first computer acquiring the personal information of the determined user from the personal time series information, acquiring the contact destination of the user who matches the personal information from the personal management information, and transmitting the message included in the search range information to the contact destination.

3. The information processing system according to claim 1, characterized by ​ ​ ​ ​ ​ ​ ​ The first computer retrieves personal time series information including personal information using search range information including an identifier of the device to acquire personal information, acquires a contact destination from personal information management information using personal information of the search result, and transmits a message included in the search range information to the contact destination.

4. The information processing system according to claim 2, wherein The first computer generates the personal time series information including attribute information of the user in addition to the identifier of the user, and generates processed time series information by encrypting the identifier of the user as personal information, The second computer generates the search range information by specifying an object to which the message is transmitted using the attribute information, The first computer acquires personal information by searching the personal time series information using a search condition including the search range information including the attribute information, and determines the user who transmits the message.

5. The information processing system according to claim 1, wherein The first site and the second site belong to different countries or organizations, The first computer consults the possibility of transmission when the processed time series information transmitted is a type that is newly generated, 6. An information processing method of transmitting a message with a first computer operated at a first site, a second computer operated at a second site, and a client terminal connected to the first computer, characterized by The information processing method includes the steps of: A personal management information holding step in which the first computer holds personal management information including an identifier of a user and a contact destination as personal information of the user who uses the client terminal; A personal time series information generating step in which the first computer acquires operation information of the client terminal, and generates personal time series information in which the operation information is attached to personal information of the user and a time; A processed time series information transmitting step in which the first computer generates processed time series information by encrypting the personal information of the personal time series information according to a predetermined encryption method, and transmits the processed time series information to the second computer; A processed time series information receiving step in which the second computer receives the processed time series information from the first computer; A search range information transmitting step in which the second computer generates search range information including a search condition for determining the processed time series information of the user of the first site and a message to be transmitted to the user of the first site, and transmits the search range information to the first computer; A search range information receiving step in which the first computer receives the search range information from the second computer; And A user determining step in which the first computer determines the user by searching personal time series information including the personal information using a search condition of the search range information, The information processing method further includes the steps of: A device time series information transmitting step in which the first computer collects operation information of a device operated at the first site and an identifier of the device as device time series information, and transmits the device time series information to the second computer; and And an equipment time series information analysis step in which the second computer analyzes the equipment time series information received from the first computer, determines an identifier of a maintenance target equipment, in the personal time series information generation step, personal time series information is generated including an identifier of a user who performed the maintenance of the equipment and an identifier of the maintenance target equipment as the operation information of the client terminal, in the search range information transmission step, search conditions for searching for the determined identifier of the equipment from the processed time series information not including the personal information are generated, a maintenance content of the maintenance target equipment is generated as a message to be delivered to the user of the first site, and the search range information is generated based on the search conditions and the message, in the user determination step, the personal time series information including the personal information is searched with the search conditions of the search range information received from the second computer, and the user and the maintenance target equipment are determined.

7. The information processing method according to claim 6, characterized by, The information processing method further includes the steps of: a personal information acquisition step in which the first computer acquires personal information of the determined user from the personal time series information; a contact destination acquisition step in which the first computer acquires the contact destination of the user who matches the personal information from the personal management information; and a message transmission step in which the first computer transmits the message included in the search range information to the contact destination.

8. The information processing method according to claim 6, wherein in the user determination step, the personal information is acquired by searching the personal time series information including the personal information with the search range information including the identifier of the equipment, the contact destination is acquired from the personal information management information using the personal information of the search result, and the message included in the search range information is transmitted to the contact destination.

9. The information processing method according to claim 7, wherein in the personal time series information generation step, the personal time series information is generated including attribute information of the user in addition to the identifier of the user, in the processed time series information transmission step, the processed time series information is generated with the identifier of the user being encrypted as personal information, in the search range information transmission step, the search range information is generated by specifying an object to which the message is transmitted using the attribute information, in the user determination step, the personal information is acquired by searching the personal time series information with the search conditions of the search range information including the attribute information, and the user to which the message is transmitted is determined.

10. The information processing method according to claim 6, wherein the first site and the second site belong to different countries or organizations, the information processing method further includes a step in which the first computer consults about the possibility of transmission in a case where the transmitted processed time series information is of a type that is initially present. ​ 11. A computer having a processor and a memory and operating at a first site, characterized by the processor holding personal management information including an identifier of a user and a contact destination as personal information of a user using a client terminal, acquiring operation information of the client terminal, generating personal time series information to which personal information of the user and a time are added to the operation information, generating processed time series information by performing prescribed security on the personal information of the personal time series information, transmitting the processed time series information to a second computer, when receiving search range information from the second computer, searching for personal time series information including the personal information with search conditions of the search range information to determine the user, the processor collecting operation information of an apparatus operating at the first site and an identifier of the apparatus as apparatus time series information and transmitting to the second computer, the processor including an identifier of a user who performed maintenance of the apparatus and an identifier of the apparatus as a maintenance object as the operation information of the client terminal, generating processed time series information by performing security on the identifier of the user as personal information, the processor searching for personal time series information including the personal information with search conditions of the search range information received from the second computer to determine the user and the apparatus as a maintenance object.

12. The computer according to claim 11, characterized by the processor acquiring personal information of the determined user from the personal time series information, acquiring the contact destination of the user who matches the personal information from the personal management information, and transmitting a message included in the search range information to the contact destination.

Images