WO2023238369A1

WO2023238369A1 - Travelling support device, system and method, and computer-readable medium

Info

Publication number: WO2023238369A1
Application number: PCT/JP2022/023420
Authority: WO
Inventors: 大輔川崎
Original assignee: 日本電気株式会社
Priority date: 2022-06-10
Filing date: 2022-06-10
Publication date: 2023-12-14

Abstract

A travelling support device (1) according to the present invention is provided with: an acquisition unit (11) that acquires health condition information of a traveller; an authentication control unit (12) that controls biometric authentication for the traveller; an identification unit (13) that identifies medical history information concerning medicine, as well as an itinerary, for the traveller when the biometric authentication is successful; and a processing unit (14) that performs processing in accordance with the health condition information, the medical history information, and the itinerary. The processing unit (14) determines the content of a medical service, a medical institution (a place), and a consultation schedule in accordance with the health condition information, the medical history information, and the itinerary, presents these items of information to the traveller or a person concerned, and changes the existing itinerary so that the traveller can receive the medical service.

Description

TRAVEL ASSISTANCE DEVICES, SYSTEMS AND METHODS AND COMPUTER READABLE MEDIA

The present disclosure relates to a travel support device, system, method, and program.

In recent years, facial recognition technology has become applicable to various services. For example, Patent Document 1 discloses a technique for providing attribute information including medical information associated with a user who has successfully undergone facial authentication to a medical institution or the like.

International Publication No. 2021/240754

Here, there is a problem that when a traveler becomes unwell during a trip, it is difficult for the traveler or his or her related persons to appropriately judge the location and timing of medical services that the traveler should receive. . The reason for this is that the location and timing of medical services that a traveler who becomes unwell should receive should take into account not only the traveler's physical condition, but also the traveler's medical history information and future itinerary.

In view of the above-mentioned problems, the purpose of the present disclosure is to provide a travel support device, system, method, and program for supporting a traveler who becomes unwell during a trip to receive medical services at an appropriate place and timing. Our goal is to provide the following.

The travel support device according to the present disclosure includes:
an acquisition means for acquiring traveller's physical condition information;
authentication control means for controlling biometric authentication for the traveler;
Identification means for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully completed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
Equipped with

The travel support system according to this disclosure is
A storage device in which the traveler's biometric information, the medical history information regarding the traveler's medical care, and the itinerary are registered in association with each other;
a travel support device connected to the storage device;
Equipped with
The travel support device includes:
an acquisition means for acquiring physical condition information of the traveler;
authentication control means for controlling biometric authentication for the traveler using the storage device;
identification means for identifying the medical history information and the itinerary associated with the traveler who has successfully passed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
Equipped with

The travel support method according to this disclosure is
The computer is
Obtain information on the traveler's physical condition,
controlling biometric authentication for the traveler;
Identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
Processing is performed according to the physical condition information, the medical history information, and the itinerary.

The travel assistance program related to this disclosure is
Acquisition processing for acquiring traveler's physical condition information;
an authentication control process that controls biometric authentication for the traveler;
identification processing for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
Processing according to the physical condition information, the medical history information, and the itinerary;
have the computer execute it.

According to the present disclosure, it is possible to provide a travel support device, system, method, and program for supporting a traveler who becomes unwell during a trip to receive medical services at an appropriate place and timing.

1 is a block diagram showing the configuration of a travel support device according to the first embodiment; FIG. 3 is a flowchart showing the flow of the travel support method according to the first embodiment. FIG. 2 is a block diagram showing the configuration of a travel support system according to a second embodiment. 2 is a block diagram showing the configuration of an authentication device according to a second embodiment. FIG. FIG. 2 is a block diagram showing the configuration of a travel support device according to a second embodiment. 7 is a flowchart showing the flow of travel support information registration processing by the travel support device according to the second embodiment. 7 is a flowchart showing the flow of face information registration processing by the authentication device according to the second embodiment. FIG. 7 is a sequence diagram showing the flow of travel support processing according to the second embodiment. 7 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. 7 is a flowchart showing the flow of travel support information management processing according to the second embodiment. FIG. 7 is a diagram showing an example of an itinerary change proposal screen according to the second embodiment. FIG. 3 is a block diagram showing the configuration of an authentication device according to a third embodiment.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and for clarity of explanation, redundant explanation will be omitted as necessary.

<Embodiment 1>
FIG. 1 is a block diagram showing the configuration of a travel support device 1 according to the first embodiment. The travel support device 1 is an information processing device that provides travel support services to support travelers traveling based on a specific itinerary. Here, it is assumed that the traveler has previously registered his or her biological information, medical history information, and itinerary in a predetermined storage device in association with each other. Note that the traveler may register emergency contact information, such as a family member's phone number, in association with his or her biometric information, etc., in the storage device. Biometric information is information that uniquely identifies a traveler, and is feature information that indicates a feature amount acquired from the traveler. The medical history information is historical information regarding the medical care of the traveler, and includes records of medical services received by the traveler. The itinerary is schedule information including the dates, destinations, means of transportation to be used, etc. for the traveler's current trip. It is assumed that the travel support device 1 includes the storage device described above or is connected to the storage device.

The travel support device 1 includes an acquisition section 11, an authentication control section 12, an identification section 13, and a processing section 14. The acquisition unit 11 acquires the traveler's physical condition information. Here, physical condition information is information indicating the physical condition of the traveler during the trip, and may be a value input by the traveler, a companion, or a related person after determining the traveler's physical condition, or a value specified by the traveler. These are measured values etc. measured using a measuring device.

The authentication control unit 12 controls biometric authentication for travelers. For example, the authentication control unit 12 performs biometric authentication by comparing biometric information acquired from a traveler with biometric information registered in the storage device. Alternatively, the authentication control unit 12 may transmit the biometric information acquired from the traveler to an external authentication device to perform biometric authentication, and obtain the biometric authentication result.

The specifying unit 13 specifies the medical history information and itinerary regarding the medical care of the traveler who has successfully undergone biometric authentication. Specifically, the identification unit 13 identifies a traveler whose biometric authentication has been successfully performed by the authentication control unit 12, and retrieves medical history information and itinerary associated with the identified traveler's biometric information from the storage device. get.

The processing unit 14 performs processing according to physical condition information, medical history information, and itinerary. For example, the processing unit 14 may recommend medical services (contents, medical institutions (locations), consultation dates, etc.) to travelers or related parties according to physical condition information, medical history information, and itinerary. Additionally, the processing unit 14 may change an existing itinerary in order for the traveler to receive medical services. At that time, the processing unit 14 may arrange for changes to reservations for transportation, accommodation, restaurants, etc. included in the itinerary. Further, the processing unit 14 may present the changed itinerary to the traveler or related parties.

FIG. 2 is a flowchart showing the flow of the travel support method according to the first embodiment. First, the acquisition unit 11 acquires the traveler's physical condition information (S11). Next, the authentication control unit 12 controls biometric authentication for the traveler (S12). Then, the specifying unit 13 specifies the medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication (S13). Thereafter, the processing unit 14 performs processing according to the physical condition information, medical history information, and itinerary (S14).

As described above, in this embodiment, a traveler can accurately and easily transmit medical history information even when traveling through biometric authentication. Furthermore, based on the itinerary specified by biometric authentication, it is possible to take into account the traveler's current location (travel destination), future travel destination, and the duration of the travel. Therefore, taking into account the traveler's current physical condition, medical history information, and future plans, we decide whether to undergo medical examination or treatment at the destination, or whether to return to the place of residence and see a family doctor. Travelers, companions, local medical institutions, or family doctors can appropriately decide whether to receive medical treatment. Therefore, it is possible to support a traveler who becomes unwell during a trip to receive medical services at an appropriate place and timing.

Note that the travel support device 1 includes a processor, a memory, and a storage device as components not shown. Further, the storage device stores a computer program in which the processing of the travel support method according to the present embodiment is implemented. Then, the processor loads a computer program or the like from the storage device into the memory, and executes the computer program. Thereby, the processor realizes the functions of the acquisition section 11, the authentication control section 12, the identification section 13, and the processing section 14.

