GB2583031A - Billing processing device, toll collection system, billing processing method, and program - Google Patents

Abstract

A billing processing device (10) is provided with: a payment-related information acquisition unit that acquires payment-related information associated with each of a plurality of users of a vehicle (A) to be billed, on the basis of information read from the vehicle (A); a payer determination processing unit that determines which user's payment-related information included in the acquired payment-related information should be used as a basis for performing a billing process; and a billing processing unit that performs the billing process on the basis of the determined payment-related information.

Description

DESCRIPTION

Title of Tnvention

BILLING PROCESSING DEVICE, TOLL COLLECTION SYSTEM, BILLING PROCESING METHOD, AND PROGRAM

Technical Field

[0001] The present inventionin relates to a bill a processing device, a toll collection system, a oiiiyng ocessina net od, and a program-Backgrbund Art.

[0002] A tollgate of a toll road the like is provided with toll collection stem for collecting tolls from USCfS. :a this toll collection system, tnere is a case where an REID asilo freq.-Lie z identifier is used (refer to, for example, PTL 1). In this case, the tom collection system reads identi rwon information of a REID tag attached to a vehicle body of the vehicle which travels on the tollgate through a radio comm-nication device. icsy RSID reader) installed on aroa.dside. Then, the toll collection. system specifies personal information registered in advance in a rear server, based on thP on information read fro' the RFID tag, and performs billing processing. Citation List Patent Literature [0003] [PTL 2] Japanese Unexamined Patent. Application Publication No. 2017-004132

Summary of Invention

Technical Problem [0004] In the toll collection system using the RFID, generally, identification information of one aF1D tag attached to a vehicle, personal information (a name or the like) of one user who boards the vehicle, and payment-related information (a bank account number or the like) are associated with each other, However, in this case, it is not possible to cope with a case where a plurality of users share one vehicle.

In this manner, it is desired to enable toll collection from one designated user among a plurality of users who share and use one vehicle to be billed, based on information acquired from the vehicle.

[0005] In view of the above-mentioned problem, the present invention provides a billing processing device, a toll collection system, a billing processing method, and a program, in which it is possible to collect a toil from one designated user among a plurality of users who share and use one vehicle to be billed, based on information acquired from the vehicle.

