JP5433675B2 - Bus point exchange system - Google Patents

Description

  The present invention relates to a technique for converting points into monetary values on a vehicle.

A technique is known in which, when a product is purchased, points are assigned and the points are allocated to a fare or the like. (Patent Document 1)
In addition, a service is known in which points are not allocated directly to a fare or the like, but points are returned as SF (Stored Fare). SF is a monetary value recorded on an IC card ticket, which is used for payment of fare or exchange for tickets.

  When the card issuer company manages the points owned by the user, it is necessary to go to a point exchange owned and installed by the card issuer company in order to convert the points to SF.

JP 2002-157311 A

  If the reader / writer for reading and writing IC tickets on the bus is used as an SF point exchange, the bus is always moving and cannot be connected to an external point management device. Even if a ticket can be recognized, it cannot grasp its possession point and cannot be operated as a point exchange.

  In addition, if you want to send point exchange request data such as points you have to the bus in advance, in a large point system with a large number of members, the point exchange data for that member will be large, so point exchange data When everything is sent to a large number of readers / writers, the network line is loaded, so processing is performed in a limited transmission time zone on a terminal that cannot be connected to the point exchange system for a long time, such as a bus. Is difficult and efficient point exchange cannot be realized.

  In order to solve the above-described problems, the present invention provides a bus having a bus vehicle point exchange system, a bus vehicle system provided at each of a plurality of bus vehicle locations, and a bus system provided at each of the plurality of buses. The point exchange system is a point exchange system that accepts point card specifying information and exchange points from a user and stores the received exchange points and point card specifying information in a distribution database as distribution data in association with each other. The distribution data is transmitted to the bus station system, and the bus station system receives the distribution data received from the bus system on the bus vehicle when the bus system is connectable to the bus station system. Sends data to the bus system, and the bus system accepts it from the user when it is disconnected. The point system information and the point card identification information in the received distribution data are collated and given to the point card of the user who accepts the monetary value of the exchange points of the matching point card. When it is possible to connect to the system, information indicating that the point exchange has been completed is transmitted to the bus station system, and the bus station system transmits the received completion information to the bus onboard system. Features.

  The on-vehicle point exchange system further receives route information from the user, stores the exchange point, the point card specifying information, and the route information in association with each other in the exchange information database, and for each vehicle information specifying the vehicle. In addition, the vehicle location information for identifying the vehicle location and the route information are associated with each other, stored in the bus operation database in the order of operation, the information in the exchange information database and the information in the bus operation database are collated, and each point card is specified. The vehicle location information and vehicle information corresponding to the information are specified, the specified vehicle location information and the vehicle information are stored in the distribution database in association with each other, and the first one of the vehicle locations specified by the distribution data is operated. The exchange point, point card identification information and body information corresponding to the bus depot system are transmitted, and the bus depot system receives The bus system of the vehicle corresponding to both information, and transmits the switching point and the point card identification information thus received corresponding to the vehicle information.

  The on-vehicle point exchange system further accepts information indicating the priority corresponding to the point card specific information for each user, creates a plurality of distribution databases according to the priority, and creates a plurality of distribution databases. The bus vehicle system transmits the received exchange point and point card specific information corresponding to the vehicle information to the bus system of the vehicle corresponding to the vehicle information based on the vehicle information in order from the high-priority distribution database. Is transmitted.

  The on-vehicle point exchange system transmits the exchange points, point card specifying information, and vehicle body information to the bus vehicle systems at a plurality of specified vehicle locations.

  An efficient monetary value can be given to the point card on the bus car.