Alternatively, each component of the travel support device 1 may be realized by dedicated hardware. Further, a part or all of each component of each device may be realized by a general-purpose or dedicated circuit, a processor, etc., or a combination thereof. These may be configured by a single chip or multiple chips connected via a bus. A part or all of each component of each device may be realized by a combination of the circuits and the like described above and a program. Further, as the processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field-Programmable Gate Array), a quantum processor (a quantum computer control chip), etc. can be used.

Further, in the case where a part or all of each component of the travel support device 1 is realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged, It may also be distributed. For example, information processing devices, circuits, etc. may be realized as a client server system, a cloud computing system, or the like, in which each is connected via a communication network. Further, the functions of the travel support device 1 may be provided in a SaaS (Software as a Service) format.

<Embodiment 2>
The second embodiment is a specific example of the first embodiment described above. FIG. 3 is a block diagram showing the configuration of a travel support system 1000 according to the second embodiment. Here, it is assumed that at least the traveler U1 has already registered in the authentication device 200 and the travel support device 300 a facial image, medical history information, and itinerary in association with each other as biometric information of the traveler U1. Furthermore, it is assumed that the travelers U1 and U2 are traveling according to the registered itinerary, and that the traveler U1 becomes unwell at the travel destination A1. In this case, traveler U2 can be said to be a companion of traveler U1. Further, it is assumed that there is a medical institution in the area of the travel destination A1 where the doctor U3 can perform a medical examination, and that the medical institution has a medical institution terminal 103 that can be operated by the doctor U3. Further, it is assumed that the traveler's place of residence A2 indicates at least the place of residence of the traveler U1, where the traveler U1's family U4 is present. The user terminal 104 is an information terminal that can be operated by the traveler's family U4. In addition, in the area of the traveler's residence A2, there is a medical institution where the family doctor U5 of the traveler U1 can perform medical examination, and the medical institution has a medical institution terminal 105 that can be operated by the family doctor U5. Assume that there exists.

The travel support system 1000 provides a travel support service that supports the traveler to receive appropriate medical services in consideration of the traveler's medical history information and future itinerary even if the traveler becomes unwell during the trip. It is an information system for The travel support system 1000 includes

user terminals

101 and 104,

medical institution terminals

103 and 105, an authentication device 200, and a travel support device 300. Each of the

user terminals

101 and 104, the

medical institution terminals

103 and 105, the authentication device 200, and the travel support device 300 are communicably connected via a network N. Here, the network N is a communication network including a wireless communication line, such as the Internet, a wireless communication line network, a mobile phone line network, etc. Furthermore, the type of communication protocol used by the network N does not matter.

The user terminal 101 is a portable information terminal operated by the traveler U1 or U2, and is equipped with a wireless communication function, a camera, a touch panel, etc. The user terminal 101 is, for example, a smartphone, a tablet terminal, or the like. The user terminal 101 photographs the face of the traveler U1. Further, the user terminal 101 receives the physical condition information of the traveler U1 input by the traveler U1 or U2. Further, the user terminal 101 acquires location information indicating the current location using a GPS (Global Positioning System) function or the like. The user terminal 101 then transmits the face image, physical condition information, and location information of the traveler U1 to the travel support device 300 via the network N.

The user terminal 104 is an information processing device operated by the traveler's family U4. The user terminal 104 is a mobile phone, a smartphone, a tablet terminal, a notebook or desktop PC (Personal Computer), or the like.

The

user terminals

101 and 104 receive the changed itinerary from the travel support device 300 via the network N, or at least medical schedule information determined due to the traveler U1 becoming unwell during the trip. , display the received information, etc.

The

medical institution terminals

103 and 105 are information processing devices installed in medical institutions or carried by medical personnel such as doctors. The

medical institution terminals

103 and 105 are mobile phones, smartphones, tablet terminals, notebook or desktop PCs, and the like.

Medical institution terminals

103 and 105 receive a medical inquiry including traveler U1's physical condition information, current location, medical history information, and itinerary from travel support device 300 via network N, and display the received information. Furthermore, the

medical institution terminals

103 and 105 send back the answers input by the medical worker's operations to the travel support device 300 via the network N. Furthermore, the

medical institution terminals

103 and 105 may receive medical schedule information and display the received information.

The authentication device 200 is an information processing device that manages facial feature information of a user (traveler) and performs facial authentication. In addition, in response to a face authentication request received from the outside, the authentication device 200 matches the facial image or facial feature information included in the request with the facial feature information of each user, and requests the matching result (authentication result). Reply to original.

FIG. 4 is a block diagram showing the configuration of the authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210, a face detection section 220, a feature point extraction section 230, a registration section 240, and an authentication section 250. The face information DB 210 stores the user ID 211 and the facial feature information 212 of the user ID in association with each other. The facial feature information 212 is a set of feature points extracted from the facial image. Note that the authentication device 200 may delete the facial feature information 212 in the facial information DB 210 in response to a request from a user or the like corresponding to the facial feature information 212. Alternatively, the authentication device 200 may delete the facial feature information 212 after a certain period of time has passed since registration.

The face detection unit 220 detects a face area included in a registration image for registering face information, and outputs it to the feature point extraction unit 230. The feature point extraction unit 230 extracts feature points from the face area detected by the face detection unit 220 and outputs facial feature information to the registration unit 240. Further, the feature point extraction unit 230 extracts feature points included in the facial image received from the travel support device 300 or the like, and outputs facial feature information to the authentication unit 250.

The registration unit 240 issues a new user ID 211 when registering facial feature information. The registration unit 240 associates the issued user ID 211 with the facial feature information 212 extracted from the registered image and registers it in the facial information DB 210. The authentication unit 250 performs face authentication using the facial feature information 212. Specifically, the authentication unit 250 compares the facial feature information extracted from the facial image with the facial feature information 212 in the facial information DB 210. When the verification is successful, the authentication unit 250 identifies the user ID 211 associated with the verified facial feature information 212. The authentication unit 250 returns whether or not the facial feature information matches to the request source as a facial authentication result. Whether or not the facial feature information matches corresponds to the success or failure of authentication. Note that facial feature information matches (match exists) when the matching degree is equal to or higher than a threshold value. Further, the face authentication result shall include the specified user ID when the face authentication is successful.

FIG. 5 is a block diagram showing the configuration of the travel support device 300 according to the second embodiment. The travel support device 300 is an example of the travel support device 1 described above. The travel support device 300 at least performs processing related to the medical services that a traveler who becomes unwell during a trip should receive, thereby providing support to the traveler, related parties (such as family members, travel agencies), and medical personnel such as doctors at medical institutions. This is an information processing device that supports people. The travel support device 300 may be made redundant with multiple servers, and each functional block may be implemented with multiple computers.

The travel support device 300 includes a storage section 310, a memory 320, a communication section 330, and a control section 340. The storage unit 310 is an example of a storage device such as a hard disk or flash memory. The storage unit 310 stores a program 311 and travel support information 312. The program 311 is a computer program (travel support program) in which travel support processing and the like according to the second embodiment are implemented.

The travel support information 312 is management information for supporting a traveler's travel. The travel support information 312 stores a user ID 3121, personal attribute information 3122, medical history information 3123, itinerary 3124, and retention period 3125 in association with each other. In addition to the medical history information 3123 and the itinerary 3124, the travel support information 312 may further store insurance subscription information such as travel insurance or medical insurance in association with the user ID 3121. The user ID 3121 is identification information of a traveler who is a user. The user ID 3121 is information that is the same as or uniquely corresponds to the user ID 211 that is managed in the face information DB 210 of the authentication device 200 in association with the facial feature information 212. Therefore, the travel support information 312 can be said to be information associated with the traveler's biometric information via the user ID 3121. Furthermore, the storage unit 310 can be said to be an example of a storage device in which biological information of a traveler, medical history information regarding the medical care of the traveler, and itinerary are registered in association with each other.

Personal attribute information 3122 is attribute information that includes personal information of the traveler corresponding to user ID 3121. The personal attribute information 3122 may include, for example, age (date of birth), gender, place of residence (country of residence and address), emergency contact information such as family members, payment information, etc. Emergency contacts include, but are not limited to, telephone numbers, e-mail addresses, SNS (Social Network Service) accounts, and the like. The payment information includes credit card information, electronic money, code payment account information, bank debit account information, and the like.

