JP2012198717A - Infection notification method and infection notification device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve accuracy of specifying a warning target terminal related to a person likely to be infected.SOLUTION: A server 4 comprises a collection unit 41 for collecting, from a mobile terminal 2, an action history including a user ID for identifying the mobile terminal 2, a staying area for identifying a position of the mobile terminal 2 and staying time for identifying the time at the position, and storing the action history in an action history table 34. Further, the server 4 comprises a specifying unit 42 for, when the user ID of the mobile terminal 2 of an infected person is detected, specifying the user ID of the mobile terminal 2 which has been present within a dangerous area inside the same space during a specified period on the basis of the action history including the user ID of the infected person. Further, the server 4 comprises a notification unit 43 for notifying the person likely to be infected related to the specified user ID of warning information.

Description

  The present invention relates to an infection notification method and an infection notification apparatus.

  In recent years, for example, various preventive measures have been taken to prevent the spread of infectious diseases such as influenza virus. Therefore, as a measure to prevent the spread of infectious diseases, not only the early detection of infected people, but also informing the contacts who contacted the infected people early on the onset of the infection of the contact partner, Infectious disease prevention systems that can prevent infection are known.

  The infectious disease prevention system has a server provided with a database that manages the telephone number, contact date and mail address of a contact person's mobile phone in contact with an infected person in association with each other. Then, the server reads the mail address of the contact person who has contacted the infected person judged to be positive by a medical institution or the like from the database, and sends a warning mail using the read contact person's mail address (for example, Patent Document 1). As a result, the contact person who has contacted the infected person sees the warning mail and recognizes the contact with the infected person, and can prevent the infection and thus the spread of the infection to a third party.

  In addition, there is a function of acquiring the current position of the terminal using GPS (Global Positioning System) of each terminal. In this system, the distance between the two is calculated based on the current position of the meeting partner and the current position, and a warning sound is acoustically output when the calculated distance is less than a predetermined threshold (see, for example, Patent Document 2). As a result, the user can recognize the approach of the meeting partner based on the warning sound.

JP 2009-217649 A JP 2002-232947 A

  However, in Patent Document 1, since information on a contact person managed on the database side is left to the self-report of the infected person, a warning mail cannot be notified to a contact person who is not managed despite contact with the infected person. Moreover, for example, when an infected person makes air contact with an unspecified number of passengers in a closed space such as a crowded train, it is difficult for the infected person to report information on all the contacts.

  Patent Document 2 is a technique for calculating the distance between two terminals from GPS position information, although the purpose is not to determine the risk of infection. Therefore, by combining the techniques of Patent Documents 1 and 2, GPS location information for each terminal is recorded as a history, and contacts existing within a predetermined distance from the location information of the infected person's terminal, that is, the terminal of an infected person It is possible to identify a system that warns people with infection.

  However, whether or not there is a risk of infection cannot be determined simply by the approach distance with the infected person, even if both are close to the distance of contact, both are shut off pneumatically in a closed space such as a room. The risk of airborne infection is low.

  Therefore, the system does not consider air shut-off and simply determines the risk of infection based on only the approach distance, so if both are shut off pneumatically in a closed space, the risk of infection is low. Regardless, because they are just before contact, they are identified as the terminals of infected people. As a result, the accuracy of identifying infected people is reduced.

  In one aspect, an object of the present invention is to provide an infection notification method and an infection notification device that can improve the accuracy of identifying a terminal related to an infected person.

  In one aspect of the disclosed method, the computer collects a history including an identifier for identifying the terminal device, position information for identifying the position of the terminal device, and time information for identifying the date and time of the position from the terminal device. Is stored in the storage unit. Further, when the computer detects the identifier of the terminal device of the infected person, based on the history including the identifier of the terminal device of the infected person, the identifier of the terminal device existing within the specified distance in the same space based on the history including the identifier of the terminal device of the infected person. Is identified from the storage unit. Further, the computer notifies the user related to the terminal device having the identified identifier.

  With the disclosed method, it is possible to improve the accuracy of identifying a terminal related to an infected person.

