JP2009070111A - Driving support server and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve convenience for a drive service agent such as taxi service agent or proxy driving service agent and a user thereof. <P>SOLUTION: The server comprises a receiving means for receiving a card ID read by a card reader set in a shop, a drive order including a dispatch desired time and a designation, and a reader ID assigned to the card reader; a reading means for reading an address corresponding to the reader ID from a first storage medium storing the reader ID in association with the address of the shop; a transmitting means for transmitting the address read by the reading means and the dispatch desired time to an agent terminal; and a report means for reporting drive availability information returned from the agent terminal to the card reader. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a driving support server and system, and more particularly, to a driver support server and system such as a taxi driver or a substitute driver.

  Patent Document 1 discloses a technique for improving convenience of taxi users and taxi drivers. In the system shown in Patent Document 1, the vehicle dispatch center receives the customer information input from the customer terminal after confirming the authentication by the member ID transmitted from the customer terminal at the time of the customer information registration / change request, and receives the customer information. The customer ID is stored in association with the member ID. On the other hand, corresponding customer information is read from the customer information DB based on the member ID transmitted at the time of customer information request from the wireless mobile station, and transmitted to the requesting wireless mobile station. The wireless mobile station receives and presents the transmitted customer information via a wireless line.

JP 2007-025897 A

  By the way, recently, social momentum toward eradication of drunk driving is increasing. For this reason, alcohol cannot be provided to visitors by car, mainly in local restaurants, causing a decrease in sales, leading to a serious situation for restaurant managers.

  On the other hand, driving agency services are used more frequently in rural areas than in urban areas. However, service providers for driving agency are often small and the service level is unstable. Specifically, even if a user requests a vehicle dispatch, it may take a long time before the vehicle is actually dispatched to a restaurant. In the first place, the user feels bothered by telling the driving agent the destination and paying with cash including coins, and these improvements are also required.

  On the other hand, it is a problem for taxi drivers or driving agents to avoid empty conditions as much as possible. Regarding this issue, there is also an environmental demand to reduce fuel consumption. Therefore, it is desired to construct an efficient vehicle allocation system.

  Then, this invention makes it a subject to provide the structure which improves the convenience of both a taxi driver or a driving agent, and its user.

