JP5616920B2 - Management device, management method, and management program - Google Patents

Description

  The present invention relates to a management device and the like.

  In the event of a disaster such as an earthquake, tsunami, or fire, it is important to confirm the safety of family members, friends, and company colleagues. In the following explanation, family members, friends, company colleagues, etc. are collectively referred to as acquaintances.

  Here, most users use a mobile phone or a landline phone to call an acquaintance directly and confirm safety. However, since many users use the telephone all at once, there are many situations where the telephone line is congested and the telephone with the acquaintance is not connected. In addition, when a disaster occurs, call restriction may be performed, and it is difficult to quickly contact an acquaintance using a telephone.

  In view of the above problems, there are various conventional techniques for confirming the safety and location of a user without using a telephone. For example, in the prior art 1, when a user passes through a ticket gate of a station using an IC (Integrated Circuit) card, information that associates the position information of the ticket gate with the information of the user is generated, A technique for enabling browsing is disclosed.

  Further, in the prior art 2, the personal identification information recorded on the user's IC card is read by a card reader, and the information in which the personal identification information and the position information of the card reader are associated with each other is approved for disclosure of the information. After that, a technique for transmitting to a public server is disclosed.

JP 2006-2111288 A JP 2008-102656 A JP 2003-281655 A JP 2006-140620 A JP 2002-245150 A

  However, the above-described conventional technology has a problem that safety cannot be confirmed quickly and reliably.

  For example, when collecting user information using a plurality of servers, it is impossible to determine in advance which server stores the user information. For this reason, in the prior art, since user information is sequentially inquired, it takes time to acquire user information.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a management device, a management method, and a management program capable of confirming safety quickly and reliably.

  The disclosed management device includes a registration unit, a priority setting unit, a history information request unit, and a notification unit. The registration unit acquires user history information including user identification information that uniquely identifies a user from a plurality of servers, and registers the acquired history information in a history information management table. The priority setting unit sets the priority of each server for each user identification information based on the history information registered in the history information management table. When receiving public request information including user identification information from a client, the history information request unit sends a request to each server based on the priority of each server corresponding to the user identification information included in the public request information. Request history information. The notification unit notifies the client of history information obtained from the server.

  According to the disclosed management device, there is an effect that safety can be confirmed promptly and reliably.

FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. FIG. 2 is a diagram (1) illustrating an example of a data structure of history information generated by a child server. FIG. 3 is a diagram (2) illustrating an example of a data structure of history information generated by the child server. FIG. 4 is a diagram (3) illustrating an example of a data structure of history information generated by the child server. FIG. 5 is a diagram (4) illustrating an example of a data structure of history information generated by the child server. FIG. 6 is a diagram illustrating an example of the data structure of the response presence / absence information. FIG. 7 is a functional block diagram showing the configuration of the management apparatus. FIG. 8 is a diagram illustrating an example of a data structure of the member information management table. FIG. 9 is a diagram illustrating an example of a data structure of the history information management table. FIG. 10 is a diagram illustrating an example of a data structure of the first priority management table. FIG. 11 is a diagram illustrating an example of a data structure of the second priority management table. FIG. 12 is a diagram illustrating an example of the data structure of the child server location information. FIG. 13 is a diagram showing an example of public safety information. FIG. 14 is a flowchart illustrating a processing procedure in which the management apparatus receives history information. FIG. 15 is a flowchart illustrating a processing procedure when the management apparatus receives disclosure request information from a client terminal. FIG. 16 is a flowchart illustrating a processing procedure in which the management apparatus requests history information based on the second priority management table. FIG. 17 is a flowchart illustrating a processing procedure when the management apparatus receives response presence / absence information.

  Hereinafter, embodiments of a management device, a management method, and a management program disclosed in the present application will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  An example of a system configuration according to the present embodiment will be described. FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. As shown in FIG. 1, the system includes parent servers 10, 20, 30, 40, and child servers 10a, 10b, 10c, 20a, 20b, 20c, 30a, 30b, 30c, 40a, 40b, and 40c. The system also includes a management device 100.

  The management device 100 is connected to the parent servers 10 to 40 via the network 80. The parent server 10 is connected to the child servers 10a to 10c. The parent server 20 is connected to the child servers 20a to 20c. The parent server 30 is connected to the child servers 30a to 30c. The parent server 40 is connected to the child servers 40a to 40c.

  Here, the parent servers 10 to 40 are shown as an example, but other parent servers may be connected to the network 80. The parent servers 10 to 40 may be connected to child servers other than those shown in FIG. The parent servers 10 to 40 correspond to servers.

  The parent server 10 is a “company internal server”, and manages the working status of employees of the company. When the parent server 10 acquires the history information from the child servers 10a to 10c, the parent server 10 transmits the acquired history information to the management apparatus 100.

  The child servers 10a, 10b, and 10c are child servers arranged in offices at different positions, and generate history information regarding the work status of employees. For example, when an employee goes to work or leaves the office, the IC card for the employee is held over the reader / writer, and the child servers 10a to 10c read information from the reader / writer and generate employee history information. The child servers 10a to 10c transmit the generated history information to the parent server 10.

  FIG. 2 is a diagram (1) illustrating an example of a data structure of history information generated by a child server. As shown in FIG. 2, the history information includes an employee number, an attendance date, an attendance time, a place, and a planned business trip place.

  In FIG. 2, the employee number is information for identifying the employee. The attendance date and attendance time indicate the attendance date and attendance time of the employee. The location indicates the location of the child server and corresponds to the employee's attendance location. The planned business trip location indicates the planned business trip location of the employee. In addition to this, the history information may include a work day, a work time, and the like.

  In the example shown in FIG. 2, the date and time when the employee with the employee number “W1001” went to work is “28:28 on February 28, 2012”, and the employee's place of work is “Musashi Kosugi”. . In addition, the employee with the employee number “W1001” is planning to make a business trip to “Yokohama”.

  The parent server 20 is a “bank server” and manages the usage status of ATMs (Automated Teller Machines) by customers. When the parent server 20 acquires history information from the child servers 20a to 20c, the parent server 20 transmits the acquired history information to the management apparatus 100.

  The child servers 20a, 20b, and 20c are child servers arranged in bank branches at different positions, and generate history information related to customer ATM usage information. For example, the child servers 20a to 20c perform data communication with the ATM and generate history information. The child servers 20a to 20c transmit the generated history information to the parent server 20.

  FIG. 3 is a diagram (2) illustrating an example of a data structure of history information generated by the child server. As shown in FIG. 3, the history information includes a bank account number, a use date, a use time, and a store name.

  In FIG. 3, the bank account number is the customer's bank account number. The use date and the use time indicate the use date and the use time when the customer uses the ATM. The store name indicates the store name having the ATM used by the customer.

  The parent server 30 is a “railway company server” and manages information related to getting on and off of the customer. When the parent server 30 acquires history information from the child servers 30a to 30c, the parent server 30 transmits the acquired history information to the management apparatus 100.

  The child servers 30a, 30b, and 30c are child servers installed in automatic ticket gates at different stations, and generate history information related to customers getting on or getting off. For example, when the customer passes the automatic ticket gate, the IC card is held over the reader / writer, and the child servers 30a to 30c read the IC card information from the reader / writer and generate customer history information. The child servers 30a to 30c transmit the generated history information to the parent server 30.

  FIG. 4 is a diagram (3) illustrating an example of a data structure of history information generated by the child server. As shown in FIG. 4, this history information includes an IC card identification number 1, an entry date, an entry time, an exit time, and a station name.

  In FIG. 4, an IC card identification number 1 is an identification number of an IC card that a customer uses when getting on or getting off. The admission date indicates the date when the customer enters the station through the automatic ticket gate. The admission time indicates the time when the customer enters the station through the automatic ticket gate. The leaving time indicates the time when the customer leaves the station through the automatic ticket gate. A station name shows the name of the station of the automatic ticket gate which the customer passed.

  The parent server 40 is a “beverage company server”, and manages the purchase date and place and the purchase location of the customer's beverage. When the parent server 40 acquires the history information from the child servers 40a to 40c, the parent server 40 transmits the acquired history information to the management apparatus 100.

  The child servers 40a, 40b, and 40c are child servers installed in vending machines at different positions, and generate history information regarding the purchase date and place of the customer's beverage. For example, it is assumed that a vending machine is provided with a reader / writer, and a customer purchases a product from the vending machine using an IC card. IC card information is read from the child servers 40a to 40c, and customer history information is generated. The child servers 40a to 40c transmit the generated history information to the parent server 50.

  FIG. 5 is a diagram (4) illustrating an example of a data structure of history information generated by the child server. As shown in FIG. 5, the history information includes an IC card identification number 2, a purchase date, a purchase time, and a purchase place.

  In FIG. 5, an IC card identification number 2 is an identification number of an IC card used when a customer purchases a product with a vending machine. The purchase date and time indicate the date and time when the customer purchased the product. A purchase place shows the place where the customer purchased goods with the vending machine.

  By the way, each parent server 10-40 performs data communication with a child server regularly, and determines whether there is a response from each child server. Then, the parent servers 10 to 40 transmit response presence / absence information as a determination result to the management server 100. FIG. 6 is a diagram illustrating an example of the data structure of the response presence / absence information.

  As shown in FIG. 6, the response presence / absence information associates the child server identification information with the response presence / absence. The child server identification information is information that uniquely identifies the child server. The presence / absence of response is information indicating whether or not there is a response from the child server. The response presence / absence information shown in FIG. 6 is response presence / absence information generated by the parent server 10. In the example shown in FIG. 6, the response from the child servers 10a and 10b is “present”, and the response from the child server 10c is “none”.

  Furthermore, each parent server 10-40 receives the history request information from the management apparatus 100 described later. The parent servers 10 to 40 request history information corresponding to the history request information from the child server. When history information corresponding to the history request information is received from the child server from the child server, the received history information is transmitted to the management apparatus 100. Specific explanation regarding the history request information will be described later.

  The management device 100 is a device that receives history information from each parent server 10 to 40 and manages the received history information in association with a member identification number. The member identification number is a number that uniquely identifies the employee and customer. In the following explanation, employees and customers are collectively referred to as members.

  When the management apparatus 100 receives from the client terminal (not shown) public request information that requests member information disclosure, the management apparatus 100 generates public safety information that collects history information corresponding to the member. The management apparatus 100 transmits the generated public safety information to the client terminal.

  Here, an example of the configuration of the management apparatus 100 will be described. FIG. 7 is a functional block diagram showing the configuration of the management apparatus. As illustrated in FIG. 7, the management apparatus 100 includes a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

  The communication unit 110 is a processing unit that performs data communication with the parent servers 10 to 40 and the client terminal. For example, the communication unit 110 corresponds to a communication device such as a communication card. The control unit 150 described later performs data communication with the parent servers 10 to 40 and the client terminal via the communication unit 110.

  The input unit 120 is an input device that inputs various types of information. For example, the input unit 120 corresponds to an input device such as a keyboard, a mouse, and a touch panel. The display unit 130 displays information output from the control unit 150. For example, the display unit 120 corresponds to a display, a touch panel, or the like.

  The storage unit 140 stores a member information management table 141, a history information management table 142, a first priority management table 143, a second priority management table 144, and child server location information 145. The storage unit 140 corresponds to a semiconductor memory device such as a random access memory (RAM), a read only memory (ROM), or a flash memory, or a storage device such as a hard disk or an optical disk.

  The member information management table 141 is a table that associates a member identification number with a plurality of types of user identification information. FIG. 8 is a diagram illustrating an example of a data structure of the member information management table. As shown in FIG. 8, the member information management table 141 has a member identification number, name, address, IC card number 1, IC card number 2, employee number, bank account number, and point card identification number.

  The member identification number is information for uniquely identifying a member. The name is the name of the member. The address is the member's address. The IC card identification number 1 corresponds to the IC card identification information 1 of the history information shown in FIG. The IC card identification number 1 is information recorded on the IC card used when the member passes the automatic ticket gate.

  The IC card identification information 2 corresponds to the IC card identification information 2 of the history information shown in FIG. The IC card identification number 2 is information recorded on the IC card used when a member purchases a product with a vending machine.

  The employee number corresponds to the employee number in the history information shown in FIG. The employee number is information recorded on an IC card for an employee used at the work place of the member.

  The bank account number corresponds to the bank account number of the history information shown in FIG. The bank account number is the number of the bank account opened by the member.

  The point card identification number is information included in history information received from a server other than the parent servers 10 to 40, and is included in, for example, a point card used by a member at a rental shop or the like.

  The history information management table 142 is a table that stores each history information acquired from each parent server 10 to 40 for each member identification number. FIG. 9 is a diagram illustrating an example of a data structure of the history information management table. As shown in FIG. 9, in the history information management table 142, each history information corresponding to the member identification number is registered. The member identification number and the history information are linked based on the member information management table 141 shown in FIG. For example, each history information shown in FIGS. 2 to 5 is associated with the member identification number “K101” when compared with the member information management table 141 shown in FIG. Therefore, each history information shown in FIGS. 2 to 5 is registered in the history information management table 142 in association with the member identification information “K101”.

  The first priority management table 143 is a table for managing the priority of each parent server for different time zones. FIG. 10 is a diagram illustrating an example of a data structure of the first priority management table. As shown in FIG. 10, the first priority management table 143 associates a member identification number, name, time zone, priority 1 server identification information, priority 2 server identification information, and priority 3 server identification information. Here, the parent server identified by the priority 1 server identification information has the highest priority, and the priority decreases in the order of the parent server of the priority 2 server identification information and the parent server of the priority 3 server identification information.

  For example, in the time zone “8:00 to 9:00” of the member identification number “K101” and the name “Fujitaro”, the parent server 10 has the highest priority, and the parent server 20 and the parent server 30 in this order. Becomes lower. The priority of each parent server in the first priority management table 143 is set based on the daily life of the member. For example, in the example of FIG. 10, “Taro Fuji” with the member identification number “K101” has a high use frequency of the child servers 10a to 10c in the time zone “8:00 to 9:00”. This means that the usage frequency of the servers 20a to 20c and the child servers 30a to 30c is high.

  The 2nd priority management table 144 is a table which manages the priority with respect to each parent server of a member. FIG. 11 is a diagram illustrating an example of a data structure of the second priority management table. As shown in FIG. 11, the second priority management table 144 associates member identification numbers, names, server identification numbers, and priorities. Here, priority 1 is the highest priority and priority 5 is the lowest priority. For this reason, when the member identification number “K101” and the name “Fujitaro” are listed in order from the parent server with the highest priority, the parent servers 40, 20, 10, and 30 are in this order.

  The priority of the second priority management table 144 is determined according to the number of transmissions of the parent server that transmits member history information after an event has occurred. For example, in the example illustrated in FIG. 11, the parent server 40 has the largest number of transmissions of the history information corresponding to the member with the member identification number “K101”. Therefore, after a certain event occurs, the member with the member identification number “K101” means that the usage frequency of the child servers 40a to 40c under the parent server 40 is high.

  The child server position information 145 stores child server position information. FIG. 12 is a diagram illustrating an example of the data structure of the child server location information. As shown in FIG. 12, the child server position information 145 associates child server identification information for identifying a child server with position coordinates. For example, the position coordinates of the child server 10a are (x1, y1).

  The control unit 150 includes a registration unit 151, a priority setting unit 152, a history information request unit 153, a damaged area identification unit 154, and a notification unit 155. The control unit 150 corresponds to an integrated device such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Moreover, the control part 150 respond | corresponds to electronic circuits, such as CPU and MPU (Micro Processing Unit), for example.

  The registration unit 151 is a processing unit that receives history information from each parent server 10 to 40 and registers the received history information in the history information management table 142. When the registration unit 151 receives the history information, the registration unit 151 compares the user identification information of the history information with the member information management table 141 and identifies the member identification number corresponding to the history information. The registration unit 151 registers history information in the history information management table 142 in association with the determined member identification number.

  Here, there are a plurality of types of user identification information in the history information depending on the contents of the history information. For example, when the history information is the history information shown in FIG. 2, the user identification information is an employee number. When the history information is the history information shown in FIG. 3, the user identification information is a bank account number. When the history information is the history information shown in FIG. 4, the user identification information is the IC card identification number 1. When the history information is the history information shown in FIG. 5, the user identification information is the IC card identification number 2.

  For example, a case where the registration unit 151 acquires the history information illustrated in FIG. 2 will be described. When the registration unit 151 compares the user identification information “w1001” of the history information with the member information management table 141, the registration unit 151 hits the record in the first row of the member information management table 141, and thus the member identification number is “K101”. It becomes. Therefore, the registration unit 151 registers the history information in FIG. 2 in association with the member identification number “101” in the history information management table 142.

  The priority setting unit 152 is a processing unit that sets the priority of each parent server 10 to 40 for each member identification number based on the history information management table 142. The priority setting unit 152 sets priorities in the first priority management table 143 and the second priority management table 144.

  Processing in which the priority setting unit 152 sets priority in the first priority management table 143 will be described. The priority setting unit 152 analyzes the history information management table 142, calculates the behavior pattern of the member, and calculates the priority of the parent server in each time slot for each member. The priority setting unit 152 registers each piece of information in the first priority management table 143 based on the calculation result.

  For example, the priority setting unit 152 classifies history information corresponding to a certain member identification number for each time zone. The priority setting unit 152 analyzes each classified history information, and totals the transmission frequency of the history information of the parent server in each time zone. And the priority setting part 152 sets a priority so that it may become a high priority, so that the parent server with high transmission frequency of historical information becomes high. The priority setting unit 152 registers priority 1 server identification information, priority 2 server identification information, and priority 3 server identification information in the first priority management table 143 in association with the member identification number and the time zone.

  Here, the priority setting unit 152 distinguishes the parent server that transmitted the history information based on the user identification information of the history information. When the user identification information of the history information is an employee number, the parent server that has transmitted the history information is the parent server 10. When the user identification information of the history information is a bank account number, the parent server that has transmitted the history information is the parent server 20. When the user identification information of the history information is the IC card identification number 1, the parent server that has transmitted the history information is the parent server 30. When the user identification information of the history information is the IC card identification number 2, the parent server that transmitted the history information is the parent server 40.

  For example, in the time zone “8:00 to 9:00” of the member identification number “K101”, the transmission frequency of history information is highest in the parent server 10, followed by the parent server 20 and the parent server 30 in this order. . In this case, the priority setting unit 152 adds “parent server 10” and “parent” to the priority 1 to 3 server identification information of the member identification number “K101” and the time zone “8:00 to 9:00”, respectively. Server 20 "and" parent server 30 "are registered. The priority setting unit 152 repeatedly executes the above process for all time zones of all member identification numbers.

  Processing in which the priority setting unit 152 sets priority in the second priority management table 144 will be described. The priority setting unit 152 sets a priority in the second priority management table 144 after a predetermined event occurs. Here, the predetermined event corresponds to, for example, a case where a disaster such as an earthquake, a tsunami, or a fire occurs, or a case where a search request for a certain member is issued. For example, the predetermined event is notified from an external device (not shown) via the network 80.

  The priority setting unit 152 determines the priority of each parent server for each member identification number based on the transmission frequency of history information transmitted from each parent server 10 to 40 after a predetermined event occurs. , Information is registered in the second priority management table 144.

  For example, when the member identification number “K101” is arranged in order from the parent server having the highest history information transmission frequency, the parent servers 40, 20, 10, and 30 are obtained. In this case, as shown in FIG. 11, the priority setting unit 152 sets the priorities of the parent servers 10 to 40 to the member identification number “K101” to 3, 2, 4, 1, respectively. The priority setting unit 152 determines the priorities of the parent servers 10 to 40 corresponding to all member identification numbers, and sets them in the second priority management table 144. The priority setting unit 152 executes the above process every time history information is received, and updates the priority of the second priority management table 144.

  The history information request unit 153 is a processing unit that generates public safety information when public request information is received from a client terminal. It is assumed that the public request information includes a member identification number. The history information request unit 153 outputs the generated public safety information to the notification unit 155. Further, the history information requesting unit 153 refers to the first priority management table 143 and the second priority management table 144, and records the history information corresponding to the member with the member identification number in the order according to the priority. Request to servers 10-40. Hereinafter, the processing of the history information request unit 153 will be specifically described.

  First, the history information request unit 153 detects history information corresponding to the member identification number from the history information management table 142 using the member identification number included in the disclosure request information as a key, and discloses each detected history information. Generated as safety information. FIG. 13 is a diagram showing an example of public safety information. In the example shown in FIG. 13, the public safety information corresponding to the member identification number “K101” is shown. The history information request unit 153 outputs the public safety information to the notification unit 155. The history information request unit 153 may black out a part of the user identification information included in the public safety information from the viewpoint of safety.

  Next, processing in which the history information request unit 153 requests history information from the servers 10 to 40 using the first priority management table 143 or the second priority management table 144 will be described. The history information request unit 153 requests history information using the first priority management table 143 before a predetermined event occurs. On the other hand, the history information request unit 153 requests the history information once using the first priority management table 143 after a predetermined event occurs, and thereafter the second priority management table 144. Is used to request history information. It is considered that the members are taking actions that are not much different from usual before or after the occurrence of a predetermined event. On the other hand, it is because it is thought that a member will take a different behavior after a predetermined event occurs for a while.

  A process in which the history information request unit 153 requests history information from the parent servers 10 to 40 using the first priority management table 143 will be described. The history information request unit 153 compares the first priority management table 143 with the member identification number included in the disclosure request information and the current time, and sets the parent server corresponding to the priority 1-3 server identification information. judge. The history information request unit 153 generates history request information including user identification information, a parent server corresponding to priority 1 server identification information, a parent server corresponding to priority 2 server identification information, and priority 3 server identification information. The history request information is transmitted in the order of the parent servers corresponding to.

  For example, when the current time is “8:30” and the member identification number “K101” included in the disclosure request information, this corresponds to the record in the first line in FIG. Therefore, the history information request unit 153 transmits history request information in the order of the parent servers 10, 20, and 30.

  The history information request unit 153 generates public safety information including the received history information at the time when the historical information in response to the history request information is received from the parent server, and outputs the public safety information to the notification unit 155. . When the history information cannot be received from the parent server corresponding to the priority 1-3 server identification information, the history information request unit 153 sequentially transmits the history request information to other parent servers.

  Next, processing in which the history information requesting unit 153 requests history information from the servers 10 to 40 using the second priority management table 144 will be described. The history information request unit 153 compares the second priority management table 144 with the member identification number included in the disclosure request information, and determines the priority of each parent server 10-40. The history information request unit 153 transmits history request information in order from the parent server with the highest priority.

  For example, in FIG. 11, regarding the member identification number “K101” included in the disclosure request information, when the parent servers 10 to 40 are arranged in order of priority, the parent servers 40, 20, 10, and 30 are obtained. For this reason, the history information requesting unit 153 transmits the history request information in the order of the parent servers 40, 20, 10, 30.

  The history information request unit 153 generates public safety information including the received history information at the time when the historical information in response to the history request information is received from the parent server, and outputs the public safety information to the notification unit 155. . When the history information cannot be received from the parent servers 10 to 40, the history information request unit 153 sequentially transmits the history request information to other parent servers.

  By the way, each parent server 10-40 requests the history information from the child server using the user identification information included in the history request information as a key. For example, the parent server 10 acquires employee number history information from the child servers 10a to 10c using the employee number in the user identification information. The parent server 20 uses the bank account number in the user identification information, and acquires history information of the corresponding bank account number from the child servers 20a to 20c. The parent server 30 acquires the history information of the corresponding IC card identification number 1 from the child servers 30a to 30c using the IC card identification number 1 of the user identification information. The parent server 40 acquires the history information of the corresponding IC card identification number 2 from the child servers 40a to 40c using the IC card identification number 2 of the user identification information. Each parent server 10-40 transmits history information to the management apparatus 100 when the history information can be acquired from the child server.

  Each parent server 10 to 40 holds history request information, and compares the user identification information of the history information with the user identification information of the history request information when it is transmitted from the child server. Each parent server 10-40 may transmit history information to the management apparatus 100 immediately when each user identification information corresponds. When the parent servers 10 to 40 execute such processing, the history information requesting unit 153 can quickly acquire member history information.

  The damaged area specifying unit 154 is a processing unit that receives response presence / absence information from each of the parent servers 10 to 40 and specifies the magnitude of damage and the damaged area. The damaged area identification unit 154 outputs damage status information that is the identification result to the notification unit 155. Hereinafter, the processing of the damaged area specifying unit 154 will be specifically described.

  Based on the response presence / absence information and the child server position information 145, the damaged area specifying unit 154 specifies the position of the child server that does not respond as the damaged area. Further, the damaged area specifying unit 154 specifies the magnitude of damage based on the ratio of the non-response child servers among all the child servers located in a certain area. For example, when the ratio is less than the first threshold, the damage area specifying unit 154 sets the damage size to “small”. The damaged area specifying unit 154 sets the magnitude of damage to “medium” when the ratio is equal to or higher than the first threshold and the ratio is lower than the second threshold. The damaged area specifying unit 154 sets the magnitude of damage as “large” when the ratio is equal to or greater than the second threshold. However, the first threshold value is smaller than the second threshold value. In addition, the damaged area specifying unit 154 determines that there is no damage when all the child servers located in a certain area respond.

  The notification unit 155 is a processing unit that transmits the public safety information acquired from the history information request unit 153 to the client terminal that is the transmission source of the public request information. Further, when acquiring the damage status information from the damaged area specifying unit 154, the notification unit 155 transmits the damage status information to the client terminal that is the transmission source of the public request information. Note that the notification unit 155 may transmit the damage status information to the client terminal when the location specified by the public safety information includes an area of damage magnitude “small” to “large”. .

  Next, a processing procedure of the management apparatus 100 according to the present embodiment will be described. A process in which the management apparatus 100 receives history information before a predetermined event occurs will be described. FIG. 14 is a flowchart illustrating a processing procedure in which the management apparatus receives history information.

  As shown in FIG. 14, the management apparatus 100 determines whether or not history information has been received from the parent server (step S101). If the history information has not been received from the parent server (step S101, No), the management apparatus 100 moves again to step S101. When receiving history information from the parent server (step S101, Yes), the management apparatus 100 determines a member identification number corresponding to the history information based on the member information management table 141 and the history information (step S101). S102).

  The management apparatus 100 registers history information in the history information management table 142 for each member identification number (step S103). The management apparatus 100 analyzes the history information in the history information management table 142 to calculate the behavior pattern of the member, and calculates the priority of the parent server in each time zone (step S104).

  Next, a processing procedure when the management apparatus 100 receives disclosure request information from a client terminal will be described. FIG. 15 is a flowchart illustrating a processing procedure when the management apparatus receives disclosure request information from a client terminal. As illustrated in FIG. 15, the management apparatus 100 determines whether or not disclosure request information has been received from a client terminal (step S <b> 201). When the management apparatus 100 has not received the disclosure request information from the client terminal (No at Step S201), the management apparatus 100 proceeds to Step S201.

  On the other hand, when receiving the disclosure request information from the client terminal (Yes in step S201), the management apparatus 100 generates the safety information for disclosure using the member identification number as a key (step S202).

  The management apparatus 100 transmits the public safety information to the requesting client terminal (step S203). The management device 100 selects the parent server having the highest priority at the current time (step S204), and transmits history request information to the selected parent server (step S205).

  The management apparatus 100 determines whether history information has been received from the parent server (step S206). If the history information has not been received from the parent server (No at Step S206), the management apparatus 100 selects the parent server with the next highest priority (Step S207), and proceeds to Step S205.

  On the other hand, when the history information is received from the parent server (step S206, Yes), the management apparatus 100 generates public safety information including the newly received history information and transmits it to the client terminal (step S208). .

  Next, a processing procedure in which the management apparatus 100 requests history information based on the second priority management table 144 will be described. FIG. 16 is a flowchart illustrating a processing procedure in which the management apparatus requests history information based on the second priority management table. For example, the management apparatus 100 executes the process shown in FIG. 16 after a predetermined event occurs.

  As shown in FIG. 16, the management apparatus 100 selects a parent server with the highest priority based on the second priority management table 144 (step S301). The management device 100 transmits history request information to the selected parent server (step S302).

  The management device 100 determines whether history information has been received from the parent server (step S303). When the history information has not been received from the parent server (No at Step S303), the management apparatus 100 selects the parent server with the next highest priority (Step S304), and proceeds to Step S303.

  On the other hand, when the history information is received from the parent server (step S303, Yes), the management apparatus 100 generates public safety information including the newly received history information and transmits it to the client terminal (step S305). . The management apparatus 100 updates the priority of the second priority management table according to the frequency of transmitting the history information (step S306).

  Next, a processing procedure when the management apparatus 100 receives response presence / absence information will be described. FIG. 17 is a flowchart illustrating a processing procedure when the management apparatus receives response presence / absence information.

  As shown in FIG. 17, the management apparatus 100 receives response presence / absence information of each child server from the parent server (step S401). Based on the child server location information 145 and the response presence / absence information, the management device 100 identifies the magnitude of damage and the damaged area, and generates damage status information (step S402).

  The management apparatus 100 determines whether or not the position of the member specified by the history information is included in the damaged area (step S403). When the position of the member is included in the damaged area (step S403, Yes), the management apparatus 100 transmits the damage status information to the client terminal (step S404). On the other hand, if the position of the member is not included in the damaged area (No in step S403), the management apparatus 100 ends the process.

  Next, effects of the management apparatus 100 according to the present embodiment will be described. The management apparatus 100 registers the member history information acquired from each parent server 10 to 40 in the member information management table 141, and determines the priority of each parent server 10 to 40 based on each registered history information. . When the management apparatus 100 receives the disclosure request information from the client terminal, the management apparatus 100 sequentially requests the history information based on the priorities of the parent servers 10 to 40, and transmits the history information obtained from the parent server to the client terminal. . Here, it can be said that the higher the priority parent server, the easier it is to acquire the member history information from the past results. For this reason, by requesting history information from the parent servers 10 to 40 in the order according to the priority, the latest history information of the members can be efficiently collected, and safety confirmation can be performed quickly and reliably. .

  Moreover, the management apparatus 100 sets the priority with respect to each time slot | zone for every member identification number to each server based on the transmission frequency of the historical information of each time slot | zone by the parent servers 10-40. For this reason, the management apparatus 100 can set the priority according to the behavior pattern in a member's daily life to each parent server 10-40, and collects the historical information of the member in daily life efficiently. Can do.

  Moreover, the management apparatus 100 sets the priority of a member identification number to each server 10-40 based on the transmission frequency of the historical information by the parent servers 10-40 after a predetermined event occurs. For this reason, even if a predetermined event occurs and the member takes an unusual action, the priority of the parent server that easily obtains the member's history information can be set high, and by using this priority, Even in situations different from daily life, it is possible to efficiently collect member history information.

  Moreover, the management apparatus 100 acquires response presence / absence information indicating whether or not there is a response from the child server from each of the parent servers 10 to 40, and identifies the damaged area based on the response presence / absence information. For this reason, according to the management apparatus 100, not only the safety of a member but the local damage situation by a predetermined event can be specified.

  Moreover, each parent server 10-40 retains history request information, and compares the user identification information of the history information with the user identification information of the history request information when it is transmitted from the child server. When the user identification information matches, the history information is immediately transmitted to the management apparatus 100. When the parent servers 10 to 40 execute such processing, the management apparatus 100 can quickly acquire member history information.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different forms other than the embodiments described above.

  Of the processes described in the present embodiment, all or part of the processes described as being performed automatically can be performed manually, or all of the processes described as being performed manually or A part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Furthermore, each processing function performed by each device may be realized by a CPU and a program that is analyzed and executed by the CPU, or may be realized as hardware by wired logic.