FIG. 1 is an explanatory diagram illustrating an example of an infection notification system according to the present embodiment. FIG. 2 is a functional block diagram showing an example of the inside of the mobile terminal. FIG. 3 is a functional block diagram illustrating an example of the inside of the server. FIG. 4 is an explanatory diagram illustrating an example of table contents of the user table. FIG. 5 is an explanatory diagram showing an example of the table contents of the area table. FIG. 6 is an explanatory diagram showing an example of the table contents of the virus table. FIG. 7 is an explanatory diagram illustrating an example of a range in which an action history is searched. FIG. 8 is an explanatory diagram showing an example of the contents of the action history table. FIG. 9 is an explanatory diagram illustrating an example of table contents of the user infection table. FIG. 10 is an explanatory diagram illustrating an example of table contents of the system table. FIG. 11 is an explanatory diagram showing an example of the table contents of the sterilization area table. FIG. 12 is an explanatory diagram illustrating an example of table contents of the risk aggregation table. FIG. 13 is an explanatory diagram of an example of the list contents of the warning target list. FIG. 14 is an explanatory diagram illustrating an example of a dangerous area range. FIG. 15 is an explanatory diagram illustrating an example of the dangerous area range in the area. FIG. 16 is an explanatory diagram illustrating an example of the operation of the second point calculation unit and an example of a dangerous area range in the area. FIG. 17 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the infection registration process. FIG. 18 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the action history extraction process. FIG. 19 is an explanatory diagram illustrating an example of a data acquisition image related to the action history extraction process. FIG. 20 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the infection rich person extraction process. FIG. 21 is a flowchart showing an example of the processing operation of the control unit on the server side related to the first infection rich person extraction process. FIG. 22 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the first infection rich person extraction process. FIG. 23 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the second infection rich person extraction process. FIG. 24 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the second infection rich person extraction process. FIG. 25 is a flowchart showing an example of the processing operation of the control unit on the server side related to the first infection point setting process. FIG. 26 is a flowchart showing an example of the processing operation of the control unit on the server side related to the second infection point setting process. FIG. 27 is a flowchart showing an example of the processing operation of the control unit on the server side related to the third infection point setting process. FIG. 28 is a flowchart illustrating an example of the processing operation of the server-side control unit related to the sterilization registration process. FIG. 29 is a flowchart illustrating an example of the processing operation of the control unit on the server side related to the risk point totaling process. FIG. 30 is a flowchart illustrating an example of the processing operation of the server-side control unit related to the warning notification process. FIG. 31 is an explanatory diagram of a computer that executes an infection notification program.

  Hereinafter, an embodiment of an infection notification method and an infection notification apparatus disclosed in the present application will be described in detail based on the drawings. The disclosed technology is not limited by the present embodiment.

  FIG. 1 is an explanatory diagram illustrating an example of an infection notification system according to the present embodiment. The infection notification system 1 shown in FIG. 1 includes a mobile terminal 2 of a plurality of users, an action history server 3 that manages an action history of the mobile terminal 2, and a server 4 that manages infection information of the user. The mobile terminal 2 is communicatively connected to the action history server 3 and the server 4 through a radio base station (not shown). The server 4 is communicatively connected to the action history server 3 via a communication network such as the Internet or a private line network (not shown).

  FIG. 2 is a block diagram illustrating an example of the inside of the mobile terminal 2. The mobile terminal 2 illustrated in FIG. 2 includes a wireless unit 11, an operation unit 12, a display unit 13, a storage unit 14, and a control unit 15. The wireless unit 11 performs wireless communication with a communication partner via a wireless base station. The operation unit 12 inputs various commands corresponding to the operation content. The display unit 13 displays various information. The storage unit 14 stores various information. The control unit 15 controls the entire mobile terminal 2. The control unit 15 includes a position acquisition unit 15A that acquires GPS information using a GPS (Global Positioning System) function. The GPS information includes a mobile terminal 2, that is, a user ID that is an identifier for identifying a user of the mobile terminal 2, a stay area that is position information of the current position of the mobile terminal 2, and a stay date and time that is date and time information of the current position. Have When acquiring the GPS information, the position acquisition unit 15A transmits the acquired GPS information to the action history server 3. The action history server 3 stores GPS information received from each mobile terminal 2 in an action history database (hereinafter simply referred to as DB) 3A. In the action history DB 3A, for example, a user's action history for every second is stored. Furthermore, the action history server 3 transmits the action history stored in the action history DB 3 </ b> A to the server 4.

  FIG. 3 is a block diagram illustrating an example of the inside of the server 4. The server 4 illustrated in FIG. 3 includes a communication unit 21, an operation unit 22, a display unit 23, a storage unit 24, and a control unit 25. The communication unit 21 communicates with the radio base station of the mobile terminal 2 and the action history server 3. The operation unit 22 inputs various commands corresponding to the operation content. The display unit 23 displays various information. The storage unit 24 includes a user table 31, an area table 32, a virus table 33, an action history table 34, a user infection table 35, and a system table 36. Furthermore, the storage unit 24 includes a sterilization area table 37, a risk count table 38, a warning target list 39, and an infected person action table 40. FIG. 4 is an explanatory diagram showing an example of the table contents of the user table 31. The user table 31 shown in FIG. 4 has a user ID 31A, a mail address 31B, and an attribute 31C. The user ID 31A is an ID for identifying the mobile terminal 2, that is, the user of the mobile terminal 2. The mail address 31B is the mail address of the user's notification destination. The attribute 31C is attribute information of a user, for example, attribute information such as an elderly person, a twenties, and a newborn. The control unit 25 can recognize, for example, “USR0001” of the user ID 31A, “usr01@dodomo.ne.jp” of the mail address 31B, and the attribute 31C “elderly” with reference to the user table 31 illustrated in FIG.

  FIG. 5 is an explanatory diagram showing an example of the table contents of the area table 32. The area table 32 illustrated in FIG. 5 includes an area ID 32A, a position information start point 32B, a position information end point 32C, an area name 32D, and a virus survival rate 32E. The area ID 32A is an ID for identifying the stay area. The position information start point 32B is the start point coordinates of the position information of the stay area. The position information end point 32C is an end point coordinate of the position information related to the stay area. The area name 32D is a name for identifying the stay area. The virus survival rate 32E is the virus survival rate in the stay area. The virus survival rate varies depending on changes in environmental temperature and humidity. The control unit 25 can recognize, for example, “AREA00001” of area ID 32A, “center building first floor entrance” of area name 32D, and “20%” of virus survival rate 32E with reference to the area table 32 shown in FIG.

  FIG. 6 is an explanatory diagram showing an example of table contents of the virus table 33. The virus table 33 shown in FIG. 6 includes a virus ID 33A, a virus name 33B, a first infection point 33C, a second infection point 33D, and a third infection point 33E. Furthermore, the virus table 33 has a maximum survival time 33F, a pre-onset infection possible time 33G, a post-onset infection possible time 33H, and a pre-onset latency 29I. The virus ID 33A is an ID for identifying a virus. The virus name 33B is a name for identifying a virus.

  The first infection point 33C is a point indicating a degree of risk given to a user who stays in a “narrow range” of a danger area range described later. The second infection point 33D is a point indicating a degree of risk given to a user who stays in a “medium range” of a danger area range described later. The third infection point 33E is a point indicating a degree of risk given to a user who stays in a “wide area” of a dangerous area range described later. The maximum survival time 33F is the maximum time during which a virus can survive in the stay area. The possible infection time 33G before onset is a period during which infection is possible before onset. The post-onset infection possible time 33H is a period during which infection is possible after onset. The onset latency 33I is a latent period until onset. The control unit 25 refers to the virus table 33 shown in FIG. 6, for example, “VRS001” of the virus ID 33A, “Hong Kong influenza” of the virus name 33B, “300” of the first infection point 33C, and the second infection point. 33D “100” can be recognized. Further, the control unit 25 sets the third infection point 33E to “50”, the maximum survival time 33F to “24”, the pre-onset infection possible time 33G “24”, the post-onset infection possible time 33H “48”, the pre-onset “48” of the incubation time 33I can be recognized.

  FIG. 7 is an explanatory diagram illustrating an example of a range in which an action history is searched. The action history search range shown in FIG. 7 is the action history search range between the pre-onset infection possible time and the post-onset infection possible time starting from the onset date. For example, the possible infection time before onset is 24 hours, and the possible infection time after onset is 48 hours. The control unit 25 searches the behavior history for the period from the pre-onset infection possible time (24 hours) before the onset date based on the onset date and time to the current date and time after the onset onset time (48 hours) after the onset date. Range. If the current date and time exceeds the infection possible time after onset, the range from the pre-onset infection possible time to the post-onset infection possible time is set as the search range of the action history.

  FIG. 8 is an explanatory diagram showing an example of the contents of the action history table 34. The action history table 34 illustrated in FIG. 8 includes a user ID 34A, a stay date 34B, and a stay area 34C. The user ID 34A is an ID for identifying the mobile terminal 2, that is, the user of the mobile terminal 2. The stay date 34B is the date and time when the user stayed in the stay area. The stay area 34 </ b> C is position information (GPS position coordinates) where the mobile terminal 2, that is, the user stayed. The control unit 25 can recognize, for example, “USR0001” of the user ID 34A, “2010/2/2 17:59:59” of the stay date 34B, and the stay area 34C with reference to the action history table 34 shown in FIG. . In order to effectively use the memory resources of the action history table 34, the control unit 25 automatically deletes the contents of the action history table 34 after a predetermined period of time has elapsed since the registration of the action history. Also good.

  FIG. 9 is an explanatory diagram illustrating an example of table contents of the user infection table 35. The user infection table 35 shown in FIG. 9 has a user ID 35A, an infected virus ID 35B, and an onset date 35C. The user ID 35A is an ID of a user who has developed an infection. The infectious virus ID 35B is an ID for identifying a virus that has developed an infection. The onset date and time 35C is the onset date and time of the infectious virus. The control unit 25 refers to the user infection table 35 shown in FIG. 9, for example, “USR0003” of the user ID 35A, “VRS003” of the infected virus ID 35B, and “2010/2/17 03:00:00 of the onset date 35C. Can be recognized. Note that the control unit 25 may delete the record of the infected person from the user infection table 35 when the infected person is completely cured.

  FIG. 10 is an explanatory diagram showing an example of the table contents of the system table 36. The system table 36 shown in FIG. 10 has a system value classification 36A, a system code name 36B, and a system value 36C. The system table 36 sets and manages condition threshold values, condition points, and the like. The control unit 25 refers to the system table 36 shown in FIG. 10. The “wide area” of the danger area range has a radius of 3 m, the “medium area” has a radius of 2 m, the “narrow area” has a radius of 1 m, and the behavior of the action history table 34. It can be recognized as 7 days as a period for storing and holding the history. Further, the control unit 25 can recognize that the dangerous point threshold “level AAA” is 10,000 points, the dangerous point threshold “level AA” is 5000 points, and the dangerous point threshold “level A” is 3000 points. The control unit 25 can recognize that the danger point threshold “level B” is 2000 points and the danger point threshold “level C” is 1000 points.

  FIG. 11 is an explanatory diagram showing an example of the table contents of the sterilization area table 37. The sterilization area table 37 illustrated in FIG. 11 includes a sterilization virus ID 37A, an implementation date 37B, a target area 37C, and a target area ID 37D. The sterilized virus ID 37A is an ID of a sterilized virus. The implementation date 37B is the date and time when the virus was sterilized. The target area 37C is the position coordinates of the area where sterilization is performed. The target area ID 37D is an ID for identifying an area where sterilization is performed. The control unit 25 refers to the sterilization area table 37 shown in FIG. 11, for example, “VRS001” of the sterilization virus ID 37A, “2010/2/2 17:59:59” of the implementation date 37B, and the target area 37C. And the area ID 37 can be recognized.

  FIG. 12 is an explanatory diagram showing an example of the table contents of the risk tabulation table 38. The risk tabulation table 38 illustrated in FIG. 12 includes a user ID 38A, a stay date / time 38B, a stay area 38C, an infectious virus ID 38D, and a danger point 38E. The user ID 38A is an ID for identifying the mobile terminal 2 staying within the dangerous area range, that is, the user of the mobile terminal 2. The stay date and time 38B is the stay date and time of the user of the mobile terminal 2 who stayed in the stay area within the dangerous area range. The stay area 38C is the position coordinates of the stay area within the danger area where the user stayed. The infectious virus ID 38D is an ID for identifying an infectious virus within the dangerous area. The danger point is an evaluation point indicating the risk of infection according to the staying position of the user within the danger area. The control unit 25 can recognize, for example, “USR0001” of the user ID 38A, “2010/2/2 17:59:59” of the stay date and time 38B, and the stay area 38C with reference to the risk aggregation table 38 shown in FIG. . Further, the control unit 25 can recognize “VSR001” of the infected virus ID 38D and “300” of the danger point 38E.

  FIG. 13 is an explanatory diagram showing an example of the list contents of the warning target list 39. The warning target list 39 shown in FIG. 13 includes a user ID 39A and a totaling point 39B. The user ID is an ID for identifying a contact person close to the infected person, that is, an infected dense person. The totaling point 39B is a point obtained by counting the risk points of the infected rich person. The control unit 25 can recognize, for example, “USR0001” of the user ID 39A and “1500” of the aggregation point 39B with reference to the warning target list 39 of FIG.

  The control unit 25 includes a collection unit 41, a specification unit 42, and a notification unit 43. The collection unit 41 collects the behavior history of each mobile terminal 2 registered in the behavior history DB 3 </ b> A of the behavior history server 3, and registers the collected behavior history in the behavior history table 34. The specifying unit 42 includes a search unit 42A, an infected person specifying unit 42B, a risk area calculating unit 42C, a contact person specifying unit 42D, a first point calculating unit 42E, an adjusting unit 42F, and a second point calculating unit 42G. And have. When the search unit 42A detects the user ID, virus ID, and onset date of the infected person, the search unit 42A acquires from the virus table 33 the pre-onset infection possible time 33G and the post-onset infection possible time 33H corresponding to the virus ID 33A. Furthermore, the search unit 42A calculates a specified period that is a search range based on the infection possible time before the onset and the infection possible time after the onset based on the onset date and time of the infected person. Furthermore, the search unit 42A searches the behavior history table 34 for the behavior history of the infected person within the specified period.

  The infected person specifying unit 42B specifies the action history of the infected person based on the search result of the searching unit 42A. The dangerous area calculation unit 42C calculates area information of the dangerous area range based on the stay area of the action history of the infected person and the dangerous area range in the system table 36. In the risk area range, for example, the level of infection risk increases in the order of “wide range” → “medium range” → “narrow range”. FIG. 14 is an explanatory diagram illustrating an example of a dangerous area range. As shown in FIG. 14, the dangerous area calculation unit 42 </ b> C creates a spherical dangerous area range centered on the stay area of the infected person. A range of 1 m radius centered on the stay area of the infected person is “narrow range”, a range of 2 m radius centered on the stay area is “medium range”, a range of 3 m radius centered on the stay area is “wide area” To do. That is, the dangerous area calculation unit 42C calculates the area information of the dangerous area range based on the stay area of the infected person who has acted within the designated period. Further, the dangerous area calculation unit 42C searches the area table 32 for the area ID 32A and the virus survival rate 32E using the area information of the dangerous area range of the infected person.

  The contact identification unit 42D acts on the behavior history of the mobile terminal 2 staying in the dangerous area range and the stay area with the same area ID at the same date and time as the infected person within the specified period, that is, the behavior history of the infected person of the mobile terminal 2. It is specified from the history table 34. Further, the first point calculation unit 42E obtains an infection point corresponding to the dangerous area range for each action history of the infected rich person from the virus table 33, and uses the infection point as the risk point 38E for each action history of the infected rich person. Register in the tabulation table 38.

  FIG. 15 is an explanatory diagram illustrating an example of the dangerous area range in the area. The first point calculation unit 42E identifies the user of the mobile terminal 2 who stayed within the danger area range of the same area ID and the same date and time within the specified period, that is, the infection rich person, and determines the infection risk of the infection rich person. Calculate the infection point indicated. User B in the stay area (meeting room 1) shown in FIG. 15 stayed in the “narrow area” of the danger area range, so the danger point is “1” because the first infection point corresponds to the “narrow area”. 300 ". Since the user C stayed in the “medium range” of the risk area range, the risk point is “100” because of the second infection point corresponding to the “medium range”. Since the user E stayed in the “wide area” of the dangerous area range, the risk point is “50” because the third infection point corresponds to the “wide area”. Users D and F stay in the “wide area” of the dangerous area range, but the area ID of the stay area in which the infected person stayed is different, that is, outside the conference room 1, so that they are excluded from the infected dense person. become. That is, if the area ID is different, for example, because the space such as a room is different, it is determined that the risk of infection by the infected person is low. Since the user G is outside the dangerous area range even in the same area as the infected person, the user G is excluded from the infected dense person.

  In addition, even if an infected person staying in a stay area such as a room leaves the room, the virus remains in the room for a certain period of time. There is a good chance of being infected. Therefore, the contact identification unit 42D records the behavior history of the user who has left the room in the stay area and stayed within the risk area of the same area ID within the remaining period of the virus residue, that is, the behavior history of the infected person. It is specified from the table 34. Further, the adjustment unit 42F acquires the maximum survival time 33F corresponding to the virus ID 33A of the infected person from the virus table 33. Furthermore, the adjustment unit 42F acquires the virus survival rate 32E of the space corresponding to the area ID 32A of the stay area of the infected person from the area table 32. The adjustment unit 42F calculates the maximum survival time of the virus in the stay area based on the maximum survival time of the virus and the virus survival rate in the stay area. Furthermore, the adjustment unit 42F calculates the first infection point, the second infection point, and the third infection point corresponding to the elapsed time of the remaining period and the dangerous area range based on the maximum survival time of the stay area. FIG. 16 is an explanatory diagram illustrating an example of the operation of the second point calculation unit 42G and an example of the dangerous area range in the stay area. In the virus table 33 shown in FIG. 16, the virus ID 33A of the target virus is “VRS001”, the first infection point 33C is “300”, the second infection point 33D is “100”, the third infection point 33E is “50”, the maximum The survival time 33F is “24” hours. Further, in the area table 32, the area ID 32A is “AREA00006”, and the virus survival rate 32E is 40%. Accordingly, the adjustment unit 42F has a maximum survival time of 9.6 hours based on the maximum survival time of 24 hours × virus survival rate of 40%.

  Further, the adjustment unit 42F divides the maximum survival time 9.6 hours into 1/4, and the first time zone after 0 hours ≦ X <2.4 hours, 2.4 hours ≦ X <4.8 hours later. The second time zone, 4.8 hours ≦ X <7.2 hours after the third time zone, and 7.2 hours ≦ X <9.6 hours after the fourth time zone. Furthermore, the adjustment unit 42F sets the virus survival rate corresponding to the first time zone to 100%, the first infection point to 300, the second infection point to 100, and the third infection point to 50. In addition, the adjustment unit 42F has a virus survival rate corresponding to the second time period of 75%, the first infection point is 300 × 75%, the second infection point is 100 × 75%, and the third infection point is 50 × 75%. And In addition, the adjustment unit 42F sets the virus survival rate corresponding to the third time zone to 50%, the first infection point to 300 × 50%, the second infection point to 100 × 50%, and the third infection point to 50 × 50%. And Furthermore, the adjustment unit 42F has a virus survival rate corresponding to the fourth time zone of 25%, the first infection point is 300 × 25%, the second infection point is 100 × 25%, and the third infection point is 50 × 25%. And In other words, as the time passes from the first time zone → the second time zone → the third time zone → the fourth time zone, the residual virus in the room also decreases and the risk of infection decreases, so descend.

  The second point calculation unit 42G acquires an infection point corresponding to the dangerous area range and the time zone based on the infection point calculated for each time zone after the infected person exits the area, and the acquired infection point of the user Are registered in the risk tabulation table 38 as danger points. FIG. 16 is an example of the second time zone and the third time zone. In the example of the second time zone, since the user I stayed in the “narrow range” of the dangerous area range, the dangerous point is the first infection point 300 × 75% = 225. Since the user H stayed in the “middle range” of the risk area range, the risk point is the second infection point 100 × 75% = 75. Since the user J stayed in the “wide area” of the danger area range, the danger point is the third infection point 50 × 75% = 37.5. Although the users K and L stay in the stay area with the same area ID, they are outside the danger area range, and thus are excluded from the infected rich people. Furthermore, although the user M stayed in the “wide area” of the dangerous area range, the area ID is different, so the user M is excluded from the infected dense person.

  Further, in the example of the third time zone, the user H stays in the “narrow range” of the dangerous area range, so the dangerous point is the first infection point 300 × 50% = 150. Since the user I stayed in the “middle range” of the risk area range, the risk point is the second infection point 100 × 50% = 50. Since the user J stayed in the “wide area” of the risk area range, the risk point is the third infection point 50 × 50% = 25. Since the user K is outside the dangerous area range, the user K is excluded from those who are infected. Furthermore, the user M is excluded from the infected dense person because the area ID is different from the outside of the dangerous area range.

  The notification unit 43 includes a counting unit 43A and a determination unit 43B. The tabulating unit 43A tabulates the risk points already registered in the risk tabulation table 38 in units of user IDs of the infected dense person, and registers the risk points tabulated in association with the user IDs in the warning target list 39. The determination unit 43B determines whether or not the dangerous point registered in the warning target list 39 exceeds the dangerous point threshold registered in the system table 36. When the dangerous point of the infected rich person exceeds the dangerous point threshold, the notification unit 43 notifies the warning information to the mail address of the mobile terminal 2 of the infected rich person. As a result, the user of the mobile terminal 2 can recognize that he is a highly infected person with a high risk of infection based on the warning information.

  Next, the operation of the infection notification system 1 of this embodiment will be described. When the position acquisition unit 15A of the mobile terminal 2 acquires its own GPS information, the position acquisition unit 15A transmits the GPS information to the action history server 3. When the action history server 3 receives the GPS information of each mobile terminal 2, the action history server 3 stores the received GPS information in the action history DB 3 </ b> A as the action history of the user related to the mobile terminal 2. Further, the collection unit 41 in the control unit 25 of the server 4 communicates with the behavior history server 3 via the communication unit 21 to receive the behavior history of each mobile terminal 2 stored in the behavior history DB 3A, and these are received. The action history is stored in the action history table 34.

  FIG. 17 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the infection registration process. The infection registration process shown in FIG. 17 is a process of registering information about an infected person in the user infection table 35 in response to an infected person registration request. In FIG. 17, the control unit 25 determines whether or not an infected person registration request is detected from the mobile terminal 2 through the communication unit 21 (step S11). When detecting the registration request of the infected person (Yes at Step S11), the control unit 25 registers the infected user ID 35A, the infected virus ID 35B corresponding to the virus name, and the onset date and time 35C in the user infection table 35 (Step S12). ), The processing operation shown in FIG. If the control unit 25 does not detect the registration request for the infected person (No at Step S11), the control unit 25 ends the processing operation shown in FIG. In the infection registration process shown in FIG. 17, the user's infection is registered in the user infection table 35 in response to the registration request of the mobile terminal 2. As a result, the control unit 25 can recognize the infected person with reference to the user infection table 35.

  FIG. 18 is a flowchart showing the processing operation of the control unit 25 on the server 4 side related to the action history extraction process. FIG. 19 is an explanatory diagram illustrating an example of a data acquisition image related to the action history extraction process. In the action history extraction process shown in FIG. 18, the action history of the infected person is extracted from the action history table 34. In FIG. 18, the search unit 42A in the specifying unit 42 of the control unit 25 acquires the user ID, virus ID, and onset date of the infected person from the user infection table 35 (step S21). The search unit 42A acquires the infection possible time before the onset of the virus and the infection possible time after the onset from the virus table 33 according to the acquired virus ID (step S22). As shown in FIG. 19, the search unit 42A specifies an action history record in the action history table 34 (step S23). The search unit 42A determines whether or not the user ID of the designated action history record matches the user ID of the infected person (step S24). When the search unit 42A matches the user ID of the infected person (Yes at step S24), the stay date and time in the action history record is (onset date-pre-attack possible time) to (onset date + infection possible time). It is determined whether it is within the designated period (step S25).

  If the stay date / time is within the specified period (Yes at step S25), the infected person specifying unit 42B sets the user ID, the stay date / time and the stay area as the infected person's action history as the action history record as shown in FIG. It registers in the action table 40 (step S26). Then, the search unit 42A determines whether or not there is an unprocessed action history record in the action history table 34 (step S27). If there is no unprocessed action history record (No at Step S27), the search unit 42A ends the processing operation illustrated in FIG.

  Further, when the user ID of the action history record does not match the user ID of the infected person (No at Step S24), the search unit 42A specifies an unprocessed action history record from the action history table 34 (Step S28). The process proceeds to S24. If the stay date and time in the action history record is not within the specified period (No at Step S25), the search unit 42A proceeds to Step S28 to specify an unprocessed action history record from the action history table 34. Further, when there is an unprocessed action history record (Yes at Step S27), the search unit 42A designates an unprocessed action history record from the action history table 34 (Step S29), and proceeds to Step S24.

  In the behavior history extraction process shown in FIG. 18, the behavior history of the infected person within the specified period can be extracted from the behavior history table 34 and the behavior history of the infected person can be registered in the infected person behavior table 40. As a result, the control unit 25 can recognize the action history of the infected person with reference to the infected person action table 40.

  FIG. 20 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the infection rich person extraction process. In the infection rich person extraction process, the infected rich person staying in the dangerous area range of the same area ID and the same date and time as the infected person, and staying in the dangerous area range of the same area ID within the remaining period after leaving the infected person This is a process of extracting the action history of the infected rich person from the action history table 34. The specifying unit 42 in the control unit 25 shown in FIG. 20 executes a first extraction process for extracting the action history of the infected dense person who stayed in the dangerous area range of the same area ID at the same date and time as the infected person (step S31). ). After executing the first extraction process, the specifying unit 42 executes the second extraction process for extracting the action history of the infected dense person who stayed in the dangerous area range of the same area ID within the remaining period after leaving the infected person. (Step S32), the processing operation shown in FIG.

  FIG. 21 and FIG. 22 are flowcharts showing an example of the processing operation of the control unit 25 on the server 4 side related to the first extraction processing. The first extraction process shown in FIG. 21 is a process of extracting the action history of an infected dense person who stayed in the dangerous area range in the same area ID at the same date and time as the infected person. In FIG. 21, the dangerous area calculation unit 42C in the control unit 25 acquires the stay area and the stay date and time in the action history record of the infected person from the infected person action table 40 (step S41). As shown in FIG. 19, the dangerous area calculation unit 42C acquires, from the area table 32, the area ID 32A, the position information start point 32B, and the position information end point 32C corresponding to the stay area for each stay area of the infected person (step S42). . The dangerous area calculation unit 42C generates a concentric dangerous area range centered on the stay area based on the position information start point 32B and the position information end point 32C of the stay area and the system value of the dangerous area range registered in the system table 36. Area information is calculated (step S43). That is, the danger area calculation unit 42C calculates “narrow range”, “medium range”, and “wide range” area information of the concentric danger area range with the stay area as the center, and obtains area information corresponding to each range. Register in a dangerous area range table (not shown). As shown in FIG. 14 and FIG. 15, the “wide range” is within a radius of 3 m around the stay area of the infected person, and the “medium range” is within a radius of 2 m around the stay area of the infected person. The “narrow range” is within a radius of 1 m around the stay area of the infected person.

  The contact identification unit 42D designates the behavior history record of the user from the behavior history table 34 in order to extract the behavior history of the infected dense person who stayed in the dangerous area range at the same date and time as the infected person from the behavior history table 34 ( Step S44). The contact person identifying unit 42D determines whether or not the stay date and time in the designated action history record is the same as the stay date and time of the infected person (step S45). When the stay date / time in the action history record is the same as the stay date / time of the infected person (Yes at Step S45), the contact person identifying unit 42D has the stay area in the action history record within the “narrow range” of the dangerous area range. Is determined (step S46). When the stay area is within the “narrow range” (Yes at Step S46), the first point calculation unit 42E acquires the first infection point corresponding to the virus ID of the infected virus of the infected person from the virus table 33 (Step S47). ), The process proceeds to M1 in FIG.

  If the stay area in the action history record is not within the “narrow range” (No at step S46), the contact identification unit 42D determines whether the stay area is within the “medium range” of the danger area range. (Step S48). When the stay area is within the “medium range” (Yes at Step S48), the contact identification unit 42D acquires the second infection point corresponding to the virus ID of the infected person from the virus table 33 (Step S49), and FIG. To M1. If the stay area is not within the “medium range” (No at Step S48), the contact identification unit 42D determines whether the stay area is within the “wide range” of the dangerous area range (Step S50). In addition, when the stay area is within the “wide area” (Yes at Step S50), the contact identification unit 42D acquires a third infection point corresponding to the virus ID of the infected person from the virus table 33 (Step S51). It moves to M1 of 22.

  Further, when the stay date / time in the action history record is not the same as the stay date / time of the infected person (No at Step S45), the contact person identifying unit 42D sets M2A in FIG. 22 to designate the next unprocessed action history record. Transition. In addition, when the stay area in the action history record is not within the “wide range” (No at Step S50), the contact identification unit 42D determines that this action history is not the target, and specifies the next unprocessed action history record. Therefore, the process proceeds to M2A in FIG.

  In M1 of FIG. 22, when the contact identification unit 42D acquires the risk point in step S47, step S49, or step S51, the contact person identification unit 42D acquires the area ID of the user corresponding to the stay area in the behavior history record from the area table 32. (Step S61). Then, the contact identification unit 42D determines whether or not the area ID of the user in the action history record is the same as the area ID of the infected person acquired in step S42 (step S62). When the area ID of the user and the area ID of the infected person in the action history record are the same (Yes at Step S62), the contact identification unit 42D recognizes the user as an infected rich person. Then, the contact identification unit 42D registers the user ID, stay date and time, stay area, danger point, and virus ID of the user who is an infected rich person in the risk count table 38 (step S63). Further, the contact identification unit 42D determines whether there is an unprocessed next behavior history record in the behavior history table 34 (step S64). When there is an unprocessed next action history record in the action history table 34 (Yes at Step S64), the contact identification unit 42D designates the next action history record (Step S66), and proceeds to M2 in FIG. . In step S64, it is determined whether or not there is an unprocessed action history record. However, when the action history record is specified in order of the stay date and time, the contact identification unit 42D determines that the stay date and time is It is determined whether or not it is after the infection possible time after the onset of the infected person, and when the stay time is after the infection possible time after the onset of the infected person, the process may move to step S65.

  When there is no unprocessed action history record in the action history table 34 (No at Step S64), the contact identification unit 42D determines whether there is an unprocessed action history record of the infected person in the infected person action table 40. Determination is made (step S65). When there is an unprocessed infected record (Yes at Step S65), the contact identification unit 42D specifies an action history record of the next unprocessed infected person in the infected person behavior table 40 (Step S67). And contact person specific part 42D shifts to M3 of Drawing 21 in order to acquire a stay date and a stay area from an infected person's action history record. Further, when there is no action history record of an unprocessed infected person (No at Step S65), the contact identification unit 42D ends the processing operation of FIG.

  In the first extraction process, the behavior history of the infected dense person who stayed in the dangerous area range of the same area ID at the same date and time as the infected person is extracted from the behavior history table 34. As a result, it is possible to acquire an action history of an infected rich person who is a user staying in the dangerous area range of the same area ID at the same date and time as the infected person.

  Further, in the first extraction process, different infection points can be registered as risk points in the risk count table 38 according to the “narrow range”, “medium range”, or “wide range” of the dangerous area range where the infected rich person stayed.

  23 and 24 are flowcharts illustrating an example of the processing operation of the control unit 25 on the server 4 side related to the second extraction process. The second extraction process shown in FIG. 23 is a process for extracting an action history of an infected dense person who has entered the dangerous area range of the same area ID within the remaining period after leaving the infected person. In FIG. 23, the adjustment unit 42F of the control unit 25 acquires the first infection point, the second infection point, the third infection point, and the maximum survival time corresponding to the virus ID for identifying the infected virus of the infected person from the virus table 33. (Step S71). The infected person identifying unit 42B acquires the stay area and the stay date and time in the action history record of the infected person from the infected person action table 40 (step S72). The adjustment unit 42F acquires the area ID 32A, the position information start point 32B, the position information end point 32C, and the virus survival rate 32E corresponding to the stay area from the area table 32 for each stay area of the infected person (step S73). As shown in FIG. 16, the adjustment unit 42 </ b> F is based on the maximum survival time corresponding to the virus ID of the infected virus of the infected person and the virus survival rate corresponding to the area ID of the stay area, and the maximum survival time × virus survival rate. To calculate the maximum survival time of the stay area (step S74). Furthermore, the adjustment unit 42F divides the maximum survival time (residual period) into 1/4 and divides it into four time zones, and calculates the first infection point, the second infection point, and the third infection point for each time zone. (Step S75).

  The dangerous area calculation unit 42C calculates area information of the dangerous area range at the center of the stay area based on the position information start point and position information end point of the stay area and the system value of the dangerous area range registered in the system table 36. (Step S76), the process proceeds to M4 in FIG.

  In M4 shown in FIG. 24, the contact person identifying unit 42D designates an action history record from the action history table 34 (step S81). The contact identification unit 42D determines whether or not the stay date and time in the behavior history record is within the remaining period (step S82). When the stay date and time in the action history record is within the remaining period (Yes at Step S82), the contact identification unit 42D determines whether or not the stay area in the action history record is within the “narrow range” of the dangerous area range. Is determined (step S83). When the stay area is within the “narrow range” (Yes at Step S83), the contact identification unit 42D executes the first infection point setting process for acquiring the first infection point corresponding to the corresponding time zone within the remaining period. (Step S84).

  If the stay area in the action history record is not within the “narrow range” (No at step S83), the contact identification unit 42D determines whether the stay area is within the “medium range” of the danger area range. (Step S85). When the stay area is within the “medium range” (Yes at Step S85), the contact identification unit 42D executes a second infection point setting process for acquiring a second infection point corresponding to the corresponding time zone within the remaining period. (Step S86).

  If the stay area is not within the “medium range” (No at Step S85), the contact identification unit 42D determines whether the stay area is within the “wide range” of the dangerous area range (Step S87). In addition, when the stay area is within the “wide range” (Yes at Step S87), the contact identification unit 42D executes the third infection point setting process for acquiring the third infection point corresponding to the corresponding time zone within the remaining period. (Step S88).

  When the contact identification unit 42D acquires the infection point in step S84, step S86, or step S88, the contact identification unit 42D acquires the area ID of the user corresponding to the stay area in the behavior history record from the area table 32 (step S89). Then, the contact identification unit 42D determines whether or not the area ID of the user in the behavior history record is the same as the area ID of the infected person acquired in step S73 (step S90). When the area ID of the user in the action history and the area ID of the infected person are the same (Yes at Step S90), the contact identification unit 42D recognizes the user as an infected rich person. Then, the contact identification unit 42D determines whether or not the same record including the user ID of the infected rich person, the stay date and time, and the stay area exists in the risk tabulation table 38 (step S91). When the same record does not exist in the risk totaling table 38 (No at Step S91), the contact identification unit 42D registers the user ID, the date and time of stay, the staying area, the infection point, and the virus ID in the risk totaling table 38. (Step S92).

  Further, the contact identification unit 42D determines whether there is an unprocessed action history record in the action history table 34 (step S93). When there is an unprocessed next behavior history record in the behavior history table 34 (Yes at Step S93), the contact identification unit 42D specifies the next behavior history record (Step S94), and proceeds to Step S82. Further, when there is no unprocessed next action history record in the action history table 34 (No in step S93), the contact identification unit 42D has an unprocessed infected person action history record in the infected person action table 40. Whether or not (step S95). In step S93, it is determined whether or not there is an unprocessed action history record. If the action history record is specified in the order of the stay date and time, the contact identification unit 42D determines that the stay date and time is that of the infected person. It is determined whether or not it is after the onset possible infection time, and if the stay time is after the infection possible time after the onset of the infected person, the process may proceed to step S95.

  When there is an unprocessed infected person action history record (Yes at step S95), the contact identification unit 42D specifies an unprocessed infected person action history record in the infected person action table 40 (step S96). And the contact person specific | specification part 42D transfers to M5 of FIG. 23 in order to acquire a stay date and stay area from an action history of an infected person. If there is no action history record of an unprocessed infected person (No at Step S95), the contact identification unit 42D ends the processing operation of FIG. Further, when the same record is in the risk totaling table 38 (Yes at Step S91), the contact identification unit 42D proceeds to Step S93 in order to determine whether or not there is an unprocessed next action history record. Also. If the area IDs are not the same (No at Step S90), the contact identification unit 42D proceeds to Step S93 in order to determine whether or not there is an unprocessed next action history record. Further, when the stay date and time in the action history record is not within the remaining period (No at Step S82) or when the stay area in the action history record is not “wide” (No at Step S87), The process proceeds to S93.

  In the second extraction process, after leaving the infected person, the action history of the infected dense person who stayed in the dangerous area range of the same area ID within the remaining period is extracted from the action history table 34. As a result, it is possible to acquire the action history of an infection-rich person who has a risk of infection staying in the risk area range of the same area ID within the remaining period.

  Furthermore, in the second extraction process, different infection points can be registered as risk points in the risk count table 38 according to the “narrow range”, “medium range”, or “wide range” of the danger area range where the infected rich person stayed.

  FIG. 25 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the first infection point setting process. The first infection point setting process shown in FIG. 25 is a process of setting the first infection point as a danger point according to the elapsed time zone of the remaining period in the stay area. In FIG. 25, the 2nd point calculation part 42G determines whether a user's stay date is a 1st time slot | zone (step S101). The second point calculation unit 42G sets the first infection point (× 100%) in the first time zone when the stay date and time of the user is in the first time zone (Yes in Step S101) (Step S102). The processing operation shown in FIG.

  When the user's stay date is not the first time zone (No at Step S101), the second point calculation unit 42G determines whether the user's stay date is the second time zone (Step S103). When the user's stay date is in the second time zone (Yes at Step S103), the second point calculation unit 42G sets the first infection point (× 75%) in the second time zone (Step S104). The processing operation shown in FIG.

  When the user's stay date / time is not in the second time zone (No at Step S103), the second point calculation unit 42G determines whether the user's stay date / time is in the third time zone (Step S105). The second point calculation unit 42G sets the first infection point (× 50%) in the third time zone (step S106) when the stay date and time of the user is in the third time zone (Yes in step S105). The processing operation shown in FIG.

  In addition, when the stay date and time of the user is not in the third time zone (No at Step S105), the second point calculation unit 42G sets the first infection point (× 25%) in the fourth time zone (Step S107), The processing operation shown in FIG. 25 ends.

  In the first infection point setting process shown in FIG. 25, the first infection corresponding to the virus survival rate for the infected dense person who stayed in the “narrow range” of the dangerous area range according to the elapsed time zone of the residual period. You can set points.

  FIG. 26 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the second infection point setting process. In the second infection point setting process shown in FIG. 26, the second infection point is set according to the elapsed time zone of the remaining period in the stay area. In FIG. 26, the 2nd point calculation part 42G determines whether the said user's stay date is a 1st time slot | zone (step S111). The second point calculation unit 42G sets the second infection point (× 100%) in the first time zone (step S112) when the stay date and time of the user is in the first time zone (Yes in step S111). The processing operation shown in FIG.

  When the user's stay date is not the first time zone (No at Step S111), the second point calculation unit 42G determines whether the user's stay date is the second time zone (Step S113). The second point calculation unit 42G sets the second infection point (× 75%) in the second time zone (step S114) when the stay date and time of the user is in the second time zone (Yes in step S113). The processing operation shown in FIG.

  When the user's stay date / time is not in the second time zone (No at Step S113), the second point calculation unit 42G determines whether the user's stay date / time is in the third time zone (Step S115). The second point calculation unit 42G sets the second infection point (× 50%) in the third time zone (step S116) when the stay date and time of the user is in the third time zone (Yes in step S115). The processing operation shown in FIG.

  In addition, when the stay date and time of the user is not in the third time zone (No at Step S115), the second point calculation unit 42G sets the second infection point (× 25%) in the fourth time zone (Step S117), The processing operation shown in FIG. 26 ends.

  In the second infection point setting process shown in FIG. 26, the second infection point corresponding to the virus survival rate is given to the infected dense person staying in the “medium range” of the dangerous area range according to the elapsed time zone of the remaining period. Can be set.

  FIG. 27 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the third infection point setting process. The third infection point setting process shown in FIG. 27 is a process of setting the third infection point according to the elapsed time zone within the remaining period in the stay area. In FIG. 27, the 2nd point calculation part 42G determines whether the said user's stay date is the 1st time slot | zone (step S121). The second point calculation unit 42G sets the third infection point (× 100%) in the first time zone (step S122) when the staying date and time of the user is in the first time zone (Yes in step S121). The processing operation shown in FIG.

  When the user's stay date is not the first time zone (No at Step S121), the second point calculation unit 42G determines whether the user's stay date is the second time zone (Step S123). When the user's stay date is in the second time zone (Yes at Step S123), the second point calculation unit 42G sets the third infection point (× 75%) in the second time zone (Step S124). The processing operation shown in FIG.

  When the user's stay date is not the second time zone (No at Step S123), the second point calculation unit 42G determines whether the user's stay date is the third time zone (Step S125). The second point calculation unit 42G sets the third infection point (× 50%) in the third time zone (step S126) when the stay date and time of the user is in the third time zone (Yes at step S125). The processing operation shown in FIG.

  In addition, when the stay date and time of the user is not in the third time zone (No at Step S125), the second point calculation unit 42G sets the third infection point (× 25%) in the fourth time zone (Step S127), The processing operation shown in FIG. 27 ends.

  In the third infection point setting process shown in FIG. 27, the third infection point corresponding to the virus survival rate is assigned to the infected dense person who stayed in the “wide area” of the dangerous area according to the elapsed time zone of the residual period. Can be set.

  FIG. 28 is a flowchart illustrating an example of processing operation inside the control unit 25 on the server 4 side related to the sterilization registration processing. In the sterilization registration process shown in FIG. 28, when the virus in the area is sterilized by sterilization or the like, the sterilization in the area is registered in the sterilization area table 37 in association with the area ID. In FIG. 28, the control unit 25 determines whether or not the sterilization work has been registered (step S131). When the sterilization work has been registered (Yes at Step S131), the control unit 25 ends the processing operation illustrated in FIG. When the sterilization operation has not been registered (No at Step S131), the control unit 25 sterilizes the sterilization virus ID of the sterilization target virus, the date and time of sterilization, and the area ID for identifying the target area to be sterilized. Information is registered in the sterilization area table 37 (step S132). Then, the control unit 25 ends the processing operation shown in FIG.

  In the sterilization registration process shown in FIG. 28, when the sterilization operation is executed, the sterilization virus ID, the sterilization date and time, and the area ID of the sterilization target virus can be registered in the sterilization area table 37. As a result, the control unit 25 can recognize the sterilization virus ID, the sterilization date and time, and the area ID with reference to the table contents of the sterilization area table 37.

  FIG. 29 is a flowchart showing an example of the processing operation of the control unit 25 on the server 4 side related to the dangerous point totaling process. The danger point totaling process shown in FIG. 29 is a process for totalizing the infection points of each user registered in the risk totaling table 38 in units of users. The totaling unit 43A of the control unit 25 shown in FIG. 29 sorts in order of the user ID, stay date and virus ID in the risk totaling table 38 (step S141), and specifies an unprocessed action history record from the risk totaling table 38. (Step S142). The counting unit 43A refers to the table contents of the sterilization area table 37, and determines whether or not the stay date and time in the action history record is after the sterilization date and time (implementation date and time) of the virus (step S143). When the stay date / time in the action history record is after the sterilization date / time (Yes in step S143), the counting unit 43A determines whether the area ID of the stay area in the action history record is the same as the area ID of the sterilization target area. It is determined whether or not (step S144).

  When the area ID is the same as the area ID of the sterilization target area (Yes in step S144), the aggregation unit 43A does not add the risk points in the action history record and there is an unprocessed action history record in the risk aggregation table 38. It is determined whether or not (step S145). When there is an unprocessed action history record in the risk totaling table 38 (Yes in step S145), the totaling unit 43A specifies an unprocessed action history record in the risk totaling table 38 (step S146). Further, when the unprocessed action history record is designated, the counting unit 43A proceeds to step S143 in order to determine whether or not the stay date / time in the action history record is after the sterilization date / time.

  Further, when the stay date and time in the action history record is not after the sterilization date and time (No at Step S143), the totaling unit 43A determines whether or not the summation of the risk points corresponding to the user ID of the action history record has been completed ( Step S147). When the summation of the risk points corresponding to the user ID in the action history record is not completed (No at Step S147), the summation unit 43A adds the current risk point to the previous risk points corresponding to the user ID. (Step S148). And total part 43A totals a dangerous point in Step S148, and shifts to Step S145 to determine whether there is an unprocessed action history record in risk total table 38.

  Further, when the aggregation of the risk points corresponding to the user IDs in the action history record is completed (Yes at Step S147), the aggregation unit 43A registers the user ID and the risk points of the user in the warning target list 39 (Step S147). S149). And total part 43A shifts to Step S145 to determine whether there is an unprocessed action history record. If the area ID of the stay area in the action history record is not the area ID of the area to be sterilized (No at step S144), the counting unit 43A has completed the summation of the risk points corresponding to the user ID in the action history record. In order to determine whether or not, the process proceeds to step S147.

  In the risk point totaling process shown in FIG. 29, the risk points in the risk total table 38 are totaled for each infected person, and the total risk points are registered in the warning target list 39 as the total points. As a result, the control unit 25 can totalize the risk points as the total points for each infected dense person.

  Furthermore, in the risk point totaling process, the area of virus sterilization can be reflected by removing it from the addition of the user's risk points after the sterilization date and time related to the sterilized target area.

  FIG. 30 is a flowchart illustrating an example of a processing operation of the control unit 25 on the server 4 side related to the warning notification process. The warning notification process shown in FIG. 30 is a process of notifying infection-rich warning information to infection-rich people when the total points for each user registered in the warning target list 39 exceeds a predetermined risk point threshold. is there. In FIG. 30, the determination unit 43B in the control unit 25 determines whether or not the total point of the user ID registered in the warning target list 39 is greater than or equal to the risk point threshold AAA (step S151). When the total point is equal to or higher than the risk point threshold AAA (Yes at Step S151), the determination unit 43B notifies the warning information of the risk level AAA to the mail address of the user ID (Step S152). Further, the determination unit 43B determines whether or not there is an unprocessed record in the warning target list 39 (step S153). When there is no unprocessed record in the warning target list 39 (No at Step S153), the determination unit 43B ends the processing operation illustrated in FIG. When there is an unprocessed record in the warning target list 39 (Yes at Step S153), the determination unit 43B specifies the next unprocessed record (Step S154), and proceeds to Step S151.

  Moreover, the determination part 43B determines whether a total point is more than danger point threshold value AAA (step S155), when a total point is not more than danger point threshold value AAA (step S151 negative). When the total point is greater than or equal to the risk point threshold AA (Yes at Step S155), the determination unit 43B notifies the warning information of the risk level AA to the mail address of the user ID (Step S156), and proceeds to Step S153.

  Moreover, the determination part 43B determines whether a total point is more than the danger level A, when a total point is not more than the danger point threshold value AA (step S155 negative) (step S157). When the total point is equal to or higher than the risk point threshold A (Yes at Step S157), the determination unit 43B notifies the warning information of the risk level A to the mail address of the user ID (Step S158), and proceeds to Step S153.

  Moreover, the determination part 43B determines whether a total point is more than the danger point threshold value B, when a total point is not more than the danger point threshold value A (step S157 negative) (step S159). When the total point is equal to or higher than the risk point threshold B (Yes at Step S159), the determination unit 43B notifies the warning information of the risk level B to the mail address of the user ID (Step S160), and proceeds to Step S153.

  Moreover, the determination part 43B determines whether a total point is more than the dangerous point threshold value C, when a total point is not more than the dangerous point threshold value B (step S159 negative) (step S161). When the total point is equal to or higher than the risk point threshold C (Yes at Step S161), the determination unit 43B notifies the warning information of the risk level C to the mail address of the user ID (Step S162), and proceeds to Step S153.

  Further, when the total point is not equal to or higher than the risk point threshold C (No in step S161), the determination unit 43B notifies the safety level warning information to the mail address of the user ID (step S163), and proceeds to step S153. In addition, although the control part 25 notified the warning information of the safety level in step S163, since it is a safety level, it is not necessary to notify warning information.

  In the warning notification process shown in FIG. 30, when the total points of each infected person registered in the warning target list 39 is equal to or higher than the risk point threshold, the warning information corresponding to the dangerous point threshold is sent to the e-mail address of the infected person. Notify As a result, the user can recognize the risk of infection richness based on the warning information corresponding to the risk point threshold.

  In the present embodiment, the server 4 collects the action history of the user of each mobile terminal 2 and registers it in the action history table 34. Further, when the server 4 detects the user ID of the infected person, the server 4 obtains the user ID of the infected rich person who stayed in the dangerous area range of the same area ID within the specified period based on the behavior history including the user ID of the infected person. Identify. Further, the server 4 notifies the warning information to the infected rich person of the specified user ID. In other words, if the space (room) is different even within the same dangerous area range, that is, if the area ID is different, the risk of air infection is low, so it is not specified as an infection dense person, and in the case of the same area ID, Identify. As a result, the infection notification system 1 can improve the accuracy of identifying an infected dense person, thereby avoiding notification of unnecessary warning information due to erroneous identification of an infected dense person.

  In this embodiment, when the user ID and onset date / time of the infected person's mobile terminal 2 are detected, from the pre-onset possible infection period before the onset date / time to the current date / time within the post-onset infection possible period after the onset date / time. The period was designated. As a result, the server 4 can identify the infected dense person who stayed within the dangerous area range of the same area ID as the infected person within the designated period.

  In this example, the maximum survival time (residual period) of the virus in the space was calculated based on the virus survival rate for each space (room) and the maximum survival time of the virus, and the residual period was designated as the specified period. As a result, the server 4 can identify the infected dense person who stayed in the danger area within the remaining period after leaving the space where the infected person stayed.

  In the present embodiment, infection points corresponding to distance categories (“narrow range”, “medium range”, and “wide range”) that divide the danger area range are managed in the virus table 33. If the user ID of an infected person who stayed in the dangerous area range in the same space is specified, an infection point corresponding to the corresponding distance category in the dangerous area area where the infected person stayed is acquired, and the infection point is obtained for each user ID. When the infection points counted for each user ID exceed a predetermined risk point threshold value, the server 4 notifies the warning information to the infected dense person of the user ID. Can recognize the risk of infection based on the warning point based on the warning point reflecting the distance classification.

  In this embodiment, the infection points corresponding to the distance division for dividing the dangerous area range and the time division for dividing the remaining period are managed. When the server 4 identifies the user ID of the infected person who stayed in the dangerous area range in the same space within the remaining period, the server 4 acquires the infection point corresponding to the corresponding distance category and the corresponding time category in the dangerous area range. The user ID of the mobile terminal 2 is acquired. Further, the server 4 acquires the user ID of the mobile terminal 2 and totals the risk points for each user. When the infection points counted for each user ID of the mobile terminal 2 exceed the risk point threshold, the server 4 notifies the warning information to the infected dense person of the user ID. As a result, the infected person can recognize the risk of infection based on the warning information based on the warning points reflecting the distance category and the time category.

  In the above embodiment, the GPS information of the mobile terminal 2 is used as the user action history, but the current position of the mobile terminal 2 is specified from the communication area range of a plurality of radio base stations that wirelessly connect the mobile terminal 2. You may create a user's action history with position information and time information.

  In the above embodiment, the GPS information is acquired on the mobile terminal 2 side, the acquired GPS information is transmitted to the action history server 3, and the action history is created on the action history server 3 side. The mobile terminal 2 may transmit GPS information to the server 4 without going through the server 3. Then, the server 4 may create an action history based on the GPS information of each mobile terminal 2.

  Moreover, in the said Example, although GPS information was acquired from the mobile terminal 2, you may acquire the GPS information of the mobile terminal 2 from the wireless base station which carries out wireless connection with the mobile terminal 2. FIG.

  In the above embodiment, the space where the user stays in the action history is specified by the area ID of the area table 32. However, the entry record of the user of the mobile terminal 2 is obtained from another system, and based on the entry record. The space where the user stays may be specified.

  Moreover, in the said Example, a virus resistance may be set according to a user's attribute, for example, an elderly person, a newborn, etc., and you may make it change an infection point with the virus resistance according to a user's attribute. For example, since newborns have weak virus resistance, infection points are increased compared to those in their 20s. As a result, it is possible to determine infection risk that reflects the user's attributes.

  Further, in the above embodiment, the danger area range has three stages of “narrow range”, “medium range”, and “wide range”, but it may be one or a plurality of stages, and is not limited to the number of stages.

  Moreover, in the said Example, after performing the 1st extraction process in the infection rich person extraction process, the 2nd extraction process was performed, However, You may perform a 1st extraction process after performing a 2nd extraction process. . Moreover, in the said Example, although the 1st extraction process and the 2nd extraction process were performed by the infection rich person extraction process, it becomes possible to select any one extraction process among the 1st extraction process and the 2nd extraction process. May be executed.

  Further, in the above-described embodiment, the warning information is notified to the infected person when the total point of the dangerous points of the infected person who has been registered in the warning target list 39 is equal to or greater than a predetermined dangerous point threshold. However, regardless of the risk point threshold value, warning information may be notified to an infected person when the person is recognized as an infected person based on the action history.

  Moreover, in the said Example, although the infection registration request | requirement of the infected person was transmitted from the mobile terminal 2, for example, the transmission from the communication terminal of the medical institution connected to the server 4 or the operation unit of the server 4 The infection registration request may be input by the input operation 22.

  In addition, each component of each part illustrated does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each part is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured.

  Furthermore, various processing functions performed in each device are performed on a CPU (Central Processing Unit) (or a microcomputer such as an MPU (Micro Processing Unit), MCU (Micro Controller Unit), etc.) in whole or in part. You may make it perform. Various processing functions may be executed entirely or arbitrarily on a program that is analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU) or hardware based on wired logic. Needless to say.

  By the way, various processes described in the present embodiment can be realized by executing a program prepared in advance by a computer. In the following, an example of a computer that executes a program having the same function as that of the above embodiment will be described with reference to FIG. FIG. 31 is an explanatory diagram of a computer that executes an infection notification program.

  As shown in FIG. 31, in a computer 100 as an infection notification program, an HDD (Hard Disk Drive) 110, a RAM (Random Access Memory) 120, a ROM (Read Only Memory) 130, and a CPU 140 are connected via a bus 150. .

  The ROM 130 or HDD 110 stores in advance an infection notification program that exhibits the same function as in the above-described embodiment. It should be noted that the infection notification program may be recorded on a computer-readable recording medium instead of the ROM 130 and the HDD 110. The recording medium may be, for example, a portable recording medium such as a CD-ROM, a DVD disk, or a USB memory, or a semiconductor memory such as a flash memory. As the infection notification program, as shown in FIG. 31, there are a collection program 131, a management program 132, a specific program 133, and a notification program 134. Note that the programs 131 to 134 may be appropriately integrated or distributed in the same manner as the components of the server 4 shown in FIG.

  Then, the CPU 140 reads these programs 131 to 134 from the ROM 130 and executes them. The programs 131 to 134 function as a collection process 141, a management process 142, a specific process 143, and a notification process 144.

  The CPU 140 collects from the mobile terminal 2 a user action history including a user ID for identifying the mobile terminal 2, position information for identifying the position of the mobile terminal 2, and time information for identifying the date and time of the position. And stored in the RAM 120. When the CPU 140 detects the user ID of the mobile terminal 2 of the infected person, the CPU 140 stays in the dangerous area range in the same space within the specified period based on the position information and time information of the action history including the user ID of the infected person. The user ID of the mobile terminal 2 is specified from the RAM 120. Then, the CPU 140 notifies the warning information to the user of the specified user ID. As a result, it is possible to improve the accuracy of identifying the warning target terminal related to the infected person.

  As described above, the following supplementary notes are further disclosed regarding the embodiment including the present example.

