Support information management server, communication terminal, management method, and program for selectively providing necessary support information for those in need of support

Abstract

To provide a mechanism that provides appropriate supporters with personal information of a person requiring support that is necessary to support the person requiring support.SOLUTION: A server includes: a memory unit that stores support information indicating necessary support contents for a person requiring support who holds a communication tag, tag identification information of the communication tag, and personal information of the person requiring support in association with each other; a reception unit that receives the tag identification information obtained from the communication tag from a communication terminal; and a provision unit that provides the support information corresponding to the received tag identification information to the communication terminal. The provision unit provides the personal information to the communication terminal when information identifying a user of the communication terminal satisfies predetermined conditions.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a support information management server, a communication terminal, a management method, and a program. [Background technology]

[0002] As a background technique of this technical field, there is JP 2015-210710 A (Patent Document 1). This publication states that "the system includes a recognition ring 10 that is worn by a person requiring care at all times or when going outside a contact facility F, a reception telephone 20 that is installed in the contact facility F, and a computer search system 30 that searches for stored personal information of the person requiring care, and the recognition ring 10 is configured to display only the name of the facility 11 or the name of the care support system, the reception telephone number 12, and the personal recognition code 13, and the computer search system 30 includes a personal information creation and registration means for the person requiring care, a database that stores and accumulates personal information, and a search and display means that searches for the personal information of the person requiring care using the personal recognition code 13 and displays it on a screen" (see abstract). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2015-210710 A Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned Patent Document 1 describes a care support system for quickly dealing with unexpected situations such as a person in need of support getting lost or experiencing changes in physical condition while out and about. However, the above-mentioned Patent Document does not consider a method for selectively providing information required to support the person in need of support to a supporter. Therefore, this embodiment provides a mechanism for selectively providing information required to support a person in need of support. [Means for solving the problem]

[0005] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes a number of configurations and methods for solving the above-mentioned problems, and one example is a server comprising: a memory unit that stores support information indicating the support content required for a person in need of support who holds a communication tag, tag identification information of the communication tag, and personal information of the person in need of support in association with each other; a reception unit that receives the tag identification information obtained from the communication tag from a communication terminal; and a provision unit that provides the support information corresponding to the received tag identification information to the communication terminal, wherein the provision unit provides the personal information to the communication terminal when information identifying a user of the communication terminal satisfies certain conditions. Effect of the Invention

[0006] According to the present invention, it is possible to provide a mechanism for selectively providing information required to support a person in need of support. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is an example of a configuration diagram of an entire information management system 1. As shown in FIG. [Diagram 2] FIG. 2 shows an example of the hardware configuration of the communication terminal 102. As shown in FIG. [Diagram 3] FIG. 3 shows an example of the hardware configuration of the management server 103. [Figure 4A] FIG. 4A is an example of a configuration of case 410. [Figure 4B] FIG. 4B shows an example of the hardware configuration of the communication tag 101. [Figure 5A] FIG. 5A is an example of support information table information 510. [Figure 5B] FIG. 5B is an example of personal information permission subject table information 520. [Figure 6] FIG. 6 is an example of the target group table information 600. [Figure 7] FIG. 7 is an example of a personal information authority level table information 700. [Figure 8A] FIG. 8A is an example of authority level table information 810 for a terminal user. [Figure 8B] FIG. 8B is an example of table information 820 of terminal user IDs, attribute groups, and authority levels. [Figure 9A] FIG. 9A is an example of a support information acquisition request 910. [Figure 9B] FIG. 9B is an example of communication data 920 that includes assistance information. [Figure 10] FIG. 10 is an example of an information management method sequence 1000 . [Figure 11] FIG. 11 shows an example of a flow 1100 for determining whether or not personal information can be provided. [Figure 12A] FIG. 12A is an example of a display screen 1210 indicating that a communication tag 101 has been detected. [Figure 12B] FIG. 12B is an example of a display screen 1220 indicating that a communication tag has been detected. [Figure 13A] FIG. 13A is an example of a display screen 1310 indicating that a communication tag 101 has been detected. [Figure 13B] FIG. 13B is an example of a display screen 1320 indicating that a communication tag has been detected. [Figure 14] FIG. 14 is an example of a display screen 1400 in the AR display mode. [Figure 15] FIG. 15 is an example of a display screen 1500 for support information. [Figure 16] FIG. 16 is an example of a display screen 1600 of the permission personal information. [Figure 17] FIG. 17 shows an example of a tag user information registration screen 1700. As shown in FIG. [Figure 18A] FIG. 18A shows an example of a pairing operation screen 1810 for the communication tag 101. In FIG. [Figure 18B] FIG. 18B is an example of a pairing completion notification screen 1820. [Figure 19A]FIG. 19A is an example of a tag user information registration screen 1910. [Figure 19B] FIG. 19B is an example of a tag user information registration screen 1940. [Figure 19C] FIG. 19C is an example of a tag user information registration screen 1960. [Figure 20] FIG. 20 shows an example of the hardware configuration of the communication tag 105. [Figure 21] FIG. 21 is an example of a sequence 2100 according to the second embodiment. [Figure 22] FIG. 22 is an example of a sequence 2200 according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments will be described with reference to the drawings. [Example 1]

[0009] FIG. 1 is an example of a configuration diagram of an entire information management system 1. As shown in FIG. The information management system 1 includes a communication tag 101 and a communication terminal 102, and the communication terminal 102 is connected to a management server 103 via a network. The communication tag 101 is connected to the communication terminal 102 via the network. The communication tag 101, the communication terminal 102, and the management server 103 can transmit and receive information via the network. The communication tag 101 is an IC tag. The communication terminal 102 is a mobile terminal used by a user. The management server 103 is a server computer that manages personal information and support information. Although FIG. 1 shows only one communication tag 101 and one communication terminal 102, the information management system 1 may include a plurality of each.

