Transportation service reservation management device and method

Abstract

To manage a reservation of a transportation service useful for each user.SOLUTION: In first reservation processing (1110), a use reservation for a transportation service is performed for a first object person based on first reservation request information (620) of the first object person received from a first terminal apparatus. In second reservation processing (1120), a use reservation of the transportation service is performed for a second object person based on second reservation request information (640) of the second object person received from a second terminal apparatus. After those reservation processing, a reservation management apparatus can perform allocation change processing. The allocation change processing includes right provision processing (1140) that provides a use right of a transportation facility allocated to the first object person by the first reservation processing to the second object person, and liquidation processing (1160) that grants consideration based on a preferential usage fee collected from the second object person to the first object person.SELECTED DRAWING: Figure 21

Description

Technical Field

[0001] The present invention relates to a reservation management device and method for transportation services.

Background Art

[0002] When using transportation services, users may not be able to use the transportation services as desired. For example, when the demand for transportation services exceeds the supply, users need to wait until there is an available transportation vehicle (such as a taxi).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

Effect of the Invention

[0007] According to the present invention, it is possible to provide a reservation management device and method for transportation services that are beneficial to each user.

Brief Description of the Drawings

[0008] [Figure 1] It is a schematic overall configuration diagram of a system according to an embodiment of the present invention. [Figure 2] It is a schematic block diagram of a terminal device according to an embodiment of the present invention. [Figure 3] It is a diagram showing the internal configuration of a reservation management device, several terminal devices related to the operation of the system, and the users of each terminal device according to an embodiment of the present invention. [Figure 4] It is a diagram showing the relationships of a plurality of persons related to the operation of the system according to an embodiment of the present invention. [Figure 5] It is a flowchart showing the overall flow of the system according to an embodiment of the present invention. [Figure 6] It is a diagram showing the flow of information in the user registration process according to an embodiment of the present invention. [Figure 7] This figure shows the configuration of user registration information and user storage information according to an embodiment of the present invention. [Figure 8] This diagram shows the flow of information in the registration process of a provider, according to an embodiment of the present invention. [Figure 9] This figure shows the configuration of the provider information and the first type of stored information according to an embodiment of the present invention. [Figure 10] This diagram shows the flow of information in the priority usage application process according to an embodiment of the present invention. [Figure 11] This diagram shows the configuration of priority request information and second type stored information according to an embodiment of the present invention. [Figure 12] This diagram shows the flow of information in the checking process, matching process, and rights granting process according to an embodiment of the present invention. [Figure 13] This figure shows how service vehicles are exchanged between a provider and a priority user according to an embodiment of the present invention. [Figure 14] This figure shows the configuration of the assignment result information according to an embodiment of the present invention. [Figure 15] This diagram shows the flow of information in the results reporting process according to an embodiment of the present invention. [Figure 16] This figure shows the configuration of the provided result information according to an embodiment of the present invention. [Figure 17] This diagram shows the configuration of the request result information according to an embodiment of the present invention. [Figure 18] This figure shows table data relating to member points according to an embodiment of the present invention. [Figure 19] This figure shows how symbols are assigned to various types of information corresponding to potential providers, according to an embodiment of the present invention. [Figure 20] This figure shows how symbols are assigned to various types of information corresponding to priority users, according to an embodiment of the present invention. [Figure 21] This is a sequence diagram showing the operation flow of the system according to a first embodiment belonging to the embodiments of the present invention. [Figure 22]This figure shows various information relating to the first embodiment of the present invention, including information on the provider and the priority user requester. [Figure 23] This is a conceptual diagram of the first to third determination conditions, which determine success or failure in the matching process, relating to a second embodiment of the present invention. [Figure 24] This figure shows a fourth embodiment belonging to the embodiments of the present invention, illustrating how two or more priority users are associated with a specific provider. [Figure 25] This is a functional block diagram of a reservation management device according to a seventh embodiment of the present invention. [Modes for carrying out the invention]

[0009] Hereinafter, examples of embodiments of the present invention will be specifically described with reference to the drawings. In each of the referenced drawings, the same parts are denoted by the same reference numerals, and redundant descriptions relating to the same parts are omitted as a general rule. In addition, in this specification, for the sake of simplification of the description, symbols or reference numerals that refer to information, signals, physical quantities, functional parts, circuits, elements, or components may be indicated, and the names of the information, signals, physical quantities, functional parts, circuits, elements, or components corresponding to such symbols or reference numerals may be omitted or abbreviated.

[0010] Figure 1 shows a schematic overall configuration diagram of a system SYS according to an embodiment of the present invention. The system SYS comprises a reservation management device 100 and a service provider-side device 200. Figure 1 shows a plurality of terminal devices TM. Each terminal device TM is an electronic device operated by the operator of each terminal device TM. For example, a smartphone, tablet, or personal computer can be used as a terminal device TM. Each terminal device TM may be understood as not being included as a component of the system SYS, or it may be understood as being included as a component of the system SYS.

[0011] The reservation management device 100 and each terminal device TM are wirelessly connected via a predetermined communication network NET, and the reservation management device 100 and each terminal device TM can communicate bidirectionally with each other via the communication network NET. Furthermore, the reservation management device 100 and the service provider-side device 200 are wirelessly connected via the same communication network NET, and the reservation management device 100 and the service provider-side device 200 can communicate bidirectionally with each other via the communication network NET. The communication network NET includes all or part of the Internet, wireless LAN (Local Area Network), and short-range wireless communication lines. The wireless LAN may be, for example, compliant with Wi-Fi®. The short-range wireless communication line may be, for example, compliant with Bluetooth®. The communication network NET may include wireless communication systems. The wireless communication system here includes wireless communication systems compliant with the IMT-Advanced standard, and may be, for example, a fourth-generation mobile communication system.

[0012] The reservation management device 100 makes reservations for transportation services to be provided to users. In transportation services, users of system SYS become passengers and travel from their departure point to their destination by boarding a vehicle that is a means of transportation. Vehicles as means of transportation include road vehicles and trains that run on railway tracks, and may also be ships or airplanes. Examples of road vehicles include taxis and buses (including on-demand buses). In the following explanation, unless otherwise specified, it is assumed that the means of transportation (vehicles) in transportation services are vehicles such as taxis (hereinafter referred to as service vehicles). However, the type of means of transportation may be arbitrary.

[0013] Figure 2 shows a schematic block diagram of one terminal device TM. In system SYS, any two terminal devices TM may be of different types. That is, for example, one terminal device TM may be a smartphone and the other terminal device TM may be a personal computer. Alternatively, any two terminal devices TM may be smartphones of different types. However, in the following description, it is assumed that each terminal device TM has the configuration shown in Figure 2. That is, each terminal device TM in system SYS shall be equipped with the parts referenced by reference numerals 510, 520, 530, 540, 550, 560 and 570.

[0014] The terminal control unit 510 is equipped with a arithmetic processing unit 510a, including a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), as hardware resources, and comprehensively controls the operation of each part of the terminal device TM. The CPU and GPU may be integrated into the arithmetic processing unit 510a (for example, the GPU may be built into the CPU).

[0015] The memory 520 includes non-volatile memory such as ROM (Read-only memory) or flash memory, and volatile memory such as RAM (Random Access Memory). All or part of the memory 520 may be memory built into the terminal control unit 510.

[0016] Camera 530 captures subjects within its shooting area and generates image data of the images within the shooting area (hereinafter referred to as captured images). The generated image data is sent to the terminal control unit 510. Camera 530 sequentially captures images at a predetermined frame period, thereby acquiring multiple captured images arranged in chronological order. A moving image is formed from these multiple captured images arranged in chronological order.

[0017] The communication processing unit 540 enables bidirectional communication between the terminal device TM and the other device via the communication network NET. The other device of the terminal device TM includes the reservation management device 100.

[0018] The GPS processing unit 550 detects the position of the terminal device TM (the current location of the terminal device TM) by receiving signals from multiple GPS satellites that form the GPS (Global Positioning System). The detected position of the terminal device TM is referred to as the terminal position, and the information representing the terminal position is referred to as terminal position information. The terminal position information is sent from the GPS processing unit 550 to the terminal control unit 510. The terminal position of a certain terminal device TM can be considered to represent the current location of the user of the terminal device TM. The user of the terminal device TM is the owner or operator of the terminal device TM, and can also be described as the person corresponding to the terminal device TM.

[0019] The date and time information acquisition unit 560 acquires date and time information indicating the current date and time and sends it to the terminal control unit 510. The date and time information acquisition unit 560 may also acquire date and time information from other devices (not shown) via the communication network NET.

[0020] The interface unit 570 is a man-machine interface between the terminal device TM and the user of the terminal device TM, and includes a display screen 571, an operation unit 572, a microphone 573, and a speaker 574. The display screen 571 is configured as a liquid crystal display panel or the like and displays any image under the control of the terminal control unit 510. The operation unit 572 receives input of any operation from the user of the terminal device TM. The display screen 571 and the operation unit 572 may constitute a touch panel, and operations on the operation unit 572 may also be operations on the touch panel. The microphone 573 picks up ambient sound and converts the picked-up sound into an electrical signal. The speaker 574 outputs any sound under the control of the terminal control unit 510.

[0021] Figure 3 shows the internal configuration of the reservation management device 100, as well as several terminal devices involved in the operation of the SYS system and the users of each terminal device.

[0022] The reservation management device 100 comprises a data input handling unit 10, a priority usage handling unit 20, a priority usage management unit 30, and a data storage unit 40. The reservation management device 100 is composed of one or more computer devices (server devices) connected to the communication network NET wirelessly or via wired connection. The reservation management device 100 may also be a cloud server configured using cloud computing.

[0023] The data input unit 10 comprises a data receiving unit 11, a data identification unit 12, and a data writing unit 13. The priority usage unit 20 comprises a data reading unit 21, an allocation change unit 22, and a provision result reporting unit 23. The priority usage management unit 30 comprises a data reading unit 31, a data analysis unit 32, an allocation result reporting unit 33, and a point update unit 34. The data storage unit 40 consists of a non-volatile recording medium composed of a magnetic disk and semiconductor memory, and stores various types of data. Databases 41 to 45 are stored in the data storage unit 40. Hereinafter, databases will be referred to as DB. DB 41 is the user registration DB. DB 42 is the available users DB. DB 43 is the priority usage DB. DB 44 is the allocation result DB. DB 45 is the point information DB.

[0024] Users of the SYS system are registered in advance with the reservation management device 100. Registered users are referred to as User A. The terminal device TM corresponding to User A is referred to as Terminal Device TM_A. User A is a user of Terminal Device TM_A. In addition, a Service Provider B is also registered with the reservation management device 100. The terminal device TM corresponding to Service Provider B is referred to as Terminal Device TM_B. Service Provider B is a user of Terminal Device TM_B.

[0025] There is at least one registered user A and at least one provider B. In the following, as shown in Figure 4, unless otherwise specified, it is assumed that there are multiple registered users A and providers B. Each registered user A is assigned a terminal device TM_A, and each provider B is assigned a terminal device TM_B. It is possible that one registered user A and one provider B are the same person.