In order to solve the above problems, the driving business support server and system of the present invention include:
Receiving means for receiving a card ID read from a payment card by a card reader installed in a store, a driving order including a desired dispatch time and a destination, and a reader ID assigned to the card reader;
Reading means for reading out the location corresponding to the reader ID from the first storage medium in which the reader ID and the location of the store are stored correspondingly;
Transmitting means for transmitting the location read by the reading means and the desired dispatch time to a dealer terminal;
Notification means for notifying the card reader of driving availability information returned from the dealer terminal is provided.
Note that the card ID, the driving order, and the reader ID received by the receiving unit may be transmitted from a single terminal or from different terminals.

  As a result, a user such as a taxi does not need to inform the driver of the destination, and smooth payment can be made with a payment card. In addition, by obtaining the location and the desired dispatch time, taxi drivers and the like can efficiently make a dispatch plan so as not to waste the traffic. Furthermore, as a restaurant, it is possible to improve sales by increasing the number of visitors who use driving agents.

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a functional block diagram of the driving support system according to the first embodiment of the present invention. FIG. 1 shows a reader 100, a server 200, a collection terminal 300, a trader terminal 400, a network 500, and an IC card 600, which will be described below.

  The reader 100 is usually installed near a cash register in a store. Alternatively, the reader 100 is connected to a personal computer (hereinafter referred to as “PC”) of a vendor installed in a store via a USB (Universal Serial Bus) terminal or the like. Each reader 100 is assigned a unique reader ID.

  The reader 100 reads the card ID, member information, etc. stored in the IC card 600. Further, as will be described later, for example, the reader 100 has a deposit / withdrawal mode for depositing / withdrawing to / from the IC card 600, a payment mode for paying from the deposit amount of the IC card 600, and a dispatch mode for using the driving support system Are prepared so that a member of the IC card 600 or a store clerk can select one of the modes.

  When the reader 100 is a dedicated machine, a display 110 and several input keys 120 may be provided. On the other hand, when the reader 100 is connected to the PC, for example, an application program that causes the PC to execute the processing described below instead of the reader 100 may be installed in the PC.

  In this embodiment, as an example, an RFID (Radio Frequency Identification) tag is embedded in the IC card 600 and an RFID reader is employed as the reader 100. In addition, the reader 100 adds a reader ID uniquely assigned to the reader to the read information and the like, and transmits the information to the server 200.

  In the server 200, member information and the like, a card ID, and the number of points given to the member are associated and registered. Although a specific configuration of the server 200 will be described later, for example, a multi-task method or an event-driven method is adopted for processing in the server 200.

  The collection terminal 300 is mounted on a taxi or an accompanying car for substitution driving (so-called substitution car). The collection terminal 300 performs data communication with the server 200 via the network 500, and takes charge of deposit / withdrawal processing and payment processing.

  The vendor terminal 400 performs data communication with the server 200 via the network 500. The dealer terminal 400 is typically a PC and is used by a taxi driver or the like.

  The network 500 is a general term for networks including a wide area communication network such as the Internet or a high-speed LAN (Local Area Network) network that connects a PC and a wide area communication network.

  As described above, for example, an RFID (Radio Frequency Identification) tag is embedded in the IC card 600. Further, a unique card ID is assigned to the IC card 600. The IC card 600 has a credit function, a deposit function, and the like.

  The server 200 includes a communication unit 210, a determination unit 220, a location reading unit 230, and a registration unit 240 described below.

  The communication unit 210 communicates with the reader 100, the collection terminal 300, and the trader terminal 400 through the network 500. In the present embodiment, the communication unit 210 typically receives a card ID and vehicle allocation reservation information transmitted from the reader 100, transmits vehicle allocation reservation information to the dealer terminal 400, and a card transmitted from the collection terminal 300. Receive ID and payment amount. Other communication modes will be described later.

  The discriminating means 220 discriminates the contents of the vehicle allocation reservation information transmitted from the reader 100. Specifically, the dispatching reservation information includes, for example, the type of taxi and substitute vehicle, the destination, the desired dispatch time, the designation of a specific dealer, the route to the destination (relay point), and the like. ing. Further, the determination unit 220 also determines whether or not it is possible to deal with a vehicle allocation reservation returned from the dealer terminal 400.

  As a result of the discrimination by the discriminating unit 220, the location reading unit 230 determines that the destination is the home of the cardholder, a home whose location is registered in advance in a database attached to the server 200 (hereinafter referred to as “DB”), or In the case of a member store or the like, the corresponding location information is read from the DB. The DB may be provided in the server 200, or may be connected to the server 200 via a dedicated line or the network 500.

  Here, in the DB, a card ID registered in the IC card 600, member information (name, home location, telephone number, e-mail address, etc.), and a dealer assigned to a member driver and a member driver agency. ID, supplier information (name, location, telephone number, e-mail address, etc.), sales area of member driver, etc., reader ID assigned to reader 100, and store information (name) where reader 100 is installed , Location, telephone number, e-mail address, etc.). The DB may be built in the server 200, or may be externally attached to the server 200 via a dedicated line or the network 500.

  The registration means 240 registers various information transmitted from the reader 100, the collection terminal 300, and the trader terminal 400 in the DB. As an example, the registration unit 240 registers a card ID and member information in the DB before member registration. The registration means 240 registers the deposit / withdrawal information, payment information, and the number of points given to the member in the DB after the member registration.

  FIG. 2 is a time chart showing an example of the operation of the driving support system shown in FIG. First, when using the driving support system, a member or a store clerk sets the reader 100 to the vehicle allocation mode (step S1).

  The reader 100 selectively transmits information indicating that the vehicle allocation mode is set to the server 200 via the network 500. At this time, the reader 100 transmits the information after adding a unique reader ID assigned to the reader.

  In the server 200, the communication unit 210 receives the information transmitted from the reader 100. Then, the location reading unit 230 refers to the DB based on the reader ID added to the information, and stores the trader information in which the area including the store where the reader 100 is installed is registered as a business area (in the same municipality, etc.) Furthermore, the store information in the business area is read out. The trader information and the like are transmitted to the reader 100 through the network 500 by the communication unit 210.

  On the other hand, when a member or a store clerk puts the IC card 600 on the reader 100, the reader 100 is stored in the IC card 600 on condition that the IC card 600 is located within a predetermined distance from the reader 100. The card ID is read (step S2).

  Next, when the member or the store clerk presses the input key 120 provided on the reader 100, the type of taxi and the substitute vehicle, the destination, the desired dispatch time, the designation of a specific trader, the destination By instructing or selecting a route or the like, the dispatch reservation information is input to the reader 100 (step S3).

  Here, if the reader 100 obtains the vendor information from the server 200 prior to step S2, for example, when “type of taxi and substitute vehicle” is selected, the reader 100 reads the vendor information. The information is displayed on a display attached to 100, and a store clerk or the like is urged to specify a trader.

  When the member does not desire a specific trader, for example, by selecting a destination key 120 provided in the reader 100, the member moves to a destination selection screen. Items with high selection frequency such as “restaurant” and “home” are registered in advance as destinations.

  In addition, for example, store information is displayed on the display 110 attached to the reader 100 in order to select “destination” or “relay location”, and a store clerk or the like prompts the user to specify a destination or relay location store. If the relay point is not registered, the location of the relay point is entered. With regard to the “desired dispatch time”, for example, it is one method that reservations can be made within 3 hours from the current time and can be selected in units of 15 minutes.

  When a store clerk or the like finishes inputting the vehicle allocation reservation information, and presses the transmission key 120 provided in the reader 100, the reader 100 makes the reader 100 the self-reader with respect to the read card ID and the input vehicle allocation reservation information. The assigned unique reader ID is added and transmitted to the server 200 via the network 500.

  In the server 200, the communication unit 210 receives the card ID and the like transmitted from the reader 100, and the registration unit 240 registers the card ID and the like in the DB (step S4).

  Next, in the server 200, the determination unit 220 determines the contents of the vehicle allocation reservation information transmitted from the reader 100. Specifically, the determination unit 220 first determines whether or not a specific trader is designated. Secondly, the determination unit 220 determines whether or not corresponding information is registered with reference to the DB based on the destination related to the reservation content.

  As a result of determination by the determination unit 220, if a specific contractor is designated, an event to that effect is generated. When the communication unit 210 detects this event, for example, the communication unit 210 reads out an e-mail address corresponding to the supplier, and transmits an e-mail asking whether or not a vehicle allocation reservation is possible to the e-mail address.

  In addition, as a result of the determination by the determination unit 220, when the corresponding information is registered with reference to the DB based on the destination related to the reservation content, the destination is typically “home” or “any one” If it is “the store where the reader 100 is installed”, an event to that effect is generated. When the location reading means 230 detects this event, the location reading means 230 reads the location corresponding to the card ID included in the reservation content from the DB and includes it in the email.

  On the other hand, if the specific contractor is not designated as a result of the determination by the determination means 220, an event to that effect is generated. When the communication means 210 detects this event, it reads out the mail addresses corresponding to all the traders, and sends an email asking whether or not a vehicle allocation reservation is possible to each of the mail addresses.

  As a result, the mail is typically received by mail software installed in the vendor terminal 400. Upon receipt of this mail, the trader terminal 400 performs registration processing for this mail (step S5).

  Then, if necessary, the operator of the trader terminal 400 inquires of the driver or the like whether or not the vehicle allocation reservation is possible based on the reservation contents using communication means such as a radio or a telephone. Thereafter, the operator or the like operates the trader terminal 400 to return whether or not the vehicle allocation reservation is possible to the server 200.

  In the server 200, the communication unit 210 receives the reply, and the determination unit 220 determines whether or not it is possible to deal with the vehicle allocation reservation returned from the dealer terminal 400 (step S6). Although not shown for convenience of explanation, the contents of the determination result are actually recorded in the DB by the registration unit 240 after steps S6 and S7 are executed.

  As a result of the determination, if the vehicle allocation reservation is available, the communication unit 210 notifies the corresponding reader 100 to that effect. At this time, when a reply indicating that it is possible to respond to the reservation for dispatch is also sent from the other merchant terminal 400, it may be notified to the corresponding reader 100, or the earliest Only the above reply may be notified to the corresponding reader 100, and the notification may be omitted for other replies.

  On the other hand, if it is not possible to respond to the reservation for dispatching vehicles, the communication means 210 reads out the email addresses corresponding to all other vendors excluding the specific vendor when the specific vendor is designated, An e-mail is sent to the address asking whether the reservation for dispatch is possible.

  Then, in the same manner as after execution of step S5, the server 200 shifts to a waiting state for determining whether or not it is possible to cope with the vehicle allocation reservation returned from the dealer terminal 400 (step S6).

  Thereafter, when a reply is made from any of the dealer terminals 400, as in step S6, the determination means 220 determines whether or not the vehicle allocation reservation returned from the dealer terminal 400 can be handled (step S7).

  As a result of the determination, if a reply indicating that the vehicle allocation reservation is available is made, the communication unit 210 is not capable of responding to the vehicle allocation reservation by the specific vendor to the corresponding reader 100, but by another vendor. Notify that it is possible to respond to a reservation for dispatch.

  On the other hand, when a reply indicating that the vehicle dispatch reservation is not available is made, the state transits to a reply waiting state from another trader excluding the trader. That is, the reply waiting state and the determination process in step S7 are repeated a predetermined number of times.

  Thereafter, when a reply indicating that the vehicle allocation reservation is available is sent from any trader including the specific trader, and after notification to that effect is sent to the reader 100, a notification indicating the reservation confirmation is sent back from the server 200 to the server 200. The server 200 requests a formal request for reservation from the corresponding trader terminal 400.

  On the other hand, when a reply to the vehicle allocation reservation is not received from any of the dealers and the reader 100 is notified of this, the processing shown in FIG.

  If the e-mail address set for the mobile terminal owned by the member is registered in the DB as the member information related to the IC card 600, or instead of the notification after the execution of steps S6 and S7, Along with the notification, the notification may be sent to the mail address.

  FIG. 3 is a flowchart showing the operation of the reader 100 or the collection terminal 400 shown in FIG.

  First, the reader 100 or the collection terminal 400 transitions to a mode selection input waiting state when a member or the like has not performed an operation for a certain period of time. In this state, when a member or the like performs an operation on the reader 100 or the like, a mode selection input process corresponding to step S1 in FIG. 2 is executed (step S10).

  When the mode selection input is made, the reader 100 and the like determine the mode selection content by the determination unit 220 and generate an event corresponding to the determination result.