The medical history information 3123 is an example of medical history information regarding the traveler corresponding to the user ID 3121. The medical history information 3123 includes, for example, medical examination history, treatment history, medication history, chronic disease, past medical history, medicines being taken, family doctor, family medical institution, region of the medical institution, and the like. Furthermore, the medical history information 3123 may include medical insurance enrollment status, contract details, contract period, and the like. Note that the medical history information 3123 is not limited to these.

Itinerary 3124 is information indicating the travel schedule of the traveler corresponding to user ID 3121. The itinerary 3124 includes, for example, dates, destinations, planned or reserved transportation, user IDs of companions, expenses, and the like. Examples of destinations include, but are not limited to, areas, planned or reserved accommodations and restaurants, reserved local tours, and other facilities visited. Examples of transportation means include, but are not limited to, airplanes, trains, buses, taxis, ships, and rental cars. Examples of costs include, but are not limited to, the cost of the entire itinerary 3124, various usage fees, reservation fees, cancellation fees, and the like.

The storage period 3125 is a period for storing the travel support information 312, facial feature information 212, etc. The retention period 3125 is preferably a period determined according to the itinerary 3124. The storage period 3125 is defined from the time of registration of the travel support information 312 to the storage expiration date. The storage expiration date is, for example, the last day of the itinerary 3124, or a predetermined period of time, such as one week or one month from the last day. The retention period 3125 is a period specified by the traveler at the time of applying for a trip or registering travel support information, or a period determined at the time of a contract for travel. For example, the retention period 3125 may be linked to the contract period of travel insurance. Further, the retention period 3125 may be arbitrarily changeable by a traveler, a travel agent, or the like. Note that the retention period 3125 may be indefinite.

Incidentally, the itinerary 3124 and the retention period 3125 may be collectively referred to as travel information. Further, one user ID 3121 may be associated with two or more pieces of travel information. That is, the travel support information 312 may be information that records the history of multiple travel information for the traveler corresponding to the user ID 3121.

The memory 320 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 340 operates. The communication unit 330 is a communication interface with the network N.

The control unit 340 is a processor that controls each component of the travel support device 300, that is, a control device. The control unit 340 loads the program 311 from the storage unit 310 into the memory 320 and executes the program 311. Thereby, the control unit 340 realizes the functions of the information management unit 341, the acquisition unit 342, the authentication control unit 343, the identification unit 344, and the processing unit 345.

The information management unit 341 manages the travel support information 312. Specifically, the information management section 341 registers the travel support information 312 in the storage section 310 in response to a request for registration of travel support information. When the information management unit 341 receives a request to update the retention period 3125 from the user terminal 101 or the like via the network N, the information management unit 341 may update the retention period 3125 according to the specified period. Further, the information management unit 341 deletes the facial feature information 212, the personal attribute information 3122, the medical history information 3123, and the itinerary 3124 after the retention period 3125 corresponding to the itinerary 3124 has elapsed. Note that the information management unit 341 may delete the corresponding travel support information 312 from the storage unit 310 in response to a request to delete travel support information. Furthermore, the information management unit 341 may calculate usage fees related to information management according to the retention period 3125.

The acquisition unit 342 acquires the physical condition information of the traveler U1 from the user terminal 101 or the like via the network N. Note that the acquisition unit 342 may register the acquired physical condition information in the travel support information 312 corresponding to the traveler U1. For example, the acquisition unit 342 may periodically acquire and register the physical condition information of the traveler U1 from the user terminal 101 or the like during the travel period of the traveler U1.

The authentication control unit 343 uses the face information DB 210 of the authentication device 200 to control face authentication for the traveler U1. In particular, the authentication control unit 343 according to this embodiment controls facial authentication of the traveler U1 using facial feature information extracted from the facial image of the traveler U1.

The specifying unit 344 refers to the travel support information 312 and specifies personal attribute information 3122, medical history information 3123, and itinerary 3124 associated with the traveler who has successfully passed facial authentication.

The processing unit 345 performs processing according to the acquired physical condition information, the specified medical history information, and the itinerary. It is preferable that the processing unit 345 performs processing by further taking the identified personal attribute information into account. This makes it possible to provide more appropriate medical services to travelers.

Specifically, the processing unit 345 determines medical schedule information regarding medical services that the traveler should receive based on the physical condition information, medical history information, and itinerary. Furthermore, the processing unit 345 may determine the medical schedule information by taking personal attribute information into consideration. Additionally, the processing unit 345 transmits a medical inquiry including physical condition information, medical history information, and itinerary to a medical institution specified based on the medical history information, and uses the information received from the medical institution in response to the medical inquiry. It is a good idea to determine medical schedule information based on this information. For example, the processing unit 345 notifies the medical institution terminal 105 of changes in the physical condition of the traveler U1, medical history information, current location (travel destination), future itinerary, and the like. This allows traveler U1's family doctor U5 to comprehensively consider traveler U1's physical condition, situation, itinerary, etc., and determine the content of medical services to be received, as well as the appropriate place and timing to receive medical services. . Note that the notification destination may be a medical institution terminal 103 at a medical institution near the travel destination A1. In this case, although the doctor U3 is not the personal physician of the traveler U1, the doctor U3 may decide whether emergency measures are necessary based on changes in the traveler U1's physical condition, medical history information, current location (travel destination), future itinerary, etc. It becomes possible to make judgments, etc.

Then, the processing unit 345 changes the itinerary to reflect the medical schedule information. As a result, when the traveler U1 who is unwell receives medical examination or treatment at the travel destination A1 or the like, the itinerary is rescheduled based on the medical service schedule of the traveler U1. Note that the processing unit 345 may additionally register medical schedule information in the travel support information 312 of the traveler U1. Furthermore, the processing unit 345 updates the itinerary 3124 of the travel support information 312 with the changed itinerary.

Specifically, the processing unit 345 determines medical schedule information including the dates and medical institutions at which the traveler should receive medical services, and adds information to the itinerary so that the traveler can receive medical services at the dates and medical institutions. It is advisable to perform a process of changing the existing reservation information included. This allows travelers to cancel or change reservations for reserved accommodations, local tours, transportation, etc. on their behalf, making it easier for travelers to receive medical services smoothly.

Additionally, the processing unit 345 may output the changed itinerary to an external device. Examples of external devices include, but are not limited to,

user terminals

101 and 104,

medical institution terminals

103 and 105, and the like. By the processing unit 345 transmitting the changed itinerary to the user terminal 101, it becomes easier for the traveler U1 and the accompanying traveler U2 to understand the changed itinerary. Further, the processing unit 345 transmits the changed itinerary to the user terminal 104, thereby notifying the family U4 of the traveler U1 who is unwell. This makes it easier for the family U4 to understand that the itinerary of the traveler U1 has been changed.

Furthermore, in this case, the processing unit 345 may transmit the physical condition information of the traveler U1, the reason for determining the location and schedule of the medical service by the doctor, etc. to the user terminal 104. As a result, the family member U4 is contacted in an emergency manner, and the family member U4 can easily understand that the traveler U1 has become unwell during the trip, the extent of the illness, the symptoms, the reason for the doctor's decision, etc.

Additionally, the processing unit 345 may output the medical schedule information to a terminal owned by the traveler U1 or a person related to the traveler U1. Specifically, the terminal possessed by the traveler U1 is the user terminal 101, and the terminal possessed by a person related to the traveler U1 (terminal of the person concerned) is at least one of the user terminal 104, the

medical institution terminals

103 and 105, etc. It will be. That is, the processing unit 345 preferably transmits the medical schedule information to at least one of the

user terminals

101 and 104, the

medical institution terminals

103 and 105, and the like.

FIG. 6 is a flowchart showing the flow of travel support information registration processing by the travel support device 300 according to the second embodiment. Here, a case will be described in which the traveler U1 registers his own travel support information before traveling. For example, the traveler U1 uses the user terminal 101 at the traveler's residence A2 to input personal attribute information, medical history information, itinerary, and retention period, and photographs his or her own face. Alternatively, the user terminal 101 may acquire a facial image of the traveler U1 photographed by an external photographing device. The user terminal 101 then transmits a registration request including the face image, personal attribute information, medical history information, itinerary, and storage period of the traveler U1 to the travel support device 300 via the network N.

In response, the travel support device 300 receives a registration request including the face image, personal attribute information, medical history information, itinerary, and storage period of the traveler U1 from the user terminal 101 at the travel destination A1 via the network N. (S101). Then, the travel support device 300 acquires a facial image from the registration request, and transmits a facial information registration request including the facial image to the authentication device 200 via the network N (S102). In response to this, the authentication device 200 performs face information registration processing.