(Supplementary note 1)
A history including an identifier for identifying the terminal device, position information for identifying the position of the terminal device, and time information for identifying the date and time of the position is collected from the terminal device and stored in the storage unit.
When the identifier of the terminal device of the infected person is detected, based on the history including the identifier of the terminal device of the infected person, the identifier of the terminal device existing within the specified distance in the same space is stored from the storage unit within a predetermined period. Identify,
An infection notification method, comprising: performing each process of notifying a user related to a terminal device having an identified identifier.

(Additional remark 2) The said computer further memorize | stores beforehand the positional information on the said space for every space identifier which identifies the said space, and the said process to specify is carried out to the said log | history containing the identifier of the said infected person's terminal device Based on the identified space identifier and the history, the identifier of the terminal device existing within the specified distance within the same space is identified from the storage unit based on the identified space identifier and the history. The infection notification method according to appendix 1, which is characterized.

(Additional remark 3) The said process to identify is based on the said onset date from the 1st designated period before the said onset date based on the said onset date, when the identifier of the said infected person's terminal device and the onset date of onset are detected. In the supplementary note 1 or 2, the identifier of the terminal device existing within the designated distance in the same space within the second designated period after the onset date and time within the period up to the current date and time is specified The infection notification method described.

(Additional remark 4) The said process to identify specifies the identifier of the terminal device which existed within the designated distance in the same space within the designated period from the timing after leaving the said space where the infected person existed, The infection notification method according to appendix 1 or 2.