If the event is the “deposit / withdrawal mode” in which the deposit / withdrawal to / from the IC card 600 is performed, the process proceeds to step S11.
When the event is “payment mode” in which payment is made from the deposit amount of the IC card 600, the process proceeds to step S21.
If the event is “allocation mode” that is performed when the driving support system is used, the process proceeds to step S31.

  When the reader 100 or the like is in the “deposit / withdrawal mode”, the member or the like puts the IC card 600 on the reader 100, and the IC card 600 is positioned within a predetermined distance from the reader 100. The card ID stored in the IC card 600 is read and stored in a memory (not shown) (step S11).

  Next, it is assumed that, with the IC card 600 placed on the reader 100, a member or the like has instructed the deposit / withdrawal amount via the input key 220 or the like. In this case, the reader 100 or the like executes a deposit / withdrawal amount input process in which the deposit / withdrawal amount inputs an instruction and stores it in a memory not shown (step S12).

  Subsequently, the reader 100 or the like reflects the input deposit / withdrawal amount on the IC card 600, reads the deposit / withdrawal amount stored in the memory, creates a deposit / withdrawal record, and transmits it to a settlement center (not shown). Then, a deposit / withdrawal amount update process is executed (step S13).

  In the settlement center, various information transmitted from the reader 100 or the like is recorded, and point management given to the member is performed.

  In addition to the above processing of the reader 100 and the like, when an input for depositing is made, typically, the store clerk collects the amount of cash from the member. On the other hand, when an input for making a withdrawal is made, the store clerk typically repays the amount of cash from the member.

  On the other hand, when the reader 100 or the like is in the “payment mode”, the member or the like puts the IC card 600 on the reader 100 so that the IC card 600 is located within a predetermined distance from the reader 100. The card ID stored in the IC card 600 is read and stored in a memory (not shown) (step S21).

  Next, it is assumed that the payment amount is output from the POS terminal (register) or the like with the IC card 600 placed on the reader 100, or the payment amount is instructed from the member or the like through the input key 220 or the like. In this case, the reader 100 or the like executes a payment amount input process of inputting the output payment amount and storing it in a memory (not shown) (step S22).

  Subsequently, the reader 100 or the like clears the input payment amount from the deposit recorded in the IC card 600, reads out the payment amount stored in the memory, creates a payment record, and sends it to a settlement center (not shown). Payment amount update processing is executed (step S23).

  In addition, when performing the payment amount update process, you may perform the point provision process mentioned later collectively.

  In addition, at the time of payment at the store where the reader 100 is installed, two receipts may be issued from the reader 100 or the POS system. One of them is given to the user of the IC card 600, and the other one is given to a taxi driver. The receipt usually includes the date and time of issue, so it can be used effectively for accounting management of taxi drivers, etc., and daily report creation.

  On the other hand, in the “allocation mode”, the reader 100 and the like read the card ID stored in the IC card 600 corresponding to step S2 in FIG. 2 and store it in a memory (not shown) (step S31).

  In addition, after step S31, as described above, the reader 100 may acquire the merchant information and the like from the server 200 by transmitting the card ID to the server 200.

  Next, it is assumed that the type of taxi or substitute vehicle is instructed by a member or the like. In this case, the reader 100 or the like executes a vehicle allocation type input process corresponding to a part of step S3 shown in FIG. 2, in which the instructed type is input and stored in a memory (not shown) (step S32).

  Next, it is assumed that the destination is instructed by a member or the like. In this case, the reader 100 or the like executes a destination input process corresponding to a part of step S3 shown in FIG. 2, in which the instructed destination is input and stored in a memory (not shown) (step S33).

  Further, it is assumed that a desired dispatch time is instructed by a member or the like. In this case, the reader 100 or the like performs a time input process corresponding to a part of step S3 shown in FIG. 2, in which the instructed desired dispatch time is input and stored in a memory (not shown) (step S34).

  After that, it is assumed that a transmission instruction is given from a member or the like. In this case, the reader 100 or the like executes a reservation information transmission process in which various information recorded in the memory is read out, vehicle allocation reservation information is created and transmitted to the server 200 (step S35).

  If the reservation is confirmed, a message indicating the completion of the reservation is transmitted to a settlement center (not shown), points are subsequently given to the member, or points returned from the settlement center are stored in the IC card 600. You may perform the point provision process of reflecting. Incidentally, the point grant processing is roughly divided into two types. One is to give the member points that are redeemed according to the purchase price of the product, and the other is to give the members a uniform point by confirming the dispatch reservation.

  In addition, the e-mail address assigned to the member's mobile phone is registered in advance in a DB or the like, and instead of or with the above points, for example, an electronic coupon is addressed to the member's mobile phone. You may distribute by e-mail. Further, at the time of accounting, when printing two receipts at the time of payment processing from the reader 100 or the POS system, a coupon ticket may be printed.