FIG. 7 is a flowchart showing the flow of face information registration processing by the authentication device 200 according to the second embodiment. First, the authentication device 200 receives a face information registration request (S201). For example, the authentication device 200 receives a face information registration request from the travel support device 300 via the network N. Next, the face detection unit 220 detects a face area from the face image included in the face information registration request (S202). Then, the feature point extraction unit 230 extracts facial feature information (a set of feature points) from the face area detected in step S202 (S203). Then, the registration unit 240 issues the user ID 211 (S204). Then, the registration unit 240 registers the extracted facial feature information 212 and the issued user ID 211 in the facial information DB 210 in association with each other (S205). Thereafter, the registration unit 240 returns the issued user ID 211 to the request source (for example, the travel support device 300) (S206). Note that the authentication device 200 may perform face information registration processing in response to a face information registration request received from an arbitrary information registration terminal. For example, the information registration terminal is an information processing device such as a personal computer, a smartphone, or a tablet terminal.

Returning to FIG. 6, the explanation will be continued.
The travel support device 300 receives the face information registration result (user ID) from the authentication device 200 via the network N (S103). Then, the travel support device 300 associates the received user ID 3121 with the personal attribute information 3122, medical history information 3123, itinerary 3124, and storage period 3125 received in step S101 and registers them in the travel support information 312 (S104).

Note that the personal attribute information, medical history information, itinerary, and storage period do not necessarily need to be input into the user terminal 101 by the traveler U1. For example, the travel support device 300 may acquire the personal attribute information 3122 of the traveler U1 from a server of a public institution with the consent of the traveler U1, and register it in the travel support information 312. Further, the travel support device 300 may acquire the medical history information 3123 of the traveler U1 from a server of a medical institution, health insurance association, etc., with the consent of the traveler U1, and register it in the travel support information 312. Further, the travel support device 300 may acquire the itinerary 3124 contracted by the traveler U1 from a server such as a travel agency when the traveler U1 applies for (contracts) a trip, and may register it in the travel support information 312. At this time, the travel support device 300 may acquire the storage period specified by the traveler U1 or the storage period determined based on the contract, and register it in the travel support information 312.

FIG. 8 is a sequence diagram showing the flow of travel support processing according to the second embodiment. As a premise, at least the traveler U1 has registered travel support information and facial feature information in advance through the facial information registration process described above. It is assumed that travelers U1 and U2 are at travel destination A1, and traveler U1's physical condition worsens during the trip.

Therefore, the user terminal 101 acquires the physical condition information of the traveler U1 (S111). Specifically, the user terminal 101 receives text information and level values input from the traveler U1 indicating whether the user is in good or bad physical condition, the degree of symptoms, the state of injury, etc. as physical condition information. Alternatively, if input is difficult, such as when the traveler U1 is unconscious, unable to move even if conscious, or unable to operate due to an injury, the traveler U2 instead of the traveler U1 may request the traveler U2 from the user terminal 101. Person U1's physical condition information may also be input. In that case, the physical condition information may be information indicating the presence or absence of consciousness, symptoms, injury status, etc. of the traveler U1. Note that the traveler U2 may use an information terminal that he or she carries as the user terminal 101. That is, the user terminal 101 may be an information terminal carried by the traveler U2. Alternatively, the traveler U1 may wear a wearable device that can measure body surface temperature, pulse rate, heart rate, blood pressure, etc. In that case, the user terminal 101 acquires the measured value measured by the wearable device as physical condition information from the wearable device through short-range wireless communication or the like. Note that the user terminal 101 may be integrated with a wearable device.

Then, the user terminal 101 photographs the face of the traveler U1 (S112). Specifically, the user terminal 101 photographs the traveler U1 with a built-in camera in response to an operation by the traveler U1 or U2, and acquires a facial image. Note that the user terminal 101 may store the face image of the traveler U1 in a built-in storage device in advance. In that case, the user terminal 101 reads the face image of the traveler U1 from the built-in storage device.

Additionally, the user terminal 101 acquires the current location (S113). The user terminal 101 acquires position information using the GPS function as described above. Alternatively, the user terminal 101 may obtain the facility name, address, area name, etc. of the place of stay input by the traveler U1 or the like as the current location.

Thereafter, the user terminal 101 generates a travel support request that includes the face image photographed in step S112, the physical condition information acquired in step S111, and the current location acquired in step S113. Then, the user terminal 101 transmits a travel support request to the travel support device 300 via the network N (S114). In response, the travel support device 300 receives a travel support request from the user terminal 101 via the network N. Then, the travel support device 300 acquires a face image from the travel support request, and transmits a face authentication request including the face image to the authentication device 200 via the network N (S115). In response, the authentication device 200 performs face authentication processing (S116).

FIG. 9 is a flowchart showing the flow of face authentication processing by the authentication device 200 according to the second embodiment. First, the authentication device 200 receives a face authentication request from the travel support device 300 via the network N (S211). Next, the authentication device 200 extracts facial feature information from the facial image included in the facial authentication request, similarly to steps S202 and S203 described above. Then, the authentication unit 250 of the authentication device 200 compares the facial feature information extracted from the facial image included in the face authentication request with the facial feature information 212 of the facial information DB 210 (S212), and calculates the degree of matching. Then, the authentication unit 250 determines whether the degree of matching is greater than or equal to the threshold (S213). If the facial feature information matches, that is, if the degree of matching of the facial feature information is equal to or greater than the threshold, the authentication unit 250 identifies the user ID 211 associated with the facial feature information 212 (S214). Then, the authentication unit 250 returns the face authentication result including the fact that the face authentication was successful and the specified user ID 211 to the travel support device 300 via the network N (S215). If the matching degree is less than the threshold in step S213, the authentication unit 250 returns the face authentication result including the fact that the face authentication has failed to the travel support device 300 via the network N (S216).

Returning to FIG. 8, the explanation will be continued.
The travel support device 300 receives the face authentication result from the authentication device 200 via the network N. The travel support device 300 then determines whether or not face authentication has been successful. Specifically, the travel support device 300 refers to the face authentication result and determines that the face authentication has been successful if the face authentication result includes the user ID. Note that if it is determined that the face authentication has failed, the travel support device 300 may send a reply to the user terminal 101 via the network N to the effect that the user has failed the face authentication.

Here, the explanation will be continued assuming that the face authentication result includes the fact that the face authentication was successful and the user ID of the traveler U1. The travel support device 300 identifies personal attribute information 3122, medical history information 3123, and itinerary 3124 associated with the user ID 3121 included in the face authentication result from the travel support information 312 (S118).

Then, the travel support device 300 provides medical care based on the physical condition information and current location included in the travel support request, the date and time of receipt of the travel support request (or the current date and time), the specified personal attribute information 3122, medical history information 3123, and itinerary 3124. Schedule information is determined (S119). Specifically, first, the travel support device 300 identifies the medical institution or the like to which the medical care inquiry is to be made. The travel support device 300 then sends the medical inquiry including physical condition information, current location, date and time of receipt of the travel support request, personal attribute information 3122, medical history information 3123, and itinerary 3124 to the medical institution of the medical inquiry destination via the network N. Send to the institution terminal. The travel support device 300 then receives a reply from a doctor or the like via the network N from the medical institution terminal to which the medical care inquiry was made. The answer includes a judgment result by a doctor, etc. based on the medical inquiry. The travel support device 300 then determines medical schedule information based on the answer. Alternatively, the answer may include the medical schedule information itself. Here, the medical schedule information includes the schedule and medical institution at which the traveler U1 should receive medical services. For example, the medical schedule information may include various information regarding medical institutions, map information of the medical institution, route information from the traveler's current location to the medical institution, transportation means, required time, and the like. Further, medical services include, but are not limited to, examination, treatment, first aid, prescription of medicine, emergency transportation of traveler U1, surgery, hospitalization, and the like.

For example, the travel support device 300 may specify the family doctor U5 of the traveler U1, his medical institution, and the medical institution terminal 105 as the medical inquiry destination from the medical history information 3123. The travel support device 300 then transmits the medical inquiry to the medical institution terminal 105. In this case, the family doctor U5 inputs into the medical institution terminal 105 an answer determined from information included in the medical inquiry received by the medical institution terminal 105. The medical institution terminal 105 then returns the input answer to the travel support device 300.