Solution. to Problem [00061 According to a first aspect of the present invention, there is provided a billing processing device (10) including: a payment-related information acquisition unit (1001) that acquires payment-related information associated with each of a plurality of users who use a vehicle (A.) to be billed, based on information read from the vehicle; a payer determination processing unit (1002) that determines which us-ere payment-related information in the acquired payment--related information is to be used as a basis for performing billing processing; and a billing processing unit (1003) that performs the billing processing, based on the determined payment-related information.

In this way, the payment-related information of each of a plurality of users who share and use one vehicle is acquired based on the in which is read from the vehicle when the vehicle passes through a tollgate. Then, the payment using the designated payment-related information in the acquired plurality of pieces of payment-related information is determined. Therefore, based. on information acquired from one vehicle to be billed, it is possible to collect a toll from one designated user among a plurality of users who share and use the vehicle.

[00071 Further, according to a second aspect of the present. invention, the payer determination processing unit. determines which user's payment-reiated information is to be used as a basis for performing billing processing, based on a determination result as to whether or not at least. one of use time and a use location satisfies a condition determined in advance.

In this way, a user to pay a toil, among the plurality of users, is automatically determined according to the conditions for the use time and use location set in advance. Therefore, when using the toll road, it is possible to reduce the trouble of designating a. user to pay the toll.

[00081 Further, according to a third aspect of the present. invention, in. a case where at least one of the use time and the use location does not meet any of the conditions, the paver determination processing unit determines to perform billing processing, based on the payment--related information of a predetermined user in the acquired payment-related information_ in this way, even in a case where there is no user who meets the conditions for the use time and the use location set in advance, the payment of the toil by the representative of the plurality of users is automatically determined. Therefore, when using the to road, it is possible to further reduce the trouble of designating a user to pay the toil.

[00091 According to a fourth aspect of the present invention, the billing processing device further includes a condition setting reception unit (1000) that receives setting of the condition from a use r in advance.

in this was the user can optionally set the conditions for allowing the payer determination processing unit to determine which user's payment-related information is to be used as a basis f r billing orocecinci, [00101 Further, according to a fifth aspect of the present invention, in a case of receiving designation of a user who makes payment, the payer determination processing unit determines to perform billing processing, based on the payment-related information of the designated user.

In this way, in a case where the user who makes the payment is designated by the user, billing processing is performed using the payment-related. information. of the designated user.

[0011] According to a sixth aspect or the present invention, the payment-related information acquisition unit reads, as information which is read. from the vehicle, identification information of REID tags (T1 and Ti) attached to a vehicle body of the vehicle, and acquires the payment-related information associated with the identification information.

By using REID, it is possible to realize a simple and inexpensive toll collection system.

[0012] Further, according to a sev,=ntn, aspect of the present invention, there is provided. a toll collection system (1) including: the billing processing device described above; and vehicle information acquisition means (12, 12a) for acquiring, from a traveling vehicle, information related to the vehicle.

[00131 Further, according to an eighth aspect of the present invention, there is provided a billing processing method. including: a step of acquiring payment-related information associated with each of a plurality of users who use a vehicle to be billed, based on information read

-

from the vehicle; a step of determining which user's payment-related informatiofl.

in the acquired payment-related information is to be used as a basis for performing billing. processing; and a step of performinp the billing processing, based on the determined payment-related information.

[0014] According to a ninth aspect of the present invention, there is provided a program that causes a computer of a billing processing device to function as: a payment-. related information acquisition unit that acquires payment-related information associated. with each of a plurality of users who use a vehicle to be billed, based.

information read from the vehicle; a payer determination processing unit that determines which user's payment-related information in the acquired payment-related. information Is to be used as a basis for performing billing processing; and a billing processing unit that performs the billing processing, based on the determined payment related information.

Advantageous Effects of Invention [0015] According to the billing processing device, the toll collection system, the billing processing method, and the program described, above, it is possible to collect a toll.

from one designated user among a plurality of users who share and use one vehicle to be billed, based. on the information acquired from the vehicle.

Brief Description of Drawings

[0016] Fig. I is a diagram showing an overall configuration of a toll. collection system according to a. first. embodimant.

Fig. 2 is a diagram showing a functional configuration of a billing processing device according to the first embodiment.

Fig. 3 is a diagram specifically showing contents of registration information according to the first embodiment.

Fig. 4 is a diagram showing a processing flow of billing processing device according to the first embodiment.

Fig., 5 is a. diagram specifically. showing contents of registration information according to a second embodiment, Fig. 6 is a diagram showing a processing flow of a billing processing device according to the second embodiment.

Fig. 7 Is a diagram showing an overall configuration. of a toll collection system according to a third embodiment.

Fig. 8 is a diagram specifically showing contents of registration information according to the third embodiment. Description of Embodiments [0017] <First. Embodiment> Hereinafter, a toll collection system according to a first embodiment will be described in detail with reference to Figs. 1 to 4.

[0018] (Overall Configuration of Toll Collection System) Fig, 1 is a diaeram showing the overall configuration of the toll collection system according to the first embodiment, A. toll collection system 1 shown in Fig, 1 is a system for performing toil collection with respect to a vehicle A which passes through a tollgate R. on a toil road.

[0019] As shown in Fig. I, the toll collection system I includes a billng processing device 10, a terminal device 11, and a radio communication device 12. The billing processing device 10, the terminal device 11, and the radio communication device 12 can communicate with each other through a wide area conariunication network N such as an Internet line.

[0020] The billing processing device 10 performs billing processing with respect to a user who uses the toil road. Specifically, the billina processing device 10 has a database in which a tag ID of an REID indiaidually issued to a user. (-dentification info mat. ion th c can be wirelessly read. from the REID tag) and regisrr information registered in advance with respect the user are associated wit__ each other. Then, the billing processing device 10 specifies registration information associated tag ID read at the tollgate R, and perfor= billing processirr on the user, based on the specified registration information [00211 The termi al device 11 is a termi al device to which a user of the toll road inputs registration information to be registered A the billing oroces device 10. For example, the user accesses a predetermined registration website by us-n the terminal device 11 and inputs in advance a series of registration information necessary for na the toll road, such as personal information (a name or the like of the user) or a bank account number from hich a toll is to be paid. The personal information, the bank account numner, and the like input through the terminal device 11 are recorded in association with the tag ID of the REID tag issued to each user. Further, after e registration information is reaistered, tixe user can access the registration website by using the terminal device 11 and change or delete the registered registration information.

The terminal device 11 may be a dedicated computer which is provided to a user from an operation company for the toil road, or may be a desktop personal computer, a notebook personal computer, a smartphone, a tablet terminal, or the like owned by a user.

[00221 The radio communication device 12 is installed at a roadside of a lane laid at the tollgate R. The radio communication. device. 12 reads the REID tag attached to a vehicle body of a. vehicle which travels on the lane of the tollgate R. Specifically, the radio communication device 12 forms a communicable area by transmitting radio waves toward the lane, reads the tag ID of the REID tag of the vehicle that has entered the communicable area, and transmits the read tag ID to the billing processing device 10. In a case where. a plurality of REID tags have entered the communicable area, the radio communication device 12 is configured to be able to read all of the plurality of REID tags. For example, the radio con-mrylicm device. 12 is configured to be able to read all of the plurality of REID tags by limiting the number of REID tags to be attached to one vehicle, or setting a speed limit in the -11 section of the lane belonging to the communicable area (extending time during which a vehicle exists in the communicable area).

The radio communication device 12 is an aspect of vehicle information acquisition means for acquiring information related to a vehicle traveling on the lane of the tollgate R from the vehicle.

[0023] As shown in Fig. 1, the vehicle A which travels on a toll road has two REID tags Ti and T2 attached to the vehicle body thereof. The two REID tags Ti and T2 attached to the vehicle A are tags respectively issued from the operation company for the toll road to two users who share and use the vehicle A. That is, the two users who share and use the vehicle A use the toil road after the REID tags Ti and T2 respectively owned by (issued to) the use are attached. to the vehicle body of the same vehicle A. The vehicle A to which the two REID tags Ti and 12 are attached. is an example of a vehicle traveling on the tollgate P. having the toll collection system 1 applied thereto, and other vehicles are not limited to this aspect. That is, in a case where one vehicle is shared. and used by three persons, three REID tags are attached to the vehicle body thereof, and in a case where one vehicle is used by one person (it is not shared and used by a plurality of persons) , only one. RFID tag is attached to the vehicle body thereof.

[0024] (Functional Configuration of Billing Processing Device) Fig 2 is a diagram showing the functional configuration of the hilling processing device according to the first embodiment.

Asshown in Fig, 2, the billing processing device 10 includes a CPU 100, a recording medium 101, and a connection interface 102.

The CPU 100 is a processor that controls the entire processing of the billing processing device 10. The CPU 100 operates as various functional units (described later) by operating according to a dedicated program read into a main memory (not shown).

The recording medium 101 is a large-capacity storage device (auxiliary storage device) built in the billing processing device 10, and is, for example, a hard disk drive (HDD), a solid state drive (SSD), or the like. In The recording medium 101, registration information of users who use the toll road is recorded_ The recording medium 101 according to this embodircient has been described as a large-capacity storage ---13 -device built in the billing processing device 10. However, in other embodiments, it is not limited to this aspect. The recording medium 101 on which, the registration information of the users is recorded may be an external-type large-capacity storage device communicably connected to the billing processing device 10.

The connection interface 1.02 is a connection interface for allowing the CPU 100 of the billing processing device 10 to communicate with the terminal device 11 and the radio communication device 12 through the wide area communication network N. [00251 Next, the functions of the CPU 100 of the piiiibe processing device 10 will be described.

The CPU 100 functions as a registration information reception unit 1000, a payment-related information acquisition unit 1001, a payer determination processing unit 1002, and a billing processing unit 1003 by operating based on a dedicated program.

[0026] The registration information reception unit 1000 receives registration informabion input, by a user through. the terwAnal device 11 and records the registration information on the recording. medium 101. The registration information reception unit 1000 also functions as a -14 -condition setting reception unit that receives setting of a condition for allowing the payer determination processing unit 1002 (described later) to determine which user's payment-related information (bank account numdger) is to be used as a basis for performing billing processing, as one of the registration information.

Specific contents of the registration information received from the terminal device 11 will he described later.

[00271 The payment-related information acquisition unit. 1001 acquires payment xelated information associated with each of a plurality of users who use the vehicle to be billed, based on information which is read from the. vehicle. In this embodiment, "information which is read from a vehicle, to be billed" is a tag ID which is reed from the RE-ID tag attached to the vehicle. Further, "payment-related information." is information associated with each user, and is information necessary for collecting a toll road use toil. from the user. in this embodiment, the payment'--related information is a bank account number of each user. In another embodiment, the "payment-related information" may be, for example, a credit card number or the like.

For example, in a case where the vehicle A. (Fig, 1) that is going to pass through the tollgate R is a billed target, the payment-related information acquisition unit 1001 acquires the tag ID of each of the two REID tags Ti and T2 (Fig. I) read. hr the radio communication device 12. Then, the payment related information acquisition. unit. 1001 acquires the payment-related information (bank account number) associated with the tag ID of the REID tag TI and the payment-related information. (bank account. number) associated with the tag ID of the REID tag. 12, with reference to the registration information recorded on the recording. medium 101 in advance.

[0028] The payer determination processing unit 1002 determines which user's payment-related information in the payment-related information of a. plurality of users acquired by the payment-related information acquisition unit 1001 should be used as a basis for performing billing processing. In particular, the paver determination processing unit 1002 according to this embodiment determines whether or not tine at which traveling related to billing is performed and a location where traveling related to billing is performed satisfy conditions determined in advance. Then, the payer determination processing unit 1002 determines which user's payment-related information is to he used as a basis for -16 -performing billing processing, based on the determination result.

[00291 The billing processing unit. performs billing processing, based on the payment-related information of one user determined by the payer determination processing unit 1002 with respect to traveling related to billing. Specifically, the billing processing unit 1003 performs, for example, every day, processing of deducting tolls from billing targets (bank accounts) totaled on that day.

[00301 (Contents of Registration Information) Fig, 3 is a diagram specifically showing the contents of registration information according to the first embodiment.

As shown Fig. 3, in registration information which is recorded on the recording medium 101 (Fig. 2), various types of information such as "NAVE", "ACCOUNT NUMBER", "VEHICLE NUMBER", "REPRESENTATIVE", "TRAVELING TIME CONDITION", "TRAVELING LOCATION CONDITION", and "PRESENCE OR ABSENCE OF DESIGNATION" input by a user are recorded in association with each of "tag IDs" ("401", "#02", ".) which are recorded on the REID tags< [0031] In the "NAME" column, Information indicating a name ("AA", "BB", ...) of a user associated with each of the "tag IDs" ("#01"" "#02", ...) (that is, a user who owns an REID tag in which each "tag ID" is recorded) is recorded. [0032] in the "ACCOUNT NUMBER" column, a number (bank account number) indicating a bank account of a user.

associated with each of the "tag IDs" ("401", "#02", .) is recorded.

[0033] In the "VEHICLE NUMBER" column, a vehicle number of a vehicle which is used by a user associated with each of the "tag IDS" ("#01", "#02", ...) iS recorded. In other words, in the -VEHICLE, NUMBER' column, a vehicle number of a vehicle to which an REID tag in which each "tag ID" is recorded is attached is recorded.

Here, in a case where a plurality of users share and use the same vehicle, the same vehicle number is recorded in the "VEHICLE NUMBER" columns associated with the plurality of users. For example, in the case of the example shown in Fig. 3, the same vehicle number "N0000" is recorded in the "VEHICLE NUMBER" associated with the user "AA" and the "VEHICLE NUMBER" associated with the user "BB". This inthcates that the user "Jul" and the user "BB" share and use one vehicle which is specified by the vehicle number "N0000", In this case, the vehicle having the vehicle number "N0000" is provided with an REID tag in which the tag ID "#01" is recorded and an FFID tag in which the tag ID "#02" is recorded.

[0034] in the "REPRESENTATIVE" cormmn, information indicating whether or not the user associated with each of the "Lag IDs" ("#01", "#02", .") is a representative of a group who shares and uses one vehicle is recorded ("Y" = representative, "N" non-representative). One representative, is selected from the group that shares and uses one vehicle.

In the example shown in Fig. 3, a representative of the group ("AA", "BE") using the vehicle with the vehicle number "N0000" is "AA". Further, a representative of the group ("CC", "CD", "FE") using the vehicle with the vehicle number "N0001" is "CC".

[0035] n. the "TRAVELING TIME CONDITION" column and "TRAVELING LOCATION CONDITION" column, conditions for allowing the payer determination processing unit 1002 to determine which user's bank account number (payment-related information) is to be used as a basis for performing billing processing are recorded.

In the "TRAVELING TIME CONDITION", a condition for the time at which traveling related to billing was -19 -performed (more specificasi the time at which the vehicle has pass d through the tollgate R, hereinafter, it is also described as "traveling time") se Further, in the "TRAVELING LOCATION CONDITION", a condition for a location. where traveling related to billing was performed (more specifically, an area to which the tollgate a th-ough which the vehicle has passed be c hereinafter, it i_s also described as "traveling location") is set.

a case where the traveli..g time and the traveling location meet t'e conditions set in the "TRAVELING TIME. CONDITION" and the "TRAVELING LOCATION CONDITION", re,,pc tively, he paver determination processing unit 1002 determines to perform billing processing by using the bank account number of the user for whom the met conditions are set, or example., in the example shown in 3, in a case where one vehicle (vehicle number = "N0000") to which two REID tags (tag ID = "#01", "#02") are attached passes th r u -f the tollgaLe R, two tag ID_: "#01" and "#02" are read from the radio communication device 12. In This case, in a case where tine time at ch the tag IDs were read belongs to a. time zone from 8:0C to 20:00, the payer determination processina unit. 1002 determines to perform billing processing by using the bank account number of the user "BE".

---20 --Further, although not shown in Fig. 3, for example, (assuming that the first tag ID is a representative.), a traveling time condition of "8:00 to 19:59" may be set to the second tag ID, and a traveling time condition of "20:00 to 07:59" may be set to the third tag ID. In this case, in a case where the time at which each tag ID was read belongs to a time zone from 8:00 to 19:59, the payer. determination. processing unit 1002 nerforms hilling processing by using the bank account number of the user associated with the second tag ID. Further, in a case where the time at which each tag ID was read belongs to a time zone of 20:00 to 07:59, the payer determination processing unit 1002 performs billing processing by using the bank account number of the User associated with the third. tag ID.

Further, for example, in the example shown in Fig. 3, in a case where one vehicle (vehicle number = "N0001") to which three REID tags (tag ID = "403", "#04", "#05") are attached) have passed through the tollgate R, three tag IDs "#03", "#04", and "#05" are read from the radio communication device 12. In this case, in a case where the tollgate R where the tag ID has been read. belongs to an "X section", the payer determination processing unit 1002 determines to perform, billing processing by using the L. account. number of the user flDD", [00.36] Further, in a case where the traveling time and the traveling location do not meet any of the conditions recorded in the "TRAVELING TIME CONDITION" and the "TRAVELING LOCATION CONDITION", the payer determination processing unit 1002 determines to perform billing processing by using the bank account number of the representative.

For example, in the example shown in Fig. 3, in a case where the time at which the two tag IDs "#01" and "#02" were read through the radio communication device 12 does not belong to the time zone of 8:00 to 20:00, the payer determination. processing unit 1002 determines to perform billing processing by using the bank account. number of the user "AA" who is a representative, Further, for example, in the example shown in Fig. 3, in a. case where the tollgate R where the three tag IDs "403", "#04", and "#05" have been read through the radio communication device 12 does not belong to any of the "X section" and the "I section", the payer determination processing unit 1002 determines to perform billing processing by using the bank account number of the user "CC" who is a representative.

[00371 In the "PRESENCE OR ABSENCE OF DESIGNATION" column, ---22 --information indicating whether or not there is a prior registration for designating a user to pav a usage toll recorded. In a case where there is a user designated as "PRESENCE" in the "PRESENCE OR. ABSENCE OF DESiiNNITON" in a group sha 1 and using one vehicle, the payer determination processing unit. 1002 determines to perform _Ling processing by using the bank account Pnber of the user designated as "PRESENCE" nthe "PRESENCE OR ABSENCE OF DESIGNATION", regardless of information recorded in "REPRESENTATIVE", "TRAVELING TIME CONDITION", and "TRAVELING LOCATION CONDITION" columns, For example, in the example shown. in Fig. 3, in a. case where the vehicle with the vehicle number "N0002" passes through the tollgate R, three tag IDs "#06", "#07", and "#08" are react from the radio communication device 12_ In this case, the payer.etc Lin tic= processing unit 1002 determines to perform billing processing by using tne bank account number of the user "Ha" designated. as "PRESENCE" in the "PRESENCE OR ABSENCE OF DESIGNATION", regardless of information recorded in "REPRESENTATIVE", "TRAVEMING TIME CONDITION", ana "TRAVELING LOCATION CONDITION" columns [0038] The registration information reception unit 1000 receives the input of "tag ID", "NAME", "ACCOUNT NUMBER", "VEHICLE NUMBER", "REPRESENTATIVE", "TRAVELING TIME CONDITION.", "TRAVELING LOCATION CONDITION", and "PRESENCE OR ABSENCE OF DESIGNATION" described above, from each user having the issued REID tag through the terminal device 11. Then, the registration information reception unit 1000 records the received various types of information in association with each other on the recording medium 101 as regdstration information. The setting of "TRAVELING TINE CONDFTiON", "TRAVELING IOCAIIION CONDITION", and "PRESENC'E OR ABSENCE OF DESIGNATION" is optional, and may not be input. in a case where in is not necessary for the user. Further, in a case where billing processing was actually performed by the billing processing unit 1003 by using the payment-related information, of the user designated as "PRESENCE" in the "PRESENCE OR ABSENCE OF DESIGNATION", the registration information recent ion unit 1000 may automatically delete the setting of "PRESENCE". Further, an expiration date may be provided to the setting of "PRESENCE." in "PRESENCE OR ABSENCE OE DESIGNATION" In this case, in a case where the expiration date is passed without using. the toll road, the registration information reception unit. 1000 automatically deletes the setting of "PRESENCE".

[0039] (Processing Flow of Billing Processing Device) Fig. 4 is a diagram showing a processing flow of the billing processing device according to the first. embodiment_ The processing from step SOO to step S09 shown 7 r, Fig. 4 is to be executed by the payment-related information acquisition unit 1001 and the payer determination processing unit 1002 of the CPU 100, and is regularly and repeatedly executed in a period that can wait for a vehicle passing through the tollgate R. Further, the processing of step SiO is to be executed by the billing processing unit 1003 of the CPU 100 and is executed, for example, every predetermined unit time (for example, one day).

[0040J The payment-related information acquisition unit 1001 determines whether or not the tag ID of the RFID tag has been read through the radio communication device 12 installed at the tollgate F (step 000) . In a case where the tag ID of the REID tag has not been read (step 500: NO), the payment-related information acquisition unit 1001 repeats the determination processing of step 500 until the tag ID of the RFID tag is read, and performs standby.

It is assumed that even while the tag ID of the. REID tag is not read (step SOO: NO), a vehicle without an REID tag (an unauthorized vehicle) passes. Therefore, the toll collection system 1 may further include separate means

-

(for example, a surveillance camera) for leaving as evidence the passage of the vehicle, in addition to the radio communication device 12.

[0041] In a case where the t.a.g ID of the REID tag has been read (step SOO: IES), the payment-related information acquisition unit 1001 refers to the recording medium 101 (Fig. 2) and acquires the registration information ("NAME", "ACCOUNT NUMBER", "VEHICLE NUMBER", "REPRESENTATIVE", "TRAVELING TIME-CONDITION", "TRAVELING LOCATION CONDITION", AND "PRESENCE OR ABSENCE OF DESIGNATION" shown in Fig. 3) associated with the read tag ID (step. Sal).

In a case where a plurality of tag IDs are read in step SOO as a result of a plurality of REID tags being attached to one vehicle which passes, the payment-related information acquisition unit 1001 acquires all of the registration information associated with each of the plurality of tag IDs.

[00421 Next, the payment-related information acquisition unit 1001 determines whether or not all the REID tags belonging to the same group have been read. (step SO2).

For example, i7 the example shown in Fig. 3, it is assured that the tag ID "#01" is read in step SOO. In this case, according to the registration information (Fig. -26 - :;), the tag ID "402", which is associated with the same vehicle number as the vehicle number "N0000" associated with the tag In "#01", should be read at the same time. Therefore, in a case where the tag ID "#01" is read by the radio communication device 12 in step 502, the payment-related information acquisition unit 1001 determines whether or not the tag ID "#02" is also read at the same time.

In a case where some of the RFID tags belonging to the same group have not been read (step 502: NC), it is assumed that the REID taus that should be originally attached to the vehicle have been peeled off or have failed. For example, according to the example shown in Fig. 3, when the vehicle with the vehicle number "N0000" passes through the tollgate R, two tag IDs "401" and "#02" should be read. However, in a case where only the to ID "#01" is read from the radio communication device 12, it is suggested that the RFID tag havinc the tag ID "#02" has been peeled off from the vehicle body or has failed. Therefore, in this case, the eayment-related infbrmation acquisition unit 1001 performs alert processing on the user associated with the read tag ID ("#01") (step 503) . The alert processing is processing of notifying that there is a possibility that inconsistency may occur between the combination of the RFID tags actually attached to one ---27 --vehicle to be billed and the contents recorded on the recording medium 101 as the registration information. (a set of tag Ins to be read. at the same time). A. specific aspect of the "notifying processing" may be, for example, mail distribution or the like to a terminal device owned by each user.

After the alert processing in step 503, the payer. determination processing unit 1002 performs the processing of step SO4 and later, which will be described later, on the REID tag read. in step SOC.

Further., the user who has been notified of the alert. prbcessing may be able to designate to the billing processing device 10 which user belonging to the same group pays the toll road usage toil. In this case, the payer determination processing unit: 1002 determines to perform, billing processing by using the bank account number of the single user designated. here.

[0043] On the other hand, in a case where all the REID tags belonging. no the same group have been read (step S02: It is determined that the combination of the REID tags actually attached to the vehicle to he billed and the contents recorded in the recording medium 101 as registration information are consistent with each other. Therefore, the payer determination processing unit 1.002 ---28 --determines which bank account number among The bank account numbers associated with each of the plurality of read tag Ins is to be used for payment, through the processing of step 504 and later.

[0044] Specifically, the payer determination processing unit 1002 first determines whether or not There is registration information designated as "PRESENCE" in "PRESENCE OR ABSENCE 02 DESIGNATION-(refer to Fig. 3) among various types of registration information associated with the read tag ID (step 304). In a case where there is the registration information set. as "PRESENCE" in "PRESENCE OR ABSENCE OF DESIGNATION-among various types of registration information associated with the read tag ID (step 304: YES), the payer determination processing unit 1002 determines to perform billing processing by using the bank account number of the registration information designated as "PRESENCE" in "PRESENCE OR ABSENCE OF DESIGNATION" (step R05). Specifically, in step 505, the payer determination processing unit 1002 adds the bank account number of the user designated as "PRESENCE" in "PRESENCE, OR ABSENCE OF DESIGNATTON" to the list of bank account numbers to be subjected to the billing processing (step. 510) which is performed at thp end of the-. day,

---29 --[0045; In a where there is no regist on information sPt as "PRESENCE" in. "PRESENcE OR ABSENCE C7 DESIGNATION" amo g various types of re g a,red information associated with the read. tag ID (step SU4: NO), next, the payc determination processing unit. 1002 determines whether or not t re registration aormation iemsich at leant one of "TRAVELING TIME CONDITION' AN7 "TRAVELING LOCATION DaNDITION" is set, o g various types of regls_ tion o. ation associated with the read. tag ID G« S06), [0046] eL case where there is no registration information in which. at lea m one of "TRAVELING TIME CONDITION" AND "TRAVELING LOCATION' CONDITION' is set, among various types of registration infor ration associated with the read tag ID, (step S06: NO), the payer determination processing unit 1002 determines to perform aiming processing. by using the bank. account number of the registration information in which "REPRESENTATIVE' among various tmes of registration in formation associated. th the read tag ID. (step S07). Specifically, in step S07, the payer detemin ion processing umit On° adds the bank. account number of the usei in whic'n "P7PRESENTAffIVE" is "Y" to the list of bank account numbers to be subjected to the billing processing (stet) S10), It has been described that in a case where some of the REID tags belonging to the same group have not been read (step 502: NO), the paver determination processing unit 1002 performs the processing of step SO4 and later on only sonic of the REID tags read in step 500.

Here, for example, even in a case where the condition of step 302: NO is satisfied because the REID tag of the representative of the group could not be read, in a case where at least one of other REID tags belonging to the group has been read, it. is possible to acquire information of the representative of the group to which the read REID tag belongs, with reference to the registration information (li.g. 3). Therefore, even in a case where the condition of step 302: NO is satisfied because the REID tag of the representative could. not be read, in a case where the condition of step 306: NO (or, step 508 (described later) : NO) is satisfied, the payer. determination processing unit 1002 determines to perform billing processing by using the bank account number of the representative.

[0047] Ts a case where there is registration information in. which at least one of 'TRAVELING TIME CONDITION" AND "TRAVELING LOCATION CONDITION" is set, among various types of registration information associated with the read tag ID (step 506: 'IPS), next, the payer determination processing unit 1002 determines whether or not there is registration information that meets at least one of the set "TRAVELING TIME CONDITION" and "TRAVELING LOCATION CONDITION" (step SO8), [00481 In a case where there is no registration information that meets at least one of the set "TRAVELING TIME CONDITION" and "TRAVELING LOCATION CONDITION" (step 508: NO), the payer determination precessinq unit 1002 determines to perform billing processing by using the bank account number of the registration ihformtlen in which -REPRESENTATIVE" is among various types of registration information associatPs with the read tag ID (step 507), On the other hand, in a case where there is registration information that meets at least one of the set "TRAVELING TIME CONDITION" and "TRAVELING LOCATION CONDITION" (step 508: YES), 1-he paver determination processing unit 1002 determines to perform b*Jiintq processing, based on the bank account number of the registration information Which Meets the condition, among various types of registration information associates with the read tag ID (step 309). Specifically, in step 509, the payer determination processing =it 1002 adds the bank ---32 --account. number of the use_ who meets at least one of wIRAVELJNO TIME CONDITMON" and. wIRAVELJNO LOCATION CaNDITION" to the list of bank account numbers to be jected to billing processi [0049J the end of the day, the billing ocessing it 1003 0 ' eCPU 100 exec) processing of deducti g a toil from each user proces g) with reference to the list of bank accouAt numbers to be >Sled on th (step 312.

[0050] (Operation and Effeb s) As described above, the billing processing device 10 according to the fi rst embodiment includes: the payment-related information acquisition. units tha acquiret payment-related information (bank account number) associated with each of a p ran v of users w c use a vehicle to be billed, based on information 4 ag ID) read from the vehicle; the payer itein ion bromassing unit 1002 thatdetermines which user's bayment-related information in the acquired payment-related information is to be used. as a or. Mid ocessing; a the billing processing -:x 1002 that performs billing processing, based on the determined payment-related information.

In this way, the payment-related information of each of a plurality of users who share and use one vehicle is acquired with the information which is read when the vehicle passes through the tollgate R as a key. Then, the payment using the designated payment-related information in the acquired plurality of pieces of payment-related information is determined. Therefore, based on information acquired from one vehicle to be billed, it is possible to collect a toll from one designated user among a plurality of users who share and use the vehicle.

[0051] Further, the payer dc-termination processing unit 1002 according to the first embodiment determines which user's payment-related information is to be used as a basis for performing billing processinm based on a determination result as to whether or not at least one of traveling time (use time) and a traveling location (use location.) satisfies a condition determined in advance (refer to step 509).

In this way, a user to pay a toll, among the plurality of users, is automatically determined according to the conditions for the traveling time and traveling location set in advance. Therefore, when using the toll road, it is possible to reduce the trouble of designating a user to pay the toll.

--- :3 4 --[0052] Further, the payer determination processing unit 1002 accordincr to the first embodiment determines to perform bill i.fl processing, based on payment-related information of a predetermined user (representative) in the acquired payment-related information, in a case where at least one of the traveling Lime (use Lime) and the traveling location (use location) does not meet any of the conditions determined in advance (refer to step SOS: NO -step 307).

In this way, even in a case where there is no user who meets the conditions for the traveling time and traveling location set. in advance, the -oayment of the toll by the representative of the plurality of users is automatically determi.ned. Therefore, when using the toll road, it is possible to further reduce the trouble of designating a user to pay the toil.

[0053] Further, the billing processing device. 10 according to the first embodiment further includes the registration information reception unit 1000 (condition setting reception unit) that receives setting. of the condition. from a user in advance.

In this way, the user can optionally set the conditions for allowing the payer determination processing

-

unit 1002 to determine which user's payment-related information is to be used as a basis for performing billing processing.

[0054] Further, in a case of receivin6i designation of a user to make payment, the payer determination processing unit 1002 according-to the first embodiment determines to perform billing processing, based on payment-related information of the designated user (refer to step 5.05).

In this way, in a case where the user directly desiccates a person to make payment, billing processing is performed using the payment-related information of the designated use [00551 The payment-related information acquisition unit 1001 according to the first embodiment reads, as information which is the vehicle passing through the tollgate,, identification information (tag ID) of an REID tag attached to a vehicle body of the vehicle, and acquires the payment-related information associated with the identification information.

By using RFTD, it is possible to realize a simple and inexpensive toll collection system.

[0056] The billing processing device 10 and the toll. --36

collection system I according to the first embodiment have been described above in detail. However, the specific aspects of the billing processing device 10 and the toll collection system 1 are not limited to the embodiment described above, and various design. changes and the like can be made within a scope which does not depart from the gist of the invention.

[0057] <Second Embodiment> Hereinafter, a toil collection system according to a second embodiment will be described in detail with reference to Figs. 5 and S. The configurations of the toll collection system and the billing processing device according to the second embodiment are the same as those in the first embodiment (Figs 1 and 2) , and therefore, illustration thereof is omitted. However., the second embodiment is different from the first embodiment in that in the second. embodiment, even in a case where a single vehicle is shared and used by a plurality of users, only one RFID tag is attached to the vehicle body of the vehicle.

[0058] (Contents of Registration Information) Fig. 5 is a diagram specifically showing the contents of registration information according to the 3.

second embodiment.

As shown in Fig. 5, in the registration. information according to the second embodiment, registration information of a plurality of users is associated with one "tag ID".

For example, according to the example of the registration information shown in Fig. 5, registration information of two users ("AA" and "BB") is recorded with respect to one tag ID "411". In this case, a single,. REID tag in which. the tag ID "411" is recorded. is attached to a vehicle body of a vehicle that is shared and used by the two users "AA" and "JIB" Similarly, according to the example of the registration, information shown in Fig. 5, registration information of three users ("CC", "DD", and "ER") is recorded. with respect to one tag ID "412". In this case, a single REID tag in which the tag ID "12" is recorded is attached. to a vehicle body of a vehicle that is shared by the three users "CC", "DD", and "EE".

[0059] in this manner, in the billing processing device 10 according to the second embodiment, the registration information of a pluality of users who share and use the same vehicle is recorded in association with the tag ID of one REID tag.

[0060] ---38 -- (Processing Flow of Billing Processing Device) 0 is a diagram showing a processing flow of the bfflin.g processing device according to the second embodiment, As shown in Fig. 6, the payment relatedinformation acquisition unit '1001 according to the second embodiment determines whether or not the tag ID of the REID tag has been read. through the radio communication device 12 installed at the tollgate R (step S00). In a case where the tag ID of the REID tag has not been read (step SOO: NO), the payment-related information acquisition unit 1001 repeats the determination processing of step SOO until the tag ID of the RFID tag is read, and performs standby.

[0061; In a case where the tag ID of the REID tag has been read through the radio communication device 12 (step SOO: YES), the payment-related information acquisition unit 1001 refers to the recording medium 101 and acquires registration information ("NAME", "ACCOUNT NUMBER", "VEHICLE NUMBER", "REPRESENTATIVE", "TRAVELING TINE CONDITION", "TRAVELING LOCATION CONDITION", AND "PRESENCE OR ABSENCE OF DESIGNATION" shown in Fig. 5) associated with the read tag ID (step 501a).

Here, in the second embodiment, a case where only one RFID tag is always attached to one vehicle regardless ---39 --of whether or not a plurality of persons share the vehicle will be described. Therefore, only one tag ID is always read from a vehicle which passes through the tollgate R. In step SOla, the payment-related information acquisition unit 1001 according to the second embodiment acquires all of a plurality of pieces of registration information in a case where the registration information of a plurality of users is associated with one tag ID, as a result of referring to the recording medium 101.

[00621 Hereinafter, the processing of steps SO4 to 510 shown in Fig. 6 is the same as that in the first ernbodiment.

The processing of steps SO2 and SO-R of the processing flow (Fig. 4) of the billing processing device 10 according to the first embodiment is unnecessary in the second embodiment on the presumption that only one tag ID is a3wavs read.

[00631 As described above, an aspect may be adopted in which only one aFili tag is always attached to a vehicle and the registration information of a plurality of persons who share and use the vehicle is associated with the tag TD of the one RETD tag.

[0064] <Third Embodiment> Hereinafter, a toll collection system according to a third embodiment will be described in detail with reference to Figs, 7 and S. [0065] (Overall Configuration of Toll Collection System) Fig 7 is a diagram showing the overall configuration of the toll collection system according to the third eMbodiment.

As shown in Fig. 7, the toll collection system 3 includes the billing processing device 10, the terminal device 11, and a license plate reader 12a. The billing processing device 10, the terminal device 11, and the license plate. reader 12a are made to be communicate with each other through the wide area communication network N such as an Internet line.

[0066] The license plate reader 12a is a device for automatically reading a vehicle number wriften on a license "plate of a vehicle passing through the tollgate R, and is one aspect of vehicle information acquisition means for acquiring information related to a vehicle traveling on a lane from the vehicle. The payment-related information acquisition unit 1001 of the billing processing device 10 according to the third embodiment acquires the vehicle number read by the license plate reader. 12a. and acquires user specific payment-related information associated with the vehicle number.

[0067] (Contents of Tz.egistration Information) Fig. 8 is a diagram specifically showing the contents of registration information according to the third. embodiment.

As shown in Fig. 8, in the registration information according to the third embodiment, registration information of a plurality of Users is associated with one "VEHICLE NUMBER".

For example, according to the example of the registration information shown in Fig. 8, registration information of two users ("AA" and "BB") is recorded with respect to a vehicle number "N0000". This means that the two users "AA" and "BB" share and use the vehicle with the vehicle number "N0000". Similarly, according to the example of the registration information shown in Fig. 8, registration information of three users ("CC", "DD", and "EE") is recorded with respect to a vehicle number "N0001". This means that. the three users "AA", "BB", and "CC" share and use the vehicle with the vehicle number "N0001".

[0068] in this case, the payment--related information --42 acquisition unit 1001 of the billing processing device 10 acquires the vehicle number read through the license plate reader-12a. Then, the payment-related information acquisition unit. 1001 acquires all the payment-related information associated with the read vehicle number with reference to the registration information shown in Fig. 2.

[0069] In this manner, an aspect may be adopted in which the registration information of a plurality of users who share and use the vehicle with each vehicle number is recorded in association with each vehicle number. In this way, it is possible to reduce the trouble of issuing a REID tag and attaching it to a vehicle body.

[00701 The toll collection system 1 according to the first to third embodiments has been described as being applied to a tollgate on a toll road. However, in other. embodiments, it is not limited to this aspect.

For example, the toll collection system 1 is applicable to a free-flow tvpe toll road, a toll tunnel, a toil bridge, a toll parking lot, or the like, which performs toll collection with respect to vehicles traveling on a main line non-stop.

[00711 in each of the embodiments described above, the processes of various types of processing of thebilling processing device 10 described above are stored a computer -readable recording medium in the form of a progxam, and computer reads and executes the program, whereby the various types of proheo performed.

Further, the computer-readable recording medium refers to a magnetic gneto-opt c i disk, a. CD-ROM, a DVD-ROM, a semiconductor memory, or the like, Further, the computer program may be distributed to a computer by a communication liner and the computer that has received the distribution may execute the procrram.

[0072] The program may be for realizing some of the functions described above. FurthPr, the program map be a so-called differential. file (diffe.P tial proglam) that can realize the functions described above in combination with a program already recorded on a computer system.

Further, the billing processing device 10 may be configured with a single r. 'muter having all of various functionsdescribed above, or may be configured with a plurality of computers having some of the functions and connected to be comrmnicate with each other.

[00731 Some embodiments of the present invention have been described above. However, these embodiments have been presented as examples and are not intended to limit the scope of the invention. Each of the embodiments described above can be implemented in other various forms, and various omissions, replacements, and changes can be made within a scope which does not depart from the gist of the invention. These modification examples are included in the scope or gist of the invention and are also LI-1CjIKIed in the inventions described in the claims and the equivalents thereof.

Industrial. Applicability

[0074] According to the billing processing device, the toll collection system, the billing processing method, and the program described above, it is possible to collect a toll from one designated user amotrg a plurality of users who share and use one vehicle to be billed, based on the information acquired from the vehicle, Reference Signs List [00751 1: toll collection system 10: billing processing device 100: CPU 1000: registration information reception unit 1001: p.svrent-related information acquisition unit 1002: paver determination 'orocessing unit 1003: billing processing unit 101: recording medium 102: connection. interface 11: terminal device 12: radio communication device (vehicle information acquisition means) 12a: license plate reader (vehicle information acquisition means) N: wide area communication network -46 -

Claims (1)

1. Claims [Claim 1] A billing processing device comp-H sing: a payment-related information acquisition unit that acquires payment-related information associated with each of a plurality of users who use a vehicle to be billed, based on information read from the vehicle; a payer determination processing unit that determines which user's oayment-related information in the acquired payment--related information is to be used as a basis for performing hilling processing; and a billing -orocehhing unit that performs the billing-processing, based on the determined payment-related information.[Claim 2] The billing processing device according to claim. 1, wherein the payer determination processing unit determines which user's payment related. information is to be used as a basis for performing billing processing, based on a determination result as to whether or not at least one of use time and a use location satisfies a condition determined in advance. 47 -[Claim 3] The billing processing device according to claim 2, wherein in a case where at least one of the use time and the use location does not meet any of the conditions, the payer determination processing unit determines to perform billing processing, based on the payment-related information of a predetermined user in the acquired payment-related information_ [Claim 4] The billing processing device according to claim 2 or 3, further comprising: condition setting reception unit that receives setting of the condition from a user in advance.[Claim 5] The billing processing device according to any one of claims 1 to 4, wherein in a case of receiving designation of a user who makes payment, the payer determination processing unit determines to perform billing processing, based on the paymentt-reiated information of the designated user.[Claim 6] The billing processing device according to any one ---48 --of claims 1 to 5, wherein the pavment-related information acquisition unit reads, as information which is read from the vehicle, identification information of an REID tap attached to a vehicle body of the vehicle, and acquires the payment related information associated with the identification information.[Claim 7] A toil collection system comprising: the billing processing device according to any one of claims 1 to 6; and vehicle information acquisition means for acquiring, from a travelinb vehicle, information related to the vehicle.[Claim 8] A billing processing method comprising: a step of acquiring payment relatedinformation associated with each of a plurality of users who use a vehicle to be billed, based on information read from the vehicle; a step of determining which user's payment-related.--ormation in the acquired payment-related information is to be used as a basis for performing billing processing; and 49 -a step of performing the billing processing, based on the determined payment-related information, [Claim 9] A program that causes a computer of a billing processing device to function as: a payment-related information acquisition unit that-acquires payment-related information associated with each of a plurality of use who use a vehicle to be billed, based on information read from the vehicle; a payer determination processing unit that determines which user's payment-related information in the acquired payment-related, information is to be used as a basis for performing billing processing; and billing processing unit that performs the billing processing, based on the determined payment-related information.