It is an example of a lineblock diagram of a bus car point exchange device. The data block diagram of bus stop DB is shown. The data structure figure of bus operation DB is shown. The data structure figure of member information DB is shown. The data block diagram of exchange information DB is shown. A data structure diagram of the distribution DB is shown. A data structure diagram of a vehicle distribution DB (Gold) is shown. The data structure diagram of the vehicle distribution DB (Silver) is shown. A data structure diagram of the vehicle distribution DB (Bronze) is shown. A data structure diagram of the on-vehicle replacement DB is shown. The data block diagram of reception status DB is shown. The data structure figure of boarding customer DB is shown. The data block diagram of vehicle replacement DB is shown. The flowchart of the point exchange on a vehicle is shown.

  Hereinafter, examples will be described with reference to the drawings.

  In the present embodiment, a system will be described in which points generated with the use of an IC card such as a credit card are converted into electronic money and returned to an IC ticket.

  FIG. 1 is an example of a configuration diagram of the bus point exchange system of this embodiment. A WEB connection terminal is connected to a bus car point exchange system 1, a point management system 4, a bus management system, a bus vehicle system 2, and a bus system 3 via a network. The bus management system includes a bus stop DB 10 and a bus operation DB 11 as DBs. The bus operation DB 11 and the bus stop DB 10 are not limited to the bus management system, but may be on the bus vehicle point exchange system 1.

  The point management system 4 has a member information DB 12 as a DB. This is not limited to the point management system, but may be on the bus vehicle point exchange system 1. The on-board point exchange system 1 includes an exchange information DB 13 and a distribution DB 14 as DBs.

  The bus vehicle system 2 includes a vehicle distribution DB (Gold) 15, (Silver) 16, (Bronze) 17, and a vehicle replacement DB 21 as DBs. The bus system 3 includes an on-board exchange DB 18, a reception state DB 19, and a passenger customer DB 20 as DBs. The IC card has card information and a replacement flag as data.

  The WEB connection terminal is an internet connection terminal that is widely spread. In addition, DBs are distributed due to performance concerns when communicating directly between the bus and the point exchange system on the bus vehicle due to the narrow line between the point exchange system on the bus vehicle and the bus vehicle point. The vehicle distribution DBs 15 to 17 and the vehicle replacement DB 21 which are the side DBs may be on the bus vehicle point exchange system side.

  In FIG. 2, the data block diagram of bus stop DB10 is shown. This DB stores a bus stop name (101) and route numbers (102 to 106). There are a plurality of route numbers because the relationship between the bus stop and the route using the bus stop is a 1: N relationship. The bus bower DB10 is used when the customer designates a route number from the WEB. Specifically, it is used in the processing of (S004) described later.

FIG. 3 shows a data configuration diagram of the bus operation DB 11. This DB stores the bus vehicle number (111) and the route (102 to 106). The bus operation DB 11 uses the bus vehicle No. (111) as a primary key, and the departure vehicle location, route number, and arrival vehicle location can be known in sequence, as in operation information (112) ⇒operation information (113). Yes.
In FIG. 4, the data block diagram of member information DB12 is shown. This DB stores the card number (121), password (122), possession point (123), Mail (124), member classification (125), and deletion date (126).

  FIG. 5 shows a data configuration diagram of the exchange information DB 13. This DB includes the exchange serial number (131), card number (132), number of exchange points (133), membership classification (134), exchange start date (135), exchange end date (136), route number ( 137), route number (138), and exchange completion flag (139) are stored.

  FIG. 6 shows a data configuration diagram of the distribution DB 14. This DB stores vehicle number (145 to 147), vehicle number (148, 149), exchange serial number (141), card number (142), number of exchange points (143), and member classification (144). To do.

  In FIGS. 7-9, the data block diagram of DB15-17 for vehicle place distribution is shown. This DB stores vehicle numbers (151, 161, 171), exchange serial numbers (152, 162, 172), card numbers (153, 163, 173), number of exchange points (154, 164, 174), member categories (155, 165, 175), and exchanged flags (156, 166, 176).

  FIG. 10 shows a data configuration diagram of the on-vehicle replacement DB 18. This DB stores the exchange serial number (181), card number (182), exchange point (183), and exchanged flag (184).

  FIG. 11 shows a data configuration diagram of the reception state DB 19. This DB stores a vehicle number (191), a completed member category (Gold) (192), a completed member category (Silver) (193), and a completed member category (Bronze) (194).

  In FIG. 12, the data block diagram of boarding customer DB20 is shown. This DB stores a vehicle number (201) and card numbers (202 to 205).

  In FIG. 13, the data block diagram of vehicle replacement DB21 is shown. This DB stores a replacement vehicle number (211) and a replacement vehicle number (212).

