Information processing methods, programs, information processing systems, and servers

Abstract

This provides an information processing method that allows for group configuration and unified service use while guaranteeing the identities of multiple individuals. [Solution] An information processing method performed by at least one processor, comprising: controlling the reading of basic group member information from the identification card of a group member belonging to a group to which the terminal user belongs; acquiring group member input information, which is information about a group member obtained by an input operation to the terminal's input section; creating a group information record by adding the group member personal information, which includes the group member basic information and the group member input information, to the user personal information, which includes information generated by reading the user's basic information from the user's identification card; transmitting the group information record to an external device; and storing the group information record in the terminal's memory.

Description

Technical Field

[0001] The present disclosure relates to an information processing method, a program, an information processing system, and a server.

Background Art

[0002] Conventionally, in order to ensure secure transactions using blockchain technology, devices and methods for using biometric technology are known. This device uses biometric authentication to confirm that the user of the service and the person in whose name the digital wallet is registered are the same when the user uses the digital wallet (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The system of Patent Document 1 does not assume that a plurality of persons such as family members use the service in a group. Therefore, there is room for improvement in setting up a group and using the service while guaranteeing the identities of the members within the group.

[0005] The present disclosure provides an information processing method, a program, an information processing system, and a server that can perform group setting and batch service use while guaranteeing the identities of multiple persons.

Means for Solving the Problems

[0006] One aspect of the present disclosure is an information processing method performed by at least one processor, comprising: controlling the reading of basic group member information from the identification card of a group member belonging to a group to which the user of the terminal belongs; acquiring group member input information, which is information about the group member obtained by an input operation to the input unit of the terminal; creating a group information record by adding the group member personal information, which includes the group member basic information and the group member input information, to user personal information, which includes information generated by reading the user's basic information from the user's identification card; transmitting the group information record to an external device; and storing the group information record in the memory of the terminal. [Effects of the Invention]

[0007] According to this disclosure, the service can be used while guaranteeing the identity of members within the group. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example configuration of the DIW system in the first embodiment of this disclosure. [Figure 2A] Diagram showing an example configuration of a user terminal. [Figure 2B] A diagram showing an example of the functional configuration of a user terminal. [Figure 3A] Diagram showing an example configuration of a DIW server. [Figure 3B] A diagram showing an example of the functional configuration of a DIW server. [Figure 4] Diagram showing an example configuration of a terminal in an evacuation shelter. [Figure 5] Diagram showing an example of a local government server configuration. [Figure 6] A diagram showing an example of a service master list. [Figure 7] A diagram showing an example of a user's personal information record. [Figure 8] A diagram showing an example of an integrated personal information master list. [Figure 9A]Sequence diagram (part 1) showing an example of the operation when registering family information by the DIW system [Figure 9B] Sequence diagram (part 2) showing an example of the operation when registering family information by the DIW system [Figure 9C] Sequence diagram (part 3) showing an example of the operation when registering family information by the DIW system [Figure 10] Diagram showing an example of a family information record [Figure 11] Diagram showing an example of an integrated family information master list [Figure 12A] Diagram (part 1) showing an example of the screen transition of the screen displayed on the user terminal when registering family settings [Figure 12B] Diagram (part 2) showing an example of the screen transition of the screen displayed on the user terminal when registering family settings [Figure 13] Diagram showing an example of the screen transition when checking the personal information of each family member held on the user terminal [Figure 14A] Sequence diagram (part 1) showing an example of the operation when setting up the cooperation between the family and the service by the DIW system [Figure 14B] Sequence diagram (part 2) showing an example of the operation when setting up the cooperation between the family and the service by the DIW system [Figure 15] Diagram showing an example of an available service list [Figure 16] Diagram showing an example of a list of services with cooperation consent [Figure 17] Diagram showing an example of a list of services with family cooperation [Figure 18] Sequence diagram showing the first example of the operation of batch personal confirmation and registration confirmation of evacuee information during evacuation [Figure 19] Sequence diagram showing the continuation of the first example of the operation of batch personal confirmation and registration confirmation of evacuee information during evacuation [Figure 20] Sequence diagram showing the second example of the operation of batch personal confirmation and registration confirmation of evacuee information during evacuation [Figure 21] Diagram showing an example of evacuee information [Figure 22] Diagram showing an example of log information [Figure 23A] Figure (1) shows an example of screen transitions displayed on the evacuation center terminal when using the service. [Figure 23B] Figure (2) showing an example of screen transitions displayed on the evacuation center terminal when using the service. [Modes for carrying out the invention]

[0009] The embodiments will be described in detail below, with reference to the drawings as appropriate. However, unnecessary details may be omitted. For example, detailed explanations of already well-known matters or redundant explanations of substantially identical configurations may be omitted. This is to avoid the following explanation becoming unnecessarily verbose and to facilitate understanding by those skilled in the art. The accompanying drawings and the following explanation are provided to enable those skilled in the art to fully understand this disclosure and are not intended to limit the subject matter described in the claims.

[0010] (First Embodiment) Figure 1 shows an example configuration of a Digital Identity Wallet (DIW) system 5 in a first embodiment of the present disclosure. The DIW system 5 includes a user terminal 10, a DIW server 20, a shelter terminal 30, and a local government server 40. At least some of the devices of the user terminal 10, DIW server 20, shelter terminal 30, and local government server 40 may be connected to each other via a network so that they can communicate with one another, or at least some of the devices may be directly connected to each other so that they can communicate with one another. In Figure 1, as an example, the user terminal 10 is connected to the DIW server 20 and the shelter terminal 30 so that they can communicate with each other, the DIW server 20 is connected to the shelter terminal 30 and the local government server 40 so that they can communicate with each other, and the local government server 40 is connected to the shelter terminal 30 so that they can communicate with each other.

[0011] The DIW server 20 and the local government server 40 may each be configured as an on-premise server device or as a cloud-based system on a network. The DIW server 20 and the local government server 40 may each be configured as a single computer or as a distributed system across multiple computers. Furthermore, at least one computer may combine at least some of the functions of the user terminal 10, the DIW server 20, the evacuation center terminal 30, and the local government server 40.

[0012] User terminal 10 is a terminal owned by a user who enjoys various services. User terminal 10 can handle personal information about the user, as well as personal information about individuals belonging to the user's family (also referred to as family members).

[0013] The DIW server 20 performs processing related to the digital ID wallet (DIW). The DIW server 20 manages the personal information of each user obtained from one or more user terminals 10, as well as the personal information of one or more family members.

[0014] The evacuation center terminal 30 is a terminal installed in an evacuation center. An evacuation center is a place where people can take refuge in the event of a disaster such as an earthquake or typhoon. One or more evacuation center terminals 30 may be installed in one evacuation center. The evacuation center terminal 30 can provide evacuation center services to users and their families.

[0015] The local government server 40 is a server that processes information related to the local government. The local government server 40 can be installed in any location, for example, within or outside the local government. The local government server 40 can provide various administrative services offered by the local government. The local government server 40 manages the evacuation center terminals 30.

[0016] User H1 is the person who possesses user terminal 10. User H1 is, for example, a representative within the family to which the user belongs. Note that family is just one example of a group composed of multiple people, and other groups may also be used. For example, several people who have a trusting relationship (e.g., staff and care recipients of a care facility) may be considered one group. In the case of a tour, the tour leader may be the group representative, and the participants in the tour may be group members, and the group may consist of the participants and the tour leader.

[0017] In Figure 1, there is a family consisting of user H1 and family members H2-H5. User H1 possesses an identification card CD1, for example, user H1's My Number Card. Family member H2 possesses an identification card CD2, for example, family member H2's My Number Card. Family member H3 possesses an identification card CD3, for example, family member H3's My Number Card. Family member H4 possesses an identification card CD4, for example, family member H4's My Number Card. Family member H5 possesses an identification card CD5, for example, family member H5's My Number Card. For example, user H1 and family member H2 are adults, while family members H3-H5 are children (minors). The My Number Card is just one example of an identification card. Note that the number of family members is not limited to four.

[0018] Figure 2A shows an example configuration of the user terminal 10.

[0019] The user terminal 10 comprises a processor 11, memory 12, imaging unit 13, display operation unit 14, network communication unit 15, and short-range wireless communication unit 16.

[0020] The processor 11 may be configured using, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or a Graphical Processing Unit (GPU). The processor 11 may also be configured using various integrated circuits (for example, a Large Scale Integration (LSI) or a Field Programmable Gate Array (FPGA)). The processor 11 implements various functions by executing programs held in memory 12. The processor 11 comprehensively controls each part of the user terminal 10 and performs various processes.

[0021] Memory 12 includes, for example, Random Access Memory (RAM) or Read Only Memory (ROM). Memory 12 may include volatile memory or non-volatile memory. Memory 12 may include, for example, a Hard Disk Drive (HDD), Solid State Drive (SSD), optical disc, SD card, etc. Memory 12 may also be an external storage medium and may be detachable from the user terminal 10. Memory 12 stores various data, information, or programs.

[0022] Memory 12 may, for example, hold information related to a digital ID wallet. The digital ID wallet may hold various digital certificates. The digital certificate may include user personal information, which is personal information about user H1. User personal information may include, for example, basic user information obtained from user H1's identification card CD1, and may also include other information. User personal information may also include information about user H1's facial image. In addition, the digital ID wallet may hold digital certificates of family members along with user H1's digital certificate. The digital certificates of family members may include family member personal information, which is personal information about the family member. Family member personal information may include, for example, basic family member information obtained from the family member's identification cards CD2 to CD5 for each family member, and may also include other information. Family member personal information may also include information about the family member's facial image.

[0023] The imaging unit 13 captures an image of the subject. The subject may include, for example, the face of user H1 or the faces of family members H2 to H5, and may also include other objects.

[0024] The display operation unit 14 accepts input operations for various types of data and information, and displays various types of data and information. The display operation unit 14 is, for example, a touch panel. The display operation unit 14 may be operated by user H1, family members H2-H5, or other persons. The display by the display operation unit 14 may be confirmed by, for example, user H1, family members H2-H5, or other persons.

[0025] The display operation unit 14 accepts, for example, general operations of the user terminal 10 and operations related to the execution of applications. The display operation unit 14 displays, for example, screens used in service applications 110 (see Figure 2B) and DIW applications 120 (see Figure 2B), digital certificates, facial image data, etc.

[0026] The display operation unit 14 may be divided into a display unit that displays various data and information, and an operation unit (input unit) that accepts input operations for inputting various data and information. The operation unit may include various buttons, keys, a mouse, a keyboard, a touch panel, a microphone, or other input devices. The display unit may include, for example, a liquid crystal display or an organic EL display.

[0027] The network communication unit 15 communicates various data or information with external devices (e.g., DIW server 20, evacuation center terminal 30) via a network according to a wired or wireless communication method. The communication method used by the network communication unit 15 may include, for example, a Local Area Network (LAN), a Wide Area Network (WAN), etc.

[0028] The short-range wireless communication unit 16 performs short-range wireless communication with an external communication medium (e.g., an identification card). The short-range wireless communication unit 16 may perform short-range wireless communication using, for example, an NFC antenna. NFC stands for Near Field Communication.

[0029] The user terminal 10 may communicate using communication units other than the network communication unit 15 and the short-range wireless communication unit 16. For example, the communication method used by this communication unit may include a mobile phone network or a power line communication method.

[0030] Figure 2B shows an example of the functional configuration of the user terminal 10.

[0031] The various functions implemented by the processor 11 include, for example, a service application (also referred to as a service app 110) that performs processing related to various services, a DIW application (also referred to as a DIW app 120) that performs processing related to a digital ID wallet, and a data management unit 130 that manages various types of data. The services here include, for example, various services for evacuation shelters, and may also include other services.

[0032] The DIW app 120 has the following functions: a service master list acquisition unit 121, a user personal information acquisition unit 122, an available service extraction unit 123, a service provision condition output unit 124, a linkage consent acquisition unit 125, a face matching unit 126, an information provision request reception unit 127, a provided information extraction output unit 128, and a provided information history output unit 129.

[0033] The service master list acquisition unit 121 acquires the service master list. The service master list contains information regarding the cooperation between various services and the DIW server 20.

[0034] The user personal information acquisition unit 122 acquires user personal information. User personal information includes personal information relating to user H1. User personal information includes, for example, the basic user information contained in user H1's identification card CD1 and the input information entered via the display operation unit 14 (i.e., manually entered information). User personal information may also include attribute information relating to the user's attributes (user attribute information) based on the basic user information and the manually entered information.

[0035] The available service extraction unit 123 extracts services that are available to user H1 and family members from the service master list. The available services are those for which the personal information of user H1 and family members meets the prescribed service provision conditions.

[0036] The service provision conditions output unit 124 outputs (e.g., displays, transmits) information regarding the service provision conditions. The service provision conditions are the conditions for providing services to users and family members, and include, for example, the terms of use of the service and information on the items of personal information to be acquired. One example of a service provision condition is that the user resides in a specific residential area.

[0037] The cooperation consent acquisition unit 125 acquires information regarding consent to the cooperation between the service provider server (service server, e.g., local government server 40) that provides the service (e.g., evacuation shelter service) and the family information (also referred to as family information) provided by the DIW server 20 (also referred to as cooperation consent information). Family information includes user personal information and family member personal information of each family member.

[0038] The face matching unit 126 matches the faces of user H1 and family members H2-H5 captured by the imaging unit 13. For example, the face matching unit 126 matches faces for each person by comparing the face images of user H1 and family members H2-H5 captured by the imaging unit 13 with the face images of user H1 and family members H2-H5 included in the family information. Note that requests for information provision may be made at a different time than described above.

[0039] Family information includes user personal information and family member personal information. Family member personal information exists for each family member. For each family member, family member personal information includes the information contained in each of the identification cards CD2 to CD5 of family members H2 to H5 (i.e., identification information, family member basic information) and input information entered via the display operation unit 14 (i.e., manually entered information). Family member personal information may include attribute information regarding the attributes of the family member (family member attribute information). Attribute information may include information based on family member basic information or manually entered information, such as age, whether the person is an adult or a minor, and residential area.

[0040] The information request reception unit 127 receives requests for various types of information. For example, when using the service, the information request reception unit 127 receives requests for information such as family information and evacuee information from the service application 110 or the evacuation center terminal 30. Note that requests for information may be made at times other than those described above.

[0041] The provided information extraction and output unit 128 extracts information such as family information and evacuee information (provided information) provided when family members agree to link with the service or when using the service. The provided information extraction and output unit 128 outputs the extracted provided information to the service application 110 or to the evacuation center terminal 30 which acts as a service terminal (for example, by transmission). The provided information may be extracted and output at a different time than described above.

[0042] The provided information history output unit 129 identifies the service to which the provided information was provided, for example, when the service is first linked or when the service is used, generates information as a history of the provided information (also referred to as provision history information), and outputs (e.g., transmits) it to the DIW server 20. Note that the provision history information may be generated and output at a different time than described above.

[0043] The Data Management Unit 130 manages data and information related to the service master list. This management includes, for example, acquisition, generation, updating, and storage. The Data Management Unit 130 manages data and information related to user H1's user personal information record. The Data Management Unit 130 manages data and information related to family information records. Family information records are records that contain family information. The Data Management Unit 130 manages data and information related to the available services list, which includes information on services available to user H1 and family members H2-H5. The Data Management Unit 130 manages data and information related to the consented services list, which users H1 and family members H2-H5 have agreed to be linked to.

[0044] The service master list may be pre-stored in the data management unit 130, i.e., memory 12, and may be updated as appropriate. User personal information records may be pre-stored in the data management unit 130, i.e., memory 12, and may be updated as appropriate.

[0045] Figure 3A shows an example configuration of the DIW server 20. Note that in Figure 3A, the explanation of configurations similar to those of the user terminal 10 shown in Figure 2A is omitted or simplified.

[0046] The DIW server 20 comprises a processor 21, a communication unit 22, memory 23, and storage 24.

[0047] The processor 21 implements various functions by executing programs stored in memory 23. The processor 21 comprehensively controls each part of the DIW server 20 and performs various processes.

[0048] The communication unit 22 communicates various data or information with external devices (e.g., user terminal 10, evacuation center terminal 30, local government server 40) according to a wired or wireless communication method. The communication method used by the communication unit 22 may include, for example, a Local Area Network (LAN), Wide Area Network (WAN), a mobile phone network, or power line communication.

[0049] Memory 23 includes, for example, RAM or ROM. Memory 23 may include volatile memory or non-volatile memory. Memory 23 stores various data, information, or programs.

[0050] The storage 24 includes, for example, an HDD, SSD, optical disc, or SD card. The storage 24 may also be an external storage medium and may be detachable from the DIW server 20. The storage 24 stores various data, information, or information from various lists.

[0051] Figure 3B shows an example of the functional configuration of the DIW server 20.

[0052] The various functions implemented by the processor 21 include, for example, a service provision condition notification unit 211, a service master list management unit 212, an ID generation unit 213, an integrated personal information master list management unit 214, an integrated family information master list management unit 215, a family-linked service list management unit 216, a face matching unit 217, an information provision request reception unit 218, a provided information extraction and output unit 219, a provided information history management unit 220, and a data management unit 230.

[0053] The service provision conditions notification unit 211 notifies an external device (e.g., user terminal 10) of the service provision conditions.

[0054] The Service Master List Management Unit 212, together with the Data Management Unit 230, manages and maintains the service master list. This management includes, for example, retrieval, generation, updating, and storage.

[0055] The ID generation unit 213 generates IDs as various types of identification information. For example, the ID generation unit 213 generates a service-specific family ID that is defined for each service and each family.

[0056] The Integrated Personal Information Master List Management Department 214, together with the Data Management Department 230, manages and maintains the Integrated Personal Information Master List. The Integrated Personal Information Master List contains information on the personal information records of one or more users H1 (i.e., family representatives).

[0057] The Integrated Family Information Master List Management Unit 215, together with the Data Management Unit 230, manages and maintains the Integrated Family Information Master List. The Integrated Family Information Master List contains information on family information records for one or more families.

[0058] The Family Linked Service List Management Unit 216, together with the Data Management Unit 230, manages and maintains the Family Linked Service List. The Family Linked Service List contains information on agreed-upon service lists for one or more families.

[0059] The face matching unit 217 matches the acquired face of user H1. The face matching unit 217 matches the face by, for example, comparing the face image of user H1 captured by one of the imaging units with the face image of user H1 stored in the personal information record or the integrated family information master list.

[0060] The information request receiving unit 218 receives requests for various types of information via the communication unit 22. For example, when using the service, the information request receiving unit 218 receives requests for information such as family information and evacuee information from the service application 110 on the user terminal 10 or from the evacuation center terminal 30, etc. However, requests for information may be made at times other than those described above.

[0061] The provided information extraction and output unit 219 extracts information such as family information and evacuee information (provided information) provided when family members agree to link with the service or when using the service. The provided information extraction and output unit 219 outputs (e.g., transmits) the extracted provided information to the service application 110 on the user terminal 10, or to the evacuation center terminal 30 which acts as a service terminal. The provided information may be extracted and output at a different time than described above.

[0062] The provided information history management unit 220 identifies the service to which the provided information was provided, for example, when the service is first linked or when the service is used, and generates and manages information as a history of the provided information (provided information). One of the purposes of retaining the provided information history is to comply with the Personal Information Protection Act and to allow users and family members to check which information they have provided to which service when they want to. The provided information history management unit 220 may also acquire and manage the provided information history information generated by the user terminal 10 via the communication unit 22. The provided information history information may be generated and output at a different time than described above. The provided information history information may be stored, for example, in the family linked service list.

[0063] Data Management Department 230 manages the service master list. Data Management Department 230 manages the integrated personal information master list. Data Management Department 230 manages the integrated family information master list.

[0064] Figure 4 shows an example of the configuration of the evacuation center terminal 30. In Figure 4, the explanation of configurations similar to those of the user terminal 10 shown in Figure 2A is omitted or simplified.

[0065] The evacuation center terminal 30 includes a processor 31, memory 32, imaging unit 33, display operation unit 34, network communication unit 35, and short-range wireless communication unit 36.

[0066] The processor 31 implements various functions by executing programs stored in the memory 32. The processor 31 comprehensively controls each part of the evacuation center terminal 30 and performs various processes. The processor 31 also functions as a terminal ID generation unit 311. The terminal ID generation unit 311 generates an evacuation center terminal ID that identifies the evacuation center terminal 30 and stores it in the memory 32.

[0067] Memory 32 stores various data, information, or programs. Memory 32 may be an external storage medium and may be detachable from the evacuation center terminal 30.

[0068] The imaging unit 33 captures an image of the subject. The subject may include the face of user H1, or the faces of other people (e.g., family members H2-H5), and may also include other objects.

[0069] The display operation unit 34 accepts input operations for various types of data and information, and displays various types of data and information. The display operation unit 34 may be operated by user H1 or other persons (e.g., family members H2-H5). The display by the display operation unit 34 may be confirmed, for example, by user H1 or other persons (e.g., family members H2-H5).

[0070] The display operation unit 34 accepts, for example, general operations of the evacuation center terminal 30 and operations related to the execution of applications. The display operation unit 34 displays, for example, screens used in applications, facial image data, etc.

[0071] The network communication unit 35 communicates various data or information, etc., with external devices (for example, user terminal 10, DIW server 20, local government server 40) via the network according to a wired or wireless communication method.

[0072] The short-range wireless communication unit 36 ​​performs short-range wireless communication with an external communication medium (for example, the identification card of a person who has evacuated).

[0073] Furthermore, the evacuation center terminal 30 may communicate using communication units other than the network communication unit 35 and the short-range wireless communication unit 36. For example, the communication method used by this communication unit may include a mobile phone network or a power line communication method.

[0074] Figure 5 shows an example configuration of the local government server 40. In Figure 5, the explanation of configurations similar to those of the DIW server 20 shown in Figure 3A is omitted or simplified.

[0075] The local government server 40 comprises a processor 41, a communication unit 42, memory 43, and storage 44.

[0076] The processor 41 implements various functions by executing programs stored in memory 43. The processor 41 comprehensively controls each part of the local government server 40 and performs various processes. The processor 41 has the functions of an evacuee information management unit 411 and an authenticity determination unit 412. The evacuee information management unit 411 manages evacuee information. The authenticity determination unit 412 determines the authenticity of various types of information (for example, information about family members).

[0077] The communication unit 42 communicates various data or information with external devices (e.g., DIW server 20, evacuation center terminal 30) according to a wired or wireless communication method.

[0078] Memory 43 stores various data, information, or programs. Storage 44 stores various data, information, or information from various lists.

[0079] Next, we will describe the various lists provided by the DIW system 5.

[0080] Figure 6 shows an example of a service master list L1.

[0081] The Service Master List L1, for example, stores and associates the following information for each service provided: a service ID that identifies the service, the service content, the service provider ID (e.g., local government ID), the terms of use, the items of personal information necessary for service provision, the service provision conditions, the service linkage date, and the service provision period. The information in the terms of use includes, for example, URL and file name information. The service provision conditions are the conditions that the items of personal information must satisfy. The Service Master List L1 may also include other information.

[0082] The service master list L1 managed by the data management unit 130 of the user terminal 10 and the service master list L1 managed by the data management unit 230 of the DIW server 20 may be the same. The service master list L1 is generated when various services are linked with the DIW server 20. The linked service master list L1 is registered in the memory 12 of the user terminal 10 and in the memory 23 or storage 24 of the DIW server.

[0083] Figure 7 shows an example of a user personal information record R1.

[0084] User personal information record R1 stores, for example, a user ID that identifies user H1, along with the following information: name, address, date of birth, gender, facial image, phonetic spelling of name (full and last name), mobile phone number, email address, password, age, information indicating whether the user is 20 years of age or older (adult), and residential area. The user ID is, for example, an ID assigned by the DIW server 20. The name, address, date of birth, gender, and facial image are information (basic information) contained in the IC chip of the identification card CD1 (for example, a My Number Card). The phonetic spelling of name (full and last name), mobile phone number, email address, and password are, for example, manually entered information. The age, whether the user is 20 years of age or older, and residential area are user attribute information derived from the user's basic information or manually entered information by the DIW application 120. Note that user personal information record R1 may also include other information. Manually entered information may include the relationship to user H1 (e.g., self, father, mother, child).

[0085] Figure 8 shows an example of the Integrated Personal Information Master List L2.

[0086] The integrated personal information master list L2 aggregates and stores the personal information records of each user H1. For example, in case only attribute information is presented when using the service, the attribute information of user H1 may be extracted in advance from the integrated personal information master list L2.

[0087] The Integrated Personal Information Master List L2, for example, stores and associates the following information for each user: User ID, Name, Name (Phonetic spelling), Address, Date of Birth, Gender, Facial Image, Mobile Phone Number, Email Address, Password, Age, and Residential Area. The Integrated Personal Information Master List L2 may also include other information.

[0088] The service master list L1 may be pre-held in the data management unit 130, i.e., the memory 12, of the user terminal 10 and may be updated as appropriate. Also, the service master list L1 may be pre-held in the data management unit 230, i.e., the memory 23 or the storage 24, of the DIW server 20 and may be updated as appropriate. The user personal information record R1 may be pre-held in the data management unit 130, i.e., the memory 12, of the user terminal 10 and may be updated as appropriate. The integrated personal information master list L2 may be pre-held in the data management unit 230, i.e., the memory 23 or the storage 24, of the DIW server 20 and may be updated as appropriate.

[0089] <Operation of the DIW System> Next, the operation of the DIW system 5 will be described.

[0090] FIGS. 9A, 9B, and 9C are sequence diagrams showing operation examples at the time of registering family information by the DIW system 5. In the DIW system 5 here, the user personal information record R1, the integrated personal information master list L2, and the service master list L1 are registered (held) in advance.

[0091] First, the user terminal 10 receives an input from the user H1 by the display operation unit 14, selects the DIW application (step S101), and the DIW application 120 starts the DIW application (step S102). The DIW application 120 causes the display operation unit 14 to display the menu screen of the DIW application 120 (step S103). The display operation unit 14 selects the family setting menu on the menu screen (step S104).

[0092] When the Family Settings menu is selected, the DIW app 120 displays information on the display operation unit 14 explaining the purpose and situations (also referred to as the terms of use) for using Family Settings (registration of family information) (step S105). The display operation unit 14 accepts input from user H1 and family members H2-H5 confirming the above explanatory information and agreeing to the terms of use for Family Settings (consent information) (step S106). Once the DIW app 120 obtains the consent information from the display operation unit 14, it displays a guidance screen for Family Settings on the display operation unit 14 (step S107).

[0093] Specifically, the DIW app 120 displays information on the personal information items of family members that are acquired by the DIW server 20, information on the purpose of use of these items, and information prompting user H1 or family members H2-H5 to give their consent to the use of these items. The personal information items acquired by the DIW server 20 are, for example, the personal information items necessary for providing the service, which are included in the service master list L1. The DIW app 120 then acquires information indicating the user's intention to give consent (for example, information indicating consent or information indicating disagreement).

[0094] User H1 and family members H2-H5 should prepare their own identification cards CD1-CD5 (e.g., official identification cards).

[0095] The display operation unit 14, upon receiving input from user H1 on the guidance screen, inputs the verification number of user H1's identification card CD1, user H1's date of birth, the expiration date of the identification card, the security code, etc. The DIW application 120 acquires the above input information. As a result, the DIW system 5 can recognize that the user of the system is user H1, the user whose personal information record R1 is registered. This user H1 becomes the family representative for family settings.

[0096] Next, the DIW system 5 registers the personal information of each family member H2 to H5 in order. Specifically, it performs the following processes. The following example shows registration starting with the information of family member H2, but it is not limited to this.

[0097] The display operation unit 14 receives input from user H1 or family member H2 on the guidance screen and inputs the verification number of family member H2's identification card CD1, family member H2's date of birth, the expiration date of the identification card, the security code, etc.

[0098] The DIW app 120 reads and retrieves the information (family member basic information) stored on the IC chip of the ID card CD2 via the short-range wireless communication unit 16 (step S108).

[0099] The DIW app 120 displays information regarding the identity verification request for family member H2 on the display operation unit 14 (step S109). The identity verification request information includes, for example, information requesting an image of family member H2's face.

[0100] User H1 and family member H2 confirm the information requested for identity verification and bring family member H2's face closer to the imaging unit 13. The imaging unit 13 captures an image of family member H2's face (step S110). The DIW application 120 acquires the facial image of family member H2 obtained by the imaging unit 13 (step S111).

[0101] The DIW app 120 performs face matching for family member H2 based on the acquired face image (step S112). For example, the DIW app 120 performs face matching by comparing the face image acquired from the imaging unit 13 with the face image acquired from the IC chip.

[0102] The DIW app 120 determines whether the face matching of family member H2 was successful (OK) (step S113). If the face matching is successful (Yes in step S113), the DIW app 120 displays information indicating the face matching result of family member H2 and information indicating manual input items (information requesting manual input) on the display operation unit 14 (step S114).

[0103] The display operation unit 14 receives input from user H1 or family member H2 and inputs information into the manual input fields (step S115). The manual input fields include phonetic spelling, relationship (for example, relationship to user H1, who is the representative), etc.

[0104] The DIW app 120 retrieves the information of the manually entered items (manual input information). The DIW app 120 generates family member personal information for family member H2, including the basic family member information and the manually entered information. The DIW app 120 integrates (adds) the generated family member personal information of family member H2 to the user personal information contained in the user personal information record R1 to generate family information (step S116).

[0105] The DIW application 120 sends the generated family information to the local government server 40 via the network communication unit 15 and requests authentication of the family information (step S117).

[0106] The local government server 40's communication unit 42 obtains family information from the DIW application 120 on the user terminal 10 and receives a request for authentication of the family information (step S118). The local government server 40's processor 41 performs a verification of the authenticity of the family information (step S119). In the verification of the authenticity of the family, it is determined whether user H1 and family member H2, who has been added to the family information along with the family member's personal information, belong to the same family. Specifically, the verification of the authenticity of the family information is performed by comparing the user's personal information and the family member's personal information of family member H2 contained in the family information with the resident registration or family register information stored in the local government server 40.

[0107] If the processor 41 determines that the family information is true (OK) if it determines that the personal information of the family member and the added family member H2 belong to the same family, the processor 41 determines that the family information is false (NG) if it determines that the personal information of the family member and the added family member H2 do not belong to the same family.

[0108] The communication unit 42 transmits the result of the authenticity determination (OK or NG) to the user terminal 10 (step S120).

[0109] Furthermore, the authenticity of family information may be verified by the DIW application 120. For example, the authenticity of family information can be verified by allowing the DIW application 120 to access information such as resident registration or family register held by the municipal server 40.

[0110] The DIW application 120 on the user terminal 10 obtains information on the authenticity determination result via the network communication unit 15 (step S121). The DIW application 120 determines whether the authenticity determination result is true (OK) or false (NG) (step S122).

[0111] If the authenticity determination result is true (OK) (Yes in step S122), the DIW app 120 displays the acquired family information (for example, the personal information of family member H2) on the display operation unit 14 (step S123).

[0112] If the authenticity determination result is false (NG) (No. in step S122), the DIW app 120 displays information on the display operation unit 14 notifying that the acquired family information (for example, the personal information of family member H2) will be deleted, or information notifying that an error has occurred (step S124).

[0113] After processing in step S123, the DIW app 120 displays information on the display operation unit 14 regarding the input items of personal information of family members that need to be entered (i.e., manually entered) by user H1 via the display operation unit 14 (step S125). This display prompts user H1's family members to enter personal information that needs to be manually entered. The display operation unit 14 receives input from user H1 or family member H2 and enters the personal information of family member H2 that needs to be manually entered (step S126). The personal information that needs to be manually entered here includes, for example, the contact information and telephone number of family member H2.

[0114] The DIW app 120 acquires personal information of each family member manually entered from the display operation unit 14 (step S127). For each family member, the DIW app 120 extracts (for example, calculates) attribute information of family member H2 based on the acquired basic family member information or manually entered information (step S128). For example, the DIW app 120 extracts the age of family member H2 as attribute information based on the date of birth and current time of family member H2.

[0115] The processing in steps S108 to S128 is performed for each family member. Therefore, the DIW system 5 repeats the processing in steps S108 to S128 for each family member. For example, once the processing for family member H2 is completed, the processing for family member H3 is performed next. In this case, family member H2 in steps S108 to S128 is replaced with family member H3.

[0116] Furthermore, in step S116, the personal information of the family member being processed is added to the already generated family information. For example, if the family member being processed is family member H4, the personal information of family member H4 will be added to the already generated family information (user personal information, family member personal information of family member H2, and family member personal information of family member H3).

[0117] Once the processing in steps S108 to S128 is completed for each family member, the DIW application 120 associates the user personal information and each family member's personal information included in the acquired family information and groups them as information for one family (i.e., sets them as one family). Then, the DIW application 120 assigns a family ID to the family information to identify the family and generates a family information record R2 (step S129). The DIW application 120 has the data management unit 130 store the family information record R2 (step S129). In the case of groups other than families, a group ID is assigned to each group and a group information record is generated.

[0118] The DIW application 120 notifies the DIW server 20 of the family information record R2 via the network communication unit 15 (step S130).

[0119] The DIW server 20's communication unit 22 obtains the family information record R2 from the DIW application 120 on the user terminal 10 (step S131). The processor 21 updates the integrated family information master list L3 by adding the obtained family information record R2 to the integrated family information master list L3, which is a compilation of the family information records R2 of each family, and stores it in the data management unit 230 (step S132).

[0120] When the DIW application 120 notifies the family information record R2 in step S130, it displays information (official registration information) on the display operation unit 14 indicating that the family information (i.e., family information record R2) has been officially registered with the DIW server 20 (step S133). This allows user H1 and family members H2 to H5 to recognize that family information record R2 has been officially registered, that is, that the family setup is complete. The official registration information includes, for example, information indicating that family information record R2 has been registered, and family information record R2 which has been set up (registered).

[0121] As shown in the operation examples in Figures 9A to 9C, the DIW system 5 can set up a family including user H1 and family members H2 to H5, with user H1, whose user personal information is registered, as the representative. In other words, the DIW system 5 can generate a family information record R2 that associates user personal information and family member personal information, and add it to the integrated family information master list L3. Therefore, the DIW system 5 can use the family information record R2 held in the user terminal 10 or the family information record R2 stored in the integrated family information master list L3 held in the DIW server 20 to provide various services (e.g., shelter services) to families in a batch.

[0122] Note that while Figures 9A to 9C illustrate the process of facial recognition, this process may be omitted. The facial recognition process includes, for example, steps S109 to S113. The DIW application 120 may perform facial recognition for each family member if the basic family member information obtained from the IC chips of the identification cards CD2 to CD5 of family members H2 to H5 includes a facial image, but does not need to perform facial recognition if the basic family member information does not include a facial image. Note that newly issued My Number cards generally do not include a child's facial image. Furthermore, the facial recognition process may be performed at a different timing than that illustrated in Figures 9A to 9C.

[0123] Figure 10 shows an example of a family information record R2.

[0124] Family information record R2 stores the family ID, the user personal information of the representative user H1, and the family member personal information of each family member. In other words, family information record R2 stores the following information in association: business ID, service ID, family ID, relationship, user ID of user H1, name of user H1, phonetic spelling of user H1, gender of user H1, date of birth of user H1, age of user H1, address of user H1, face image of user H1, family member personal information 1, family member personal information 2, ..., family member personal information N (N is an integer). Family information record R2 may also include other information. Furthermore, each family member personal information may include the family member's name, phonetic spelling, gender, address, date of birth, relationship, and face image. Note that family member personal information does not necessarily have to include a face image. Furthermore, the relationship information included in the personal information of family members is their relationship to user H1 (e.g., father, mother, child).

[0125] In short, Family Information Record R2 is a compilation of information about families using services (e.g., evacuation shelter services) provided by a service provider (e.g., a local government). Service providers are identified by their service provider ID. Services are identified by their service ID. Families are identified by their family ID.

[0126] The user terminal 10 is configured by the DIW application 120, which extracts information contained in the user personal information record R1, which is held by the data management unit 130, including the user ID, name, address, date of birth, gender, and facial image, contained in the family information record R2.

[0127] Figure 11 shows an example of the Integrated Family Information Master List L3.

[0128] The integrated family information master list L3 is a list maintained by the DIW server 20, and is a list that integrates the family information records R2 of multiple families. Therefore, the integrated family information master list L3 contains the information contained in the family information records R2. The integrated family information master list L3 may also contain other information.

[0129] The integrated family information master list L3 stores information similar to that of family information record R2 for each service and each family, associating it with the following information: business ID, service ID, family ID, relationship to the user, user ID, name of the user, phonetic spelling of the user's name, gender of the user, date of birth of the user, age of the user, address of the user, face image of the user, family member personal information 1, family member personal information 2, ..., family member personal information N (N is an integer). The integrated family information master list L3 may also include family information record R2 for each family, separated by service. In Figure 11, as an example, it is separated by shelter services in Ward A and shelter services in Ward B.

[0130] In other words, the Integrated Family Information Master List L3 is a compilation of information about families using services (e.g., evacuation shelter services) provided by service providers (e.g., local governments), organized by service and by family.

[0131] Furthermore, the DIW system 5 may prepare a business ID master list in which each business ID that identifies each business (e.g., local government) corresponding to each local government server 40 is aggregated and stored when registering family settings. The DIW system 5 may have the local government server 40 send this business ID master list to the evacuation center terminal 30 in advance, and the evacuation center terminal 30 may store it in memory 32. The business ID master list may include, for example, personal information and facial image information about each person stored within the local government for each business (e.g., local government). This allows the DIW system 5 to perform facial recognition within the evacuation center terminal 30 even if it is unable to connect to the local government server 40 when using the service described later (e.g., during evacuation).

[0132] Figures 12A and 12B show an example of the screen transitions displayed on the user terminal 10 when registering family settings.

[0133] Screen G11 is a screen for obtaining consent to the terms of use for family members. Screen G11 includes the items of personal information of family members to be provided to the DIW server 20, the terms of use (purpose of use) for the personal information of family members to be provided, and information prompting consent to provide the personal information of family members. The DIW app 120 obtains information from user H1 or family members H2-H5 indicating their intention to give consent.

[0134] Once information indicating consent is obtained, that is, the user agrees to the terms of service, the screen transitions to screen G12, which contains information for entering a verification number. Screen G12 includes the date of birth, expiration date (e.g., year only), and security code as the verification number.

[0135] Next, the screen transitions to screen G13, where the user enters the verification number. On screen G13, the user enters the date of birth, expiration date (e.g., year only), and security code as the verification number. Subsequently, the screen transitions to screen G14, which contains guidance information for reading the information held on the family member's identification card.

[0136] As the screen transitions further, the screen moves to screen G15, where users manually enter information for family members. Screen G15 includes the phonetic spelling of the full name and the relationship of the family member to the representative as manual input fields. Information is entered (manually) into these fields via the display operation unit 14. Once the manual input is complete, the family member's personal information is registered in the data management unit 130, etc. Then, the screen moves to screen G16, indicating that the addition of family member's personal information is complete.

[0137] Using screens G11 to G16 shown above, personal information for each family member is added one by one. Therefore, for example, if there are four family members H2 to H5, the transitions between screens G11 to G16 will be repeated four times.

[0138] The DIW system 5 processes information according to these screen transitions, obtaining the identification information (basic family member information) of family members H2 to H5, adding the information from manually entered fields, and obtaining personal information for each family member, thereby deriving the family information.

[0139] Figure 13 shows an example of screen transitions when viewing the personal information of each family member stored on the user terminal 10.

[0140] Screen G21 displays information (e.g., name) that identifies family members stored in the digital ID wallet. When a desired family member is selected on screen G21, the screen transitions to screen G22, which contains the personal information of the selected family member. The digital ID wallet is managed and stored by the DIW application 120 or the data management unit 130.

[0141] In this way, the user terminal 10 owned by user H1 can easily display the personal information of each family member obtained during family setup using the DIW application 120.

[0142] In Figure 13, the trash can icon located in the upper right corner indicates the termination of the link, specifically the termination (departure) of a designated family member from the family. When the icon is pressed via the display operation unit 14, the DIW app 120 performs a deregistration process to remove the corresponding family member from the family. In the deregistration process, if the facial recognition of the family member is successful, or if the facial recognition of user H1, who is the family representative, is successful, the family member will be removed from the family link. One possible scenario for discontinuing the link is when a designated family member moves and changes their address, resulting in a difference in resident registration between family members. Furthermore, in the case of disconnection, if user H1 actively requests disconnection, the DIW server 20 may assist in the disconnection upon receiving a notification from the DIW application 120. For example, if the DIW server 20 receives a notification of a request to disconnect from the DIW application 120, it is conceivable that it would periodically obtain information regarding address changes from the local government server 40 to check if there have been any changes to the addresses of family members registered in the integrated family information master list L3. If it is not possible to match this information with the information held in the integrated family information master list L3 (i.e., if the addresses no longer match), it would notify the DIW application 120.

[0143] Next, we will explain how the DIW system 5 works when setting up integration between family members and services.

[0144] Figures 14A and 14B are sequence diagrams showing an example of operation when setting up family and service linkage using the DIW system 5. In this DIW system 5, the user personal information record R1, integrated personal information master list L2, family information record R2, integrated family information master list L3, and service master list L1 are pre-stored.

[0145] First, the DIW application 120 starts up (step S151). The DIW application 120 retrieves the service master list L1 from the data management unit 130 (step S152). The DIW application 120 receives input from user H1 via the display operation unit 14 and obtains a request to add a service (step S153).

[0146] The DIW application 120 filters available services based on the family information record R2 (step S154) and generates an available service list L4 (step S155). In this case, the DIW application 120 may determine that services that satisfy the service provision conditions based on the user personal information (e.g., attribute information) and family member personal information (e.g., attribute information) included in the family information record R2 are available services. The DIW application 120 may also acquire, for example, the location information of the user terminal 10 and filter available services based on this location information. In this case, the DIW application 120 may determine that services that satisfy the location conditions of the user terminal 10 are available services. The DIW application 120 displays an available service list screen showing a list of available services on the display operation unit 14 (step S156).

[0147] User H1 and family members H2-H5 confirm the display of the list of available services. The display operation unit 14 selects one or more available services that user H1 and family members H2-H5 wish to connect to (step S157).

[0148] The DIW app 120 obtains the selection information of the services that user H1 and family members H2-H5 wish to connect with from the display operation unit 14. The DIW app 120 requests consent to provide personal information to the selected services (step S158). Here, consent is required to provide personal information of user H1 and family members of user H1. In this case, the DIW app 120 displays, for example, a consent request screen on the display operation unit 14 to request this consent. The consent request screen includes, for example, the user's personal information and family member's personal information to be provided to the selected services. Specifically, the consent request screen includes the items of personal information of user H1 and family members H2-H5 designated to the service provider of the selected service from the family information record R2, information on the purpose of use (terms of use) for using these items of personal information, and information prompting consent to the use of these items of personal information. The designated items of personal information mentioned above may include, for example, name, address, date of birth, gender, etc.

[0149] User H1 and family members H2-H5 confirm the display of the consent request screen and verify the user personal information and family member personal information to be provided for the selected service. The display operation unit 14 receives input from user H1 or family members H2-H5 and inputs information indicating whether or not they consent to the provision of the user personal information and family member personal information to be provided (step S159).

[0150] The DIW app 120 obtains information regarding consent entered from the display operation unit 14. The information obtained here includes information indicating the intentions of user H1 or family members H2-H5 regarding the above consent acquisition (for example, information indicating consent or non-consent).

[0151] When the DIW app 120 obtains information indicating consent to the provision of user personal information and family member personal information, the DIW app 120 activates the imaging unit 13 (step S160) and displays information including the imaging request on the display operation unit 14 (step S161).

[0152] User H1 and family members H2-H5 bring their faces closer in turn. The imaging unit 13 captures images of user H1's face and the family members' faces in turn (step S162). The DIW application 120 acquires the captured facial images of user H1 and family members from the imaging unit 13 (step S163).

[0153] The DIW app 120 performs face matching for each person based on the acquired face images of user H1 and family members H2-H5 and the face images stored in the family information record R2 (step S164), and determines whether the face matching was successful or not (step S165). In this face matching, for each person, it is determined whether the acquired face images of user H1 and family members H2-H5 match the face images of user H1 and family members H2-H5 stored in the family information record R2. If they match, it is determined that the face matching was successful; if they do not match, it is determined that the face matching failed.

[0154] If it is determined that face matching has failed (No. in step S165), the DIW app 120 displays information indicating that face matching has failed and information to guide re-imaging on the display operation unit 14 (step S166). Alternatively, the DIW app 120 may display information indicating that face matching has failed and terminate the processes shown in Figures 14A and 14B.

[0155] If facial recognition is determined to be successful (Yes in step S165), the DIW application 120 requests the DIW server 20 to assign a family ID for the service via the network communication unit 15 (step S167). This request includes information on a family ID that identifies the family to which user H1 belongs, and a service ID that identifies the service for which information provision has been agreed upon. This request may also include a user ID that identifies user H1.

[0156] The DIW server 20 has a processor 21 that receives a request for assigning a service-specific user ID from the user terminal 10 via the communication unit 22, and determines a service-specific family ID based on the assignment request (step S168). For example, the processor 21 determines the service-specific family ID based on the service ID and the family ID. In this case, for example, the processor 21 may integrate the service ID and the family ID, for example, simply combine them as service ID + family ID, and calculate the service-specific family ID by converting the value of the integration result into a hash value. This allows the DIW system 5 to assign different family IDs to different services even for the same family, and can prevent the sharing of family IDs among multiple service providers (for example, among multiple municipalities).

[0157] The DIW server 20, via its communication unit 22, notifies the user terminal 10 of the family ID for the service (step S169).

[0158] The user terminal 10's communication unit 22 obtains the family ID for the service from the DIW server 20. The DIW application 120 generates or updates a list of linked consented services L5, which includes the service ID, the family ID for the service, and whether or not consent has been given (step S170).

[0159] The DIW app 120 extracts information from the family information record R2 (also referred to as linked consent information) for which consent has been given for information sharing (step S171). The DIW app 120 sends this linked consent information, including the family ID for the service, to the service app 110 (step S172). The linked consent information may include information such as name, address, date of birth, and gender.

[0160] The service app 110 obtains and stores the consent information for linking from the DIW app 120 (step S173).

[0161] The DIW app 120 notifies the DIW server 20 of the information provided to the service app 110, including the linking consent information, the service provider ID information corresponding to the service app 110, whether or not consent was given, the service linking date, etc. (step S174). The DIW app 120 then displays linking completion information on the display operation unit 14, indicating that the linking between the family and the service has been completed (step S175).

[0162] The DIW server 20's communication unit 22 acquires the linking consent information, business ID information, consent status information, service linking date, etc., from the user terminal 10. The processor 21 stores the acquired linking consent information in memory 23 or storage 24 (step S176). The processor 21 also updates the family-linked service list L6 based on the acquired information, that is, adds information for one record related to the consent for this service linking, and stores it in the data management unit 230 (step S177). The family-linked service list L6 contains information on whether or not linking has taken place.

[0163] If multiple services are selected as services to be linked, steps S158 to S177 will be repeatedly executed for each service.

[0164] As shown in the operational examples in Figures 14A and 14B, the DIW system 5 can link the family information record R2 with the family's desired service based on the consent of user H1 and each family member H2-H5. Therefore, user H1 and each family member H2-H5 can use this service.

[0165] While the DIW app 120 is shown as filtering available services based on user personal information and family member personal information contained in family information record R2, it is not limited to this. For example, the DIW app 120 may filter available services and generate an available services list L4 based on user personal information contained in user personal information record R1 or family information record R2. In this case, the DIW app 120 may filter available services by matching the user H1's user personal information record R1 with the service provider's (e.g., local government) service provision conditions. As an example, the DIW app 120 may display "〇 Ward Evacuation Shelter (Reception) Service" as an available service on the display operation unit 14. The DIW app 120 may perform facial recognition of user H1, and after successful facial recognition, link the family information record R2 of the family to which user H1 belongs with "〇 Ward Evacuation Shelter Service". The DIW app 120 may provide at least a portion of the user's personal information and family member's personal information to the service app 110 of "〇 Ward Evacuation Shelter Service", and may notify the DIW server 20 of the provision history information as a provision history.

[0166] Figure 15 shows an example of the available services list L4.

[0167] The Available Services List L4 is a list containing information about services available to user H1 (i.e., user terminal 10). The Available Services List L4 stores information from the Service Master List L1 regarding services where the user's personal information and family member personal information (e.g., attribute information of the user and family members) meet the service provision conditions. The Available Services List L4, for example, associates and maintains information such as service ID and availability. The Available Services List L4 may also include other information.

[0168] Figure 16 shows an example of the L5 list of services for which collaboration has been agreed upon.

[0169] The Linked Consent Service List L5 is a list indicating whether user H1 and family members have consented to the provision of personal information for each service whose "Availability" status in the Available Service List L4 is "Available". The Linked Consent Service List L5, for example, associates and stores information such as the service ID, the family ID for the service, and whether consent was given. The Linked Consent Service List L5 may also include other information.

[0170] Figure 17 shows an example of a family-coordinated service list L6.

[0171] The Family Linked Services List L6 is a list that holds information about the services linked to each family. When services linked to each family are added or removed, the Family Linked Services List L6 is updated accordingly. The Family Linked Services List L6 stores information such as, for example, family ID, service provider ID, service-specific family ID, linking date and time, provision information (linking consent information), and linking information related to the linking. The Family Linked Services List may also include other information. Linking information may include information indicating, for example, whether the linking is in progress or has been terminated. Figure 17 shows a specific example of a family and the services they use for reference.

[0172] Next, we will explain how the DIW system 5 operates when using services. Here, we will give shelter services as an example of a service, but it is not limited to this.

[0173] Figure 18 is a sequence diagram showing a first example of the operation of batch identity verification and registration confirmation of evacuee information during evacuation. Figure 18 mainly illustrates the case when operating the user terminal 10. The operation in Figure 18 can be performed both online and offline. In this DIW system 5, the following are pre-registered (held): user personal information record R1, integrated personal information master list L2, family information record R2, integrated family information master list L3, service master list L1, available service list L4, linked consent service list L5, and family linked service list L6.

[0174] In the event of a disaster such as an earthquake or typhoon, user H1 and family members H2-H5 will evacuate to a designated shelter and register for evacuation. During evacuation, the DIW system 5 will perform the following processes and provide shelter services to the evacuees.

[0175] First, the evacuation center terminal 30 displays a predetermined code (for example, a two-dimensional code (for example, a QR code (registered trademark))) on its display operation unit 34 (step S201). The information corresponding to this code includes an evacuation center terminal ID that identifies the evacuation center terminal 30.

[0176] User H1 brings user terminal 10 close to (for example, holds over) the evacuation center terminal 30. User terminal 10's imaging unit 13 captures a code, and the DIW application 120 reads the contents of the code through image recognition (step S202). The code reading result includes the evacuation center terminal ID. In addition, by reading the code, the DIW application 120 specifies the evacuation center service available to user H1 (for example, the evacuation center service in Ward A).

[0177] The network communication unit 15 of the user terminal 10 and the network communication unit 35 of the evacuation center terminal 30 establish a communication network between them (step S203).

[0178] The evacuation center terminal 30 instructs the user terminal 10 via the network communication unit 35 to display a matching request screen requesting to verify the face of user H1 (step S204).

[0179] The user terminal 10 receives a display instruction for the matching request screen via the DIW application 120 through the network communication unit 15, and displays the matching request screen on the display operation unit 14 based on the display instruction.

[0180] The DIW application 120 activates the imaging unit 13 (step S205). The imaging unit 13 captures the face of user H1 (step S206). The DIW application 120 acquires the face image of user H1 captured by the imaging unit 13 (step S207).

[0181] The DIW application 120 matches the face of user H1 based on the face image of user H1 acquired from the imaging unit 13 and the face image of user H1 contained in the user personal information record held in the data management unit 130 (step S208). The matching here is a one-to-one match.

[0182] The DIW app 120 notifies the evacuation center terminal 30 of the face matching result via the network communication unit 15 (step S209). The face matching result includes information on whether the matching was successful (OK) or failed (NG).

[0183] The evacuation center terminal 30 receives information on the results of facial recognition from the user terminal 10 via its network communication unit 35. The network communication unit 35 requests evacuee information regarding the evacuees who have evacuated (step S210).

[0184] When the user terminal 10 receives a request for evacuee information via the network communication unit 15 from the DIW application 120, it extracts family information (i.e., user personal information and family member personal information of each family member) from the family information record R2 held in the data management unit 130 (step S211).

[0185] The DIW app 120 displays a screen for confirming evacuees (evacuee confirmation screen) on the display operation unit 14 (step S212). The evacuee confirmation screen includes, for example, a list of family information.

[0186] User H1 confirms the displayed evacuee confirmation screen. The display operation unit 14 receives input from user H1 on the evacuee confirmation screen and selects the evacuees (user H1 and family members who have evacuated) from among the family members (step S213).

[0187] The DIW app 120 displays the evacuee information of the selected evacuee on the display operation unit 14 (step S214). This evacuee information includes the evacuee's personal information, including, for example, at least some of the user's personal information and the personal information of family members.

[0188] The DIW application 120 transmits the user terminal ID to the evacuation center terminal 30 via the network communication unit 15, along with the evacuee information (step S215). The evacuee information transmitted here includes the business operator ID, service ID, user terminal ID, and evacuation center terminal ID. The user terminal ID is stored, for example, in memory 12.

[0189] The evacuation center terminal 30 has a network communication unit 35 that acquires evacuee information from the user terminal 10.

[0190] The processes described in steps S201 to S215 above can be executed even when offline, that is, when communication with the DIW server 20 and the local government server 40 is not possible. Therefore, even when communication between each server (e.g., DIW server 20, local government server 40) and each terminal (e.g., user terminal 10, evacuation center terminal 30) is interrupted, the DIW system 5 can register evacuee information regarding evacuees who have evacuated to an evacuation center using the user terminal 10 and the evacuation center terminal 30.

[0191] Figure 19 is a sequence diagram showing a continuation of the first example of batch identity verification and registration confirmation of evacuee information during evacuation. The operations in Figure 19 can be performed when online (for example, when communication is restored from offline).

[0192] The user terminal 10 transmits the evacuee information provided by the DIW application 120 to the DIW server 20 via the network communication unit 15 (step S216). This evacuee information includes, for example, at least some of the personal information of the evacuated user and family members, a business ID, a service ID, a user terminal ID, and a shelter terminal ID.

[0193] The DIW server 20 has its communication unit 22 acquire evacuee information from the user terminal 10 and store it in memory 23 or storage 24 (step S217). The DIW server 20 may also store log information, described later, in memory 23 or storage 24 based on the acquired evacuee information.

[0194] The evacuation center terminal 30 transmits the evacuee information obtained from the user terminal 10 to the local government server 40 via the network communication unit 35 (step S218). The evacuee information transmitted here includes, for example, at least some of the personal information of the evacuated user and family members, a business ID, a service ID, a user terminal ID, and an evacuation center terminal ID.

[0195] The local government server 40, via its processor 41, acquires evacuee information from the evacuation center terminal 30 through its communication unit 42 and stores it in memory 43 or storage 44 (step S219).

[0196] The municipal server 40 has a communication unit 42 that can acquire evacuation information for one or more families. The processor 41 creates an evacuation list based on the acquired evacuation information for each family (step S220). The evacuation list includes evacuation information for one or more families.

[0197] The evacuee list, for example, stores information such as the personal information of the evacuated user and at least some of the personal information of family members, along with the business ID, service ID, user terminal ID, and evacuation center terminal ID, for each family.

[0198] As shown in the operation examples in Figures 18 and 19, the DIW system 5 can easily register the evacuation information of family members associated with user H1 by authenticating user H1 and specifying the family members who have evacuated. Furthermore, even when offline, the DIW system 5 can manage who has evacuated to which shelter on a family basis. In addition, when the DIW system 5 becomes online, it can share the evacuation information held by the user terminal 10 and the shelter terminal 30 with the DIW server 20 and the local government server 40, making it easier to disseminate and understand the evacuation information.

[0199] Alternatively, the DIW app 120 on the user terminal 10 may send the evacuee information to the service app 110 instead of sending it to the evacuation center terminal 30. Even in this case, the user terminal 10 can retain the information provided to the service app 110 in memory 12 or the like, making it available for user H1 and family members H2-H5 to review after using the service.

[0200] Figure 20 is a sequence diagram showing a second example of operations for batch identity verification and registration and confirmation of evacuee information during evacuation. Figure 20 mainly illustrates the case when operating the evacuation center terminal 30. Note that in Figure 20, the explanation of matters that are the same as those shown in the first operation example in Figures 18 and 19 is omitted or simplified.

[0201] Similar to the first example, in the event of a disaster, user H1 and family members H2-H5 evacuate to a designated shelter and register for evacuation. During evacuation, the DIW system 5 performs the following processes and provides shelter services to the evacuees.

[0202] First, the evacuation center terminal 30 has the processor 31 display a matching request screen on the display operation unit 34, requesting face matching of user H1 (step S301). The processor 31 starts up the imaging unit 33 (step S302). The imaging unit 33 captures the face of user H1 (step S303). The processor 31 acquires the face image of user H1 captured by the imaging unit 33 (step S304). The processor 31 transmits the face image of user H1 to the DIW server 20 via the network communication unit 35 and requests face matching (step S305).

[0203] The DIW server 20's communication unit 22 obtains a face image and a face matching request from the shelter terminal 30 (step S306). The processor 21 matches the face of user H1 based on the face image of user H1 captured by the imaging unit 33 from the shelter terminal 30 and the face images included in the integrated personal information master list L2 held in the data management unit 230 (step S307). Here, it is determined whether or not a face image matching user H1's face is registered in the integrated personal information master list L2. In other words, the matching here is a 1:N (N is an integer greater than or equal to 1) matching.

[0204] If the processor 21 successfully matches the face of user H1, it retrieves the user ID associated with the face matching of user H1, which is included in the integrated personal information master list L2. Based on the retrieved user ID, the processor 21 extracts the family information of user H1 from the integrated family information master list L3 (step S308). The family information of user H1 includes the family ID and the personal information of each family member.

[0205] The processor 21 transmits the extracted family information of user H1 to the evacuation center terminal 30 via the communication unit 22 (step S309).

[0206] The evacuation center terminal 30 has a network communication unit 35 that retrieves family information from the DIW server 20. The processor 31 displays a screen for confirming evacuees (evacuee confirmation screen) on the display operation unit 34 (step S310). The evacuee confirmation screen includes, for example, a list of family information.

[0207] User H1 confirms the evacuees by checking the displayed evacuee confirmation screen. The display operation unit 34 receives input from user H1 on the evacuee confirmation screen and selects the evacuees from among user H1 and family members who have evacuated (step S311).

[0208] The processor 31 obtains information about the evacuee selected (evacuee selection information) via the display operation unit 34. Based on the evacuee selection information, the processor 31 transmits evacuee information, including the information of the selected evacuee, to the local government server 40 via the network communication unit 35 (step S312). The evacuee information transmitted here includes, for example, at least some of the personal information of the evacuated user and family member, a business ID, a service ID, a user terminal ID, and an evacuation center terminal ID.

[0209] The local government server 40, via its processor 41, acquires evacuee information from the evacuation center terminal 30 through its communication unit 42 and stores it in memory 43 or storage 44 (step S313).

[0210] The local government server 40 has a communication unit 42 that can acquire evacuation information for one or more families. The processor 41 creates an evacuation list based on the acquired evacuation information for each family (step S314). The evacuation list is the same as the evacuation list described in the first example of operation.

[0211] Furthermore, the DIW server 20 stores at least a portion of the family information provided by the processor 21 to the evacuation center terminal 30 as log information in the data management unit 230 (step S315).

[0212] As shown in the example of operation in Figure 20, the DIW system 5 can easily register the evacuation information of family members associated with user H1 by authenticating user H1 and specifying the family members who have evacuated. Furthermore, even when offline, the DIW system 5 can manage who has evacuated to which shelter on a family basis. In addition, even if user terminal 10 is unavailable, evacuation information can be registered and managed by coordinating with shelter terminals 30 other than user terminal 10, the DIW server 20, and the local government server.

[0213] Figure 21 shows an example of evacuation information.

[0214] Evacuee information includes information provided to the service application 110, evacuation center terminal 30, or local government server 40 regarding the evacuated user H1 or family members from the family information. Here, we illustrate the case where the evacuees are user H1, family member H2, and family member H3, and user personal information, family member personal information 1 of family member H2, and family member personal information 2 of family member H3 are provided.

[0215] Evacuee information is stored by associating the following information: for example, the business ID, service ID, family ID, relationship to the user, user ID, name of the user, phonetic spelling of the user's name, gender of the user, date of birth of the user, age of the user, address of the user, facial image of the user, family member personal information 1, and family member personal information 2. In other words, evacuee information includes only the user personal information and family member personal information (e.g., family member personal information 1, family member personal information 2, ...) from the information contained in family information record R2 for which information has been provided, and does not include family member personal information (e.g., family member personal information 3, family member personal information 4, ...). Evacuee information may also include other information.

[0216] Figure 22 shows an example of log information.

[0217] Log information maintains a history of each service used by each family. For example, log information maintains associations with family ID, service provider ID, service ID, service used, service usage date and time, and provided information. Provided information is information provided to applications other than the DIW application or devices other than the user terminal 10. Provided information may include, for example, at least a portion of the user's personal information or the personal information of family members. Provided information may include the date and time the information was provided, the user terminal ID of the user terminal 10 to which the information was provided, or the evacuation terminal ID of the evacuation terminal 30 related to the service to which the information was provided. Log information may be provided to the user terminal 10 in a timely manner and may be checked in a timely manner by user H1 and family members H2-H5.

[0218] Figures 23A and 23B show an example of screen transitions displayed on the evacuation center terminal 30 when using the service.

[0219] Screen G31 is the reception screen on the evacuation center terminal 30. When facial recognition is selected on the reception screen, the screen transitions to screen G32 for facial recognition (face matching). Screen G32 may include guide information for capturing the faces of each family member. If face matching is successful, the screen transitions to screen G33, which indicates that evacuee information will be linked. Once the evacuee information is linked, the screen transitions to screen G34, which is the evacuee confirmation screen. On screen G34, family information, including both evacuated and non-evacuated family members, is displayed in a list. On screen G34, evacuated family members are selected as evacuees. Additionally, on screen G34, items indicating matters requiring special consideration for each family member may be displayed as selectable items.

[0220] Thus, the DIW system 5 of this embodiment can generate a family information record R2 and an integrated family information master list L3 that aggregate personal information on a family basis, and can easily implement family settings. Therefore, the DIW system 5 can easily allow families to use the service collectively by using the family information record R2 and integrated family information master list L3 when using the service. In addition, the DIW system 5 can guarantee the identity of users and family members through facial recognition. In this way, the DIW system 5 can implement group settings and collectively use the service after guaranteeing the identity of multiple people.

[0221] Furthermore, the DIW server 20 can retain log information as a history of service usage for each family. This allows user H1 and family members H2-H5 to check how their personal information included in the family information was used at any time after using the service.

[0222] In this embodiment, the service provided by the local government server is an evacuation shelter service, but it is not limited to this. For example, the service provided by the local government may be an event-related service (e.g., participation in an event), a resort-related service (e.g., reservation of a resort), a nursery school-related service (e.g., application for admission to a nursery school), a school-related service, etc.

[0223] In this embodiment, only the user terminal 10, which is the representative's terminal, holds the family information record R2, but this is not limited to this. For example, the family information record held on the user terminal 10 may be duplicated and sent to the terminal held by family member H2 (family member terminal) for storage. In this case, one of the users H1 and family members H2 to H5 within the same family becomes the representative, and the DIW system 5 can perform the evacuation operations shown in Figures 18 to 20 above.

[0224] In this embodiment, the user terminal 10 is shown as acquiring the basic information of user H1 from a physical identification card CD1, but it is not limited to this. For example, the user terminal 10 may be able to store data from various digital identification documents (e.g., a digital My Number Card, which is an electronic version of a My Number Card), and the data from the digital identification document may be used in the various processes of this embodiment. A digital My Number Card contains the same information as a My Number Card.

[0225] In this embodiment, the display of information by the display operation unit 14 and the display operation unit 34 is merely one example of information presentation, and is not limited to this. For example, information may be presented by outputting the information as audio through the speaker of the user terminal 10. Similarly, information may be presented by outputting the information as audio through the speaker of the evacuation center terminal 30.

[0226] In this embodiment, where a service-independent family ID is used, a service-dependent family ID may be used instead, as appropriate. Also, in each list, a service-dependent family ID may be used instead of a service-independent family ID, as appropriate.

[0227] (Summary of the embodiment) Based on the above, this disclosure contains at least the following information. The components and other elements in parentheses are examples of those corresponding to the embodiments described above, but are not limited to these.

[0228] (Item 1) An information processing method performed by at least one processor (processor 11), Controlling the terminal (user terminal 10) to read basic group member information, which is the basic information of the group members, from the identification cards (identification cards CD2 to CD5) of the group members (family members H2 to H5) belonging to the group (family) to which the user (user H1) of the terminal (user terminal 10) belongs, The process involves obtaining group member input information (manual input information of family members), which is information about the group members obtained through input operations to the input unit (display operation unit 14) of the terminal, By adding the group member personal information (family member personal information), which includes the group member basic information and the group member input information, to the user personal information, which includes information generated by reading the user's basic information from the user's identification document, a group information record (family information record) is created. The group information record is sent to an external device (DIW server 20), The group information record is stored in the terminal's memory (memory 12), Information processing methods including

[0229] As a result, the information processing method can obtain information from identification documents that guarantee the identity of each group member as basic group member information, and can obtain personal information of group members that includes this basic group member information. Therefore, the information processing method can set up a group while guaranteeing the identity of multiple individuals by integrating the personal information of group members with the personal information of users whose identity is guaranteed.

[0230] (Item 2) Based on the aforementioned basic group member information or the aforementioned group member input information, group member attribute information, which is attribute information relating to the group member, The group member personal information further includes the group member attribute information, The information processing method described in item 1.

[0231] This allows the information processing method to include attribute information not directly contained in the identification document information in the group member's personal information.

[0232] (Item 3) To present the following: information of a first item acquired by the external device from the personal information of the group members, information of the first purpose of use for utilizing the first item, and information prompting the acquisition of first consent for the use of the first item; This further includes obtaining information indicating a first intention to obtain the first consent, The information processing method described in item 1 or 2.

[0233] This allows the information processing method to reflect the wishes of the group members and provide their personal information to an external device, thereby enabling linkage between the external device and family information records.

[0234] (Item 4) To display the following information from the group information record: information of a second item designated for a service that uses at least a portion of the group information record; information of a second purpose for using the second item; and information prompting the acquisition of a second consent for the use of the second item. This further includes obtaining information indicating a second intention to obtain the second consent, The information processing method described in item 3.

[0235] This allows the information processing method to reflect the wishes of the group members and provide their personal information to the service provider, thereby enabling the linkage between the service and family information records.

[0236] (Item 5) If the second information indicating intent indicates consent, the consent acquisition record information (linked consent information) including information identifying the group and information identifying the service is transmitted to the external device as a record of obtaining the second consent, The information processing method described in item 4.

[0237] This allows the information processing method to notify external devices of the information provided to the service with which the integration has been agreed upon. Therefore, the external devices can retain this provided information, and users or group members can check the provided information in a timely manner.

[0238] (Item 6) If the second information indicating intent indicates consent, then based on the information identifying the service and the information identifying the group, identification information is generated that identifies the service and uniquely identifies the group. The information processing method described in item 4.

[0239] This allows the information processing method to easily identify services that the group has agreed to and collaborated on using a single identifier.

[0240] (Item 7) The system further includes, for a specified group member, authenticating that the specified group member is the person who possesses the identification document by performing a facial matching based on the facial image of the group member included in the group member basic information and the facial image of the group member captured by the terminal, An information processing method described in any one of items 1 through 6.

[0241] This allows the information processing method to further improve the accuracy of verifying the identity of group members and enable group configuration.

[0242] (Item 8) The group member personal information and the user personal information are transmitted to an external authentication server (local government server 40), The authentication server further includes receiving a determination result from the authentication server regarding whether the user and the group member belong to the same group. An information processing method described in any one of items 1 through 7.

[0243] This allows the information processing method to verify the authenticity of the user and group members belonging to the same group.

[0244] (Item 9) An information processing method performed by at least one processor, Specify the services available to the user who holds the device, Obtaining a group information record that includes, at a minimum, user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document; The user is authenticated as the person who possesses the user's identification document by facial matching based on the first facial image of the user included in the group information record and the second facial image of the user's face captured by a predetermined imaging unit (imaging units 13, 33). If the user is authenticated as the person in question, the user will be prompted to present selection request information requesting the selection of the group members, Transmitting first information, which includes at least a portion of the group member personal information corresponding to the selected group member and at least a portion of the user personal information, to an application (service app 110) on the terminal used to use the service or to equipment of the service provider (shelter terminal 30, local government server 40), An information processing method having

[0245] This means that, as a group representative, the user verifies their identity, and then both the user and each family member to which the user belongs can use the service. Furthermore, personal information of family members is generated using the identification documents of the family members. Therefore, the user and group members can use the service safely and collectively while guaranteeing the identities of multiple individuals.

[0246] (Item 10) The at least one processor is a processor provided in the terminal. The information processing method according to claim 1 or 9.

[0247] This allows for information processing methods that, based on the user's device, can guarantee the identity of multiple individuals while enabling group settings and unified service usage.

[0248] (Item 11) A program that causes a computer to execute the information processing method described in item 1.

[0249] This allows the program to achieve the same effect as item 1.

[0250] (Item 12) A program that causes a computer to execute the information processing methods described in item 9.

[0251] This allows the program to achieve the same effect as item 1.

[0252] (Item 13) An information processing system (DIW system 5) comprising a first terminal owned by a user (user terminal 10) and a server (DIW server 20), The aforementioned first terminal is, The user specifies the services available to them, Obtain a group information record that includes, at a minimum, user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document. Based on the first facial image of the user included in the group information record and the second facial image of the user captured by the imaging unit (imaging unit 13) of the first terminal, facial matching is performed to authenticate that the user is the person who possesses the user's identification document. When the user is authenticated as the person himself / herself, present selection request information that requests the selection of the group members. Transmit first information including at least some information of the group member personal information corresponding to the selected group member and at least some information of the user personal information to an application for the first terminal to use the service or to a device of an operator providing the service. Transmit the first information to the server. The server Receives and holds the first information. Information processing system.

[0253] As a result, in the information processing system, the user as the representative of the group can use the service after confirming his / her identity, and each family member of the user and the family members belonging to the group can use the service. Also, the family member personal information is generated using the identity cards of the family members. Therefore, the information processing system can ensure the identities of multiple people and enable the user and the group members to safely use the service together. Also, by holding the first information in the server, the information provided to the above application and the operator's device can be accumulated, and for example, the information provided in a timely manner for reference to the user and family members can be provided.

[0254] (Item 14) An information processing system including a first terminal owned by a user, a server, and a second terminal (shelter terminal 30) that provides a service, The server Obtains a group information record including information about the user and group members belonging to the group to which the user belongs, at least including user personal information obtained from the user's identity card and including the user's basic information, and group member personal information obtained from the identity cards of the group members and including the basic information of the group members. Obtains a second face image of the user captured by the imaging unit (imaging unit 33) of the second terminal. Based on face verification of the first face image of the user included in the group information record and the second face image, authenticate that the user is the person who holds the user's identity card. When the user is authenticated as the person, at least some of the information included in the group information record is transmitted to the second terminal as second information. Store the second information. The second terminal Obtains the second information from the server and presents selection request information that includes the second information and requests selection of group members. The first terminal transmits first information including at least some of the group member personal information corresponding to the selected group member and at least some of the user personal information to an application for using the service that the first terminal has or to a device of an operator that provides the service. An information processing system.

[0255] Thereby, the information processing system enables the user as the representative of the group to confirm their identity and then enables the user and each family member of the family to which the user belongs to use the service. Also, family member personal information has been generated using the identity cards of family members. Therefore, the information processing system enables the user and group members to safely use the service collectively while guaranteeing the identities of multiple people. Further, the information processing system can accumulate the information provided to the above application or the operator's device by holding the second information in the server, and can provide, for example, the information provided for timely reference to the user or family members.

[0256] (Item 15) A server (DIW server 20) including a processor (processor 21) and a memory (memory 23), The processor Information relating to users who use the service and group members belonging to the group to which the user belongs, including at least user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document, and a group information record is obtained. A second facial image is obtained by a designated imaging unit (imaging unit 33) in which the user's face is captured. Based on the first facial image and the second facial image of the user included in the group information record, facial matching is performed to authenticate that the user is the person who possesses the user's identification document. If the user is authenticated as the person in question, at least some of the information contained in the group information record is transmitted to the terminal providing the service. The information transmitted to the terminal is stored in the memory (memory 23 or storage 24). server.

[0257] This allows the server to achieve the same effect as item 14.

[0258] Although various embodiments have been described above with reference to the drawings, it goes without saying that this disclosure is not limited to such examples. It is clear to those skilled in the art that various modifications or alterations can be conceived within the scope of the claims, and these will naturally also fall within the technical scope of this disclosure. Furthermore, the components of the above embodiments may be combined in any way without departing from the spirit of the invention.

[0259] Furthermore, the above embodiment may also apply to a program that realizes the functions of an information processing method, which is supplied to a computer (e.g., a user terminal 10) via a network or various storage media, and which is read and executed by the processor of this computer, as well as a recording medium on which this program is stored. [Industrial applicability]

[0260] The present disclosure is useful for an information processing method, a program, an information processing system, a server, etc. that can guarantee the identities of multiple people and implement group settings and batch service usage.

Description of Reference Numerals

[0261] 5 DIW System 10 User Terminal 11 Processor 12 Memory 13 Imaging Unit 14 Display and Operation Unit 15 Network Communication Unit 16 Short-Range Wireless Communication Unit 20 DIW Server 21 Processor 22 Communication Unit 23 Memory 24 Storage 30 Refuge Terminal 31 Processor 32 Memory 33 Imaging Unit 34 Display and Operation Unit 35 Network Communication Unit 36 Short-Range Wireless Communication Unit 40 Local Government Server 41 Processor 42 Communication Unit 43 Memory 44 Storage 110 Service Application 120 DIW Application 121 Service Master List Acquisition Unit 122 User Personal Information Acquisition Unit 123 Available Service Extraction Unit 124 Service Provision Condition Output Unit 125 Cooperation Consent Acquisition Unit 126 Face Verification Unit 127 Information Provision Request Reception Unit 128 Provided Information Extraction and Output Unit 129 Provided Information History Output Unit 130 Data Management Unit 211 Service Provision Conditions Notification Section 212 Service Master List Management Department 213 ID generation section 214 Integrated Personal Information Master List Management Department 215 Integrated Family Information Master List Management Department 216 Family-Linked Service List Management Department 217 Face Recognition Unit 218 Information Request Reception Department 219 Provided information extraction output section 220 Information Provision History Management Department 230 Data Management Department 311 Terminal ID Generation Unit 411 Evacuee Information Management Department 412 Authenticity Verification Department

Claims

1. An information processing method performed by at least one processor, Controlling the system to read basic group member information, which is the basic information of the group member, from the identification card of the group member belonging to the group to which the terminal user belongs, To acquire group member input information, which is information about the group members obtained by input operations to the input section of the terminal, The group information record is created by adding the group member personal information, which includes the group member basic information and the group member input information, to the user personal information, which includes information generated by reading the user's basic information from the user's identification document. The group information record is transmitted to an external device, The group information record is stored in the memory of the terminal, Information processing methods including

2. Based on the aforementioned basic group member information or the aforementioned group member input information, group member attribute information, which is attribute information relating to the group member, The group member personal information further includes the group member attribute information, The information processing method according to claim 1.

3. To present the following: information of a first item acquired by the external device from the personal information of the group members, information of the first purpose of use for utilizing the first item, and information prompting the acquisition of first consent for the use of the first item; This further includes obtaining information indicating a first intention to obtain the first consent, The information processing method according to claim 1 or 2.

4. To display the following information from the group information record: information of a second item designated for a service that uses at least a portion of the group information record; information of a second purpose for using the second item; and information prompting the acquisition of a second consent for the use of the second item. This further includes obtaining information indicating a second intention to obtain the second consent, The information processing method according to claim 3.

5. If the second information indicating intent indicates consent, the consent acquisition record information, which includes information identifying the group and information identifying the service, is transmitted to the external device as a record of obtaining the second consent. The information processing method according to claim 4.

6. If the second information indicating intent indicates consent, then based on the information identifying the service and the information identifying the group, identification information is generated that identifies the service and uniquely identifies the group. The information processing method according to claim 4.

7. The system further includes, for a specified group member, authenticating that the specified group member is the person who possesses the identification document by performing a facial matching based on the facial image of the group member included in the group member basic information and the facial image of the group member captured by the terminal, The information processing method according to claim 1 or 2.

8. The group member personal information and the user personal information are transmitted to an external authentication server. The authentication server further includes receiving a determination result from the authentication server regarding whether the user and the group member belong to the same group. The information processing method according to claim 1.

9. An information processing method performed by at least one processor, Specify the services available to the user who holds the device, Obtaining a group information record that includes, at a minimum, user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document; The user is authenticated as the person who possesses the user's identification document by facial matching based on the first facial image of the user included in the group information record and the second facial image of the user's face captured by a predetermined imaging unit. If the user is authenticated as the person in question, the user will be prompted to present selection request information requesting the selection of the group members, Transmitting first information, which includes at least a portion of the group member personal information corresponding to the selected group member and at least a portion of the user personal information, to an application on the terminal used to use the service or to a device of the service provider that provides the service, An information processing method having

10. The at least one processor is a processor provided in the terminal. The information processing method according to claim 1 or 9.

11. A program that causes a computer to execute the information processing method described in claim 1.

12. A program that causes a computer to execute the information processing method described in claim 9.

13. An information processing system comprising a first terminal owned by a user and a server, The first terminal is, The user specifies the services available to them, Obtain a group information record that includes, at a minimum, user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document. By performing facial matching based on the first facial image of the user included in the group information record and the second facial image of the user captured by the imaging unit of the first terminal, the system authenticates that the user is the person who possesses the user's identification document. If the user is authenticated as the person in question, the system will present selection request information requesting the selection of the group members. The first information, which includes at least a portion of the group member personal information corresponding to the selected group member and at least a portion of the user personal information, is transmitted to an application on the first terminal used to use the service, or to the equipment of the service provider that provides the service. The first information is transmitted to the server, The aforementioned server, The first information is received and held, Information processing system.

14. An information processing system comprising a first terminal owned by a user, a server, and a second terminal that provides services, The aforementioned server, Obtain a group information record that includes, at a minimum, user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document. The imaging unit of the second terminal acquires a second face image in which the user's face is captured. By facial matching based on the first facial image of the user included in the group information record and the second facial image, the user is authenticated as the person who possesses the user's identification document. If the user is authenticated as the person in question, at least some of the information contained in the group information record is transmitted to the second terminal as second information. The second information mentioned above is stored, The aforementioned second terminal is, The second information is obtained from the server, and selection request information including the second information is presented requesting the selection of the group members. The first information, which includes at least a portion of the group member personal information corresponding to the selected group member and at least a portion of the user personal information, is transmitted to an application on the first terminal used to use the service, or to the equipment of the service provider that provides the service. Information processing system.

15. A server comprising a processor and memory, The aforementioned processor, Information relating to users who use the service and group members belonging to the group to which the user belongs, including at least user personal information including the user's basic information obtained from the user's identification document, and group member personal information including the group member's basic information obtained from the group member's identification document, and a group information record is obtained. A second facial image is obtained in which the user's face is captured by a designated imaging unit. By facial matching based on the first facial image of the user included in the group information record and the second facial image, the user is authenticated as the person who possesses the user's identification document. If the user is authenticated as the person in question, at least some of the information contained in the group information record is transmitted to the terminal providing the service. The information transmitted to the terminal is stored in the memory. server.

Images