For example, the family doctor U5 determines the urgency of medical services such as examination, treatment, and medication based on the traveler U1's physical condition information, date and time of reception, personal attribute information 3122, and medical history information 3123. The family doctor U5 then determines the content, schedule, and location of the medical service, taking into account the urgency, the current location of the traveler U1, and the future schedule of the itinerary 3124 (travel destination, remaining travel period, etc.). . For example, the family doctor U5 determines whether the traveler U1 will return to the place of residence A2 tomorrow or in two weeks, as well as the contents of the medical service, the schedule, etc., depending on the traveler U1's chronic illness and current symptoms. I can judge the location. If the traveler returns to his/her place of residence A2 tomorrow and his/her symptoms are mild, the traveler U1 may reply with the schedule so that he/she will receive a medical examination at his or her own medical institution after returning home.

For example, the family doctor U5 considers that medical services are highly urgent based on the medical examination history and current physical condition of the traveler U1, and the current travel destination A1 is more than a predetermined distance away from the traveler's residence A2. It is assumed that it is determined that the time required for U1 to return to residence A2 is too long. In this case, the family doctor U5 replies that the traveler U1 will receive medical services at a medical institution near the travel destination A1, which is the current location. On the other hand, the family doctor U5 determines that medical services are not urgent based on the traveler U1's examination history and current physical condition, or that specialized or advanced treatment is required. In some cases, it may be determined that the patient should receive treatment at a medical institution.

Alternatively, the travel support device 300 may specify a medical institution near the current location (travel destination A1) included in the travel support request as a medical inquiry destination. The travel support device 300 then transmits the medical inquiry to the medical institution terminal 103. In this case, the doctor U3 inputs into the medical institution terminal 103 an answer determined from information included in the medical inquiry received by the medical institution terminal 103. The medical institution terminal 103 then returns the input answer to the travel support device 300.

For example, the doctor U3 determines the urgency of medical services such as examination, treatment, and medication from the traveler U1's physical condition information, date and time of reception, personal attribute information 3122, and medical history information 3123. In particular, although the doctor U3 is not the personal doctor of the traveler U1, by referring to the personal attribute information 3122 and the medical history information 3123, it becomes easier to judge the urgency. Further, like the family doctor U5 described above, the doctor U3 determines the content, schedule, and location of the medical service, taking into consideration the urgency, the current location of the traveler U1, and the future schedule of the itinerary 3124.

Alternatively, the travel support device 300 may use an AI (Artificial Intelligence) model to determine medical schedule information. For example, the AI model uses the physical condition information and current location included in the travel support request, the date and time of receipt of the travel support request (current date and time), identified personal attribute information 3122, medical history information 3123, and itinerary 3124 as input data, and uses the medical schedule It is preferable that the information be output data. The AI model is preferably a trained model that has been machine learned using sets of input data and output data from various travelers as training data. Note that if it is determined by the family doctor U5, the doctor U3, or the above-mentioned AI model that the traveler should receive medical services at a medical institution near the travel destination, the travel support device 300 will receive medical services from a medical institution near the travel destination. It is preferable to generate the above-mentioned medical schedule information including various information regarding the medical treatment.

After step S119, the travel support device 300 adds medical schedule information to the itinerary 3124 and changes existing reservation information included in the itinerary 3124 (S120). At this time, the travel support device 300 updates the travel support information 312 with the changed itinerary 3124. Specifically, the travel support device 300 changes the subsequent itinerary 3124 according to the schedule and the location of the medical institution included in the medical schedule information. For example, the travel support device 300 may cancel or change reservations for accommodations, local tours, airplane flights, etc. as existing reservation information. Specifically, the travel support device 300 transmits a change request to an accommodation reservation system or the like. The travel support device 300 also transmits a change request to a local tour management system or the like. Further, the travel support device 300 transmits a change request to an airline company's reservation management system or the like. Alternatively, the travel support device 300 transmits a change request to a travel agency's management system or the like.

Then, the travel support device 300 transmits the changed itinerary 3124 including medical schedule information to the user terminal 101 via the network N (S121). This makes it easier for the traveler U1 or U2 to understand the changed itinerary 3124, especially the medical schedule information. For example, if it is determined that the traveler U1 should receive medical services at a medical institution near the travel destination A1, the transmitted medical schedule information may include various information regarding the medical institution near the travel destination A1, such as a map. Information, route information from the current location of the traveler U1 to the medical institution, transportation means, required time, etc. may be included. Therefore, it becomes easier for the traveler U1 or U2 to understand which medical institution to go to and how to go in an unfamiliar travel destination. Further, the traveler U1 or U2 may approve or change the medical schedule information and the changed itinerary 3124.

Additionally, the travel support device 300 transmits the changed itinerary 3124 including medical schedule information to the terminals of related parties, such as the

medical institution terminals

103 and 105 or the user terminal 104, etc. via the network N (S122). Thereby, for example, a medical worker at a medical institution who has received a medical inquiry can grasp the change result. The family doctor U5 knows when and which medical institution in the travel destination A1 the traveler U1, who is his patient, will receive a medical examination, etc., or when at the traveler's residence A2 such as the medical institution to which he belongs. You can know whether you will receive a medical examination, etc. In addition, the travel support device 300 sends information such as medical schedule information, physical condition information, and personal attribute information of the traveler U1 to the medical institution terminal 103 of a medical institution near the travel destination A1 that has been determined to receive medical services. , medical history information, etc. may be transmitted. As a result, the doctor U3 can use the medical schedule information to know in advance when the traveler U1 will receive a medical examination at the medical institution to which the doctor U3 belongs, information about the traveler U1, etc., and limit preparations such as preparations for reception. It can be done efficiently in a limited amount of time. Further, the family doctor U5 and the doctor U3 at the travel destination can cooperate in treating the traveler U1 based on the medical schedule information. In addition, the family U4 and the like of the traveler U1 can quickly learn that the traveler U1 has become unwell during the trip, changes to the itinerary, and the date and location of receiving medical services. Therefore, it becomes easier for the traveler's family U4 and others to arrive at the medical institution sooner, and to make preparations for meeting them at the airport when returning home.

Note that the order of steps S111 to S113 is not limited to that shown in FIG. Further, the user terminal 101 may periodically acquire physical condition information, and when detecting an abnormality in the physical condition information, notify the traveler U1 or U2 of this fact. For example, the user terminal 101 may display on the screen that the traveler U1 has become unwell. After that, steps S112 and S113 may be executed.

Further, the travel support request in step S114 may include the date and time when the physical condition information of the traveler U1 was acquired and the date and time when a change in physical condition was detected, and the travel support device 300 processes the date and time as the current date and time. It's okay.

Also, instead of steps S111 to S117, the following processing may be performed. For example, the user terminal 101 transmits a face authentication request including the face image of the traveler U1 to the travel support device 300 or the authentication device 200 via the network N during a trip, and receives the face authentication result. When the face authentication is successful, the user terminal 101 internally stores the face authentication result including the fact that the authentication was successful and the user ID. Thereafter, when the user terminal 101 detects a change in the physical condition information of the traveler U1 as described above, the user terminal 101 sends a travel support request including the above facial recognition result, physical condition information, and current location to the travel support via the network. Send to device 300. Then, the travel support device 300 may identify the user ID whose face authentication was successful from the face authentication result included in the received travel support request, and execute steps S118 and subsequent steps.

In addition, in FIG. 8 described above, an example was shown in which the physical condition information of the traveler U1 during the trip is inputted by the traveler U1 himself or the traveler U2 who is traveling with him or obtained by a wearable device or the like in step S111. . If it is determined that the traveler should receive medical services at a medical institution near the travel destination, the travel support device 300 can suggest information on medical institutions at the travel destination that are suitable for the traveler.

Note that in this embodiment, step S111 does not necessarily need to be executed. For example, if the traveler U1 becomes unwell during the trip, step S111 may not be executed, physical condition information may not be transmitted in S114, and medical schedule information may be determined in S119 without using the physical condition information. When it is determined that the traveler should receive medical services at a medical institution near the travel destination based on the current location, medical history information, and itinerary, the travel support device 300 provides various information regarding the medical institution at the travel destination. , you may suggest it to travelers and companions. In other words, in this case as well, it becomes easier for the traveler U1 or U2 to understand which medical institution to go to and how to go in an unfamiliar travel destination. Then, in response to the traveler U1 receiving a medical examination at a medical institution in the proposed travel destination, a doctor U3 or the like of the medical institution transmits the physical condition information of the traveler U1 to the travel support device via the medical institution terminal 103. 300 may be entered. Thereby, the family doctor U5 and the doctor U3 at the travel destination can collaborate to treat the traveler U1 based on the medical schedule information.