[0026] User A and service provider B can request the reservation management device 100 to make a reservation for the use of transportation services through terminal devices TM_A and TM_B. A reservation for the use of transportation services is, in other words, a reservation for the use of transportation. There are two types of people who can make the above request. A person of type 1 is a person who consents to transferring their assigned right to use transportation to another person. Service provider B is a person of type 1 or includes a person of type 1. A person of type 2 is a person who requests priority use of transportation services. A person of type 2 is referred to as a priority use requester C. The terminal device TM corresponding to priority use requester C is referred to as terminal device TM_C. Priority use requester C is a user of terminal device TM_C. Any user A becomes priority use requester C. When a particular user A becomes priority use requester C, the terminal device TM_A of that user A functions as terminal device TM_C.

[0027] Priority user C uses terminal device TM_C to make a reservation for the transportation service with reservation management device 100. It is possible for two or more individuals from among multiple registered users A to simultaneously become priority user C.

[0028] On the other hand, each service provider B makes a reservation for the transportation service to the reservation management device 100 using their own terminal device TM_B, separately from the priority requester C. The reservation management device 100 makes the transportation service reservation according to the request of each service provider B, but the transportation service reservation assigned to any of the service providers B may be provided to the priority requester C.

[0029] When a reservation for a transportation service assigned to provider B is provided to priority requester C, it means that the right to use the transportation service assigned to provider B is provided to priority requester C. The provision of the right to use the transportation service may be reinterpreted as the transfer or succession of the right to use the transportation service. When a reservation for a transportation service (right to use the transportation service) assigned to a particular provider B is provided (succession) to priority requester C, that particular provider B is referred to as the actual provider D. The actual provider D is the user of terminal device TM_D. When a particular provider B becomes the actual provider D, the terminal device TM_B of that particular provider B functions as terminal device TM_D.

[0030] In the reservation management device 100, a request from priority user C (a request for priority use of transportation services) may or may not be approved. When a request from priority user C is approved and the reservation for the use of transportation services (the right to use transportation services) that was allocated to the actual provider D is provided to priority user C, the priority user C who receives the reservation is specifically referred to as the recipient E. The recipient E is a user of terminal device TM_E. When a particular priority user C becomes the recipient E, the terminal device TM_C of that priority user C functions as terminal device TM_E.

[0031] Figure 5 is a flowchart showing the overall flow of the SYS system. Steps S1 to S10 can be executed in the SYS system. Step S1 is the user registration process. Step S2 is the provider registration process. Step S3 is the priority usage request acceptance process. Step S4 is the check process. Step S5 is the matching process. Step S6 is the rights granting process. Step S7 is the results reporting process. Step S8 is the settlement process. Step S9 is the actual vehicle dispatch process. Step S10 is the standard response process.

[0032] In the SYS system, steps S1 to S9 can be executed in this order. However, depending on the result of step S4, steps S5 to S9 may be skipped after step S4, and only step S10 may be executed. Also, when steps S6 to S8 are executed, the execution order of steps S6 to S8 can be arbitrarily changed, and they may be executed in parallel.

[0033] Furthermore, it is assumed that a predetermined application program (hereinafter referred to as the dispatch app) is pre-installed on each terminal device TM, and that the dispatch app can be executed on the processing unit 510a of each terminal device TM. By operating the terminal device TM while the dispatch app is running, the user of the terminal device TM can send arbitrary information described later from the terminal device TM to the reservation management device 100, and can also receive arbitrary information from the reservation management device 100 at the terminal device TM. The steps in Figure 5 will be explained below.

[0034] [Step S1: User Registration Process] First, the user registration process performed in step S1 will be explained. In the user registration process, multiple users A are registered with the reservation management device 100. Figure 6 shows the flow of information in the user registration process. In the user registration process, user storage information 610 is stored in the data storage unit 40 after the transmission and reception of user registration information 600.

[0035] A person who wishes to register as user A with the reservation management device 100 is referred to as a prospective registrant A'. The user registration process is executed for each prospective registrant A', so that each prospective registrant A' becomes a user A. Specifically, prospective registrant A' operates their corresponding terminal device TM to have the terminal device TM transmit user registration information 600 to the reservation management device 100. The user registration information 600 is received by the data receiving unit 11. The data identification unit 12 determines whether the information received by the data receiving unit 11 is user registration information 600. If the information received by the data receiving unit 11 is determined to be user registration information 600, the data writing unit 13 writes user storage information 610, including the received user registration information 600, to the user registration database 41. As a result, the user storage information 610 is stored in the user registration database 41. When user storage information 610 corresponding to prospective registrant A' is stored in the user registrant DB 41, prospective registrant A' is registered and managed as user registrant A in the reservation management device 100. Thereafter, prospective registrant A' is identified as user registrant A in the reservation management device 100, and the terminal device TM corresponding to prospective registrant A' functions as terminal device TM_A.

[0036] Figure 7 shows the structure of user registration information 600 and user stored information 610 in user registration DB 41. We will explain user registration information 600 assuming that prospective registrant A' is the same as registered user A. User registration information 600 includes personal information 601 including the name, address, age, and gender of registered user A, information 602 regarding the financial institution designated by registered user A, and information 603 representing the contact information of registered user A.

[0037] When any person of interest uses the SYS system to make reservations for transportation services, etc., that person of interest may pay a service fee. In this case, the person of interest may pay the service fee in currency. When a registered user A is a person of interest, the payment of the service fee will be settled from the financial institution account indicated in user A's information 602. The currency here may be legal tender or virtual currency. Virtual currency may be classified as electronic money. In addition, the reservation management device 100 manages points that circulate within the SYS system (hereinafter referred to as member points). Any person of interest can also pay the service fee using the member points they possess.

[0038] Information 603 represents the contact information of registered user A when the reservation management device 100 transmits arbitrary information to registered user A. Information 603 includes the telephone number or email address assigned to registered user A's terminal device TM_A, or the account information of an instant messenger executed on terminal device TM_A. Information transmitted by the reservation management device 100 to the contact information in Information 603 is transmitted to registered user A via terminal device TM_A, and if registered user A is a priority requester C and a recipient E, it is transmitted to priority requester C and recipient E via terminal devices TM_C and TM_E. Note that the transmission of information from the reservation management device 100 is synonymous with the transmission or output of information.

[0039] In the procedure for registering applicant A' as registered user A, the data input unit 10 assigns a unique member ID and sets a password for applicant A' (and therefore registered user A). User storage information 610 (see Figure 7) includes information 611 representing the assigned member ID and information 612 representing the set password, and further includes information 601 to 603 from the registered user information 600. User storage information 610 also includes information 613 representing the update date and time of the user storage information 610 itself. In the reservation management device 100, information 613 is updated each time the user storage information 610 in the registered user DB 41 is updated.

[0040] [Step S2: Registration of eligible providers] Next, the registration process for available providers, which is performed in step S2, will be described. In the registration process for available providers, multiple available providers B are registered in the reservation management device 100. Figure 8 shows the flow of information in the registration process for available providers. In the registration process for available providers, the first type of stored information 630 is stored in the data storage unit 40 after the transmission and reception of available provider information 620.

[0041] A person who wishes to register with the reservation management device 100 as a provider B is referred to as a registration applicant B'. The provider registration process is executed for each registration applicant B', so that each registration applicant B' becomes a provider B. Specifically, registration applicant B' operates the terminal device TM corresponding to themselves, causing the terminal device TM to transmit provider information 620 to the reservation management device 100. The provider information 620 is received by the data receiving unit 11. The data identification unit 12 determines whether the information received by the data receiving unit 11 is provider information 620. If the information received by the data receiving unit 11 is determined to be provider information 620, the data writing unit 13 writes the first type of stored information 630, which includes the received provider information 620, to the provider DB 42. As a result, the first type of stored information 630 is stored in the provider DB 42. The first type of stored information 630 is stored information relating to provider B. When the Type 1 stored information 630 corresponding to prospective registrant B' is stored in the provider DB 42, prospective registrant B' is registered and managed as provider B in the reservation management device 100. Thereafter, prospective registrant B' is identified as provider B in the reservation management device 100, and the terminal device TM corresponding to prospective registrant B' functions as terminal device TM_B.

[0042] Figure 9 shows the structure of the provider information 620 and the first type of stored information 630 in the provider database 42. The provider information 620 will be explained assuming that prospective registrant B' is the same as provider B. The provider information 620 includes personal information 621 including provider B's name, address, age, and gender, information 622 regarding the financial institution designated by provider B, and information 623 representing provider B's contact information.

[0043] As described above, when any person of interest uses the SYS system to make reservations for transportation services, etc., that person of interest may pay a service fee. In this case, the person of interest may pay the service fee in currency. When a certain provider B is the person of interest, the payment of the service fee will be settled from the financial institution account indicated in provider B's information 622.

[0044] Information 623 represents the contact information of provider B when the reservation management device 100 transmits arbitrary information to provider B. Information 623 includes the telephone number or email address assigned to provider B's terminal device TM_B, or the account information of an instant messenger executed on terminal device TM_B. Information transmitted by the reservation management device 100 to the contact information in information 623 is transmitted to provider B via terminal device TM_B, and if provider B is the actual provider D, it is transmitted to the actual provider D via terminal device TM_D.

[0045] The provider information 620 further includes information 624. Information 624 is information regarding provider B's desire to use transportation services, and is hereinafter also referred to as the reservation information 624. The reservation information 624 indicates the conditions under which provider B wishes to use the transportation services. Specifically, the reservation information 624 includes information indicating provider B's desired departure date and time, departure point, and destination. The departure point and destination in the reservation information 624 represent the departure point and destination of provider B when provider B travels in the service vehicle assigned to provider B. The desired departure date and time in the reservation information 624 represents the desired date and time for provider B to depart from the departure point specified in the reservation information 624 by service vehicle.

[0046] Service provider B can arbitrarily specify the reservation information 624 by operating terminal device TM_B. Service provider B may arbitrarily specify the desired departure date and time, or may specify immediate use. When immediate use is specified, the desired departure date and time is set to the current date and time, or is considered to be a predetermined small amount of time later than the current date and time. The current date and time can be obtained from the date and time information acquisition unit 560 (see Figure 2) of terminal device TM_B. Service provider B can also set their current location as the departure point, in which case the departure point may be set based on terminal location information (see Figure 2) obtained from the GPS processing unit 550 of terminal device TM_B.

[0047] In the procedure for registering applicant B' as provider B, the data input unit 10 assigns a unique member ID and sets a password for applicant B' (and therefore provider B). The first type of stored information 630 (see Figure 9) includes information 631 representing the assigned member ID and information 632 representing the set password, and further includes information 621 to 624 from the provider information 620.

[0048] As shown in Figure 9, the first type of stored information 630 includes information 633. Information 633 is reservation priority information, representing the priority of reservations for transportation services. Specifically, the reservation priority information 633 represents the date and time when a reservation for transportation services was made to provider B in step S2 (the execution date and time of the first reservation process described later), and the earlier the date and time, the higher the priority of the transportation service reservation. However, the reservation priority information 633, once set, can be updated later (details will be described later).