FIG. 14 shows a flow of processing for determining to which vehicle point exchange information is to be distributed and creating data for distribution. The point distribution process of this embodiment is performed every day. Hereinafter, description will be made along the flowchart of FIG. This flowchart is a flowchart about a series of system processes along the data flow with the on-board point exchange system 1, the bus vehicle system 2, and the bus system 3, respectively.
<As a pre-processing step>
The point management system 4 divides the membership type into Gold, Silver, and Bronze from IC card usage frequency and usage amount in advance for each member. Further, the member registers a card number, a password, and an e-mail address in the point management system 4 in advance. The card number is a number written on the back of the IC card and a unique number in each IC card. The point management system registers each item entered in the card number (121), password (122), and MAIL (124) of the member information DB 12. Specifically, the member A who registered “1001” in the card No. (121), “bus” in the password (122), “123 @ abc” in the Mail (124), and “1002” in the card No. (121). Assume that there is a member B who has registered “pass” in the password (122) and “456 @ abc” in the Mail (124) (step S001).
<Web connection>
First, the member accesses the point exchange system 4 on the bus car from a Web browser such as a personal computer. Therefore, the member A inputs the card number “1001” and the password “bus”, and the member B inputs the card number “1002” and the password “pass”, and logs in to the member page (step S002). The on-board point exchange system 1 performs authentication by checking the card number “1001” and the password “bus” against the card number (121) “1001” and the password (122) “bus” in the member information DB 12. The same process is performed for member B (step S003).

  In the point exchange system 1 on the bus car, the reservation screen display processing unit (H01) judges that the member A who is the card No (121) “1001” of the member information DB 12 on the member page for the member A is the logged-in person, (123) “300” and the current member classification (125) “Gold” are displayed, and the point exchange procedure is enabled. The same process is performed for member B, and the holding point (123) “289” and the current member classification (125) “Silver” are displayed. In the exchange reservation accepting section (H02), the member first inputs the desired number of exchange points “78” to be exchanged, the date period (start) “20110331”, and the date period (end) “20110407”. The point exchange system on the bus compares the number of retained points (123) “300” in the 1 member information DB 12 with the desired number of exchange points “78” requested by the member. In this case, the retained points (123) “300” are requested to be exchanged. Since it exceeds the point “78”, it is determined that the exchange is possible. Similarly, for member B, the holding points (123) “289” exceed the exchange desired points “30”, so that it is determined that the exchange is possible. When it is determined that the point exchange system 1 on the bus vehicle can be exchanged, the member can designate the route number of the bus to be exchanged. Specifically, first, the members A and B both specify the boarding bus stop “Hakata 1-chome” and the getting-off bus stop “Nakasu 3-chome” on the Web screen for specifying the route number. Bus car point exchange system 1 extracts “305” and “306” as route numbers common to the records of bus stop name (101) “Hakata 1-chome” and “Nakasu 3-chome” in bus stop DB10. “305” and “306” are displayed as route numbers (102, 103) passing through the designated bus bower.

  The member selects “305” and “306” from the displayed route numbers (102, 103) “305” and “306” to complete the point exchange procedure. Of course, the route number selected here may be either plural or singular (step S004).

  The point exchange system on the bus car considers that the exchange procedure has been completed with the route number designations “305” and “306” from the members A and B, and the number of exchange points from the customer's possession points (123) “300” in the member information DB 12 The subtraction process of “78” is performed by the point subtraction unit (H03). As a result of the subtraction, the possession point (123) of the member information DB 12 is changed from “300” to “222”. As a result of the point exchange procedure, the number of exchange points is stored as “78” in the exchange point number (133) of the exchange information DB 13 in the process of step S006 described later. However, since the points are given on the bus car, the points are not given yet (step S005). Here, the route number is specified after accepting the point input, but the order is not limited to this order, and the input of the point may be accepted after accepting the input of the route number.

  The point exchange system 1 on the bus car receives the card No (132) “1001”, the number of exchange points (133) “78”, the exchange start date (135) “20110331”, the exchange end date ( 136) The exchange serial number (131) “00230046” is assigned to “20110407”, route No. (137,138) “305”, “306” and stored. The exchange start date (135) and the exchange end date (136) are used when a point exchange target record is extracted in the nighttime batch processing of step S008 described later (step S006).