FIG. 10 is a flowchart showing the flow of travel support information management processing according to the second embodiment. For example, the information management unit 341 of the travel support device 300 may execute the management process periodically or at the timing when a specific itinerary is completed.

First, the information management unit 341 determines whether the retention period corresponding to the itinerary for each traveler has elapsed (S301). For example, the information management unit 341 refers to the travel support information 312 and determines whether the retention date of the retention period 3125 associated with the user ID 3121 of the traveler U1 exceeds the current date. The information management unit 341 similarly determines the retention periods of other travelers U2 and the like.

If it is determined that the retention period has elapsed, the information management unit 341 transmits a request to delete the user ID and facial feature information to the authentication device 200 (S302). For example, the information management unit 341 transmits a deletion request including the user ID 3121 of the traveler U1 to the authentication device 200 via the network N. In response, the authentication device 200 deletes the set of the user ID 211 corresponding to the user ID 3121 included in the received deletion request and the facial feature information 212 associated with the user ID 211 from the facial information DB 210. After deletion, the authentication device 200 may send a reply to that effect to the travel support device 300.

Additionally, in parallel with step S302, the information management unit 341 deletes the travel support information 312 corresponding to the traveler U1 from the storage unit 310 (S303). By combining steps S302 and S303, personal information can be strictly managed (protected). Note that travel support information is not deleted for a traveler for whom it is determined in step S301 that the retention period has not elapsed. That is, the travel support information 312 and facial feature information 212 are retained within the retention period.

Note that the information management unit 341 may delete the set of itinerary 3124 and retention period 3125 from the travel support information 312 and retain the user ID 3121, personal attribute information 3122, and medical history information 3123. In this case, the next time the same traveler travels, this can be achieved by adding the set of itinerary 3124 and storage period 3125 to the existing travel support information 312, which saves the trouble of inputting data for the second and subsequent travellers. Can be simplified. Furthermore, the medical history information 3123 may be updated by the next time the traveler travels, as a result of the traveler receiving a medical examination or the like after the travel, unrelated to the travel. On the other hand, facial feature information may change over time, and may be re-registered each time the user travels.

Alternatively, the information management unit 341 may execute step S302 and not execute S303. In other words, in the case of a second or subsequent trip, the information management unit 341 registers the facial feature information 212 in the facial information DB 210 in association with the existing user ID 3121 (user ID 211) in the travel support information registration process of FIG. , the itinerary 3124 and the retention period 3125 may be additionally registered in the travel support information 312. In this case, a plurality of sets of itineraries and retention periods (travel information) are registered for each traveler, and the travel information is accumulated as a history. Therefore, it can be used for analysis of travel information, etc. Furthermore, the travel information history may be provided to a travel agency or the like.

Here, the retention period may be arbitrarily selected by the traveler, travel agent, etc. from a plurality of patterns. For example, pattern A sets the storage expiration date as the last day of the itinerary, pattern B sets the storage expiration date as one month from the last day of the itinerary, and pattern C sets the storage expiration date as one year from the last day of the itinerary. , pattern D may have an indefinite storage period. In other words, the retention period may be linked to the organization of the itinerary.

Additionally, the traveler U1 etc. may register travel support information up to 24 hours before departure. For example, the traveler U1 or the like may register travel support information when making a reservation for a trip, or when checking in at the beginning of an itinerary.

Furthermore, the information management unit 341 may calculate the usage fee for the travel support service according to this embodiment according to the retention period. For example, the information management unit 341 may calculate the retention period by adding 500 yen per week. Furthermore, if the storage period is one year, the information management unit 341 may calculate the usage fee as 1500 yen as an annual service.

As described above, in this embodiment, even if a traveler becomes unwell during a trip, personal attribute information associated with the membership number (user ID), medical history information such as underlying diseases, and itinerary (travel medical institutions and related parties can obtain information such as schedules, accommodation hotels, etc. Therefore, appropriate measures can be taken for people who are not feeling well while traveling. This means that even if you become ill or injured while traveling, you can be provided with a high level of medical personal care. In particular, elderly people have a desire to travel, but they tend to hesitate in applying for travel due to health concerns. This embodiment can also be used as a monitoring service while traveling, making it easier for people with health concerns to apply for long-term or distant trips with peace of mind, and making it easier to continue traveling.

In addition, if a person who is unwell receives medical attention or is hospitalized while traveling, the service can cancel hotel and restaurant reservations included in the itinerary or suggest rescheduling of the itinerary. In addition, it is possible to propose the content, schedule, location, etc. of medical services, taking into account the schedule for use of transportation such as flights on the return trip, and the schedule of destinations to be visited. Additionally, travelers and related parties can select the content of the proposal.

FIG. 11 is a diagram showing an example of the itinerary change proposal screen 4 according to the second embodiment. The itinerary change proposal screen 4 is displayed on the user terminal 101 in response to step S121 in FIG. 8, for example. The itinerary change proposal screen 4 includes a current itinerary 41, a medical schedule information proposal 42, an itinerary change proposal 43, and an approval button 44. The current itinerary 41 includes the travel schedule of the traveler U1 etc. from the current time to the last day and the reservation status of each schedule. This example shows that there are reservations for a taxi to restaurant a, a taxi to hotel c, an overnight stay at hotel c, a taxi to airport d, and a flight e to return home. The medical schedule information proposal 42 is determined by the travel support device 300 and includes the proposed medical institution h, dates of medical examinations, etc. The itinerary change suggestion 43 is information that proposes a changed itinerary based on the medical schedule information. In this example, the taxi ride to restaurant a, hotel c, and stay at hotel c on X 3rd are canceled, the patient is hospitalized at medical institution h from X 3rd to X 6th, and Indicates that the taxi to travel to airport d and the flight e to return home will be rebooked. The consent button 44 is a button for consenting to changes in medical schedule information and itinerary, as well as cancellations and changes to various reservations. When the traveler U1 or U2 presses the accept button 44, the user terminal 101 sends a proposal from the current itinerary 41 to the proposal 42 for medical schedule information and the proposal 43 for changing the itinerary to the travel support device 300 via the network N. Send your approval. In response, the travel support device 300 performs proxy processing of various reservation cancellation and change procedures, notifies medical institutions, updates the itinerary 3124, and the like.

Additionally, you can inquire about medical schedule information in advance to your family doctor or a doctor near your travel destination. At this time, by providing the doctor (medical institution) with the travel itinerary in addition to the physical condition information, personal attribute information, and medical history information during the trip, the doctor etc. We can give advice (answers) on whether or not you should return to the ground for treatment.

Furthermore, in the case of travelers from overseas, the travel support information of this embodiment can be applied by using passport information as personal attribute information and by associating biometric information, passport information, medical history information, itinerary, etc. . Furthermore, by adding overseas travel insurance and medical insurance to travel support information and determining medical schedule information in consideration of the itinerary and insurance information, more appropriate medical services can be applied to overseas travelers.

Furthermore, when changing the itinerary based on the medical schedule information, it is highly convenient because it makes reservations for return transportation on your behalf. In this case, transportation operating companies such as airlines and travel agencies will be able to easily identify seats on return flights that have been canceled due to poor physical condition, etc., making it easier to operate return flights efficiently and take measures against overbooking. Become.

In addition, we will notify emergency contacts such as family members of those who are unwell about their physical condition during the trip, the fact that they will receive medical services due to their unwellness, the location of the medical institution (near the destination of travel or residence), the medical treatment schedule, etc. . Therefore, the person concerned at the emergency contact point can know in advance the condition of the person who is unwell and the upcoming schedule, etc., making it easier to take action.

Note that the travel support device 300 may, for example, consider the following cases regarding how to acquire the traveler's physical condition information and where to send the medical schedule information. However, this is not limited to the following cases.

Case 1) Physical condition information is transmitted from a user terminal, and medical schedule information is transmitted to the user terminal and medical institution terminal First, the traveler U1 or U2 inputs the physical condition information of the traveler U1 into the user terminal 101. In response, the user terminal 101 transmits the physical condition information, face image, and current location to the travel support device 300 based on steps S111 to S113 in FIG. 8 (S114). Then, the travel support device 300 transmits the face authentication results, personal attribute information, medical history information, and medical schedule information determined based on the itinerary from steps S115 to S119 to the user terminal 101 (S121). Here, when a medical institution at the travel destination is recommended, the traveler U1 or U2 is also provided with information such as the location of the medical institution at the travel destination, as described above. In addition, if the recommended medical institution and this travel support service are system-linked, the travel support device 300 sends medical schedule information, physical condition information of the traveler U1, and personal attribute information to the recommended medical institution terminal. , send medical history information, etc.