[0049] Furthermore, the first reservation process is executed during the registration process in step S2 (see Figure 5). The first reservation process is executed by the data input support unit 10. In the first reservation process, the data input support unit 10 makes a reservation for the use of transportation services (in other words, a reservation for the use of transportation) to provider B based on the provider information 620 (especially the desired usage information 624) from provider B. The reservation management device 100 is aware of the operating schedule of each service vehicle operated within the system SYS. In the first reservation process, based on the operating schedule of each service vehicle, it searches for a service vehicle that can operate according to the desired usage information 624 from among the multiple service vehicles operated within the system SYS. At this time, if there is no service vehicle that can perfectly match the desired usage information 624, it searches for a service vehicle that can satisfy the desired usage information 624 as much as possible. In the first reservation process, the searched service vehicle is assigned to provider B as a vehicle for dispatch reservation.

[0050] Information 634 included in Type 1 Preservation Information 630 is reserved vehicle information. Reserved vehicle information 634 represents a vehicle ID that identifies the vehicle assigned to provider B for dispatch reservation. Information 635 included in Type 1 Preservation Information 630 is transport reservation information. Transport reservation information 635 indicates the reserved departure date and time, departure point, and destination of the vehicle assigned to provider B for dispatch reservation. The reserved departure date and time of the vehicle for dispatch reservation is the date and time on which the vehicle is scheduled to depart and which is the reserved departure date and time. The first reservation process is performed with the aim that the reserved departure date and time, departure point, and destination in the transport reservation information 635 match the desired departure date and time, departure point, and destination in the desired usage information 624, but they may or may not match. Immediately after the first reservation process, the results of the first reservation process are reflected in information 634 and 635, but the contents of information 634 and 635 may be updated by a subsequent rights provision process.

[0051] Furthermore, the first type of stored information 630 includes information 636 that represents the update date and time of the first type of stored information 630 itself (see Figure 9). In the reservation management device 100, information 636 is updated each time the first type of stored information 630 in the available provider DB 42 is updated.

[0052] Furthermore, if a single person is both a registered user A and a provider B, a single member ID may be assigned to that person, and a common password may be set for that person. In this case, the member ID information 611 and 631 for that person will be the same, and the password information 612 and 632 for that person will be the same.

[0053] [Step S3: Request acceptance process for priority use] Next, we will explain the priority use request acceptance process performed in step S3. In the priority use request acceptance process, a request for reservation of the transportation service by priority use requester C is accepted. Priority use requester C is the person who requests priority use of the transportation service, as described above. Figure 10 shows the flow of information in the priority use request acceptance process. In the priority use request acceptance process, after the transmission and reception of priority request information 640, the second type of stored information 650 is stored in the data storage unit 40.

[0054] Of the multiple registered users A, one of them becomes the priority user requester C (see Figure 4). Priority user requester C operates the terminal device TM_C to input priority request information 640 into the terminal device TM_C and also transmits the priority request information 640 from the terminal device TM_C to the reservation management device 100. The priority request information 640 is received by the data receiving unit 11. Priority request information 640 is information that involves a request for priority use of transportation services. The data identification unit 12 determines whether the information received by the data receiving unit 11 is priority request information 640. If the information received by the data receiving unit 11 is determined to be priority request information 640, the data writing unit 13 writes the received priority request information 640, along with the second type of stored information 650, to the priority use DB 43. As a result, the second type of stored information 650 is stored in the priority use DB 43. The second type of stored information 650 is stored information related to priority user requester C.

[0055] Figure 11 shows the structure of the priority request information 640 and the second type of stored information 650 in the priority usage DB 43. The priority request information 640 includes information 641 representing the member ID of priority user requester C. The reservation management device 100 identifies which user A priority user requester C is based on information 641.

[0056] Priority request information 640 further includes information 642. Information 642 is information regarding the priority user requester C's desire to use transportation services, and is hereinafter also referred to as usage reservation information 642. Usage reservation information 642 indicates the conditions under which priority user requester C wishes to use the transportation services. Specifically, information indicating priority user requester C's desired departure date and time, departure point, and destination is included in usage reservation information 642. The departure point and destination in usage reservation information 642 represent the departure point and destination of priority user requester C when priority user requester C travels in the service vehicle assigned to priority user requester C. The desired departure date and time in usage reservation information 642 represents the desired date and time for priority user requester C to depart from the departure point specified in usage reservation information 642 by service vehicle.

[0057] Priority user C can arbitrarily specify the reservation information 642 by operating the terminal device TM_C. Priority user C may arbitrarily specify the desired departure date and time, or may specify immediate use. When immediate use is specified, the desired departure date and time is set to the current date and time, or is considered to be a predetermined small amount of time later than the current date and time. The current date and time can be obtained from the date and time information acquisition unit 560 (see Figure 2) of the terminal device TM_C. Priority user C can also set their current location as the departure point, in which case the departure point may be set based on the terminal location information (see Figure 2) obtained from the GPS processing unit 550 of the terminal device TM_C.

[0058] Priority request information 640 further includes information 643 and 644. Information 643 represents the priority usage fee, and information 644 represents the priority preference level. When priority requester C has priority request information 640 sent from terminal device TM_C, they can freely set the priority usage fee and priority preference level. How the priority usage fee and priority preference level function in this system SYS will become clear from the following explanation.

[0059] The second type of stored information 650 includes information 641 to 644 from the priority request information 640, and further includes information 651. Information 651 is reservation ranking information, which represents the priority of the transportation service reservation. Specifically, the reservation ranking information 651 represents the date and time the transportation service reservation was made, that is, the date and time when the transportation service reservation was made for priority user C in step S3 (the execution date and time of the second reservation process described later), and the earlier the date and time, the higher the priority of the transportation service reservation. However, the reservation ranking information 651, once set, may be updated later (details will be described later).

[0060] Furthermore, in the request acceptance process of step S3, the second reservation process is executed (see Figure 5). The second reservation process is executed in the data input handling unit 10. In the second reservation process, the data input handling unit 10 makes a reservation for the use of transportation services (in other words, a reservation for the use of transportation) to the priority requester C based on the priority request information 640 (especially the desired usage information 642) from the priority requester C. The reservation management device 100 is aware of the operating schedule of each service vehicle operated within the system SYS. In the second reservation process, based on the operating schedule of each service vehicle, it searches for a service vehicle that can operate according to the desired usage information 642 from among the multiple service vehicles operated within the system SYS. At this time, if there is no service vehicle that can perfectly match the desired usage information 642, it searches for a service vehicle that can satisfy the desired usage information 642 as much as possible. In the second reservation process, the searched service vehicle is assigned to the priority requester C as a vehicle for dispatch reservation.

[0061] Information 652 included in Type 2 Preservation Information 650 is reserved vehicle information. Reserved vehicle information 652 represents a vehicle ID that identifies the vehicle assigned to priority user C. Information 653 included in Type 2 Preservation Information 650 is transport reservation information. Transport reservation information 653 indicates the reserved departure date and time, departure point, and destination of the vehicle assigned to priority user C. The reserved departure date and time of the vehicle is the date and time on which the vehicle is scheduled to depart and which is the reserved departure date and time. The second reservation process is executed with the aim that the reserved departure date and time, departure point, and destination in transport reservation information 653 match the desired departure date and time, departure point, and destination in usage request information 642, but they may or may not match. Immediately after the second reservation process, the results of the second reservation process are reflected in information 652 and 653, but the contents of information 652 and 653 may be updated by a subsequent rights granting process.

[0062] Furthermore, the Type 2 stored information 650 includes information 654 that represents the update date and time of the Type 2 stored information 650 itself (see Figure 11). In the reservation management device 100, information 654 is updated each time the Type 2 stored information 650 in the priority usage DB 43 is updated.

[0063] [Step S4: Checking Process] Next, the checking process performed in step S4 will be described. The checking process is performed by the priority usage support unit 20. Figure 12 shows the flow of information in the checking process in step S4, the matching process in step S5, and the rights provision process in step S6.

[0064] When the second type of stored information 650 is newly written to the priority use DB 43 (i.e., when the priority use DB 43 is updated), the data reading unit 21 reads the first type of stored information 630 from the provider DB 42 and the second type of stored information 650 from the priority use DB 43. In step S4, the priority use response unit 20 related to the checking process determines whether the content of the transportation service reservation in the second reservation process matches the content of the usage request information 642 of priority use requester C. This is equivalent to determining whether the transportation service requested by priority use requester C was reserved as requested. If the determination in step S4 is affirmative (Y in step S4), the process proceeds to step S10; however, if the determination in step S4 is negative (N in step S4), the process proceeds to step S5. If the process proceeds to step S5, a characteristic operation is performed.

[0065] Figure 13 shows a typical example of proceeding to step S5. In the example in Figure 13, the first reservation process reserves service vehicle 801 (for example, a vehicle scheduled to depart at 15:00) as requested by service provider B. Subsequently, the second reservation process is performed for priority requester C, but because the demand for service vehicles exceeds the supply, a service vehicle as requested by priority requester C (for example, a vehicle scheduled to depart at 15:00) cannot be arranged, and instead, service vehicle 802 (for example, a service vehicle scheduled to depart at 15:30) is reserved. In the example in Figure 13, if service vehicle 801 had been assigned to priority requester C, service vehicle 801 could be operated as requested by priority requester C, but service vehicle 802 cannot be operated as requested by priority requester C due to its operating schedule. In such cases, the reservation details between service provider B and priority requester C are swapped through steps S5 and S6. As a result, service provider B will use service vehicle 802, and priority user C will use service vehicle 801.

[0066] The following explanation of the SYS system operation assumes that the user has proceeded to step S5, unless otherwise specified.

[0067] [Step S5: Matching Process] The matching process performed in step S5 will now be described. The matching process is performed by the priority usage support unit 20. In the matching process, the priority usage support unit 20 performs a matching process. In the matching process, any provider B is associated with any priority usage requester C, and based on the result of the association, the actual provider D and the recipient E are selected (in other words, the combination of actual provider D and recipient E is determined; see Figure 5).

[0068] The assignment change unit 22 can perform matching processing. In the matching processing, based on the first type of stored information 630 and the second type of stored information 650 read by the data reading unit 21, the provider B and the priority requester C are matched (associated). If the process reaches step S5, then at step S3, the transportation service requested by priority requester C has not been booked as desired. In the matching processing, the provider B who has been assigned a vehicle that matches or closely matches the request of priority requester C is associated with priority requester C. If there are multiple priority requesters C, a provider B is associated with each priority requester C.

[0069] The first type of stored information 630 (see Figure 9) includes information 624 indicating the user request of provider B, and also includes information (634 and 635) indicating the result of the first reservation process. The second type of stored information 650 (see Figure 11) includes information 642 indicating the user request of priority user C, and also includes information (652 and 653) indicating the result of the second reservation process.