[0010] The communication terminal 102 of the information management system 1 may be, for example, a portable terminal (mobile terminal) such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or may be a wearable terminal such as glasses, wristwatch, or clothing. The management server 103 may be a stationary or portable computer, or a server located on the cloud or network. In terms of function, it may be a VR (Virtual Reality) terminal, an AR (Augmented Reality) terminal, or an MR (Mixed Reality) terminal. Alternatively, it may be a combination of a plurality of these terminals. For example, a combination of one smartphone and one wearable terminal may function logically as one terminal. It may also be an information processing terminal other than these.

[0011] The communication terminal 102 and management server 103 of the information management system 1 each include a processor that executes an operating system, applications, programs, etc., a main storage device such as a RAM (Random Access Memory), an auxiliary storage device such as an IC card, a hard disk drive, an SSD (Solid State Drive), a flash memory, etc., a communication control unit such as a network card, a wireless communication module, a mobile communication module, etc., input devices such as a touch panel, a keyboard, a mouse, voice input, and input by motion detection by imaging of a camera unit, and an output device such as a monitor or a display. Note that the output device may be a device or terminal that transmits information to be output to an external monitor, display, printer, device, etc.

[0012] The main memory stores various programs and applications (modules), and the processor executes these programs and applications to realize the various functional elements of the overall system. Each of these modules may be implemented in hardware by integration or the like. Each module may be an independent program or application, or may be implemented as a subprogram or function within a single integrated program or application.