The reason for subtracting at this timing is that there is a possibility that the point exchange system 1 on the bus vehicle will accept a point exchange reservation more than the possessed points when the member exchanges points with another service. Specifically, in the case of the method of subtracting at a later date, as described above, the customer of the point (123) “300” in the member information DB 12 took the point exchange procedure of “78” points on the bus car point exchange system 1 Immediately after that, if you exchange points for “300” points in another service and become “0” in the membership information DB12, the point exchange system 1 on the exchange bus will later redeem “78” for the points you received the reservation. Even if subtraction is performed from the possession point (123) “0” in the member information DB 12, an error occurs because the subtraction cannot be performed.
<Batch at night>
The on-bus point exchange system 1 starts a night batch every night at night (step S007). In the night batch, the server system date is compared with the exchange start date (135) “20110331” and the exchange end date (136) “20110407” in the exchange information DB 13, and the exchange start date (135) <= server system date < = The record of the exchange serial number (131) “00230046” having the exchange end date (136) is extracted (step S008).

  Next, the route number (137) “305” and the route number (138) “306” of the extracted record of the exchange information DB 13 are compared with the route number (1122, 1132, 11N2) of the bus operation DB 11, and the bus operation DB 11 is compared. It can be seen that there are two records having one of “305” and “306” in the route No. (1122, 1132, 11N2). The delivery destination determination unit (H04) identifies the bus vehicle No (111) “A100” and “B100” in the bus operation DB 11 by referring to the extracted vehicle No. of the two records. Up to this point, that is, from the route No specified by the customer to the vehicle No that is actually scheduled to run on the route No can be specified.

    Next, based on the vehicle No. (111) “A100” and “B100” specified from the bus operation DB 11, the vehicle location No. (1121, 1131, 11N1) where these two vehicles stop during the day is searched. The reason for identifying the vehicle location No where the bus stops on that day is that if the vehicle location No is unknown, the vehicle location where the vehicle to which point exchange information is to be distributed (especially the vehicle location that performs the night batch) is not known. This is because it becomes unclear whether or not point exchange information should be distributed, and point exchange information must be distributed to all vehicle locations. In this case, the network load connecting the bus car point exchange system and the vehicle station and the disk capacity of the bus vehicle station become enormous. By specifying the vehicle location, the point exchange information can be distributed to the vehicle location where the vehicle to which the point exchange information is to be distributed stops, leading to reduction of the network load and the disk capacity of the bus vehicle location.

  Next, how to specify the actual vehicle location is described below. First, the bus vehicle No (111) is searched using the bus vehicle No (111) “A100” specified above as a key, and the corresponding record is referred to. Then, the bus vehicle No. (111) “A100” leaves the bus vehicle station (1121) “L001” as the first vehicle station, departs as route No. (1122) “305”, and arrives at the bus vehicle station (1131) “L002”. Next, it is understood that the bus schedule (1131) “L002” starts as route No. (1132) “306” (hereinafter repeated N times)... In other words, the vehicle stations where the vehicle No (111) “A100” stops on the day are the bus vehicle stations No (1121,1131) “L001” and “L002”, and the first vehicle station (1121) is “L001”. I understand that. Similarly, it can be seen that the vehicle No. (111) “B100” also stops at the bus depot No. (1121, 1131) “L002” and “L003” and the starting depot is (1121) “L002”.

  Here, the first vehicle station refers to a vehicle station that waits until the bus departs the next morning after finishing the work of the previous day and receives nighttime batch processing. Therefore, it is necessary to specify the first vehicle place among the vehicle places. The bus vehicles (111) “A100” and “B100” that are scheduled to run as the route No. from the route numbers (1122,1132) “305” and “306” specified by the customer are identified, and then the bus vehicles From No (111), the vehicle station where the bus stops (1121,1131) Identify “L001”, “L002” and “L003”, and among these, “L001” and “L002” are buses “A100”, “B100” It can be seen that it is the first vehicle place that performs the night batch of "." Here, the bus operation DB 11 has a structure in which an array of operation information (111 to 11N) is arranged and connected in the schedule of the day with the vehicle NO (111) as a primary key. It is structured so that the vehicle location of the operation information (1) can be automatically identified as the first vehicle location without adding an item. This reduces the number of data items and speeds up the search for the data of the starting vehicle place by always placing the starting vehicle place at the head. The plurality of distribution data creation units (H05), from the record of the exchange serial number (131) “00230046” extracted from the exchange information DB 13, card No (132) “1001”, exchange point number (133) “78”, membership classification (134) “Gold”, vehicle location No. (145-147) “L001” “L002” “L003”, vehicle No. (148,149) “A100”, “B100” are added to the distribution DB 14 and stored (step S009) .

  Next, the record of the exchange serial number (141) “00230046” in the distribution DB 14 is distributed to the bus vehicle locations of the vehicle location Nos. (145 to 147) “L001”, “L002”, and “L003”. Here, the exchange serial number is a unique key added by the on-board point exchange system 1 when point exchange is accepted via the web and data is stored in the exchange information DB 13.