[0070] Therefore, matching processing focusing on one preferred user C may be performed based on the usage request information 624 for each provider B, the result of the first reservation process for each provider B, the usage request information 642 for preferred user C, and the result of the second reservation process for preferred user C (however, referencing the usage request information 624 for each provider B is not mandatory). Matching processing focusing on multiple preferred users C may be performed based on the usage request information 624 for each provider B, the result of the first reservation process for each provider B, the usage request information 642 for each preferred user C, and the result of the second reservation process for each preferred user C (however, referencing the usage request information 624 for each provider B is not mandatory).

[0071] When we focus on a particular preferred user C, in the matching process, the provider B associated with the focused preferred user C becomes the actual provider D. That is, in the matching process, one of the provider B is selected as the actual provider D, and in this case, the focused preferred user C becomes the recipient E.

[0072] [Step S6: Rights Granting Process] In the rights provision process of step S6, following step S5, the allocation change unit 22 performs the rights provision process. Once the actual provider D and the recipient E are selected and determined in step S5, the allocation change unit 22 provides (transfers) the reservation for the use of transportation services for actual provider D to recipient E in the rights provision process. That is, the right to use transportation services that was allocated to provider B as actual provider D in the first reservation process is provided to recipient E in the rights provision process (in other words, transferred). At this time, the content of the right to use transportation services is exchanged between actual provider D and recipient E.

[0073] Specifically, the current reservation ranking information 633 and reserved vehicle information 634 (Figure 9) of provider B, who is the actual provider D, and the current reservation ranking information 651 and reserved vehicle information 652 (Figure 11) of priority user requester C, who is the recipient E, are exchanged in the rights provision process. Following this exchange, the reservation departure date and time in the transportation reservation information 635 of actual provider D is updated to match the schedule of the dispatched reserved vehicle shown in the exchanged reserved vehicle information 634. Following this exchange, the reservation departure date and time in the transportation reservation information 653 of recipient E is updated to match the schedule of the dispatched reserved vehicle shown in the exchanged reserved vehicle information 652. These updates may be performed in the allocation change unit 22. The allocation change unit 22 updates the information in DB 42 and 43 to reflect the results of the exchange by the rights provision process.

[0074] Furthermore, the allocation change unit 22 stores allocation result information 660, which indicates the content of the rights provision processing, in the allocation result DB 44. Figure 14 shows the structure of the allocation result information 660. The allocation result information 660 includes information 661 to 666. Information 661 represents the allocation management ID, which is the unique identification information of the allocation result information 660. Information 662 represents the member ID of the provider B (actual provider D) that was the subject of the rights provision processing, and information 663 represents the member ID of the priority user requester C (recipient E) that was the subject of the rights provision processing. Information 664 and 665 represent the departure and destination of the transportation service that was the subject of the rights provision processing. Information 666 represents the update date and time of the allocation result information 660 itself.

[0075] [Step S7: Results Reporting Process] The results reporting process performed in step S7 will now be described. Figure 15 shows the flow of information in the results reporting process. In the results reporting process, the provided results reporting unit 23 transmits the provided results information 670 to the terminal device TM_D of the actual provider D. The provided results information 670 is displayed on the display screen 571 of the terminal device TM_D.

[0076] Figure 16 shows the structure of the provided result information 670. The provided result information 670 includes information 671 to 674. Information 671 represents the member ID of actual provider D. Information 672 represents the reserved vehicle information ultimately assigned to actual provider D. Information 673 is transportation reservation information representing the details of actual provider D's transportation reservation. The reserved vehicle information 672 and transportation reservation information 673 match the reserved vehicle information 634 and transportation reservation information 635 (see Figure 9) that are assigned to actual provider D after the rights provision processing. Therefore, in the example in Figure 13, the reserved vehicle information 672 indicates that a reservation for the use of service vehicle 802 has been made, and actual provider D uses service vehicle 802 (the service vehicle that was originally intended for use by priority user C) according to the reserved vehicle information 672 and transportation reservation information 673. Information 674 is provided information indicating that the reservation details originally assigned to actual provider D have been transferred to another party.

[0077] Meanwhile, when allocation result information 660 is newly written to allocation result DB 44 (i.e., when allocation result DB 44 is updated), the data reading unit 31 reads the allocation result information 660 from allocation result DB 44 and also reads the second type of storage information 650 from priority usage DB 43. In the result reporting process, the data analysis unit 32 identifies the priority user requester C (i.e., recipient E) who is the target of the rights provision process based on the allocation result information 660 and the second type of storage information 650 read by the data reading unit 31. In the result reporting process, the allocation result reporting unit 33 sends request result information 680 to the terminal device TM_E of the recipient E, who is the identified priority user requester C. The request result information 680 is displayed on the display screen 571 of the terminal device TM_E.

[0078] Figure 17 shows the structure of the request result information 680. The request result information 680 includes information 681 to 684. Information 681 represents the member ID of recipient E. Information 682 represents the reserved vehicle information ultimately assigned to recipient E. Information 683 is transportation reservation information representing the details of recipient E's transportation reservation. The reserved vehicle information 682 and transportation reservation information 683 match the reserved vehicle information 652 and transportation reservation information 653 (see Figure 11) that are assigned to recipient E after the rights granting process. Therefore, in the example in Figure 13, the reserved vehicle information 682 indicates that a reservation for the use of service vehicle 801 has been made, and recipient E uses service vehicle 801 (a service vehicle that was originally intended for use by provider B) according to the reserved vehicle information 682 and transportation reservation information 683. Information 684 is provided information indicating that the reservation details originally assigned to another person (actual provider D) have been inherited (transferred) to recipient E.

[0079] Thus, the results reporting process includes the following steps: sending the provided result information 670 to the terminal device TM_D of the actual provider D, and sending the requested result information 680 to the terminal device TM_E of the recipient E.

[0080] [Step S8: Settlement Process] As described above, the reservation management device 100 manages member points that circulate within the SYS system. Member points are set for each member, and as shown in Figure 18, table data 700 related to member points is stored in the point information DB 45. User registrant A and provider B are members. Information representing each member's member points should be stored in table data 700 in a manner that is associated with each member's member ID. Member points have an expiration date, and the table data 700 shows the expiration date of the member points for each member. In addition, the table data 700 stores information indicating the update date and time of the member points for each member.

[0081] In the settlement process of step S8, the point update unit 34 performs the settlement process. In the settlement process, the point update unit 34 updates the table data 700 so that the member points of the provider B who has become the actual provider D increase (a specific example will be described later). If the same provider B becomes the actual provider D two or more times, a bonus process may be applied to increase the amount of member points gained each time compared to when the provider D becomes the actual provider D only once.

[0082] [Step S9: Actual Vehicle Dispatch Process] Based on the information stored in the data storage unit 40, the reservation management device 100 transmits the necessary information to the service provider's device 200 so that service vehicles are dispatched to the service provider's device 200 and the service provider's device 200. The reservation management device 100 may transmit all or part of the first type of stored information 630 and all or part of the second type of stored information 650 to the service provider's device 200.

[0083] In the actual vehicle dispatch process of step S9, the service provider's device 200 dispatches service vehicles to the provider B and the priority requester C based on the information received from the reservation management device 100. In the example in Figure 13, the service provider's device 200 dispatches service vehicle 802 to provider B (actual provider D) according to the reserved vehicle information 634 and transportation reservation information 635 in the first type of stored information 630, and dispatches service vehicle 801 to priority requester C (recipient E) according to the reserved vehicle information 652 and transportation reservation information 653 in the second type of stored information 650.

[0084] Furthermore, after the actual dispatch process has been completed and the service vehicle has been operated, or during the settlement process in step S9, the reservation management devices 100 and 200 and the financial institution's device (not shown) cooperate to settle the service usage fee. The service usage fee payable by any person of interest includes the fare for travel using public transportation, and may include a priority usage fee if the person of interest is a priority user C.

[0085] [Step S10: Standard Procedure] In the standard response process of step S10, service vehicles are dispatched to provider B and priority user C respectively, according to the results of the first and second reservation processing. In this case as well, after (or before) the service vehicles are actually operated, the reservation management devices 100 and 200 and the financial institution's device (not shown) cooperate to settle the service usage fee.

[0086] <<Definition of Corresponding Symbols>> Refer to Figures 19 and 20. In the following, for the sake of clarity, symbols will be assigned to various pieces of information as follows. Members of System SYS include the 1st to mth provider B and the 1st to nth priority requesters C. m and n are integers greater than or equal to 2 (however, "m=1" and "n=1" are acceptable). The ith provider B is referred to as provider B[i], and the ith priority requester C is referred to as priority requester C[i]. i represents any natural number.

[0087] The desired departure date and time, departure point, and destination indicated in the service provider B[i]'s request information 624 are referenced by the symbols J1_B[i], J2_B[i], and J3_B[i], respectively. The reservation order information 633 and reserved vehicle information 634 of service provider B[i] are referenced by the symbols J4_B[i] and J5_B[i], respectively. The reserved departure date and time, departure point, and destination indicated in the transport reservation information 635 of service provider B[i] are referenced by the symbols J6_B[i], J7_B[i], and J8_B[i], respectively. The location indicated by departure point J2_B[i] and the location indicated by departure point J7_B[i] are the same. The location indicated by destination J3_B[i] and the location indicated by destination J8_B[i] are the same. The desired departure date and time J1_B[i] and the booked departure date and time J6_B[i] may or may not match.

[0088] The desired departure date and time, departure point, and destination indicated in the preferred user request information 642 of priority user C[i] are referenced by the symbols J1_C[i], J2_C[i], and J3_C[i], respectively. The reservation ranking information 651 and reserved vehicle information 652 of priority user request C[i] are referenced by the symbols J4_C[i] and J5_C[i], respectively. The reserved departure date and time, departure point, and destination indicated in the transport reservation information 653 of priority user request C[i] are referenced by the symbols J6_C[i], J7_C[i], and J8_C[i], respectively. The location indicated by departure point J2_C[i] and the location indicated by departure point J7_C[i] are the same. The location indicated by destination J3_C[i] and the location indicated by destination J8_C[i] are the same. The desired departure date and time J1_C[i] and the booked departure date and time J6_C[i] may or may not match.

[0089] For the sake of simplicity, the following explanation will focus only on a single date, and the times shown below will be assumed to be times on that single date. Therefore, only times will be given as specific examples of dates and times. In this embodiment, times will be expressed in 24-hour format. For example, 9:30 or 9:30 represents 9:30 AM, and 15:30 or 15:30 represents 3:30 PM. When focusing only on a single date, the departure date and time are equivalent to the departure time.

[0090] Based on the operations described above, several specific operational examples, applied technologies, and modified technologies related to the SYS system will be explained in the following multiple embodiments. In this embodiment, the matters described above apply to each of the following embodiments unless otherwise specified and without contradiction. In the event of any contradiction between the matters described above and those described in each embodiment, the description in the respective embodiment may take precedence. Furthermore, unless there is a contradiction, the matters described in any of the multiple embodiments shown below can be applied to any other embodiment (i.e., it is possible to combine any two or more embodiments from the multiple embodiments).