(Supplementary Note 5) The specified process is performed by specifying a specified distance in the same space within the maximum survival time relating to the virus in the space calculated based on the virus survival rate of the space and the maximum survival time of the virus. 3. The infection notification method according to appendix 1 or 2, wherein an identifier of a terminal device existing in the terminal is specified.

(Additional remark 6) The said computer further memorize | stored the evaluation score corresponding to the distance classification which classifies the said designated distance, and the said process to notify exists within the designated distance in the same space within the said predetermined period. When the terminal device identifier is identified, an evaluation score corresponding to the corresponding distance category within the specified distance where the terminal device exists is acquired, and the evaluation score acquired within the predetermined period for each identifier of the terminal device is obtained. Any one of appendices 1 to 5, characterized in that, when the evaluation score calculated for each identifier of the terminal device exceeds a predetermined threshold, notification is made to the user of the terminal device related to the identifier. The infection notification method described in 1.

(Additional remark 7) The said computer memorize | stored the evaluation score further corresponding to the distance division which divides the said designation | designated distance, and the time division which divides the said designation | designated period, The said process to notify is carried out in the said predetermined period, When the identifier of the terminal device existing within the specified distance in the same space is specified, evaluation points corresponding to the corresponding distance class within the specified distance and the corresponding time class within the third specified period are acquired and the terminal device is acquired. The evaluation score acquired within the predetermined period is totaled for each identifier of the terminal device, and when the evaluation score totaled for each identifier of the terminal device exceeds a predetermined threshold, to the user of the terminal device related to the identifier The infection notification method according to any one of supplementary notes 1 to 5, wherein notification is performed.