[0013] In this specification, each module is described as an entity (subject) that performs processing, but in reality, a processor that processes various programs, applications, etc. (modules) executes the processing. Various databases (DB) are stored in the auxiliary storage device. A "database" is a functional element (storage unit) that stores a data set so that it can handle any data operation (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. There are no limitations on the method of implementing the database, and it may be, for example, a database management system, spreadsheet software, or a text file such as XML or JSON.

[0014] FIG. 2 shows an example of the hardware configuration of the communication terminal 102. As shown in FIG. The communication terminal 102 is a communication terminal used by a user of the information management system 1, and is, for example, a portable terminal such as a smartphone, a tablet, a notebook computer, etc. The communication terminal 102 of this embodiment is a smartphone equipped with a main memory device 201, an auxiliary memory device 202, a processor 203, an input device 204, an output device 205, a camera 206, and a communication control unit 207.

[0015] The main memory device 201 stores functional programs and functional applications such as an execution control module 211, a detection module 212, an acquisition module 213, and a display module 214. Each functional element of the communication terminal 102 is realized by the processor 203 executing the programs stored in the main memory device 201 and the support information management application (hereinafter, sometimes simply referred to as an "app") of the information management system 1.

[0016] The execution control module 211 controls the basic operations of the communication terminal 102 when using the information management system 1. The execution control module 211 cooperates with the information management module 311 of the management server 103 to display web pages and the like of the information management site of the information management system 1.

[0017] For example, the execution control module 211 is realized by the processor 203 executing a support information management application. The execution control module 211 outputs (displays) a login page, a personal information registration page, and the like of the information management system 1 on the output device 205 such as a display of the communication terminal 102, for example.

[0018] The detection module 212 transmits and receives communication signals via short-range wireless communication. For example, the detection module 212 transmits a communication signal of short-range wireless communication at regular time intervals. When the communication terminal 102 and the communication tag 101 approach within a communicable distance, the detection module 212 detects a signal of short-range wireless communication from the communication tag 101 (proximity detection function). For example, the communicable distance of short-range wireless communication is about 10 m.

[0019] The detection module 212 executes the proximity detection function of the communication tag 101 when the support information management application is executed (active state), but, for example, even when the support information management application is not executed (inactive state), the proximity detection function may be executed in cooperation with the basic OS of the communication terminal 102. This allows the communication terminal 102 to detect the communication tag 101 even when the support information management application is not running or is in an inactive state.

[0020] The acquisition module 213 acquires tag identification information (tag ID) of the detected communication tag 101 via short-range wireless communication (first acquisition unit). The acquisition module 213 may be configured to acquire the tag ID from the communication tag 101 when the user of the communication terminal 102 inputs information for acquiring the tag ID.

[0021] The acquisition module 213 transmits the acquired tag ID to the management server 103 and acquires from the management server 103 support information corresponding to the tag ID, which indicates the support content necessary for the person in need of support who is holding the communication tag 101. Specifically, the acquisition module 213 transmits to the management server 103 a support information acquisition request, which is information including the tag ID and user identification information (terminal user ID) that is information for identifying the user of the communication terminal 102 . The support information acquisition request includes the tag ID acquired by the communication terminal 102 from the communication tag 101. The user identification information (terminal user ID) is, for example, the user ID of the user who is logged in to the support information management application executed on the communication terminal 102.

[0022] [About support information and personal information] The support information acquisition request includes information requesting the management server 103 to acquire support information corresponding to the tag ID and personal information of the holder of the communication tag 101 (person requiring support). The support information (also called consideration required information) is information indicating the support content required for the carrier of the communication tag 101 (person requiring support), which is stored in the tag user registration information 321 of the management server 103. The support information is information that the carrier of the communication tag 101 wants to make known to people around them and supporters, and is provided without selecting the recipient.

[0023] Support information is information that indicates content that would like to be made known to people near the person in need of support, people who are able to support the person in need of support, pre-registered supporters, etc., and is information that anyone can see, such as "I have a food allergy and need to be careful with my diet, but it is difficult to explain this in words" or "I have hyperacusis, so please refrain from speaking loudly or making noise."

[0024] The personal information is information such as attributes of the tag holder himself / herself that is registered in advance by the user (tag holder) of the communication tag 101. The personal information includes, for example, information on items such as name, date of birth, address, telephone number, information on medications taken, emergency contact information, and contact information for a family doctor. This personal information is stored in the tag user registration information 321 of the management server 103 as permission-required personal information. The management server 103 judges whether or not disclosure of each piece of permission-required personal information is permitted based on conditions such as the subject of disclosure permission and the disclosure authority level of each piece of personal information. The management server 103 provides the personal information for which disclosure is permitted to the permitted communication terminal 102 as permitted personal information. This makes it possible to provide personal information of the user of the communication tag 101 only to appropriate third parties or supporters who have been registered in advance.

[0025] The acquisition module 213 transmits the terminal user ID of the communication terminal 102 to the management server 103, and if the terminal user ID of the communication terminal 102 satisfies a predetermined condition, acquires the consent personal information of the person requiring support transmitted from the management server 103 (second acquisition section).

[0026] When the proximity of the communication tag 101 is detected, the display module 214 displays information indicating that the communication tag 101 is near the communication terminal 102 . Specifically, when the tag ID is acquired from the communication tag 101, the display module 214 displays object information (e.g., an icon) on the display (output device 205) indicating that the communication tag 101 is present within the short-distance communication range of the communication terminal 102, i.e., that there is a person in need of assistance.

[0027] When an icon indicating the position of the communication tag 101 is displayed on the display, the display module 214 displays the support information acquired from the management server 103 upon receiving a selection operation on the icon.

[0028] Furthermore, the display module 214 displays on the display the permitted personal information acquired from the management server 103. The permitted personal information is personal information registered in correspondence with the communication tag 101, the disclosure of which is permitted. The support information and the permission personal information may be acquired simultaneously as common communication data, or may be acquired as separate communication data.

[0029] The permission personal information includes items registered in advance as personal information by the user, such as name, date of birth, address, telephone number, information on medications taken, emergency contact information, and contact information for the user's primary care doctor. This personal information is extracted by management server 103 based on conditions such as disclosure permission subjects and disclosure authority level of each personal information registered in advance by the user of communication tag 101, and is provided to communication terminal 102.

[0030] The auxiliary storage device 202 includes user identification information 221 and program information 222, and stores information such as programs necessary for the operation of the communication terminal 102. The user identification information 221 stores, for example, identification information (terminal user ID) of the user of the communication terminal 102. The program information 222 stores, for example, a support information management application executed by the execution control module 211 and the like.

[0031] FIG. 3 shows an example of the hardware configuration of the management server 103. The management server 103 of this embodiment is a server computer, and includes a main memory device 301 , an auxiliary memory device 302 , a processor 303 , an input device 304 , an output device 305 , a camera 306 , and a communication control unit 307 .

[0032] The main memory device 301 stores functional programs and functional applications such as an information management module 311, a reception module 312, a determination module 313, and a provision module 314. Each functional element of the main memory device 301 is realized by the processor 303 executing the information management application stored in the auxiliary memory device 302.

[0033] The management server 103 includes an auxiliary storage device 302 that stores support information indicating the support content required for a person in need of support who holds a communication tag 101, the tag ID of the communication tag 101, and personal information in association with each other, a reception module 312 that receives the tag ID obtained from the communication tag 101 from the communication terminal 102, and a provision module 314 that provides support information corresponding to the tag ID to the communication terminal 102, and the provision module 314 provides the personal information to the communication terminal 102 when information identifying the user of the communication terminal 102 satisfies certain conditions.

[0034] The information management module 311 cooperates with the execution control module 211 of the communication terminal 102 to provide web pages and the like of the information management site of the information management system 1. The information management module 311 acquires registration information such as support information and personal information sent from the communication terminal 102, and stores and registers the information in tag user registration information 321.

[0035] The reception module 312 receives registration information of support information and personal information transmitted from the communication terminal 102. The reception module 312 also receives a support information acquisition request transmitted from the communication terminal 102.

[0036] The determination module 313 determines whether or not personal information can be provided by referring to various table information stored in the auxiliary storage device 302, based on the support information acquisition request received by the reception module 312. Details of the determination whether or not personal information can be provided will be described later.

[0037] The providing module 314 transmits the personal information extracted by the determining module 313, that is, the permission personal information permitted to be provided, and the support information to the communication terminal 102.

[0038] The auxiliary storage device 302 stores tag user registration information 321 , permission-required personal information 322 , permission target information 323 , and authority level information 324 . The tag user registration information 321 stores support information, the tag ID of the communication tag 101, and personal information of the person requiring support in association with each other. The tag user registration information 321 stores registration information such as support information and personal information of the tag user (person requiring support) as table information sent from the communication terminal 102. The tag user registration information may be information linked to information on a My Number card, for example.

[0039] The permission subject information 323 stores, in association with each piece of personal information, subject information (permission subject information) indicating the subject (e.g., the group to which the terminal user belongs, the attribute group, an individual terminal user ID, etc.) to whom disclosure of each piece of personal information is permitted. The providing module 314 provides the communication terminal 102 with each piece of personal information associated with the target information when, as a predetermined condition, information identifying the user of the communication terminal 102 (terminal user ID) is included in the permission target information.

[0040] The authority level information 324 stores the authority level (authority level information) required for disclosing each piece of personal information (consent-required personal information) in association with each piece of personal information. The providing module 314 provides each piece of personal information to the communication terminal 102 when, as a predetermined condition, the authority level associated with the terminal user ID of the communication terminal 102 is equal to or higher than the authority level associated with each piece of personal information.

[0041] The provision module 314 may provide the consent-required personal information when, as a specified condition, the terminal user ID of the communication terminal 102 is included in the consent subject information and, further, the authority level associated with the terminal user ID is equal to or higher than the authority level associated with each personal information.

[0042] FIG. 4A is an example of a configuration of case 410. Case 410 is a case for storing communication tag 101, and a help mark designed with a cross mark and a heart mark is affixed to the outer surface of case 410. Usually, a communication tag holder holds communication tag 101 stored in case 410. Case 410 with communication tag 101 stored therein is sometimes called a help mark or a help mark tag.

[0043] FIG. 4B shows an example of the hardware configuration of the communication tag 101. The communication tag 101 includes an antenna 420 and an IC chip 430 , an inlet 440 formed to include the antenna 420 and the IC chip 430 , and a battery 450 .

[0044] The IC chip 430 has a transceiver that functions as a storage unit and a transmission / reception unit, and the storage unit stores, for example, a tag ID that is identification information of the communication tag 101. The transceiver of the IC chip 430 transmits and receives data via the antenna 420 using short-range wireless communication such as Bluetooth (registered trademark) or UWB (Ultra Wide Band). The IC chip 430 receives, for example, a tag ID acquisition request sent from the communication terminal 102 via the antenna 420. The IC chip 430 transmits its own tag ID to the communication terminal 102 based on this tag ID acquisition request.

[0045] Tag holders (Help Mark holders) need some kind of support or consideration. However, even if people around or near a Help Mark holder recognize the Help Mark holder's presence, it is common that they do not know what kind of consideration or support the Help Mark holder needs.

[0046] In this embodiment, the support and consideration required by a person requiring support who is a help mark holder can be displayed on the communication terminal 102, thereby making it possible to inform the user of the communication terminal 102. This enables the user of the communication terminal 102 to provide the necessary support and consideration to the person requiring support.

[0047] The table information will be described below with reference to the drawings. The support information table is table information that stores support information registered in association with each tag ID, and is stored in the tag user registration information 321. FIG. 5A is an example of support information table information 510. For example, support information registered in association with a tag ID “T0002” is stored in the support information table information 510. The “display contents” of the support information table information 510 are information registered as support information (consideration-requiring information) by a tag user. For example, a link to a personal information table corresponding to the tag ID "T0002" is set in the underlined portion T0002 of the record "tag ID: T0002" in the upper left of the support information table information 510. When this link "T0002" is selected, the personal information table of the tag ID (T0002) is read out.

[0048] The personal information table is table information that stores personal information registered in association with each tag ID, and is stored in the tag user registration information 321. FIG. 5B is an example of personal information permission subject table information 520. For example, the personal information permission target table information 520 stores a plurality of personal information registered in association with the tag ID "T0002." Each of these pieces of personal information is permission-required personal information that requires permission (permission) for disclosure. Each piece of permission-required personal information is associated with a permission target group that is set as a permission target. In the following, each piece of information in the column of permission-required personal information in FIG. 5B will be described as separate personal information corresponding to the tag ID "T0002," but the entire column may also be referred to as personal information.

[0049] For example, the personal information permission subject table information 520 indicates that item 02 “Name, Date of Birth, Address” is permitted for disclosure to members and employees of the permission subject groups: medical, fire, police, and government. In addition, for item 05, “Medications,” disclosure is permitted to the “Medical” permission group, and the terminal user ID is individually registered. For example, it is shown that disclosure is permitted to the tag user’s mother’s user ID “U0011” and the tag user’s older sister’s user ID “U0012.”

[0050] FIG. 6 is an example of the target group table information 600. The target group table information 600 is stored in the permission target information 323 in association with the terminal user ID of the communication terminal 102 and the target group to which the terminal user belongs. For example, it is shown that a user with a communication user ID "U0001" belongs to the target group "Medical" (medical institution). Also, it is shown that a user with a communication user ID "U0004" belongs to two target groups, "NPO" and "School".

[0051] The personal information authority level table information is table information that stores personal information registered in correspondence with each tag ID, and is stored in the tag user registration information 321. The personal authority information table information stores a plurality of permission-required personal information corresponding to each tag ID, and each permission-required personal information is stored in association with an authority level indicating the level at which disclosure is permitted. FIG. 7 is an example of a personal information authority level table information 700. The personal information authority level table information 700 is stored in the authority level information 324 of the auxiliary storage device 302 . For example, a plurality of personal information items registered in association with a tag ID "T0002" are stored in the personal information authority level table information 700. For example, authority level C is registered in association with blood type, authority level B with emergency contact information, and authority level A with medications taken. Here, the registered authority levels (A, B, C, D, ...) are, for example, A being the highest, followed by decreasing authority levels of B, C, D, ....

[0052] FIG. 8A is an example of authority level table information 810 for a terminal user. Terminal user ID authority level table information 810 includes the authority level set for each terminal user ID, and is stored in authority level information 324 . In the terminal user ID authority level table information 810, the authority level set for each terminal user ID may be a grade or a numerical value registered by the tag user. For example, the registered authority levels (A, B, C, D, ...) are A being the highest, followed by B, C, D, ..., and so on.

[0053] FIG. 8B is an example of table information 820 of terminal user IDs, attribute groups, and authority levels. Table information 820 of terminal user ID, attribute group, and authority level is table information that combines target group table information 600 in FIG. 6 and terminal user authority level table information 810 in FIG. 8A, and is stored in authority level information 324. The judgment module 313 of the management server 103 may, for example, make a double judgment based on the attribute group and the authority level based on the table information 820 of the terminal user ID, attribute group, and authority level, thereby making a more detailed judgment on the recipients of personal information. For example, if there are terminal users belonging to the attribute group "Administration" with both authority level B and authority level C, it is possible to set disclosure to be permitted for users in the attribute group "Administration" and with authority level B, but not permitted for users in the attribute group "Administration" and with authority level C.

[0054] FIG. 9A is an example of a support information acquisition request 910. The support information acquisition request 910 sent from the communication terminal 102 to the management server 103 includes the terminal user ID of the communication terminal 102 and the tag ID of the communication tag 101. In addition, the support information acquisition request 910 may include authority level information (e.g., (C)) that is preset for the terminal user ID.

[0055] FIG. 9B is an example of communication data 920 that includes assistance information. The communication data 920 includes support information, the terminal user ID of the communication terminal 102, and the tag ID of the communication tag 101. The communication data 920 also includes approved personal information that is personal information that has been determined as being available.

[0056] An information management method using the information management system 1 will now be described. FIG. 10 is an example of a sequence 1000 of an information management method. The information providing method can typically be executed according to steps 1010 to 1090 of an information management method sequence 1000. Steps 1010 to 1090 in this information management method sequence 1000 are processes in which the management server 103 provides the communication terminal 102 with support information and permission personal information of the communication tag 101 holder.

[0057] First, the detection module 212 of the communication terminal 102 detects that the communication terminal 102 and the communication tag 101 have come close enough to be able to communicate at short distances, and the acquisition module 213 transmits a tag ID acquisition request to the communication tag 101 (step 1010).

[0058] When the communication tag 101 receives a tag ID acquisition request from the communication terminal 102 (step 1020), the communication tag 101 transmits its own tag ID to the communication terminal 102 (step 1025). Next, when the acquisition module 213 of the communication terminal 102 acquires the tag ID from the communication tag 101 (step 1030), the display module 214 displays an icon corresponding to the tag ID on the display (step 1040). The execution control module 211 sets the icon to a tap input waiting state.

[0059] Here, when the execution control module 211 receives a tap input on the icon of the displayed tag ID (step 1050: Y), the acquisition module 213 sends a support information acquisition request including the tag ID and the terminal user ID of the communication terminal 102 to the management server 103 (step 1060).

[0060] In the management server 103, when the reception module 312 receives the support information acquisition request from the communication terminal 102, the determination module 313, for example, refers to the support information table information 510 and acquires the support information corresponding to the tag ID. Furthermore, the determination module 313 determines whether or not personal information can be provided (step 1070). Details of the determination of whether or not personal information can be provided will be described below.

[0061] Next, the providing module 314 transmits the assistance information corresponding to the tag ID and the personal information permitted to be provided (permission personal information) to the communication terminal 102 (step 1080). If there is no permission personal information, it notifies that there is no personal information that can be provided or that there is no authority.

[0062] In the communication terminal 102, the display module 214 displays the assistance information and the consent personal information acquired by the acquisition module 213 on the display (step 1090). When notified that there is no personal information available, the display module 214 displays "No personal information" or "No authority".

[0063] At this time, the display module 214 may display only the acquired support information. Furthermore, the display module 214 may display the approved personal information when the execution control module 211 receives a selection input for the support information or the tag ID icon.

[0064] FIG. 11 shows an example of a flow 1100 for determining whether or not personal information can be provided. A flow 1100 for determining whether or not personal information can be provided is a flow showing the process contents in step 1070 of the information management method sequence. In the following description, it is assumed that the support information acquisition request includes a tag ID (T0002) and a terminal user ID (U0003). The receiving module 312 determines whether the received support information acquisition request includes authority level information (step 1110).

[0065] In step 1110, if the authority level information is not included in the support information acquisition request (N), the determination module 313 identifies the attribute group of the terminal user based on the terminal user ID of the support information acquisition request (step 1120).

[0066] At this time, the determination module 313 refers to, for example, the target group table information 600 of the user of the communication terminal 102 in Fig. 6. The determination module 313 identifies the target group to which the terminal user ID (U0003) belongs as administration (for example, administrative staff).

[0067] Next, in step 1130, the determination module 313 extracts permission-required personal information that is permitted for the attribute group "government".

[0068] For example, the judgment module 313 refers to the personal information approval target table information 520 for the tag ID (T0002) and determines that the consent-required personal information for item 02 “Name, date of birth, address, date of birth”, item 03 “Blood type”, and item 04 “Emergency contact information”, which are personal information with the approval target of “Government”, can be provided.

[0069] On the other hand, if it is determined in step 1110 that authority level information (eg, authority level (C)) is included in the support information acquisition request (Y), the determination module 313 acquires the authority level of the user ID (step 1150).

[0070] Next, the determination module 313 refers to the personal information authority level table information 700 based on the acquired authority level (C), and compares the authority levels to determine whether or not the personal information can be provided (step 1160).

[0071] For example, based on the personal information authority level table information 700, the determination module 313 determines that item 01 “tag ID”, item 02 “name, date of birth, address”, and item 03 “blood type” can be provided, which are at authority level (C) or lower, i.e., authority levels (C) and (D). The determination module 313 extracts the approved personal information ("tag ID", "name, date of birth, address", and "blood type") that has been determined to be available (step 1190).

[0072] In the above embodiment, the case has been described in which step 1110 is included to determine whether or not the support information acquisition request includes an authority level, but the present invention is not limited to this.

[0073] That is, the determination module 313 may extract the approved personal information based only on the approval target table information 520 of the personal information, without determining whether or not the acquired support information acquisition request includes the authority level.

[0074] Furthermore, the determination module 313 may refer to the table information 820 of the terminal user ID, attribute group, and authority level to perform a double determination of whether or not to provide consent personal information based on the authority level of the attribute group and the authority level of the terminal user ID. This allows a double determination based on the attribute group and the authority level.

[0075] Next, the display screen of the support information management application in the communication terminal 102 will be described with reference to the drawings. [Display of icon when communication tag is detected] FIG. 12A is an example of a display screen 1210 indicating that the tag ID has been obtained. For example, when the acquisition module 213 of the communication terminal 102 acquires the tag ID of the communication tag 101, the display module 214 displays an icon corresponding to the communication tag 101 and a notification 1215 on the display of the communication terminal 102 as information indicating the presence of a person requiring support.

[0076] FIG. 12B is an example of a display screen 1220 indicating that the tag ID has been obtained. For example, when multiple communication tags are detected, the acquisition module 213 acquires the tag ID of each communication tag. At this time, the display module 214 displays icons and notifications 1225 and 1226 corresponding to each of the different communication tags on the display.

[0077] 12A, the acquisition module 213 transmits a support information acquisition request to the management server 103. Here, the terminal user ID included in the support information acquisition request is, for example, the user ID of a user who is logged in to a support information management application running on the communication terminal 102.

[0078] The display module 214 may display information indicating at least one of the direction in which the communication tag 101 is located, the distance to the communication tag 101, and the position of the communication tag 101, based on the radio wave intensity transmitted from the communication tag 101 and received by the communication terminal 102.

[0079] FIG. 13A is an example of a display screen 1310 indicating that a communication tag has been detected. The display module 214 adjusts the size of the communication tag icon, the display position, and the icon display indicating the distance to the communication terminal 102, for example, based on the radio wave intensity detected from the communication terminal 102, so as to indicate the relative position, direction, and distance of the communication terminal 102 to the communication tag 101.

[0080] For example, the display module 214 displays an arrow icon 1316 indicating the distance and direction to the communication tag 101 on the same screen as the communication tag icon 1315 . For example, in FIG. 13A, arrow icon 1316 indicates that communication tag 101 is located 3 m diagonally forward and to the right of a user looking at the display screen of communication terminal 102 from the front.

[0081] Furthermore, when the detection module 212 detects the proximity of a plurality of communication tags, the display module 214 may display, on the same screen, communication tag icons corresponding to each of the detected plurality of communication tags.

[0082] FIG. 13B is an example of a display screen 1320 indicating that a communication tag has been detected. As shown in FIG. 13B, when different communication tags are detected at a position 3 m diagonally forward to the right and more than 5 m diagonally forward to the left of a user looking directly at the display screen of communication terminal 102, display module 214 displays communication tag icons 1325, 1326 corresponding to the respective communication tags. Furthermore, for example, when the position of the detected communication tag is 5 m or more away from the communication terminal 102, the display module 214 may not display the arrow icon.

[0083] [AR mode display when camera is on] Furthermore, the display module 214 may display at least one of the direction, distance, and position of the communication tag 101 by superimposing it on a landscape screen captured by the camera 206 of the communication terminal 102 . FIG. 14 is an example of a display screen 1400 in the AR display mode.

[0084] The detection module 212 of the communication terminal 102 may adjust the display size and display position of the communication tag icon based on the radio wave intensity output from the communication tag 101, and perform AR (Augmented Reality) display by superimposing it on the scene captured by the camera 206 (AR display mode). For example, a display screen 1400 in AR display mode shows four photographed people, and the display module 214 displays a communication tag icon 1410 on this display screen 1400 at a position that is set based on the radio wave strength from the communication tag 101.

[0085] Furthermore, the display module 214 may display the communication tag icon 1410 by following the movement of the captured person. This makes it possible to reliably identify the holder of the detected communication tag 101 (help mark holder) even when there are multiple people around the communication terminal 102, such as in an evacuation shelter during a disaster, or when multiple people are shown on the display screen.

[0086] [Support information display screen] The display module 214 displays the support information and the permission personal information acquired from the management server 103 on a display screen. FIG. 15 is an example of a display screen 1500 for support information.

[0087] The display module 214 may display the support information acquired from the management server 103 near the communication tag icon 1510 on the display screen. For example, the display module 214 may display the acquired support information 1520 in the form of a speech bubble on the display screen displayed in the AR display mode. This makes it possible to clearly show the correspondence between the photographed communication tag 101 holder and the acquired support information, thereby enabling the terminal user to know with certainty which communication tag holder needs what kind of support.

[0088] Furthermore, when a selection input is made to the communication tag icon 1510 or the support information 1520 displayed on the support information display screen 1500 , the display module 214 may display the approved personal information corresponding to the communication tag 101 . FIG. 16 is an example of a display screen 1600 of the permission personal information. When the display module 214 receives a tap input on the communication tag icon 1510 in FIG. 15, the display module 214 may transition the entire display screen to a display screen on which the approved personal information is displayed, as shown in FIG.

[0089] The approved personal information display screen 1600 displays the approved personal information, such as name, date of birth, address, telephone number, emergency contact information, and family doctor. This personal information is permission personal information extracted by the determination module 313 of the management server 103 from personal information registered in advance by the communication tag user.

[0090] [How to register personal information and support information for tag user information] Next, a method in which a tag user (or his / her supporter) of communication tag 101 uses communication terminal 102 to register personal information, support information, disclosure permission conditions, etc. in management server 103 will be described with reference to the drawings.

[0091] FIG. 17 shows an example of a tag user information registration screen 1700. As shown in FIG. The execution control module 211 displays a tag user information registration screen 1700 of the support information management application based on an application operation on the communication terminal 102. The user of the communication tag 101 uses this tag user information registration screen 1700 to register support information and personal information (personal information requiring permission).

[0092] The execution control module 211 displays a tag user information registration screen 1700 including a user name input field 1710, a password input field 1720, a login button icon 1730, and a new registration button icon 1740 on the display.

[0093] In addition, a communication tag user who has already registered can enter a username and password into the username input field 1710 and password input field 1720, respectively, on the tag user information registration screen 1700 of the app, and tap the login button icon 1730, thereby causing the support information management application to enter a state in which the user has logged in.

[0094] When the tag user taps on the new registration button icon 1740 on the tag user information registration screen 1700, the display module 214 displays a screen for pairing operation of the communication tag 101. FIG. 18A is an example of a screen 1810 for performing pairing operations on a communication tag.

[0095] For example, when a tag holder places the communication tag 101 on the display screen while the pairing operation screen 1810 is displayed, short-range wireless communication is performed between the communication tag 101 and the communication terminal 102, and the execution control module 211 reads the tag ID of the communication tag 101. As a result, the execution control module 211 performs pairing between the communication tag 101 and the application user (pairing operation).

[0096] FIG. 18B shows an example of a pairing completion notification screen 1820 of the communication tag 101. When the tag ID of the communication tag 101 is read by the pairing operation, the display module 214 displays a pairing completion notification screen 1820. At this time, the execution control module 211 also obtains and stores the tag ID of the communication tag 101 that has been read.

[0097] In response to an input operation on the "Next" icon 1840 on the pairing completion notification screen 1820, the display module 214 displays a tag user information registration screen.

[0098] FIG. 19A is an example of a tag user information registration screen 1910. The display module 214 displays, on a tag user information registration screen 1910, text input fields 1911 to 1917 for tag user information and check boxes 1921 to 1926 corresponding to each text input field.

[0099] Check boxes 1921 to 1926 are check boxes for selecting whether text information entered in the corresponding tag user information input field is to be registered as permission-required personal information or as support information. For example, when each check box is checked, the input information in the corresponding tag user information input field is registered as permission-required personal information. When the check box is not checked, the input information in the corresponding text input field is registered as support information.

[0100] For example, in FIG. 19A, check boxes 1921, 1923, 1924, and 1926 are checked, so the name in text input field 1911, the blood type in text input field 1914, the address in text input field 1915, and the emergency contact information in text input field 1917 are registered as personal information requiring permission.

[0101] FIG. 19B is an example of a tag user information registration screen 1940. The display module 214 displays a text input field 1941 for the consideration-required information, and check boxes 1942 to 1946 for specifying the recipients (groups) of the personal information. Furthermore, the display module 214 displays a link object 1947, "To personal information input screen." In response to the selection of the link object 1947, the display module 214 displays the tag user information registration screen 1910 again.

[0102] When each check box for specifying the disclosure destination (group) of personal information is checked, the registered permission-required personal information is set to be discloseable to the corresponding target attribute group. For example, when the check box 1942 for medical or the check box 1944 for firefighting are checked, disclosure of consent-required personal information is permitted for communication terminals whose terminal user ID attribute group is medical or firefighting.

[0103] FIG. 19C is an example of a tag user information registration screen 1960. For example, when link button "to level setting screen" 1918 on tag user information registration screen 1910 is selected, display module 214 displays tag user information registration screen 1960. Display module 214 displays authority level input boxes 1961-1964 and a link button 1965 to tag user information registration screen 1940 on tag user information registration screen 1960.

[0104] In the authority level input boxes 1961 to 1964, for example, A to D can be input or selected as the authority level for disclosing personal information corresponding to each box. When the link button 1965 is selected, the display module 214 displays the tag user information registration screen 1940. On the tag user information registration screen 1960, the tag user can register and set the disclosure authority level (A to D) for each piece of personal information selected by a check box on the tag user information registration screen 1910.

[0105] The support information (information requiring consideration), personal information, and authority level information entered on the above registration screen are sent to the management server 103 by the execution control module 211 and stored in the tag user registration information 321 .

[0106] [Example 2] The information management system 2 according to the second embodiment will be described below. The information management system 2 includes a communication tag 105 and a communication terminal 102. The communication tag 105 and the communication terminal 102 communicate with each other via a network. The network is a wireless communication network, for example, a short-range wireless communication network such as Bluetooth or UWB. The configuration of the information management system 2 differs from the configuration of the information management system 1 in that it does not include a management server 103.

[0107] FIG. 20 shows an example of the hardware configuration of the communication tag 105. The communication tag 105 of the second embodiment includes an antenna 2010, a storage unit 2020, a processing unit 2030, an inlet 2040, and a battery 2050. The storage unit 2020 and the processing unit 2030 are realized by an IC chip.

[0108] The storage unit 2020 stores support information and personal information of the holder of the communication tag 105. It may also store the above-mentioned personal information permission target table information 500 in Fig. 5B and the target group table information 600 in Fig. 6. Furthermore, the storage unit 2020 may store, for example, a list of terminal user IDs for which provision of personal information is permitted.

[0109] The processing unit 2030 performs transmission and reception communication via the antenna 2010, and performs processing to accept a terminal user ID from the communication terminal 102. The processing unit 2030 also performs processing to extract permission personal information to be provided to the communication terminal 102 from the personal information of the holder of the communication tag 105, and processing to provide the extracted permission personal information to the communication terminal 102.

[0110] For example, the communication terminal 102 is a mobile terminal such as a smartphone, a tablet, a notebook computer, etc. The communication terminal 102 of this embodiment includes a main memory device 201, an auxiliary memory device 202, a processor 203, an input device 204, an output device 205, a camera 206, and a communication control unit 207, similar to the first embodiment.

[0111] The information management method of the second embodiment will be described below. FIG. 21 is an example of a sequence 2100 of an information management method.

[0112] First, when detection module 212 of communication terminal 102 detects that communication terminal 102 and communication tag 105 are in such a proximity that they can communicate with each other at short distances, acquisition module 213 transmits a tag ID acquisition request to communication tag 105 (step 2110).

[0113] When the communication tag 105 receives a tag ID acquisition request from the communication terminal 102 (step 2115), the processing unit 2030 transmits its own tag ID to the communication terminal 102 (step 2120). Next, when the display module 214 of the communication terminal 102 acquires the tag ID sent from the communication tag 105 (step 2130), it displays an icon corresponding to the tag ID on the display of the communication terminal 102 (step 2140).

[0114] Here, when the execution control module 211 receives a tap input on the displayed icon (step 2150: Y), the acquisition module 213 transmits a support information acquisition request to the communication tag 105 (step 2160). The support information acquisition request transmitted at this time includes, for example, the tag ID of the communication tag 105 and the terminal user ID of the communication terminal 102.

[0115] When the processing unit 2030 of the communication tag 105 receives the support information acquisition request, it acquires the support information stored in the memory unit 2020. Furthermore, the processing unit 2030 extracts the approved personal information by referring to the personal information approval target table information 520 and the target group table information 600 stored in the memory unit 2020 based on the terminal user ID of the support information acquisition request (step 2170).

[0116] Next, the processing unit 2030 of the communication tag 105 transmits the support information and the extracted permission personal information to the communication terminal 102 (step 2180). In the communication terminal 102, the display module 214 displays the assistance information and the approved personal information acquired from the communication tag 105 on the display (step 2190).

[0117] At this time, the display module 214 may display only the support information on the display. Furthermore, when a selection input by the terminal user for the displayed support information or tag ID icon is received, the display module 214 may display the permission personal information on the display.

[0118] In the second embodiment, the support information and the personal information requiring permission, which are stored in advance in the communication tag, can be provided to the communication terminal 102 and displayed on the communication terminal 102 . Therefore, even if a wide area network such as the Internet is not available during a disaster such as an earthquake, it is possible to provide support information and personal information required by the communication tag holder to the communication terminals 102 of pre-registered terminal users that are within the vicinity of the communication tag 105 or the range of short-range wireless communication.

[0119] [Example 3] The information management system 3 according to the third embodiment will be described below. The information management system 3 has the same hardware configuration as that in the second embodiment. The third embodiment differs from the second embodiment in that the main storage device 201 of the communication terminal 102 newly includes a display determination module (not shown). Furthermore, the third embodiment differs from the second embodiment in that the communication tag 105 stores display permission condition information, which is condition information for displaying each piece of personal information.

[0120] The information management method of the third embodiment will be described below. FIG. 22 is an example of a sequence 2200 of an information management method.

[0121] When the detection module 212 of the communication terminal 102 detects that the communication terminal 102 and the communication tag 101 have come close enough to be able to communicate at short distances, the acquisition module 213 transmits an assistance information acquisition request to the communication tag 105 (step 2210).

[0122] When the processing unit 2030 of the communication tag 105 receives a request to obtain support information (step 2120), it transmits to the communication terminal 102 (2230) the support information and personal information registered in correspondence with its own tag ID, as well as display permission condition information as conditions for displaying the personal information.

[0123] When the acquisition module 213 of the communication terminal 102 acquires the support information, personal information, and display permission condition information (step 2240), the display determination module 215 determines whether or not each personal information can be displayed on the display based on the display permission condition information, and extracts the personal information that is permitted to be displayed (step 2250).

[0124] Here, the display permission condition information may be, for example, the personal information permission target table information 520 in FIG. 5B and the target group table information 600 in FIG. The display module 214 displays on the display the acquired support information and the approved personal information extracted based on the personal information approved target table information 520 and the target group table information 600 (step 2260). At this time, the display module 214 does not display on the display of the communication terminal 102 the personal information that is determined not to have approval for display on the communication terminal 102.

[0125] In the third embodiment, assistance information and personal information requiring permission, which are stored in advance in a communication tag, are provided to a communication terminal, and the communication terminal determines whether or not the personal information can be displayed. For this reason, in this embodiment 3, even if a wide area network such as the Internet is unavailable during a disaster such as an earthquake, it is possible to display the approved personal information on the communication terminal of a previously authorized terminal user at a communication terminal within the vicinity of the communication tag or within the range of short-range wireless communication.

[0126] The present invention is not limited to the above-described embodiments, and includes various modified examples. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0127] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0128] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. The above-described embodiments disclose at least the configurations described in the claims. [Explanation of symbols]