It is a functional block diagram of the driving assistance system of Embodiment 1 of the present invention. It is a time chart which shows an example of operation | movement of the driving assistance system shown in FIG. It is a flowchart which shows operation | movement of the reader 100 or the collection terminal 400 shown in FIG.

Explanation of symbols

100 Reader 200 Server 300 Collection terminal 400 Contractor terminal 500 Network 600 IC card

Claims (4)

Receiving means for receiving a card ID read from a payment card by a card reader installed in a store, a driving order including a desired dispatch time and a destination, and a reader ID assigned to the card reader;
Reading means for reading out the location corresponding to the reader ID from the first storage medium in which the reader ID and the location of the store are stored correspondingly;
Transmitting means for transmitting the location read by the reading means and the desired dispatch time to a dealer terminal;
A driving business support server comprising notification means for notifying the card reader of driving availability information returned from the dealer terminal.   When the destination is at home, the reading means is based on the card ID from the second storage medium in which the card ID and the home location of the cardholder associated with the card ID are stored correspondingly. The driving business support server according to claim 1, wherein the corresponding location is read out. If the order includes requesting the transmission to a specific merchant terminal, perform the transmission to the specific merchant terminal,
The driving support server according to claim 1 or 2, wherein the transmission is performed to another merchant terminal when the driving propriety information returned from the specific merchant terminal is impossible to drive. The driving support server according to any one of claims 1 to 3,
A driving support system comprising: a terminal mounted on the driver's vehicle and collecting a driving fee from a card to which the card ID is assigned.

Images