10, 20, 30, 40 Parent server 10a, 10b, 10c, 20a, 20b, 20c, 30a, 30b, 30c, 40a, 40b, 40c Child server 80 Network 100 Management device

Claims (7)

A registration unit that acquires user history information including user identification information that uniquely identifies a user from a plurality of servers, and registers the acquired history information in a history information management table;
A priority setting unit for setting the priority of each server for each user identification information based on the history information registered in the history information management table;
History requesting history information to each server based on the priority of each server corresponding to the user identification information included in the disclosure request information when disclosure request information including user identification information is received from the client An information requesting unit;
And a notification unit that notifies the client of history information obtained from the server in response to a request from the history information request unit.   The priority setting unit sets a priority for each time zone for each user identification information based on the transmission frequency of history information of each time zone by the server, and the predetermined event occurs. 2. The management apparatus according to claim 1, wherein a priority for each user identification information is set in each server later based on a transmission frequency of history information by the server.   The history information request unit requests history information from each server based on the time when the disclosure request information is acquired and the priority of each server for each time zone, and is set after a predetermined event occurs. The management apparatus according to claim 2, wherein the history information is requested to each server again based on the priority of the management server.   4. The management according to claim 1, wherein the history information request unit requests each server to transmit the history information to the management apparatus when each server acquires the history information. apparatus.   Response presence / absence information indicating whether or not there is a response from a child server connected to the server is acquired from the server, and a damaged area is identified based on the response presence / absence information and the location information of the child server The management apparatus according to claim 1, further comprising a damaged area specifying unit. A management method executed by a computer,
User history information including user identification information that uniquely identifies a user is acquired from a plurality of servers, and the acquired history information is registered in a history information management table,
Based on the history information registered in the history information management table, for each user identification information, set the priority of each server,
When receiving public request information including user identification information from a client, request history information from each server based on the priority of each server corresponding to the user identification information included in the public request information,
A management method characterized by executing each process of notifying the client of history information obtained from the server. On the computer,
User history information including user identification information that uniquely identifies a user is acquired from a plurality of servers, and the acquired history information is registered in a history information management table,
Based on the history information registered in the history information management table, for each user identification information, set the priority of each server,
When receiving public request information including user identification information from a client, request history information from each server based on the priority of each server corresponding to the user identification information included in the public request information,
A management program for executing each process of notifying the client of history information obtained from the server.

Images