Case 2) Physical condition information is transmitted from a medical institution terminal, and the destination of the medical schedule information is a medical institution terminal First, the traveler U1 and the like undergo a medical examination at a medical institution near the travel destination. Then, a medical worker such as a doctor U3 at the medical institution inputs the physical condition information of the traveler U1 into the medical institution terminal. Alternatively, the testing device of the medical institution may test the traveler U1, acquire physical condition information and various measurement results of the traveler U1, and input them to the medical institution terminal. The medical institution terminal also acquires a facial image of the traveler U1. The medical institution terminal then transmits the physical condition information of the traveler U1, various measurement results, a facial image, and the location information of the medical institution (the current location of the traveler U1) to the travel support device 300. The travel support device 300 then performs facial recognition based on the received facial image, identifies personal attribute information, medical history information, and itinerary of the traveler U1 based on the facial recognition results, and determines medical schedule information based on these. . The travel support device 300 then transmits the determined medical schedule information to the medical institution terminal.

<Embodiment 3>
The third embodiment is a modification of the second embodiment described above. In the third embodiment, face recognition is possible not only when the eyes are open but also when the eyes are closed. For example, if a traveler loses consciousness at a travel destination, a companion or emergency personnel may take a photo of the traveler's face with their eyes closed and perform facial recognition to confirm the traveler's identity. Therefore, the face information DB according to the third embodiment stores, for each user, facial feature information generated based on facial images taken with the eyes closed, in addition to facial feature information with the eyes open. It is to be registered. In the third embodiment, face authentication is possible for both a face image with the eyes open and a face image with the eyes closed.

FIG. 11 is a block diagram showing the configuration of an authentication device 200a according to the third embodiment. In the authentication device 200a, a plurality of facial feature information 2121 to 212n (n is a natural number of 2 or more) are associated with one user ID 211 in the facial information DB 210, as compared to FIG. 4 described above. In addition, if the face information registration request includes a plurality of face images, for example, a face image with eyes open and a face image with eyes closed, the registration unit 240a stores facial feature information extracted from each face image. 2121 to 212n are registered in the face information DB 210 in association with the newly issued user ID 211. Alternatively, if the face information registration request specifies an already issued user ID, the registration unit 240a does not issue a new user ID, and uses the facial features extracted from the face image included in the face information registration request. The information and the specified user ID may be registered in the face information DB 210 in association with each other.

For example, in the travel support information registration process described above, the traveler U1 or a person related to the traveler U1 uses the user terminal 101 or the like to photograph the face of the traveler U1 with his eyes closed. Then, the user terminal 101 or the like transmits a registration request including a facial image of the traveler U1 with his eyes closed to the travel support device 300 via the network N. The travel support device 300 transmits a facial information registration request including the facial image included in the registration request to the authentication device 200 via the network N. At this time, if the registration request includes two or more facial images, the travel support device 300 includes the two or more facial images in the facial information registration request. Alternatively, if one or more pieces of facial feature information of the traveler U1 have been registered, the travel support device 300 identifies the user ID 3121 in the travel support information 312 of the traveler U1 based on the user ID or personal attribute information included in the registration request. can. In this case, the travel support device 300 specifies the identified user ID 3121 and transmits a face information registration request. As a result, facial feature information with eyes closed is registered in the facial information DB 210. Therefore, the information management unit 341 corresponds a plurality of pieces of biometric information including facial feature information generated based on a facial image taken with the traveler's eyes closed, and the medical history information and itinerary of the traveler. It can be said to be attached and registered in a storage device for biometric authentication.

After that, when the traveler U1 loses consciousness during the trip, the traveler U2 who is accompanying him, an emergency worker, etc. use the user terminal 101 to photograph the face of the traveler U1 (in a state where he wants to close his eyes). , it is assumed that physical condition information is input. At this time, the user terminal 101 transmits a travel support request including the physical condition information and the current location as well as a face image of the traveler U1 with his eyes closed to the travel support device 300. The travel support device 300 performs face authentication based on the face image included in the travel support request. As described above, since the facial feature information of the traveler U1 with his eyes closed has already been registered in the facial information DB 210, the facial authentication is successful and the travel support process described above is performed thereafter.

In this way, according to this embodiment, even if a traveler loses consciousness while traveling, in addition to the personal attribute information and medical history information of the traveler, the future itinerary can be identified, and related parties such as medical institutions can identify the traveler's future itinerary. can be provided to Therefore, the content, location, and schedule of appropriate medical services can be determined, and the itinerary and reservation information can be changed as necessary. In other words, the same effects as in the second embodiment described above can be achieved.

<Other embodiments>
Since each of the above-mentioned embodiments uses biometric authentication, for identity verification authentication, a ticket or paper with a code indicating identity verification information printed on it, or an IC (Integrated Circuit) card on which identity verification information is recorded is used. It is also suitable for situations where it is difficult for the user to take out the device, smartphone, etc. Examples of such situations include situations where the person has a lot of equipment and baggage for skiing, scuba diving, mountain climbing, etc., and a situation where the person is carrying a tray at a bakery or soba restaurant.

Furthermore, in each of the embodiments described above, in the case of a trip with multiple people, it is not necessarily necessary to register biometric information for all members of the trip. For example, in the case of a family trip, only the representative may be registered in the travel support information or face information DB. Alternatively, only elderly people or people with chronic illnesses may be registered in the travel support information or face information DB. Furthermore, in the case of a trip with multiple people, there is a possibility that the members may change after registration. Even in such a case, only some members may use this travel support service.

Furthermore, the registration operation in the travel support information registration process described above may be performed by someone other than the registrant himself/herself. For example, the registration operation for elderly people and young children who do not carry a user terminal or have difficulty operating it may be performed by a family member, a person scheduled to accompany the user on a trip, a staff member of a travel agency, or the like.

Incidentally, in the above-described embodiment, the person identification authentication (person identification authentication, person authentication, person identification processing, etc.) was described as face authentication, but other biometric authentication using biometric information may be used. For biometric authentication and biometric information, other techniques that use captured images of people can be applied. For example, biometric information may include data (feature amounts) calculated from physical characteristics unique to an individual, such as fingerprints, voice prints, veins, retinas, iris of pupils, and patterns on the palm of the hand. In addition, for biometric authentication, feature information indicating a person's physical characteristics is extracted from a photographed image of a part of the user's body, and the extracted feature information is compared with pre-registered feature information to determine the match. Authentication may be deemed to have been successful if the value is greater than or equal to a threshold value. For example, biometric authentication may be based on a person's external shape. In this case, the characteristic information is information regarding the external shape of the person, for example, information indicating characteristics such as body shape, height, clothing, etc. Furthermore, biometric authentication may include ear acoustic authentication.

Note that in the second and third embodiments described above, the authentication device 200 (or 200a) and the travel support device 300 are described as separate information processing devices, but they may be the same. For example, the travel support device 300 may further associate and register facial feature information with the user ID 3121 of the travel support information 312. In that case, the control unit 340 may further include the functions of the face detection unit 220, feature point extraction unit 230, registration unit 240, and authentication unit 250 shown in FIG.

In the examples above, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored on a non-transitory computer readable medium or a tangible storage medium. By way of example and not limitation, computer readable or tangible storage media may include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD - Including ROM, digital versatile disc (DVD), Blu-ray disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc storage or other magnetic storage device. The program may be transmitted on a transitory computer-readable medium or a communication medium. By way of example and not limitation, transitory computer-readable or communication media includes electrical, optical, acoustic, or other forms of propagating signals.