(Additional remark 8) The collection part which collects the history which contains the identifier which identifies the said terminal device from the terminal device, the positional information which identifies the position of the said terminal device, and the time information which identifies the date and time of the said position, and memorize | stores it in a memory | storage part When,
When the identifier of the terminal device of the infected person is detected, based on the history including the identifier of the terminal device of the infected person, the identifier of the terminal device existing within the specified distance in the same space is stored from the storage unit within a predetermined period. A specific part to identify;
An infection notification device, comprising: a notification unit that notifies a user of a terminal device related to the identified identifier.

DESCRIPTION OF SYMBOLS 1 Infection notification system 2 Mobile terminal 3 Action history server 4 Server 32 Area table 33 Virus table 34 Action history table 38 Risk totaling table 41 Collection part 42 Identification part 42A Search part 42B Infected person identification part 42C Risk area calculation part 42D Contact person identification Unit 42E first point calculation unit 42F adjustment unit 42G second point calculation unit 43 notification unit 43A counting unit 43B determination unit

Claims (5)

Computer
A history including an identifier for identifying the terminal device, position information for identifying the position of the terminal device, and time information for identifying the date and time of the position is collected from the terminal device and stored in the storage unit.
When the identifier of the terminal device of the infected person is detected, based on the history including the identifier of the terminal device of the infected person, the identifier of the terminal device existing within the specified distance in the same space is stored from the storage unit within a predetermined period. Identify,
An infection notification method, comprising: performing each process of notifying a user related to a terminal device having an identified identifier.   The computer further stores in advance position information of the space for each space identifier for identifying the space, and the specifying process is based on the history including the identifier of the terminal device of the infected person. An identifier is specified, and based on the specified space identifier and the history, an identifier of a terminal device existing within a specified distance within the same space is specified from the storage unit within the predetermined period. The infection notification method according to Item 1. The predetermined period of the specified process is:
When the identifier of the terminal device of the infected person and the onset date and time of infection are detected, the second specified after the onset date and time based on the onset date and time from the first specified period before the onset date and time based on the onset date and time. The infection notification method according to claim 1 or 2, wherein an identifier of a terminal device existing within a specified distance within the same space is specified within a specified period within a period up to the current date and time.   The identification process identifies an identifier of a terminal device existing within a specified distance in the same space within a specified period from a timing after leaving the space in which the infected person existed. Or the infection notification method of 2. A collecting unit for collecting a history including an identifier for identifying the terminal device, position information for identifying the position of the terminal device, and time information for identifying the date and time of the position from the terminal device, and storing the history in the storage unit;
When the identifier of the terminal device of the infected person is detected, based on the history including the identifier of the terminal device of the infected person, the identifier of the terminal device existing within the specified distance in the same space is stored from the storage unit within a predetermined period. A specific part to identify;
An infection notification device, comprising: a notification unit that notifies a user of a terminal device related to the identified identifier.

Images