Supporter Introduction Method

Abstract

To introduce a supporter to an impaired person requiring support.SOLUTION: A supporter introduction method includes: an acquisition step of acquiring user information concerning a user who uses a vehicle; a determination step of determining whether or not the user is an impaired person on the basis of the user information; an identifying step of identifying the position and time of support desired by the user from the user information if it is determined that the user is an impaired person; and a matching step of matching the user with a supporter capable of supporting the user on the basis of the position and the time of the desired support.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to the technical field of supporter introduction methods.

Background Art

[0002] For example, a vehicle dispatching service has been proposed in which the dispatching of vehicles such as taxis can be reserved from an application on a terminal device owned by a user (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The above-described vehicle dispatching service may be used not only by healthy people but also by disabled people. For example, when a disabled person uses the vehicle dispatching service when there is no attendant such as a caregiver, it may be difficult for the disabled person to get in and out of the vehicle.

[0005] The present invention has been made in view of the above problems, and an object thereof is to provide a supporter introduction method capable of introducing a supporter to a disabled person.

Means for Solving the Problems

[0006] A supporter introduction method according to an aspect of the present invention includes a vehicle Among a plurality of user information respectively associated with a plurality of reservation information of a ride reservation system, one related to a user one an acquisition step of acquiring user information, and based on the one user information, a determination step of determining whether the one user is a disabled person, and when it is determined that the one user is a disabled person, from the one user information, the one A specifying step of specifying the position and time when the user desires assistance, and based on the position and time when the assistance is desired, the one user, and the one A matching step of matching the user with a supporter who can assist the user, and includes see, the plurality of user information includes user information related to a healthy person as a user of the ride reservation system and user information related to a disabled person as a user of the ride reservation system That's what it is.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Modes for Carrying Out the Invention

[0008] Embodiments related to the supporter introduction method will be described with reference to the drawings. In the following embodiments, the supporter introduction method in the route bus reservation system is taken as an example. The supporter introduction method is not limited to route buses, and can also be applied to, for example, taxi dispatching systems, railway reservation systems, etc.

[0009] <First Embodiment> The first embodiment related to the supporter introduction method will be described with reference to FIGS. 1 to 3. "User" means a user of a route bus. It is assumed that users include healthy people and disabled people. "Supporter" may be a user of a route bus (that is, a user), or may not be a user of a route bus.

[0010] In FIG. 1, the support system 1 includes a server 10, a terminal device 20 possessed by a user, and a terminal device 30 possessed by a supporter. It is assumed that an application for using the support system 1 is installed in each of the terminal devices 20 and 30. In the server 10, a reservation information database 110 (hereinafter referred to as "reservation information DB 110"), a person-in-need-of-support database 120 (hereinafter referred to as "person-in-need-of-support DB 120"), a supporter database 130 (hereinafter referred to as "supporter DB 130"), and matching information 140 are stored.

[0011] The reservation information DB 110 contains reservation information input by the user via the terminal device 20. The reservation information includes, for example, vehicle information (such as a flight name) for specifying the route bus the user will board, the boarding location (such as a stop name) and the scheduled boarding time when the user boards the route bus, the alighting location (such as a stop name) and the scheduled alighting time when the user alights from the route bus, and the like. The reservation information is associated with user information for identifying the user. The user information may include, for example, name, contact information (phone number, email address, address, etc.), gender, age, information indicating the payment method, and the like. In particular, in this embodiment, the user information includes information indicating whether the user is a person with a disability.

[0012] In addition, an identification number may be assigned to the user information. The user information may be stored, together with the assigned identification number, in, for example, a user information database (not shown). In this case, the above reservation information may be associated with the identification number assigned to the user information instead of the user information.

[0013] In the support system 1, when the user information includes information indicating that the user is a person with a disability, the user can request (hope for) support regarding the use of the route bus. For example, when inputting reservation information, the user may input the details of the support. Examples of the support details include guidance to the boarding point of the route bus, assistance with boarding and alighting from the route bus, guidance from the alighting point of the route bus to the destination, etc. The support request information indicating the support details is linked to the reservation information and stored in the reservation information DB 110. Here, the location and time when the user hopes for support may be determined from the reservation information related to the user. For example, when the support detail is guidance to the boarding point of the route bus, the location and time for requesting support may be the boarding location and the scheduled boarding time when the user boards the route bus included in the reservation information. For example, when the support detail is guidance from the alighting point of the route bus to the destination, the location and time for requesting support may be the alighting location and the scheduled alighting time when the user alights from the route bus included in the reservation information.

[0014] The server 10 identifies the reservation information linked to the user information including information indicating that the user is a person with a disability among the reservation information included in the reservation information DB 110. When the support request information is linked to the identified reservation information, the server 10 stores the reservation information together with the support request information in the DB 120 for users in need of support. That is, the server 10 determines whether the user who reserved the route bus is a person with a disability based on the user information linked to the reservation information. When it is determined that the user is a person with a disability, the server 10 determines whether the support request information is linked to the reservation information of that user. When it is determined that the support request information is linked to the reservation information, the server 10 stores the reservation information together with the support request information in the DB 120 for users in need of support.

[0015] The supporter DB 130 contains supporter information input by the supporter via the terminal device 30. The supporter information may include, for example, information for identifying the supporter, support information indicating the content that can be supported, and the like. The information for identifying the supporter may include, for example, name, contact information (phone number, email address, address, etc.), gender, age, qualification information (nursing care welfare worker, mobile nursing care worker, sign language interpreter, etc.), and the like. The support information may include, for example, the available date and time and location, the possible support content, and the like.

[0016] The matching information 140 contains the matching result between the support request information linked to the reservation information contained in the person-in-need-of-support DB and the supporter information contained in the supporter DB 130. The matching between the support request information and the supporter information is performed by the server 10 (details will be described orally). The server 10 transmits the result of the matching to the terminal devices 20 and 30.

[0017] The server 10 will be described with reference to FIG. 2. The server 10 includes a processing unit 11, a storage device 15, and a communication unit 16. The processing unit 11, the storage device 15, and the communication unit 16 are connected to each other via a bus 17. The reservation information DB 110, the person-in-need-of-support DB 120, the supporter DB 130, and the matching information 140 may be constructed in the storage device 15. The processing unit 11 has an extraction unit 12, a determination unit 13, and a decision unit 14 as a logically realized logical block or a physically realized processing circuit for performing the above-described matching.

[0018] The operation of the processing unit 11 will be described with reference to the flowchart of FIG. 3 in addition to FIG. 2. In the present embodiment, when the supporter inputs supporter information via the terminal device 30, among the support request information stored in the person-in-need-of-support DB 120, the support request information corresponding to the support information included in the input supporter information is assumed to be displayed on the terminal device 30.

[0019] In FIG. 3, the processing unit 11 acquires support conditions (i.e., conditions related to support that the supporter can provide) from the support information included in the supporter information (step S101). The extraction unit 12 of the processing unit 11 extracts support request information that matches the acquired support conditions from among the support request information included in the support recipient DB 120 (step S102). At this time, the reservation information and user information associated with the support request information may also be extracted.

[0020] The processing unit 11 transmits the extracted support request information to the terminal device 30 via the communication unit 16 (step S103). Thereafter, the determination unit 13 of the processing unit 11 determines whether there is an input from the supporter via the terminal device 30 (step S104). In the process of step S104, if it is determined that there is no input from the supporter (step S104: No), the process of step S104 is performed. That is, it waits in a standby state until there is an input from the supporter.

[0021] In the process of step S104, if it is determined that there is an input from the supporter (step S104: Yes), the determination unit 14 of the processing unit 11 determines the support recipient according to the input of the supporter (step S105). At this time, the determination unit 14 associates the information related to the determined support recipient (i.e., reservation information, user information, and support request information) with the supporter information and stores it in the matching information 140. In addition, the determination unit 14 deletes the information related to the determined support recipient from the support recipient DB 120.

[0022] Specifically, when a plurality of support request information is extracted in the process of step S102, all of the extracted plurality of support request information is transmitted to the terminal device 30 in the process of step S103. In this case, in the process of step S105, the determination unit 14 determines, as the user to be supported, the user specified by the user information associated with one support request information selected by the supporter among the plurality of support request information. When one support request information is extracted in the process of step S102, in the process of step S105, the determination unit 14 determines, as the user to be supported, the user specified by the user information associated with one support request information selected by the supporter.

[0023] The processing unit 11 transmits, via the communication unit 16 to the terminal device 30, information for the supporter to identify the user to be supported among the user information related to the user corresponding to the user to be supported determined in the process of step S105. Further, the processing unit 11 transmits, via the communication unit 16 to the terminal device 20, information for the user to be supported to identify the supporter among the supporter information related to the supporter (step S106). The information for the supporter to identify the user to be supported may include, for example, the name of the user to be supported, contact information, location information indicating the current location of the user to be supported, information indicating the appearance characteristics of the user to be supported, and the like. The information for the user to be supported to identify the supporter may include, for example, the name of the supporter, contact information, location information indicating the current location of the supporter, information indicating the appearance characteristics of the supporter, and the like.

[0024] In addition, when no support request information is extracted in the process of step S102 (in other words, when there is no support request information that meets the support conditions obtained from the support information), the processing unit 11 may store the supporter information in the supporter DB 130. The determination unit 13 of the processing unit 11 may consider that the matching is not established and end the operation shown in FIG. 3 when there is no input from the supporter for a predetermined time in the process of step S104. In this case, the processing unit 11 may store the supporter information considered that the matching is not established in the supporter DB 130.

[0025] (Technical effect) According to the support system 1 according to the first embodiment, it is possible to introduce a supporter to a disabled person who needs support.

[0026] <Second Embodiment> A second embodiment related to a supporter introduction method will be described with reference to the flowchart of FIG. 4. In the second embodiment, it is the same as the above-described first embodiment except that the operation of the processing unit 11 is different. Therefore, in the second embodiment, mainly the parts different from the first embodiment will be described, and the description of the parts the same as the first embodiment will be omitted as appropriate.

[0027] In the present embodiment, supporter information is stored in the supporter DB 130. When a user who needs support (that is, a disabled person) inputs support request information via the terminal device 20, the processing unit 11 selects supporter information corresponding to the support request information.

[0028] In FIG. 4, the processing unit 11 acquires support conditions (that is, conditions related to the support required by the disabled person) from the support request information (step S201). The extraction unit 12 of the processing unit 11 extracts one or a plurality of supporter information including support information that matches the acquired support conditions from the supporter information included in the supporter DB 130 (step S202).

[0029] The processing unit 11 transmits a signal indicating a support request to the terminal device 30 of the supporter specified by the supporter information that most matches the acquired support conditions among the extracted one or a plurality of supporter information (step S203). Then, the determination unit 13 of the processing unit 11 determines whether there is a commitment from the supporter to whom the signal indicating the support request has been sent (that is, an input indicating commitment via the terminal device 30) (step S204).

[0030] In the process of step S204, when it is determined that there is no commitment from the supporter (step S204: No), the determination unit 13 determines whether there is supporter information (that is, other candidates) related to a supporter to whom the signal indicating the support request has not been sent among the supporter information extracted in the process of step S202 (step S205).

[0031] In the process of step S205, when it is determined that there is supporter information related to a supporter who has not sent a signal indicating a support request (step S205: Yes), the processing unit 11, among the supporter information related to the supporter who has not sent a signal indicating a support request, for the terminal device 30 of the supporter specified by the supporter information that best meets the obtained support conditions (step S206), sends a signal indicating a support request (step S203).

[0032] In the process of step S205, when it is determined that there is no supporter information related to a supporter who has not sent a signal indicating a support request (step S205: No), the operation shown in FIG. 4 ends. At this time, the processing unit 11 may send, for example, a signal indicating that a supporter cannot be introduced to the user's terminal device 20 via the communication unit 16. Also, when there is relatively some time margin until the date and time when the user indicated by the support request information requests support, the processing unit 11 may send, for example, a signal indicating that a supporter will be introduced by the date and time when the user requests support to the user's terminal device 20 via the communication unit 16.

[0033] In the process of step S204, when it is determined that there is a commitment from the supporter (step S204), the determination unit 14 of the processing unit 11 determines a supporter (step S207). At this time, the determination unit 14 associates the supporter information related to the determined supporter with the information related to the user in need of support (that is, reservation information, user information, and support request information) and stores it in the matching information 140. Also, the determination unit 14 may delete the supporter information related to the determined supporter from the supporter DB 130.

[0034] The processing unit 11 sends, via the communication unit 16 to the terminal device 20, the information for the supported person to identify the supporter among the supporter information related to the supporter determined in the process of step S207. Also, the processing unit 11 sends, via the communication unit 16 to the terminal device 30, the information for the supporter to identify the supported person among the user information related to the user corresponding to the supported person.

[0035] Further, in the case where there is no input from the supporter for a predetermined time in the process of step S204, the determination unit 13 of the processing unit 11 may consider that there is no approval from the supporter and perform the process of step S205.

[0036] (Technical effect) According to the support system 1 according to the second embodiment, it is possible to introduce a supporter to a disabled person who needs support.

[0037] Aspects of the invention derived from the embodiments described above will be described below.

[0038] A supporter introduction method according to an aspect of the invention includes an acquisition step of acquiring user information related to a user who uses a vehicle, a determination step of determining whether the user is a disabled person based on the user information, and when it is determined that the user is a disabled person, a specification step of specifying a position and time at which the user desires support from the user information, and a matching step of matching the user with a supporter who can support the user based on the position and time at which the support is desired.

[0039] In the supporter introduction method, the user information includes at least one of a boarding position and boarding time at which the user boards the vehicle, and a getting-off position and getting-off time at which the user gets off the vehicle, and the position and time at which the support is desired may be the at least one position and time.

[0040] The supporter introduction method may include a transmission step of transmitting user identification information for identifying the user to the supporter.

[0041] The present invention is not limited to the above-described embodiments, and can be appropriately changed without departing from the gist or idea of the invention read from the claims and the entire specification, and a supporter introduction method involving such a change is also included in the technical scope of the present invention.

Explanation of reference numerals

[0042] 1... Support system, 10... Server, 11... Processing unit, 12... Extraction unit, 13... Judgment unit, 14... Decision unit, 15... Storage device, 16... Communication unit, 20, 30... Terminal device

Claims

1. An acquisition step of acquiring one user information related to one user among a plurality of user information respectively associated with a plurality of reservation information of a vehicle reservation system for a vehicle; A determination step of determining whether the one user is a disabled person based on the one user information; A specifying step of specifying, from the one user information, a position and a time when the one user desires assistance when it is determined that the one user is a disabled person; A matching step of matching the one user with a supporter who can assist the one user based on the position and time when assistance is desired; comprising wherein the plurality of user information includes user information related to a non-disabled person as a user of the vehicle reservation system and user information related to a disabled person as a user of the vehicle reservation system A method for introducing a supporter, characterized in that.

2. The one user information includes at least one of a boarding position and a boarding time when the one user boards the vehicle, and a getting-off position and a getting-off time when the one user gets off the vehicle, The position and time when assistance is desired are the at least one of the position and time The method for introducing a supporter according to claim 1, characterized in that.

3. The method for introducing a supporter according to claim 1 or 2, characterized in that it includes a transmission step of transmitting user identification information for identifying the one user to the supporter.

Images