In addition, the data is distributed not only to the first vehicle station that performs nighttime batches, but also to the vehicle station where the bus stops, in response to a vehicle failure described later (Step S012) to (Step S013). This is because the vehicle place is used in advance as a data backup destination in order to reduce the amount of direct communication with the upper point exchange system (step S010).
<Bus vehicle station>
The bus vehicle system (145 to 147) “L001”, “L002”, and “L003” specified in the distribution DB stores the information of the distribution DB 14 distributed from the bus vehicle point exchange system 1. Sorted by member classification (144) and classified into vehicle location distribution DB (Gold) 15, vehicle location distribution DB (Silver) 16, and vehicle location distribution DB (Bronze) 17. In this embodiment, the classification is performed by the bus vehicle system 2, but the present invention is not limited to this, and the bus vehicle point exchange system 1 may perform the conversion in advance.

  The record of the exchange serial number (141) “00230046” is stored in the vehicle distribution DB (Gold) 15 for the member classification (144) “Gold”. With this organization, the night batch is completed.

  The purpose of classification is to give priority to information to be distributed and perform distribution in order of priority. As buses have many traffic delays due to vehicle breakdowns and traffic conditions, it is assumed that buses will need to start before receiving all point information from the bus vehicle place because buses give priority to timetables. . In this case, if it is decided not to leave the bus until all point exchange information is distributed, there is an increased possibility of the disruption of the timetable. Therefore, even if the point exchange information is not completely distributed, it is possible to depart in the present invention. . In the present invention, in order to prevent such non-delivery of point exchange information, basically, point exchange information is distributed to each bus in a concentrated manner at night, so point exchange information is not delivered in actual operation. There are few things. Although it is unlikely in the present invention that priority information is added and distributed, it is given priority to customers with high usage frequency in order to minimize damage by assuming that it could be sent. This is to provide a mechanism for distributing information. Also, as a mechanism, if you do not leave the bus until the point exchange information is completely distributed, bus schedule disruption may occur, but you can not send point exchange information and give priority to which one over the balance This is close to the bus company policy (step S011). At the bus depot, information distribution is performed based on the reception state DB 19 sent from the bus “A100”.

  First, select the classification (Gold, Silver, or Bronze) of the vehicle distribution DB (15-17) to be transmitted based on the completed member classification (192-194) included in the reception status DB 19, and then A record to be distributed in the vehicle place distribution DB (15 to 17) is determined from the vehicle No (151, 161, 171). Specifically, when the completion classification (192) (Gold) of the reception status DB 19 is “0”, it is considered that the vehicle distribution DB (Gold) 15, (Silver) 16, and (Bronze) 17 are not all delivered. Distribution starts in the order of the vehicle distribution DB (Gold) 15, the vehicle distribution DB (Silver) 16, and the vehicle distribution DB (Bronze) 17. When the transmission of the vehicle distribution DB (Gold) 15 is completed, the completed member classification (192) (Gold) of the reception status DB 19 of the bus “A100” is updated to “1”. Similarly, the completed member classification (192, 193, 194) is also updated when the information distribution is completed for the other completed member classification (193, 194). The bus is stopped at the vehicle station, and it is received at the bus vehicle at regular intervals. Vehicle No. (191) “A100” in DB19, Completed member category (192) (Gold), Completed member category (193) (Silver), Completed member category Send (194) (Bronze).

  The bus depot determines whether or not transmission is possible based on the vehicle No. (191) “A100” in the reception status DB 19 transmitted from the bus and the completed member categories (192 to 194) (Gold), (Silver), and (Bronze). to decide.

  That is, when the completed member classification transmitted from the bus is updated to “1”, the vehicle distribution DB (15 to 17) of the completed member classification is distributed and is not distributed. The vehicle station transmits the exchange serial number (152) “00230046”, the card number (153) “1001”, the number of exchange points (154) “78”, and the exchanged flag (156) “0” toward the bus. On the bus, the received information is stored in the on-vehicle replacement DB 18 (step S014).

  The bus checks whether the completed member classification (192) (Gold) in the reception status DB 19 is updated at regular intervals. The reason for checking only Gold is that in this patent, the condition necessary for the bus to be ready for departure is that the bus has received point exchange information for members of the member category "Gold", so see from the bus This is because it is necessary information only whether or not Gold is received and completed.

  Here, the intention that the on-board point exchange system 1 specifies and distributes the point exchange information not only to the route No. on which the customer wishes to exchange points in the on-vehicle point exchange system 1 but also to the vehicle No. The intention is to distribute not only the route No but also the vehicle No, so as to distribute point exchange information tailored to each one of the buses that is the delivery destination, instead of batching by route No. . Also, why ask members to specify route numbers instead of vehicle numbers, members usually know only the route number for buses and do not know which bus actually exchanges points. Therefore, there is no choice but to specify by route number. Therefore, in this invention, the process of specifying vehicle No. is performed by combining route No. information designated by the member and daily bus operation information. As a flow of processing for specifying the vehicle No., first, the bus No. (111) “A100” is scheduled to be the route No (1122) “305”, the route No (1132) “306” from the bus operation DB 11, and “B100”. It can be seen that route No (1122) “3” and route No (1132) “306” are scheduled. From this, the records of the exchange serial numbers (131) “00230046” and “00230047” that are desired to exchange points with the route numbers (137,138) “305” and “306” in the exchange information DB 13 are stored in the bus “A100” in the night batch. By distributing to “B100”, all information distribution can be completed in a night batch except in the case of an abnormality described later.

  On the other hand, if you try to distribute information only by route No., you will be distributed by route No. in the bus schedule where the route No. often changes every time you go to the time zone or bus station. Every time the route No. changes, it looks like it has changed to a completely different bus when viewed from the point exchange system 1 on the bus car, and the information delivery from the bus depot cannot be completed because the information delivery cannot be completed by the night batch alone. It is necessary to start over every time. In this case, since communication between the bus and the vehicle station occurs every time the vehicle departs from the bus vehicle station, there is an increased possibility that information distribution from the vehicle station to the bus will fail and the bus schedule may be disturbed.

  In other words, by specifying not only the route No but also the bus vehicle No and the bus vehicle location No., first the traffic reduction (the vehicle location where the night batch is performed by specifying the bus location and the bus used as the backup destination stops) Information can be distributed to a location). Next, it is possible to reduce the possibility of information delivery failure (by specifying a bus vehicle, it is possible to perform batch delivery in a night batch).

  In order to give priority to the diagram, the completed member classification (Gold) (192) of the reception state DB 19 is updated to “1”, and the state shifts to the bus start state. In other words, the bus cannot be started unless the point exchange information for the completed member category (Gold) (192) is delivered at the minimum, but it can start without the completed member category (Silver) (193) or (Bronze) (194). Is possible (step S015).

  The bus that has entered the bus start state then departs from the bus depot according to the schedule. The handling of point exchange information that could not be distributed here will be described in (Step S022) (Step S016).