[0091] <<First Example>> The first embodiment will be described. In the first embodiment, we will focus only on the provider B[1] and the priority requester C[1]. Figure 21 is a sequence diagram showing the operation flow of the system SYS according to the first embodiment. Figure 22 is a diagram showing information related to the provider B[1] and the priority requester C[1]. As time progresses, the times t11, t12, t13, and t14 will occur in this order. For example, the times t11, t12, t13, and t14 are 9:00, 9:30, 11:00, and 11:30, respectively.

[0092] In the example shown in Figure 21, after the first reservation process 1110 and the second reservation process 1120, an assignment change process is executed that involves modifying the contents of those reservations. The assignment change process includes processes 1130, 1140, 1150, and 1160 described later. However, it may also be considered that the assignment change process is constituted by processes 1130 and 1140.

[0093] At time t11, the provider information 620 for provider B[1] is transmitted from the terminal device TM_B of provider B[1] to the reservation management device 100, and in response, the reservation management device 100 executes a first reservation process 1110 based on the provider information 620. In the first reservation process 1110, a reservation for the use of transportation services is made for provider B[1], and service vehicle CR1 is assigned to provider B[1] as a vehicle for dispatch reservation.

[0094] Here, the desired departure date and time J1_B[1] of provider B[1] is set to time t13, and the departure point J2_B[1] and destination J3_B[1] are set to the first location (e.g., Kobe Station) and the second location (e.g., the trailhead of Mt. Rokko), respectively. Immediately after the first reservation process 1110 is performed, the reservation order information J4_B[1] represents time t11, and the reserved vehicle information J5_B[1] represents the vehicle ID of service vehicle CR1. Also immediately after the first reservation process 1110 is performed, the reserved departure date and time J6_B[1] is set to time t13. The departure point J7_B[1] and destination J8_B[1] are set to the first location and the second location, respectively. In this way, the first reservation process 1110 reserves a service vehicle as requested by provider B[1]. If the rights granting process 1140 described below is not performed, the provider B[1] will depart from the departure point in service vehicle CR1 at time t13.

[0095] At time t12, priority request information 640 for priority requester C[1] is transmitted from terminal device TM_C of priority requester C[1] to reservation management device 100, and in response, reservation management device 100 executes a second reservation process 1120 based on the priority request information 640. In the second reservation process 1120, a reservation for the use of the transportation service is made for priority requester C[1], and service vehicle CR2 is assigned to priority requester C[2] as a vehicle for dispatch reservation.

[0096] Here, the preferred departure date and time J1_C[1] of priority user C[1] is assumed to be time t13, and the departure point J2_C[1] and destination J3_C[1] are assumed to be the first location (e.g., Kobe Station) and the second location (e.g., Rokko Mountain trailhead), respectively. Immediately after the second reservation process 1120 is performed, the reservation ranking information J4_C[1] represents time t12, and the reserved vehicle information J5_C[1] represents the vehicle ID of service vehicle CR2. Priority user C[1] wishes to depart at time t13, but due to the operating schedule, service vehicle CR2 cannot depart at time t13. As a result, immediately after the second reservation process 1120 is performed, the reserved departure date and time J6_C[1] is assumed to be time t14. The departure point J7_C[1] and destination J8_C[1] are set to the first location and the second location, respectively. Thus, in the second reservation process 1120, the service vehicle requested by priority user C[1] is not reserved (although C[1] wishes to depart at time t13, only a service vehicle departing at time t14 is reserved). If the rights granting process 1140 described later is not performed, priority user C[1] will depart from the departure point at time t14 in service vehicle CR2.

[0097] After the first reservation process 1110 and the second reservation process 1120, the check process in step S4 (see Figure 5) is executed. In the check process in this example, the contents of the transportation service reservation in the second reservation process 1120 (transportation reservation information 653) do not match the contents of the desired usage information 642 of the priority user C[1]. That is, immediately after the second reservation process 1120, the desired departure date and time J1_C[1] and the reserved departure date and time J6_C[1] are different (more specifically, the reserved departure date and time J6_C[1] is later than the desired departure date and time J1_C[1]). Therefore, the process proceeds from step S4 to step S5 (see Figure 5).

[0098] In the matching process of step S5, the matching process 1130 is executed. In the first embodiment, the matching process 1130 associates the provider B[1] and the preferred user requester C[1], thereby setting the provider B[1] and the preferred user requester C[1] as the actual provider D and the recipient E, respectively. Subsequently, in step S6, the rights granting process 1140 is executed.

[0099] In the rights provision process 1140, the right to use the transportation allocated to provider B[1] as actual provider D in the first reservation process 1110 is provided (in other words, transferred) to priority user requester C[1] as recipient E. At this time, the allocation change unit 22 exchanges the right to use the transportation allocated to provider B[1] in the first reservation process 1110 with the right to use the transportation allocated to priority user requester C[1] in the second reservation process 1120. This is equivalent to exchanging the information J4_B[1] and J5_B[1] of provider B[1] immediately after the first reservation process 1110 with the information J4_C[1] and J5_C[1] of priority user requester C[1] immediately after the second reservation process 1120. As a result of this exchange, the right to use the transportation allocated to provider B[1] in the first reservation process 1110 is provided (transferred) to priority user requester C[1]. In the rights provision process 1140, the reserved vehicle information J5_C[1] of priority user C[1] will be changed from the vehicle ID of service vehicle CR2 to the vehicle ID of service vehicle CR1 (Figure 22). On the other hand, in the rights provision process 1140, the reserved vehicle information J5_B[1] of provider B[1] will be changed from the vehicle ID of service vehicle CR1 to the vehicle ID of service vehicle CR2.

[0100] Furthermore, in the rights provision process 1140, the allocation change unit 22 changes the reservation order information J4_B[1] from time t11 to time t12, and changes the reservation order information J4_C[1] from time t12 to time t11 (see Figure 22). That is, when the rights provision process 1140 is performed, the date and time when the reservation was made by the provider B[1] is considered to have been shifted from time t11 to time t12, and the date and time when the reservation was made by the priority user C[1] is considered to have been advanced from time t12 to time t11. Shifting the date and time of the reservation corresponds to a decrease in the reservation priority, and advancing the date and time of the reservation corresponds to an increase in the reservation priority.

[0101] Furthermore, in the rights provision process 1140, the allocation change unit 22 updates the reserved departure date and time J6_B[1] of the actual provider D, the provider B[1], to match the schedule of the service vehicle CR2. Here, because the service vehicle CR2 cannot depart until time t14, the reserved departure date and time J6_B[1] is changed from time t13 to time t14 (see Figure 22). Similarly, in the rights provision process 1140, the allocation change unit 22 updates the reserved departure date and time J6_C[1] of the recipient E, the priority user requester C[1], to match the schedule of the service vehicle CR1. Since the service vehicle CR1 is originally able to depart at time t13, the reserved departure date and time J6_C[1] is changed from time t14 to time t13 (see Figure 22).

[0102] After the rights granting process 1140, the result reporting process 1150 is executed. In the result reporting process 1150, the following processes are executed: sending the provision result information 670 to the terminal device TM_D of the actual provider D (B[1]), and sending the request result information 680 to the terminal device TM_E of the recipient E (C[1]).

[0103] In this example, the reserved vehicle information 672 and transportation reservation information 673 (see Figure 16) in the provided result information 670 match the reserved vehicle information 634 and transportation reservation information 635 (J5_B[1]~J8_B[1]) of the actual provider D(B[1]) after the rights provision processing 1140. Upon receiving the provided result information 670, the actual provider D(B[1]) uses the service vehicle CR2 at time t14, which is the reserved departure date and time.

[0104] In this example, the reserved vehicle information 682 and transportation reservation information 683 in the request result information 680 (see Figure 17) match the reserved vehicle information 652 and transportation reservation information 653 (J5_C[1]~J8_C[1]) of the recipient E(C[1]) after the rights granting process 1140. Upon receiving the request result information 680, the recipient E(C[1]) uses the service vehicle CR1 at the reserved departure date and time t13.

[0105] Furthermore, the rights granting process 1140 and the result reporting process 1150 are executed after time t12 and before time t13. After the rights granting process 1140, the settlement process 1160 is executed by the point update unit 34 at any time.

[0106] In settlement process 1160, the point update unit 34 values ​​the member points held by the provider B[1] who has become the actual provider D as PNT. UP Increase only (PNT UP >0). The result of the increase is reflected in table data 700. The priority usage fee (see Figure 11) represented by information 643 in the priority request information 640 from priority requester C[1] who became provider E is conveniently referred to as priority usage fee α. The larger the priority usage fee α, the higher the value PNT. UP It will get bigger.

[0107] Value PNT UPThe increase in membership points by [reason] is the consideration (in other words, the reward) received by Provider B[1] for providing (transferring) the right to use transportation facilities to Priority User C[1]. On the other hand, Priority User C[1] pays the priority usage fee set by itself. In the settlement process 1160, the point update unit 34 collects the priority usage fee from Priority User C[1]. The priority usage fee collected from Priority User C[1] becomes the original capital of the consideration received by Provider B[1]. All or part of the priority usage fee corresponds to the consideration received by Provider B[1].

[0108] Priority User C[1] can pay the priority usage fee with the membership points it holds. In this case, in the settlement process 1160, the point update unit 34 reduces the membership points held by Priority User C[1] by the value PNT DWN only. Here, it is good if "PNT DWN =PNT UP " or "PNT DWN >PNT UP " holds. At this time, the membership points corresponding to the value PNT DWN correspond to the priority usage fee.

[0109] In this way, the priority usage management unit 30 executes the settlement process 1160 for granting the consideration based on the priority usage fee collected from the recipient E (C[1]) to the actual provider D (B[1]). When the priority usage fee is paid and the consideration is received in membership points, the point update unit 34 will perform the settlement process 1160.

[0110] However, in the settlement process 1160, Priority User C[1] may pay the priority usage fee in currency (legal currency or virtual currency). Similarly, in the settlement process 1160, Provider B[1] may receive the consideration in currency. The payment of the priority usage fee and the receipt of the consideration in currency are settled based on the financial institution information 602 and 622 (see FIGS. 7 and 9) of each member, and the settlement is executed under the control of the priority usage management unit 30.

[0111] Furthermore, the reservation management device 100 exchanges currency and member points at a predetermined exchange rate. Member points may be electronic money that can be used to purchase various goods. Electronic money may also be points that can be used to pay for any service. Any member may use their member points as fares for using transportation services operated by system SYS.

[0112] Members who wish to prioritize the use of transportation services, such as those who need to reach their destination quickly, can apply for a reservation as a priority user C. On the other hand, members who are not in a hurry and are willing to relinquish their reservation can apply for a reservation as a provider B. In this case, the right to use the transportation service initially allocated to provider B may be transferred to priority user C, fulfilling the priority user C's wish. In return, priority user C pays a priority usage fee, and provider B receives compensation based on the priority usage fee. Therefore, provider B also benefits. As a result, even when demand for transportation services exceeds the supply, both provider B and priority user C can enjoy benefits.