[0129] 1...information management system, 101...communication tag, 102...communication terminal, 103...management server

Claims

1. A server, A storage unit that stores support information indicating the support content required for a person requiring support who holds a communication tag, tag identification information of the communication tag, and personal information of the person requiring support in association with each other; a reception unit that receives the tag identification information acquired from the communication tag from a communication terminal; a providing unit that provides the support information corresponding to the received tag identification information to the communication terminal, The providing unit provides the personal information to the communication terminal when information identifying a user of the communication terminal satisfies a predetermined condition. A server comprising:

2. The storage unit further stores, in association with each of the personal information, target information indicating a target to which the disclosure of each of the personal information is permitted; The providing unit provides the communication terminal with each of the personal information associated with the target information when the target information includes information that identifies a user of the communication terminal as the predetermined condition.

2. The server according to claim 1 .

3. The storage unit further stores an authority level required for disclosing each of the personal information in association with each of the personal information; When an authority level associated with information identifying a user of the communication terminal is equal to or higher than an authority level associated with each of the personal information, the providing unit performs the following as the predetermined condition: The individual pieces of personal information are provided to the communication terminal.

2. The server according to claim 1 .

4. The storage unit further stores, in association with each of the personal information, target information indicating a target to which disclosure of each of the personal information is permitted, and in association with each of the personal information, an authority level required for disclosure of each of the personal information; The providing unit provides each of the personal information to the communication terminal when, as the predetermined condition, the target information includes information for identifying a user of the communication terminal, and further, an authority level associated with the information for identifying the user of the communication terminal is equal to or higher than an authority level associated with each of the personal information.