Note that the present disclosure is not limited to the above embodiments, and can be modified as appropriate without departing from the spirit. Further, the present disclosure may be implemented by appropriately combining the respective embodiments.

Part or all of the above embodiments may be described as in the following additional notes, but are not limited to the following.
(Appendix A1)
an acquisition means for acquiring traveller's physical condition information;
authentication control means for controlling biometric authentication for the traveler;
Identification means for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully completed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
A travel support device equipped with:
(Appendix A2)
The processing means includes:
The travel support device according to appendix A1, wherein medical schedule information regarding medical services that the traveler should receive is determined based on the physical condition information, the medical history information, and the itinerary.
(Appendix A3)
The processing means includes:
The travel support device according to appendix A2, wherein the itinerary is changed to reflect the medical schedule information.
(Appendix A4)
The processing means includes:
determining the medical schedule information including the date and medical institution at which the traveler should receive the medical service;
The travel support device according to appendix A3, which performs a process of changing existing reservation information included in the itinerary so that the traveler can receive the medical service on the itinerary and at the medical institution.
(Appendix A5)
The processing means includes:
The travel support device according to appendix A3 or A4, which outputs the changed itinerary to an external device.
(Appendix A6)
The processing means includes:
The travel support device according to any one of appendices A2 to A5, wherein the medical schedule information is output to a terminal owned by the traveler or a person related to the traveler.
(Appendix A7)
The processing means includes:
Sending an inquiry including the physical condition information, the medical history information, and the itinerary to a medical institution specified based on the medical history information;
The travel support device according to any one of appendices A2 to A6, wherein the medical schedule information is determined based on information received from the medical institution in response to the inquiry.
(Appendix A8)
The identifying means further identifies personal attribute information associated with the traveler who has successfully passed the biometric authentication,
The travel support device according to any one of appendices A1 to A7, wherein the processing means performs the processing by further taking into account the personal attribute information.
(Appendix A9)
The biological information and the medical history information of the traveler are retrieved from the storage device registered for the biometric authentication by associating the traveler's biometric information, the medical history information, and the itinerary after a storage period according to the itinerary has elapsed. The travel support device according to any one of appendix A1 to appendix A8, further comprising information management means for deleting the itinerary.
(Appendix A10)
The travel support device according to appendix A9, wherein the information management means calculates a usage fee related to information management according to the retention period.
(Appendix A11)
The information management means includes a plurality of biometric information including facial feature information generated based on a face image taken with the traveler's eyes closed, the medical history information of the traveler, and the itinerary. The travel support device according to appendix A9 or A10, wherein the travel support device is associated with and registered in the storage device for the biometric authentication.
(Appendix B1)
A storage device in which the traveler's biometric information, the medical history information regarding the traveler's medical care, and the itinerary are registered in association with each other;
a travel support device connected to the storage device;
Equipped with
The travel support device includes:
an acquisition means for acquiring physical condition information of the traveler;
authentication control means for controlling biometric authentication for the traveler using the storage device;
identification means for identifying the medical history information and the itinerary associated with the traveler who has successfully passed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
A travel support system equipped with
(Appendix B2)
The processing means includes:
The travel support system according to Appendix B1, wherein medical schedule information regarding medical services that the traveler should receive is determined based on the physical condition information, the medical history information, and the itinerary.
(Appendix C1)
The computer is
Obtain information on the traveler's physical condition,
controlling biometric authentication for the traveler;
Identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
performing processing according to the physical condition information, the medical history information, and the itinerary;
Travel support methods.
(Appendix D1)
Acquisition processing for acquiring traveler's physical condition information;
an authentication control process that controls biometric authentication for the traveler;
identification processing for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
Processing according to the physical condition information, the medical history information, and the itinerary;
A non-transitory computer-readable medium that stores a travel assistance program that causes a computer to execute.

Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above embodiments (and examples). The configuration and details of the present invention can be modified in various ways that can be understood by those skilled in the art within the scope of the present invention.

1 Travel support device 11 Acquisition unit 12 Authentication control unit 13 Identification unit 14 Processing unit 1000 Travel support system A1 Travel destination A2 Traveler's place of residence N Network U1 Traveler U2 Traveler U3 Doctor U4 Traveler's family U5 Family doctor 101 User Terminal 103 Medical institution terminal 104 User terminal 105 Medical institution terminal 200 Authentication device 210 Face information DB
211 User ID
212 Facial feature information 220 Face detection section 230 Feature point extraction section 240 Registration section 250 Authentication section 200a Authentication device 2121 Facial feature information 212n Facial feature information 240a Registration section 300 Travel support device 310 Storage section 311 Program 312 Travel support information 3121 User ID
3122 Personal attribute information 3123 Medical history information 3124 Itinerary 3125 Storage period 320 Memory 330 Communication section 340 Control section 341 Information management section 342 Acquisition section 343 Authentication control section 344 Identification section 345 Processing section 4 Itinerary change proposal screen 41 Current itinerary 42 Medical Suggestions for schedule information 43 Suggestions for itinerary changes 44 Accept button

Claims

an acquisition means for acquiring traveller's physical condition information;
authentication control means for controlling biometric authentication for the traveler;
Identification means for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully completed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
A travel support device equipped with:
The processing means includes:
The travel support device according to claim 1, wherein medical schedule information regarding medical services that the traveler should receive is determined based on the physical condition information, the medical history information, and the itinerary.
The processing means includes:
The travel support device according to claim 2, wherein the itinerary is changed to reflect the medical schedule information.
The processing means includes:
determining the medical schedule information including the date and medical institution at which the traveler should receive the medical service;
The travel support device according to claim 3, wherein existing reservation information included in the itinerary is changed so that the traveler can receive the medical service on the itinerary and at the medical institution.
The processing means includes:
The travel support device according to claim 3 or 4, wherein the changed itinerary is output to an external device.
The processing means includes:
The travel support device according to any one of claims 2 to 5, wherein the medical schedule information is output to a terminal owned by the traveler or a person related to the traveler.
The processing means includes:
Sending an inquiry including the physical condition information, the medical history information, and the itinerary to a medical institution specified based on the medical history information;
The travel support device according to any one of claims 2 to 6, wherein the medical schedule information is determined based on information received from the medical institution in response to the inquiry.
The identifying means further identifies personal attribute information associated with the traveler who has successfully passed the biometric authentication,
The travel support device according to any one of claims 1 to 7, wherein the processing means performs the processing by further taking into account the personal attribute information.
The biological information and the medical history information of the traveler are retrieved from the storage device registered for the biometric authentication by associating the traveler's biometric information, the medical history information, and the itinerary after a storage period according to the itinerary has elapsed. The travel support device according to any one of claims 1 to 8, further comprising information management means for deleting the itinerary.
The travel support device according to claim 9, wherein the information management means calculates a usage fee related to information management according to the retention period.
The information management means includes a plurality of biometric information including facial feature information generated based on a face image taken with the traveler's eyes closed, the medical history information of the traveler, and the itinerary. The travel support device according to claim 9 or 10, wherein the information is associated with the information and registered in the storage device for the biometric authentication.
A storage device in which the traveler's biometric information, the medical history information regarding the traveler's medical care, and the itinerary are registered in association with each other;
a travel support device connected to the storage device;
Equipped with
The travel support device includes:
an acquisition means for acquiring physical condition information of the traveler;
authentication control means for controlling biometric authentication for the traveler using the storage device;
identification means for identifying the medical history information and the itinerary associated with the traveler who has successfully passed the biometric authentication;
processing means that performs processing according to the physical condition information, the medical history information, and the itinerary;
A travel support system equipped with
The processing means includes:
The travel support system according to claim 12, wherein medical schedule information regarding medical services that the traveler should receive is determined based on the physical condition information, the medical history information, and the itinerary.
The computer is
Obtain information on the traveler's physical condition,
controlling biometric authentication for the traveler;
Identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
performing processing according to the physical condition information, the medical history information, and the itinerary;
Travel support methods.
Acquisition processing for acquiring traveler's physical condition information;
an authentication control process that controls biometric authentication for the traveler;
identification processing for identifying medical history information and itinerary regarding the medical care of the traveler who has successfully passed the biometric authentication;
Processing according to the physical condition information, the medical history information, and the itinerary;
A non-transitory computer-readable medium that stores a travel assistance program that causes a computer to execute.