[0113] Individuals who wish to receive priority access to transportation services are designated as priority users (C), while individuals who are willing to transfer their allocated transportation rights to others are designated as service providers (B). This allows for the provision of more beneficial transportation services to each member (each user). Priority users (C) have their desire for priority access fulfilled, and service providers (B) receive compensation for transferring their transportation rights. Furthermore, it offers the advantage of increased flexibility in scheduling for the system SYS.

[0114] In the first reservation process 1110, the right to use the transportation allocated to provider B is exchanged with the right to use the transportation allocated to priority user C in the second reservation process 1120. As a result, the former right to use the transportation is provided (inherited) by priority user C. Therefore, provider B's right to use the transportation is not lost entirely, and provider B is able to travel to their destination.

[0115] <<Second Example>> A second embodiment will be described. The matching process performed on provider B[i] and priority requester C[j] will be described. i and j are arbitrary natural numbers. Assume that the judgment in step S4 performed on priority requester C[j] is negative. That is, the content of the transportation service reservation in the second reservation process for priority requester C[j] differs from the content of priority requester C[j]'s desired usage information 642. This means that at the stage of the second reservation process, the transportation service desired by priority requester C[j] could not be reserved, and the reserved departure date and time J6_C[j] (e.g., time t14) in the second reservation process is later than the desired departure date and time J1_C[j] (e.g., time t13) (see Figure 22). For the sake of simplification, provider B and B[i] may be written as person B and B[i] below, and priority requester C and C[j] may be written as person C and C[j] below.

[0116] The assignment change unit 22 can determine whether to associate persons B[i] and C[j] with each other in the matching process, based on the result of the first reservation process for person B[i], the usage request information 642 for person C[j], and the result of the second reservation process for person C[j]. The first and second matching methods are listed below.

[0117] The first matching method will now be explained. In the first matching method, the success or failure of the following first to third judgment conditions is determined, and only if all of the first to third judgment conditions are met for person B[i] and C[j] are associated with each other. Figure 23 shows a conceptual diagram of the first to third judgment conditions.

[0118] The first determination condition is that "the reservation departure date and time J6_B[i] for person B[i] in the first reservation process is earlier than the reservation departure date and time J6_C[j] for person C[j] in the second reservation process."

[0119] The second determination condition is that "the reserved departure date and time J6_B[i] of person B[i] in the first reservation process belongs to the period PP[j] based on the desired departure date and time J1_C[j] of person C[j]." The period PP[j] is the first predetermined time ΔT from the desired departure date and time J1_C[j]. A From the date and time just before, the second predetermined time ΔT is calculated from the desired departure date and time J1_C[j]. B This is the period up to the date and time after that. However, the second predetermined time ΔT B It may be zero, in which case the period PP[j] is the first predetermined time ΔT from the desired departure date and time J1_C[j]. A This period is from the date and time just before the desired departure date and time J1_C[j]. First predetermined time ΔT A It is also acceptable to set it to zero. The predetermined time ΔT A and ΔT B It is also possible to set both of these to zero. Predetermined time ΔT A and ΔT B When both of these are zero, the second condition is met only when the reserved departure date and time J6_B[i] for person B[i] in the first reservation process matches the desired departure date and time J1_C[j] for person C[j].

[0120] The third determination condition is that the distance d[i,j] between the starting point J7_B[i] of person B[i] and the starting point J7_C[j] of person C[j] is a predetermined distance d REF The condition is that the distance d[i,j] is also the distance between the starting points J2_B[i] and J2_C[j]. REF This value may be zero. In this case, the third condition will only be met if the starting points of persons B[i] and C[j] are the same.

[0121] The second matching method will now be explained. The allocation change unit 22 can derive a matching score SCR for each combination of provider B and priority requester C. The matching score SCR for the combination of persons B[i] and C[j] is specifically represented by the symbol SCR[i,j]. In the second matching method, it is determined whether to associate persons B[i] and C[j] with each other based on the matching score SCR[i,j].

[0122] The matching score SCR[i,j] is the sum of the time score and the distance score. The time score in the matching score SCR[i,j] increases as the reserved departure date and time J6_B[i] of person B[i] in the first reservation process is closer to the desired departure date and time J1_C[j] of person C[j], assuming that the first judgment condition above is met. When the difference between the reserved departure date and time J6_B[i] of person B[i] and the desired departure date and time J1_C[j] of person C[j] in the first reservation process is constant, the time score in the matching score SCR[i,j] is higher when the former date and time (J6_B[i]) is earlier than the latter date and time (J1_C[j]) than when the reverse is true. The distance score in the matching score SCR[i,j] increases as the distance d[i,j] decreases.

[0123] The assignment change unit 22 related to the second matching method associates persons B[i] and C[j] with each other if the matching score SCR[i,j] is equal to or greater than a predetermined standard score, and does not associate persons B[i] and C[j] with each other otherwise. The rules for deriving the matching score SCR[i,j] may be defined such that the matching score SCR[i,j] is equal to or greater than the standard score only if all of the above first to third determination conditions are met for persons B[i] and C[j].

[0124] The assignment change unit 22 can utilize the first or second mapping method. If persons B[i] and C[j] are mapped by the first or second mapping method and (i,j)=(1,1), then persons B[1] and C[1] are set to actual provider D and recipient E, and the operations shown in the first embodiment, including processes 1140-1160 in Figure 21, are executed.

[0125] <<Third Example>> A third embodiment will be described. Assume that the DB42 contains Type 1 storage information 630 for p people for providers B[1] to B[p], where p is any integer greater than or equal to 2. In this state, assume that the content of the transportation service reservation made in the second reservation process for priority user C[j] differs from the content of priority user C[j]'s desired usage information 642. This means that at the stage of the second reservation process, the transportation service desired by priority user C[j] could not be reserved, and the reservation departure date and time J6_C[j] (e.g., time t14) in the second reservation process is later than the desired departure date and time J1_C[j] (e.g., time t13) (see Figure 22).

[0126] In this case, the allocation change unit 22 performs a matching process based on the results of the first reservation process for persons B[1] to B[p], the usage request information 642 for person C[j], and the results of the second reservation process for person C[j]. Through this matching process, one of persons B[1] to B[p] is associated with person C[j], or none of persons B[1] to B[p] are associated with person C[j]. If, as a result of this matching process, person B[i] among persons B[1] to B[p] is associated with person C[j], then person B[i] will be set (selected) as the actual provider D. On the other hand, person C[j] becomes the recipient E, and as a result, the right to use the transportation that was assigned to the actual provider D (B[i]) in the first reservation process will be provided to the recipient E (C[j]).

[0127] The first or second matching method described above can be used as the method of matching. If persons B[i] and C[j] are matched to each other by the first or second matching method and (i,j)=(1,1), then persons B[1] and C[1] are set to provider D and recipient E, and the operations shown in the first embodiment, including processes 1140-1160 in Figure 21, are executed.

[0128] The matching process shown in this embodiment makes it possible to match suitable members who should exchange the right to use public transportation with each other.

[0129] Furthermore, when the first or second matching method is used, multiple potential providers B (e.g., individuals B[1] to B[3]) may be associated with person C[j]. In this case, for example, the matching score SCR derived between the multiple potential providers B and person C[j] may be referenced, and the potential provider B corresponding to the highest matching score SCR may be selected as the actual provider D.

[0130] <<Fourth Example>> A fourth embodiment will now be described. In the first to third embodiments, only one person C[1] or C[j] is considered as the priority requester C. However, when many members use the system SYS, a matching process is performed between multiple providers B and multiple priority requesters C. In this case as well, for each priority requester C who cannot reserve a service vehicle as desired without an assignment change process, an assignment change process including a matching process may be performed in the manner shown in the first to third embodiments.

[0131] Let's assume that currently, Type 1 storage information 630 for p people for available providers B[1] to B[p] is stored in DB42, and Type 2 storage information 650 for q people for priority users C[1] to C[q] is stored in DB43. p and q are any integers greater than or equal to 2. Let's assume that for all integers j that satisfy "1 ≤ j ≤ q", the content of the transportation service reservation in the second reservation process for priority user C[j] differs from the content of the priority user C[j]'s desired usage information 642. This means that at the stage of the second reservation process, for each priority user C, the transportation service desired by priority user C[j] could not be reserved, and the reserved departure date and time J6_C[j] (e.g., time t14) in the second reservation process is later than the desired departure date and time J1_C[j] (e.g., time t13) (see Figure 22).

[0132] In this case, the assignment change unit 22 performs a matching process based on the results of the first reservation process for persons B[1] to B[p], the usage request information 642 for persons C[1] to C[q], and the results of the second reservation process for persons C[1] to C[q]. Through this matching process, one of persons B[1] to B[p] is associated with one of persons C[1] to C[q]. Ideally, one person from B[1] to B[p] would be associated with each of persons C[1] to C[q], but this may not be the case depending on the conditions.

[0133] Case CS is one in which two or more priority requesters, persons C[1] to C[k], are associated with person B[i], a specific person among persons B[1] to B[p]. MLT Consider the following (see Figure 24). k is any integer greater than or equal to 2 and less than or equal to q. The first or second matching method described above can be used for matching. For example, when using the first matching method, if all of the first to third judgment conditions are met between person B[i] and each of persons C[1] to C[k], then person B[i] is associated with person C[1] to C[k]. Alternatively, for example, when using the second matching method, if all of the matching scores SCR[i,1] to SCR[i,k] are equal to or greater than the standard score, then person B[i] is associated with person C[1] to C[k].

[0134] Case CS MLT In this process, the assignment change unit 22 executes a recipient determination process to determine one of the persons C[1] to C[k] as the recipient E, and sets person B[i] (the specific person mentioned above) as the actual provider D for that recipient E. Then, the assignment change unit 22 provides the recipient E with the right to use the transportation that was assigned to the actual provider D (B[i]) in the first reservation process.

[0135] This explains the process of determining who will be the provider. Case CS MLTIn this process, the assignment change unit 22 refers to information 643 in the second type of stored information 650 of persons C[1] to C[k] (Figure 11), that is, it refers to each priority usage fee set by persons C[1] to C[k]. Then, the assignment change unit 22 selects the largest priority usage fee F among the priority usage fees for persons C[1] to C[k]. MAX Identify the person C[1] to C[k] and determine the person with the highest priority usage fee F. MAX The person corresponding to is determined as the provider E. For example, if the priority usage fee for person C[1] is 500 yen, and the priority usage fees for people C[2] to C[k] are all less than 500 yen, then the priority usage fee F MAX The amount is 500 yen, and person C[1] is determined to be the provider E.

[0136] According to this, transportation services will be prioritized for priority users C who have set a higher priority usage fee, thus balancing the burden and benefits. In addition, the compensation received by the actual service provider D will increase, which is also a great benefit for the actual service provider D.

[0137] When each priority requester C sends priority request information 640 from terminal device TM_C, they can select and set a priority usage fee from among several fee tiers, or they can set the priority usage fee to any fee. In particular, when the selection setting method is adopted, the same priority usage fee is often set for multiple priority requesters C.