The process of distributing information based on the reception status DB 19 is performed by the distribution determination unit (H10) every time the bus stops at each bus station “L100”, “L101”, “L003” within one day. (Step S017).
<On the bus>
Distribution of point exchange information on the bus is performed when a member who has reserved point exchange gets on or when the card is held over the IC card reader when getting off. The point processing unit (H12) of the bus system 3 on the bus compares the read card number “1001” with the card numbers (182) and “1001” of the on-vehicle replacement DB 18 and uses the replacement serial number (181) as the target record. The record “00230046” is extracted, and the SF is charged by the number of exchange points (183) “78” (step S018). Here, SF means a monetary value, which means that an IC card is given a monetary value equivalent to the number of favorable points (for example, boarding fare, electronic money, etc.).

  At the timing of charging, the record of the exchange serial number (131) “00230046” in the on-vehicle replacement DB 18 and the exchanged flag of the IC card “1001” that has been charged are updated to “1”. This prevents double exchange of points when a member with the same IC card “1001” gets on another bus “B100”.

The bus also stores the card number “1001” of the passenger who holds the IC card over the card number (202) of the boarding customer DB 20. The reason for storing the card No. in the passenger customer DB 20 will be described later in (Step S022). However, the exchange is performed even though the user wishes to exchange points and gets on the bus of the corresponding route No. This is because the data is necessary when investigating whether there was a customer who did not exist (step S019).
<Batch at night>
After the end of business, the bus “A100” returns to the bus depot “L100” and communicates with the point exchange system on the bus. The point exchange system on the bus reads the card number (202) “1001” of the passenger customer DB 20 (step S020). In this case, communication may be performed via the bus vehicle station system, but the present invention is not limited to this.

  The replacement serial number (181) “00230046” of the record of the replacement serial number (181) “00230046” in which the replacement flag (184) of the on-vehicle replacement DB 20 is updated to “1” is read, and the replacement information DB 13 is replaced. The record of the serial number (131) “00230046” is extracted, and the exchange completion flag (139) is updated to “1” (step S021).

  Next, the undelivered customer specifying unit (H08) checks whether or not there is a record in which the point exchange is desired but the point exchange is not performed even though the vehicle is on the target vehicle. Specifically, the vehicle number (201) “A100” and the card number (202) “1001” in the passenger customer DB 20 are compared, and the vehicle number “A100” and the card number (132) “1001” in the exchange information DB 13 are compared. Refer to “1” for the completion flag (139). Here, since the exchange completion flag (139) is “1”, it can be seen that points are given to the passenger.

  However, although the card numbers (132) and “1002” that are desired to be replaced with the replacement serial number (131) and “00230047” are stored in the passenger customer DB 20 of the vehicle number (201) and “A100”, The exchange completion flag of the record of the exchange serial number (131) “00230047” in the exchange information DB 13 is “0”. From this, it can be understood that the point exchange on the bus car was not able to be performed even though the customer who wanted to exchange got on the board.