2. The server according to claim 1 .

5. A communication terminal, a first acquisition unit that acquires tag identification information from a communication tag; A second acquisition unit that transmits the acquired tag identification information to a server and acquires support information corresponding to the tag identification information, the support information indicating the support content required for the support-requiring person holding the communication tag, from the server; A display unit that displays the acquired support information; A communication terminal comprising:

6. When the tag identification information is acquired from the communication tag, the display unit further displays information indicating the presence of the person requiring support.

6. The communication terminal according to claim 5,

7. The display unit further displays at least one of a direction in which the communication tag of the person requiring support is located, a distance to the communication tag, and a position of the communication tag, which are specified based on the radio wave intensity transmitted from the communication tag.

6. The communication terminal according to claim 5,

8. The display unit displays at least one of the direction, the distance, and the position by superimposing it on a landscape image captured by a camera of the communication terminal.

8. The communication terminal according to claim 7,

9. The display unit further displays an object indicating the position, and when the object is selected, displays the acquired support information.

9. The communication terminal according to claim 8,

10. The second acquisition unit transmits information identifying a user of the communication terminal to the server, and when the information identifying the user of the communication terminal satisfies a predetermined condition, further acquires personal information of the support-requiring person from the server; The display unit further displays the acquired personal information.

6. The communication terminal according to claim 5,

11. 1. A computer-implemented information management method, comprising: Support information indicating the support content required for the support-requiring person carrying the communication tag, tag identification information of the communication tag, and personal information of the support-requiring person are stored in association with each other; receiving the tag identification information acquired from the communication tag from a communication terminal; The support information corresponding to the received tag identification information and the personal information are provided to the communication terminal when information for identifying the user of the communication terminal satisfies a predetermined condition.

23. An information management method comprising:

12. A program for causing a server to execute each of the processing steps according to claim 11.

Images