[0138] Case CS MLT In this case, among persons C[1] to C[k], the highest priority usage fee F MAX If the total number of people corresponding to this is 1, the allocation change unit 22 will determine the maximum priority usage fee F MAX The person corresponding to this should be determined as recipient E. Case CS MLT In this case, among persons C[1] to C[k], the highest priority usage fee F MAX If the total number of people corresponding to the same person is 2 or more, the assignment change unit 22 will determine the highest priority usage fee F MAX Of the two or more individuals C corresponding to this, the individual C associated with the earliest reservation occurrence date and time (651) may be determined as the provider E.

[0139] <<Example 5>> A fifth embodiment will be described. In the fifth embodiment, another example of the provider determination process will be described.

[0140] The above case CS MLT In this case, among persons C[1] to C[k], the highest priority usage fee F MAX If the total number of people corresponding to this is 1, the allocation change unit 22 will determine the maximum priority usage fee F MAX The person corresponding to this should be determined as recipient E. Case CS MLT In this case, among persons C[1] to C[k], the highest priority usage fee F MAX If the total number of people corresponding to is 2 or more, the assignment change unit 22 according to the fifth embodiment further determines the provider E by referring to the priority preference level.

[0141] The priority preference level indicates the degree to which a user desires priority use of transportation services. When each priority requester C sends priority request information 640 from terminal device TM_C, they can select and set their priority preference level to one of several levels.

[0142] Case CS MLT Of these, the highest priority usage fee is F MAX Cases in which two or more corresponding individuals are included in individuals C[1]~C[k] are, in particular, case CS MLT_1 This is referred to as Case CS. MLT_1 In this case, the highest priority usage fee F MAX Let C[1]~C[r] be the two or more people corresponding to the given condition, where r is an integer satisfying "2 ≤ r ≤ k". For example, case CS MLT Of these, the case where the priority usage fee for persons C[1] and C[2] is 500 yen and the priority usage fees for persons C[3] to C[k] are all less than 500 yen is case CS. MLT_1 This applies. In this case, priority usage fee F MAX The fee is 500 yen, and persons C[1] and C[2] have the highest priority usage fee F. MAX These two individuals correspond to each other.

[0143] Case CSMLT_1 In this process, the assignment change unit 22 refers to information 644 in the second type of stored information 650 of persons C[1] to C[r] (Figure 11), and selects the highest priority preference P among the priority preference preferences of persons C[1] to C[r]. MAX The assignment change unit 22 then identifies the person with the highest priority preference P among the people C[1] to C[r]. MAX The person corresponding to this is determined as provider E. Here, the priority preference level can be set to "low," "medium," or "high." A "medium" priority preference level is higher than a "low" priority preference level, and a "high" priority preference level is even higher than a "medium" priority preference level. However, the number of priority preference level settings is arbitrary, as long as it is two or more.

[0144] Therefore, for example, case CS MLT_1 If "r=2", and the priority preference of person C[1] is "high" and the priority preference of person C[2] is "low" or "medium", then the priority preference P for "high" MAX Person C[1] corresponding to this is determined to be the provider E. Conversely, for example, in case CS MLT_1 If "r=2", and the priority preference of person C[2] is "high" and the priority preference of person C[1] is "low" or "medium", then the priority preference P for "high" MAX Person C[2] corresponding to this is determined to be the recipient E. Case CS MLT_1 The same applies when "r≧3" is true.

[0145] This embodiment allows for the determination of the recipient E who will actually receive priority access to transportation services, even when priority fees alone are insufficient to differentiate between priority users. Since the priority preference level represents the degree to which a user desires priority access, a suitable recipient E can be selected and determined by referring to this level. A person C who is likely to pay a priority fee but desperately wants priority access should set their priority preference level high. A person C who would like priority access if possible should set their priority preference level to a moderate level.

[0146] Furthermore, a minimum priority fee may be set for the priority service fee depending on the level of priority requested by priority user C. For example, if the priority level is set to "medium," the priority service fee can only be set to a minimum of 200 yen or more, and if the priority level is set to "high," the priority service fee can only be set to a minimum of 400 yen or more. The minimum fee may depend on the distance between the departure point and the destination, or on the fare required for travel between the departure point and the destination by service vehicle.

[0147] Case CS MLT_1 In such cases, even after referring to the priority preference level, it may still be impossible to determine which is superior. That is, Case CS MLT_1 In this case, among persons C[1] to C[r], priority usage fee F MAX and priority preference P MAX The total number of people corresponding to this may be 2 or more. In this case, the priority usage fee F MAX and priority preference P MAX Of the two or more persons C corresponding to this, the person C associated with the earliest reservation occurrence date and time (651) may be determined as the provider E.

[0148] <<Sixth Example>> A sixth embodiment will be described.

[0149] After the rights granting process, it is expected that the reservation will be secured according to the wishes of the recipient E, but this is not always possible. For example, when the preferred user C, who should be the recipient E, wishes to depart at 11:00, it may not be possible to reserve a service vehicle departing at 11:00 during the second reservation process, and there may be no available service providers B who have a reservation for a service vehicle that can depart at 11:00. In this case, it is best to identify a available service provider B who has a reservation for a service vehicle that can depart after 11:00 but as close to 11:00 as possible, and set that available service provider B as the actual service provider D.

[0150] The data storage unit 40 may store Type 1 stored information 630 and Type 2 stored information 650 for a certain period in the past, and may also store dispatch performance information for a certain period in the past. The dispatch performance information is the dispatch performance information of service vehicles. The reservation management device 100 (for example, the priority use support unit 20) may perform the following pre-notification processing based on the information stored in the data storage unit 40. In the pre-notification processing, based on the information stored in the data storage unit 40, the degree of congestion at a specific location at a specific time, day of the week, or date in the future is predicted, and the predicted result of the congestion degree is notified to all members of the system SYS. Notification of the predicted result of the congestion degree is achieved by sending information indicating the predicted result of the congestion degree to each member's terminal device TM. The degree of congestion here refers to the degree of congestion in the use of service vehicles operated by the system SYS. Members who receive the notification can, if necessary, apply for a reservation for transportation services early based on the predicted result of the congestion degree, and can also set a priority usage fee or priority preference level based on the content of the notification.

[0151] The congestion forecast may include predicted times for vehicle dispatch to specific locations during the specified time period, day of the week, or date (predicted time required to dispatch a service vehicle).

[0152] The reservation management device 100 (for example, the priority use support unit 20) may also disclose to each member the reservation status of the transportation service made by the provider B and the priority use requester C, while concealing each member's personal information. Priority use requester C can change various conditions related to the use of the transportation service until the reservation is finalized, while referring to the disclosed information as appropriate.

[0153] Priority user requester C may transfer the right to use the transportation that they received from another person to yet another person. For example, in the example in Figure 21, after receiving the request result information 680 at the recipient E's terminal device TM_E, person C[1] as recipient E may change their plans and become provider B. In this case, after receiving the request result information 680 at the terminal device TM_E, recipient E may send information from their terminal device TM to the reservation management device 100 indicating that they may transfer the right to use the transportation (right to use service vehicle CR1) that they received from another person to yet another person. Upon receiving this information, the reservation management device 100 may transfer the above right to use (right to use service vehicle CR1) to another priority user requester C in accordance with the intentions of the person who was recipient E.