The reason why the above processing and cases occur is that there is a possibility that a bus that starts with only Gold member information may occur in (Step S014) to (Step S016), so exchange points within the scope of normal work This is because there may be cases where information cannot be distributed. Further, the card number “1002” of the customer who could not distribute the point exchange information and the exchange serial number “00230047” can be specified by this processing (step S022).
For customers with card No. “1002” who could not distribute point exchange information in the process of (S022) above, apologize on the WEB screen of the point exchange system on the bus car and Mail “456 @ abc” in the member information DB12. Take measures such as making contact (step S023).

  The point exchange system on the bus car regards the record of the exchange serial number (131) “00230046” in which the exchange completion flag (139) of the exchange information DB 13 is updated to “1”, and regards the record as exchange completion, the exchanged data deletion unit (H07) Deletes the record from the exchange information DB 13 (step S024).

For point exchange information that has passed the exchange date (end) without the exchange completion flag (139) in the exchange information DB 13 being updated to “1”, the exchange point is exchanged as the unexchanged point addition unit (H09). Add to the points owned by the desired member. If the exchange completion flag (139) is not updated to “1” even after the exchange date (end) (136) “20110407” for the record of the exchange serial number (131) “00230047” in the exchange information DB 13, the exchange point The number (133) “30” is added to the possession points (step S025). Next, all the bus distribution DBs (15 to 17) of the respective buses and bus stations are deleted and the process ends (step S026).
<Abnormal processing>
Basically, the point exchange information is distributed from the point management server to the bus through the bus depot in a nightly batch. However, unlike other transportation systems, bus disturbances are likely to occur due to traffic conditions, and bus vehicles that were not planned in advance may operate. In this case, since the point exchange information is distributed to the bus according to the information planned in advance in the night batch, it is not possible to deal with an unscheduled bus. Specifically, if there is a bus “A100” that is delayed in arrival at the vehicle location, the spare vehicle “C100” is assigned as a substitute with the route No. “305” and a crew member is started, and the spare vehicle is started due to a vehicle failure. This is the case. In this case, since the point exchange information is not distributed to the spare vehicle in the night batch, it is not possible to shift to the start state as described in (Step S015). Therefore, when a spare vehicle is used due to a diamond disruption or the like, it is necessary to perform processing in advance in the vehicle number replacement registration unit (H06) (step S012).

  The flow of the vehicle number replacement registration unit (H06) is as follows. When it is determined that the spare vehicle “C100” is to be used at the bus depot due to a disruption of the schedule, the vehicle numbers “C100” and “A100” to be replaced are notified from the bus depot to the bus management system. The bus management system stores the replacement source vehicle No (211) “C100” and the replaced vehicle No (212) “A100” in the vehicle replacement DB 21.

  The bus management system distributes the vehicle replacement DB 21 to all bus stations at any time. The bus station refers to the replacement source vehicle No (211) “C100” and the replaced vehicle No (212) “A100” in the vehicle replacement DB 21, and performs processing in the vehicle number replacement unit (H11). Specifically, the vehicle number replacement unit (H11) replaces the vehicle number (191) “C100” in the reception state DB 19 transmitted from the bus (step S014) with “A100” according to the vehicle replacement DB 21.

  By doing so, the spare vehicle “C100” looks like the originally planned vehicle “A100” when viewed from the bus depot, and thereafter, the points are exchanged according to the contents of the reception state DB 19 as described in (Step S014). Information is distributed (step S013).