[0154] The reservation management device 100 may also combine members whose travel routes by service vehicle are similar and request the service vehicle operator to arrange for the combined members to travel in the same service vehicle (by transmitting the necessary information to the service provider's device 200).

[0155] The reservation management device 100 may perform matching processing or assign service vehicles, taking into consideration the relationships between the travel routes of each member using service vehicles. For example, if there is a second member who has set their departure point near the destination of the first member, a service vehicle common to both the first and second members may be assigned.

[0156] Persons B and C belong to the group of reservation requesters who request the reservation management device 100 to use transportation services. Reservation requesters request transportation services by transmitting reservation request information from their terminal device TM to the reservation management device 100. When the reservation requester is person B, the reservation request information is provider information 620, and when the reservation requester is person C, the reservation request information is priority request information 640. When the reservation management device 100 receives reservation request information from a reservation requester, it may allow the requester to register whether they are willing to be provider B. Priority preference information may be included in all reservation request information. In this case, among the multiple priority preference levels, the reservation requester corresponding to the reservation request information with the lowest priority preference level (in the specific example shown in the fifth embodiment, the "low" priority preference level) may be made to function as provider B, and the other reservation requesters may be made to function as priority requesters C. The priority of transportation allocation for persons registered as provider B is lower than that for priority requesters C.

[0157] Consider a case where all reservation request information includes priority preference information, and the priority preference can be set to one of five levels, from 1st to 5th. Here, the priority preference of level (i+1) is higher than the priority preference of level i. In this case, the reservation requester corresponding to the reservation request information with a priority preference of level 1 or 2 may function as provider B, and the reservation requester corresponding to the reservation request information with a priority preference of level 3, 4, or 5 may function as priority user C. The priority usage response unit 20 allocates the right to use transportation preferentially to members corresponding to relatively high priority preferences over members corresponding to relatively low priority preferences. Furthermore, the consideration (e.g., member points) given to actual provider D in the settlement process when provider B of level 2 becomes actual provider D may be higher than the consideration (e.g., member points) given to actual provider D in the settlement process when provider B of level 1 becomes actual provider D. In other words, the compensation paid to a member who transfers their right to use public transportation to another person (actual provider D) may be adjusted according to the member's priority level. The same applies if the priority level setting for provider B is three or more levels.

[0158] Provider D transfers the right to use the transportation service that it owned to recipient E. In this case, provider D will generally use alternative transportation, but may also discontinue using transportation altogether as a result of transferring the right to use the transportation service that it owned to recipient E.

[0159] The priority usage fee may include special surcharges. These special surcharges are separate from the fare for transportation by service vehicle and the payment to be made to the actual provider D, and are paid, for example, to the operating company of the reservation management device 100 or the service provider device 200, or to the driver of the service vehicle.

[0160] In this embodiment, an example of applying the present invention to transportation services has been described in detail, but the present invention can also be applied to services other than transportation services. For example, the present invention can be applied to accommodation services or food and beverage services, in which case, transportation services in the above description should be read as accommodation services or food and beverage services. A reservation management device for transportation services performs processing related to reservations for the use of transportation services. In contrast, a reservation management device for accommodation services performs processing related to reservations for the use of accommodation services (reservations for the use of accommodation facilities). A reservation management device for food and beverage services performs processing related to reservations for the use of food and beverage services (reservations for the use of restaurants).

[0161] <<Example 7>> A seventh embodiment will now be described. Figure 25 shows a functional block diagram of the reservation management device 100. Figure 25 shows each function of the reservation management device 100 as a block diagram from a different perspective than Figure 3. The reservation management device 100 is broadly composed of functional blocks F1 to F4.

[0162] Functional block F1 is an information input unit. The information input unit F1 is composed of the data receiving unit 11 in Figure 3 or the data input corresponding unit 10 in Figure 3. The information input unit F1 corresponds to an input interface that receives various information and signals from the terminal device TM.

[0163] Functional block F2 is the processing unit. Processing unit F2 includes parts of the data input handling unit 10, priority usage handling unit 20, and priority usage management unit 30 in Figure 3 that do not belong to functional block F1. For example, processing unit F2 is composed of the priority usage handling unit 20 and the priority usage management unit 30. Functional block F3 is the memory. Memory F3 includes non-volatile memory such as ROM or flash memory, and volatile memory such as RAM. Functional block F4 is the data holding unit. Data holding unit F4 is the same as data holding unit 40 in Figure 3. Note that data holding unit F4 may be a recording device provided outside the reservation management device 100 and externally connected to the reservation management device 100.

[0164] The processing unit F2 is an arithmetic processing unit including a CPU and a GPU, and each function of the processing unit F2 may be realized by executing a program stored in memory F3 in the processing unit F2. The program executed in the processing unit F2 may include multiple programs. The processing unit F2 may be provided with multiple CPUs, and multiple functions of the processing unit F2 may be realized by executing multiple programs on these multiple CPUs. The multiple functions realized in the processing unit F2 may be realized by multiple computer devices, or they may be realized using cloud computing. Here, the processing unit F2 is considered to include an output interface (information output unit) that transmits various information and signals to the terminal device TM.

[0165] The processing unit F2 performs at least the first reservation process, second reservation process, matching process, rights granting process, result reporting process, and settlement process described above. Of the processes performed in each step S1 to S10 in Figure 5, all processes other than the reception of information or signals by the functional block F1 may be performed by the processing unit F2.

[0166] A transportation service reservation management device (100) according to one aspect of the present invention includes an information input unit (F1) that receives first reservation request information (provider information 620) from a first terminal device, which includes information on a first target person (provider B) wishing to use the transportation service, and second reservation request information (priority request information 640) from a second terminal device, which includes information on a second target person (priority user requester C) wishing to use the transportation service and information on priority usage fees; and a processing unit (F2) that executes a first reservation process to make a reservation for the transportation service to the first target person based on the first reservation request information, and a second reservation process to make a reservation for the transportation service to the second target person based on the second reservation request information, wherein the processing unit is configured to execute an assignment change process after executing the first reservation process and the second reservation process (see, for example, Figure 21). The aforementioned allocation change process includes a right granting process that provides the second person with the right to use the transportation allocated to the first person in the first reservation process, and a settlement process that grants the first person consideration based on the priority usage fee collected from the second person.

[0167] The first target person corresponds to provider B. Provider B may be the representative of the first group (first group of individuals) consisting of multiple individuals. In this case, the desired usage information 624 included in the provider information 620 as the first reservation request information corresponds to the desired usage information 624 of each individual belonging to the first group (see Figures 8 and 9). The first target person can also be considered to include each individual in the first group, including provider B. If the first target person includes multiple individuals in the first group, the consideration based on the priority usage fee may be given to any one of the individuals in the first group (the individual indicated in the provider information 620), or it may be distributed and given to each individual in the first group.

[0168] The first terminal device corresponds to terminal device TM_B. Terminal device TM_B, as the first terminal device, is basically terminal device TM possessed and operated by provider B. However, the first terminal device (terminal device TM_B) may be a terminal device TM possessed by any person in the above first group.

[0169] The operation of inputting the first reservation request information into the first terminal device or the operation of transmitting the first reservation request information from the first terminal device to the reservation management device (100) (hereinafter, these are collectively referred to as the first reservation operation) is basically performed by provider B on the first terminal device. However, the first reservation operation on the first terminal device may be performed by any person in the first group, or by any person not belonging to the first group. A third party who has been requested by provider B may also perform the first reservation operation on the first terminal device.

[0170] The second target person corresponds to priority requester C. Priority requester C may be the representative of a second group (second group of people) consisting of multiple individuals. In this case, the desired usage information 642 included in the priority request information 640 as the second reservation request information corresponds to the desired usage information 642 of each person belonging to the second group (see Figures 10 and 11). The second target person can also be considered to include each person in the second group, including priority requester C. If the second target person includes multiple people in the second group, one person in the second group (the individual indicated in priority request information 640) may bear the entire priority usage fee, or each person in the second group may share the priority usage fee.

[0171] The second terminal device corresponds to terminal device TM_C. Terminal device TM_C, as the second terminal device, is basically terminal device TM possessed and operated by priority user requester C. However, it is also acceptable for terminal device TM possessed by any person in the second group mentioned above to be the second terminal device (terminal device TM_C).

[0172] The operation of inputting the second reservation request information into the second terminal device or the operation of transmitting the second reservation request information from the second terminal device to the reservation management device (100) (hereinafter collectively referred to as the second reservation operation) is basically performed by the priority user requester C to the second terminal device. However, the second reservation operation to the second terminal device may be performed by any person in the second group, or by any person not belonging to the second group. A third party who has received a request from the priority user requester C may also perform the second reservation operation to the second terminal device.

[0173] A program that causes a computer to execute any of the methods described in the embodiments of the present invention, and a recording medium that records such a program and is computer-readable and non-volatile, are included within the scope of the embodiments of the present invention. Any processing in the embodiments of the present invention may be implemented by hardware such as a semiconductor integrated circuit, software corresponding to the above-mentioned program, or a combination of hardware and software. There may be multiple instances of both the software and the hardware.

[0174] The embodiments of the present invention can be modified in various ways as appropriate within the scope of the technical idea set forth in the claims. The embodiments described above are merely examples of embodiments of the present invention, and the meaning of the terms of the present invention or each constituent element is not limited to those described above. The specific numerical values ​​shown in the above description are merely examples and can, of course, be changed to various numerical values. [Explanation of symbols]

[0175] SYS System 100 Reservation Management Device 200 Service provider equipment NET communication network TM, TM_A, TM_B, TM_C, TM_D, TM_E terminal devices 10. Data Input Support Section 11 Data receiving unit 12 Data Identification Unit 13. Data writing section 20 Priority Access Support Department 21 Data reading section 22 Assignment Change Section 23 Provision results reporting department 30 Priority Usage Management Department 31 Data reading section 32 Data Analysis Department 33. Assignment Results Reporting Department 34-point update section 40 Data storage unit 41. Registered Users Database 42 Possible provider DB 43 Priority use DB 44 Assignment Result DB 45 Point Information Database 600 User Registration Information 610 User saved information 620 Person information that can be provided 630 Type 1 preservation information 640 Priority Request Information 650 Type 2 preservation information 660 Allocation Result Information 670 Provided result information 680 Request Result Information

Claims

1. In a reservation management system for transportation services, The system comprises: an information input unit that receives first reservation request information including the usage preference information of a first target person from a first terminal device, and second reservation request information including the usage preference information of a second target person and priority usage fee information from a second terminal device; and a processing unit that performs first reservation processing for the first target person and second reservation processing for the second target person based on the first reservation information and the second reservation information. The aforementioned processing unit, In the second reservation process, if there is no transportation that perfectly matches the second person's desired usage information, a specific process is performed to search for a transportation that satisfies the second person's desired usage information as much as possible and assign it to the second person. If the specific processing is performed in the second reservation processing, an assignment change processing is performed which includes matching processing based on the results of the first reservation processing for multiple first target persons, the usage preference information of the second target persons, and the results of the second reservation processing. In the matching process, from among the multiple first target persons, the first target person who has the right to use a transportation that better satisfies the second target person's usage preferences compared to the transportation assigned to the second target person in the identification process is selected as the actual provider. The allocation change process includes a right granting process that provides the second target person with the right to use the transportation allocated to the actual provider in the first reservation process, and a settlement process that grants the actual provider consideration based on the priority usage fee. , reservation management device.

2. In the matching process, the processing unit, Based on the results of the first reservation process for each of the multiple first subjects, the usage preference information for each of the multiple second subjects, and the results of the second reservation process for each second subject, one of the multiple first subjects is associated with one of the multiple second subjects. When two or more second targets are associated with a specific first target in the matching process, the processing unit executes a recipient determination process to determine one of the two or more second targets as the recipient, sets the specific first target as the actual provider for the recipient, and provides the recipient with the right to use the transportation allocated to the actual provider in the first reservation process. In the recipient determination process, the processing unit determines the recipient based on the priority usage fees for each of the two or more second target persons. , a reservation management device according to claim 1.

3. In the matching process, the processing unit identifies the highest priority usage fee among the two or more second target persons, and determines the second target person corresponding to the highest priority usage fee among the two or more second target persons as the recipient. , a reservation management device according to claim 2.

4. The aforementioned reservation request information for each of the second target persons includes information indicating the degree of preference for priority use of the aforementioned transportation service, In the recipient determination process, the processing unit determines the recipient based on the priority usage fee and priority preference level for each of the two or more second target persons. , a reservation management device according to claim 2.

5. In the recipient determination process, the processing unit identifies the highest priority usage fee among the two or more second target persons. If the total number of second target persons corresponding to the highest priority usage fee is 1, the processing unit determines the second target person corresponding to the highest priority usage fee as the recipient. If the total number of second target persons corresponding to the highest priority usage fee is 2 or more, the processing unit determines the recipient based on the priority preference level of each second target person corresponding to the highest priority usage fee. , a reservation management device according to claim 4.

6. In the recipient determination process, if the second recipient corresponding to the highest priority usage fee consists of the first priority requester and the second priority requester, and the priority preference of the first priority requester is higher than that of the second priority requester, the processing unit determines the first priority requester to be the recipient, and if the priority preference of the second priority requester is higher than that of the first priority requester, the processing unit determines the second priority requester to be the recipient. , a reservation management device according to claim 5.

7. The aforementioned first subject includes persons who consent to transferring their assigned right to use public transportation to another person. A reservation management device according to any one of claims 1 to 6.

8. In the rights provision process, the processing unit exchanges the right to use the transportation allocated to the actual provider in the first reservation process with the right to use the transportation allocated to the second target person in the second reservation process, thereby providing the right to use the transportation allocated to the actual provider in the first reservation process to the second target person. A reservation management device according to any one of claims 1 to 6.

9. In a reservation management method performed by a reservation management device for transportation services, The system includes an information acquisition step of acquiring first reservation request information, including information on the first target person's desired usage, from a first terminal device, and second reservation request information, including information on the second target person's desired usage and information on priority usage fees, from a second terminal device, and a processing step of executing a first reservation process for the first target person and a second reservation process for the second target person based on the first reservation information and the second reservation information. In the second reservation process, if there is no transportation that perfectly matches the second person's desired usage information, a specific process is performed to search for a transportation that satisfies the second person's desired usage information as much as possible and assign it to the second person. If the specific processing is performed in the second reservation processing, the processing step includes performing an assignment change processing that includes matching processing based on the results of the first reservation processing for multiple first target persons, the usage preference information of the second target persons, and the results of the second reservation processing. In the matching process, from among the multiple first target persons, the first target person who has the right to use a transportation that better satisfies the second target person's usage preferences compared to the transportation assigned to the second target person in the identification process is selected as the actual provider. The allocation change process includes a right granting process that provides the second target person with the right to use the transportation allocated to the actual provider in the first reservation process, and a settlement process that grants the actual provider consideration based on the priority usage fee. , reservation management method.

Images