1: Bus point exchange system, 2: Bus vehicle system, 3: Bus system, 11: Bus operation database, 12: Member information database, 13: Exchange information database, 14: Distribution database, 15: Vehicle distribution Database, 18: On-vehicle exchange database

Claims (5)

A bus point exchange system having a bus vehicle point exchange system, a bus vehicle place system provided at each of a plurality of bus vehicle places, and a bus system provided at each of a plurality of buses,
The bus car point exchange system is:
Accept point card specific information and exchange points from users,
Storing the received exchange points and point card identification information in correspondence with each other in the distribution database as distribution data;
Sending the delivery data to the bus depot system;
The bus depot system is
When the distribution system is in a state where the bus system can be connected to the bus vehicle system, the received distribution data is transmitted to the bus system on the bus vehicle,
When the bus system is in a disconnected state,
The point card information received from the user and the point card specific information in the received distribution data are compared and the monetary value for the exchange point of the matching point card is given to the received user's point card,
When the bus system is in a state where it can be connected to the bus station system, information indicating that the point exchange is completed is transmitted to the bus station system, and the bus station system receives the received completion information. The bus point exchange system characterized by transmitting the information to the on-board bus exchange system. The bus point exchange system according to claim 1,
The bus vehicle point exchange system further includes:
Accept route information from users,
Storing the exchange point, the point card specifying information, and the route information in an exchange information database in association with each other;
For each vehicle information that identifies the vehicle, the vehicle location information that identifies the vehicle location and the route information are associated with each other and stored in the bus operation database in the order of operation,
Collating the information in the exchange information database with the information in the bus operation database, identifying the vehicle location information and vehicle information corresponding to each point card identification information,
Storing the identified vehicle location information and vehicle information in association with each other in a distribution database;
Of the vehicle locations identified by the delivery data, send the exchange point corresponding to the bus vehicle system that operates first, point card identification information and vehicle body information,
The bus depot system is
The bus point exchanging system, wherein the received exchanging point and point card specifying information corresponding to the vehicle information are transmitted to the bus system of the vehicle corresponding to the received vehicle information. A respective bus point exchange system according to claim 1 or 2, wherein
The bus vehicle point exchange system further includes:
Accept information indicating priority corresponding to point card specific information for each user,
Create multiple distribution databases according to the priority,
Transmitting the plurality of distribution databases to the bus vehicle system;
The system on the bus vehicle transmits the received exchange point and point card specifying information corresponding to the vehicle information to the bus system of the vehicle corresponding to the vehicle information in order from a high-priority distribution database. Bus point exchange system. A respective bus point exchange system according to claim 1 to claim 3, wherein
An exchange point, point card identification information, and vehicle body information are transmitted to a bus vehicle system at a plurality of vehicle locations where the on-board point exchange system is specified. A bus point exchanging method comprising: a bus car point exchanging system; a bus car station system provided at each of a plurality of bus car stations; and a bus system provided at each of a plurality of buses,
The bus car point exchange system is:
Receiving point card specific information and exchange points from the user;
Storing the received exchange points and point card identification information in association with each other in a distribution database as distribution data;
Transmitting the delivery data to the bus vehicle system,
The bus depot system is
When the distribution data is in a state where the bus system is connectable to the bus vehicle system, the step of transmitting the received distribution data to the bus system on the bus vehicle,
When the bus system is in a disconnected state,
A step of giving the received user's point card a monetary value corresponding to the exchange point of the point card that matches the point card information received from the user and the point card specifying information in the received distribution data. ,
When the bus system is in a state where it can be connected to the bus station system, information indicating that the point exchange is completed is transmitted to the bus station system, and the bus station system receives the received completion information. Transmitting to a bus car onboard exchange system.

Images