JP6704775B2 - Communication point information processing device, statement collection system, communication point information processing method and program - Google Patents

Description

The present invention relates to a communication point information processing device, a statement collection system, a communication point information processing method and a program.

In many cases, conventional toll collection systems on toll roads collect multiple lane servers installed for each lane belonging to one toll gate and billing detail data created by the multiple lane servers. It consists of a counting device (fee office). Here, the lane server performs charge collection processing for each vehicle traveling in each lane, and creates billing detail data for each vehicle as the processing result.
The tollgate aggregation device is usually installed in a tollgate unit on a toll road. Then, the tollgate collection device transmits a large number of billing detail data collected in units of tollgates to the host system (see, for example, Patent Document 1).
In the higher-level system, the billing detail data obtained at other toll gates is further aggregated, and a plurality of billing detail data for the same vehicle is matched to show the final billing amount for each vehicle. Detailed data creation processing and the like are performed.

On the other hand, in recent years, an FF (free flow) type toll collection system capable of toll collection processing without restricting the travel of a target vehicle has been studied. The FF type toll collection system restricts the traveling of the vehicle through the narrow area wireless communication performed between the vehicle-mounted device mounted on the vehicle and the wireless communication device (roadside antenna) installed on the lane side of the tollgate. Toll collection processing can be carried out.
In the FF type toll collection system, each lane server performs toll collection processing for each vehicle through the short-range wireless communication and creates billing detail data. Then, the tollgate collection device tallies the billing detail data created by each lane server belonging to this tollgate.

The FF type toll collection system can be applied to not only toll booths but also junctions and the like. In this case, a plurality of lane servers are installed in each lane belonging to the junction, and the tollgate totaling device totals the billing detail data created by each of the plurality of lane servers. However, normally, no charge is made at the junction, and the charge detail data is exclusively acquired for the purpose of identifying the traveling route of the vehicle.

JP, 2006-309597, A

Some of the billing detail data collected by the tollgate aggregation device in units of tollgates (or junctions) may be unnecessary in the further aggregation processing by the host system.
For example, as described above, at the junction, billing detail data is acquired exclusively for the purpose of grasping the traveling route of the vehicle, and billing is not performed. Then, the billing detail data acquired at the junction has a billing amount of “zero” at all times, and therefore, it is not necessary to perform a totaling process (a billing detail data matching process or the like) in the upper system. Therefore, the billing detail data acquired at the junction need not be transmitted to the host system.
Further, for example, even at a toll gate, in the case of a toll road where the distance toll charge is made at the exit toll gate, at the entrance toll gate, billing detail data for the purpose of identifying "where the target vehicle came from" Is created. In this case as well, the billing amount of the billing detail data is “zero” (that is, the billing is not performed at the entrance tollgate), and thus it is not necessary to transmit the billing detail data acquired at the entrance tollgate to the host system.

By the way, a management office is set up between the tollgate aggregation device and the communication system of the host system, and the management office aggregates billing details at each of a plurality of tollgates (or junctions) belonging to a predetermined area. There is a case where the data is further aggregated.
In this case, due to the above-mentioned circumstances, the management office collects the billing statement data aggregated from a plurality of toll gates (or junctions) belonging to a predetermined area according to the toll gate (or junction) that is the transmission source (the toll gate). (Or in units of junctions), the operation is performed to further determine whether or not to transmit to the host system.

However, if the above-described operation mode is adopted, relaying by the management office that determines whether or not to transmit to the upper system is indispensable, which complicates the hierarchical structure of the communication network. Further, in the case of the above-described operation mode, since the necessity of transmission is determined in units of toll gates (or junctions), each toll gate (junction) creates lanes for which billing detail data that needs to be transmitted to the upper system There is a need to be configured with only one of (the lane for which the fee is charged) and the lane for which the billing detail data that does not need to be transmitted to the host system is created (the lane for which the fee is not charged). Then, for example, it is not possible to set a tollgate (junction) in which lanes that do not charge and lanes that charge are mixed, and flexible operation modes according to geographical and structural characteristics of the tollgate or junction. The selection of can be limited.

An object of the present invention is to provide a communication point information processing device, a statement summarization system, a communication point information processing method, and a program that can simplify the structure of a communication network and flexibly select the operation mode of each lane. ..

A communication point information processing device (20) according to one aspect of the present invention is a device installed at each communication point (2) of a toll road, and a plurality of lanes installed for each of a plurality of lanes belonging to the communication point. Through the server (22), a billing detail data acquisition unit (201) for obtaining billing detail data (D) indicating a travel route and a billing amount of each vehicle traveling in the lane, and a plurality of the obtained billing detail data. And a billing statement data sending unit (202) for sending to a central system (4) provided for each predetermined business area including the communication point. Further, the billing statement data transmission unit refers to a transmission necessity table (T) that defines the necessity of transmitting the billing statement data to the central system for each lane server, and acquires the billing statement obtained. Determining whether to send data towards the central system.
By doing so, the communication point information processing device can determine whether or not to transmit each of the billing detail data acquired through the plurality of lane servers belonging to the communication point to the upper system. Therefore, the billing statement data can be directly transmitted from the communication point information processing device to the host system without going through the management office. Therefore, it is possible to simplify the hierarchical structure of the communication network.
Further, the communication point information processing device determines whether or not to transmit the acquired billing statement data for each lane in which the billing statement data is acquired. Also, it is possible to flexibly select an operation mode such as mixing lanes to be charged.

Further, according to one aspect of the present invention, the communication point information processing device converts each of the billing statement data acquired through the plurality of lane servers into a data format that can be processed by the central system. A format conversion unit (203) is further provided.
By doing so, even if the billing statement data to be transmitted is different from the data format specified by the destination higher system (central system), the billing statement received by the higher system is received. Data can be processed.

Further, according to an aspect of the present invention, in the communication point information processing apparatus described above, the billing detail data transmission unit further receives the billing detail data from a plurality of the central systems provided for a plurality of the business areas. The billing detail data is transmitted to the common system (5) for aggregation.
By doing so, the billing statement data is directly transmitted from the communication point information processing apparatus to the common system located higher than the central system. (For example, a web page creation process) is quickly performed.

Further, one aspect of the present invention is a statement summarizing system including the communication point information processing device described above, the plurality of lane servers, and the central system.

Further, one aspect of the present invention is a communication point information processing method at each communication point of a toll road by the communication point information processing apparatus , wherein a billing statement data acquisition unit of the communication point information processing apparatus belongs to the communication point. A billing detail data acquisition step of obtaining billing detail data indicating a travel route and a billing amount of each vehicle traveling in the lane through a plurality of lane servers installed for each lane, and a billing detail of the communication point information processing device. A data transmitting unit that transmits the acquired billing statement data to a central system provided for each predetermined business area including a plurality of the communication points, and a billing statement data transmitting step, the billing statement In the billing statement data transmitting step, the data transmitting unit refers to a transmission necessity table that defines the necessity of transmitting the billing statement data to the central system for each lane server, and obtains the billing statement acquired. It is a communication point information processing method for determining whether or not to transmit data to the central system.

Further, according to one aspect of the present invention, a computer of a communication point information processing device installed at each communication point of a toll road travels in the lane through a plurality of lane servers installed for each of a plurality of lanes belonging to the communication point. Billing detail data acquisition means for obtaining billing detail data indicating the travel route and billing amount of each vehicle, and the obtained billing detail data in a central system provided for each predetermined business area including a plurality of communication points. The billing detail data transmitting unit for transmitting the billing detail data to the central system, and the billing detail data transmitting unit refers to a transmission necessity table that defines the necessity of transmitting the billing detail data to the central system for each lane server. Then, it is a program for determining whether or not to transmit the acquired billing detail data to the central system.

According to the communication point information processing device, the statement totaling system, the communication point information processing method, and the program described above, it is possible to simplify the structure of the communication network and flexibly select the operation mode of each lane.

It is a figure showing the whole composition of the statement totaling system concerning a 1st embodiment. It is a figure which shows the function structure of the tollgate totaling apparatus which concerns on 1st Embodiment. It is a figure explaining the transmission necessity table which concerns on 1st Embodiment. It is a 1st figure which shows the billing detailed data which concerns on 1st Embodiment. It is a 2nd figure which shows the billing detailed data which concerns on 1st Embodiment. It is a 1st figure explaining the function of the format conversion part which concerns on 1st Embodiment. It is a 2nd figure explaining the function of the format conversion part which concerns on 1st Embodiment. It is a figure which shows the whole structure of the detailed tabulation system which concerns on a proportional relationship.

<First Embodiment>
Hereinafter, the detail collection system according to the first embodiment will be described with reference to FIGS. 1 to 8.

(overall structure)
FIG. 1 is a diagram showing an overall configuration of a detailed tabulation system according to the first embodiment.
The statement summarization system 1 is a system that tallies billing statement data D indicating a travel route, a billing amount, etc. of a user who uses a toll road such as an expressway.
As shown in FIG. 1, the detail collection system 1 according to the present embodiment includes a communication point 2, a management office 3, a central system 4, a common system 5, and a log collection device 6.

The communication point 2 is a point on the toll road where narrow-area wireless communication is performed with a traveling vehicle and billing detail data D is created. Specifically, the communication point 2 is an entrance toll gate, an exit toll gate, a junction, or the like on the toll road.
As shown in FIG. 1, the communication point 2 includes a tollgate aggregation device 20, a tollgate server 21, and a plurality of lane servers 22.

The lane server 22 is installed for each of a plurality of lanes belonging to the communication point 2. Here, the communication point 2 according to the present embodiment has a total of eight lanes in which an upstream line entrance/exit, a downstream line entrance/exit, a lane for connecting other roads (a lane functioning as a junction), and the like are mixed. The lane server 22 is installed in each of the eight lanes belonging to the communication point 2. The lane server 22 performs short-range wireless communication with a vehicle traveling in each lane via a roadside antenna. Then, the lane server 22 creates billing detail data D for each vehicle traveling through the short-range wireless communication.
Here, the lane server 22A is installed in, for example, an exit lane or the like in which a charge is required, and executes both route acquisition and charge processing. Further, the lane server 22B is installed in a lane or the like that functions as a junction and only acquires a route.
That is, the lane server 22A creates "route acquisition billing data D1" which is the billing detail data D in which the traveling route information and the billing amount are shown, and the lane server 22B shows the traveling route information and the section. The "route acquisition data D2" which is the billing detail data D in which the amount of money is "zero" is created.
Each lane server 22 transmits the created billing detail data D (route acquisition billing data D1, route obtaining data D2) to the tollgate server 21 provided separately.

The toll booth server 21 is a server device installed in an office (toll booth office) or the like at each communication point 2 on the toll road, and stores the billing detail data D created by the eight lane servers 22.

Similar to the tollgate server 21, the tollgate aggregation device 20 (communication point information processing device) is installed in an office (tollgate office) or the like at each communication point 2 on the toll road, and with respect to the billing statement data D. Performs various information processing. For example, the tollgate aggregation device 20 acquires the billing detail data D accumulated in the tollgate server 21 and transmits it to the higher-level system (in this embodiment, the central system 4 and the common system 5 described later).
The tollgate totaling device 20 according to the present embodiment converts the billing detail data D created by the lane server 22 into a predetermined data format (undetermined data Dt1 and daily confirmed data Dt2, which will be described later), and outputs it to the upper system. Output.
The detailed functional configuration of the tollgate aggregation device 20 will be described later.

The management office 3 receives the billing statement data D from a plurality of communication points 2 (toll gates or junctions) belonging to a predetermined management area (for example, one or more “municipalities”) managed by the management office 3. Then, of these, only the billing detail data D necessary for the aggregation by the upper system (the central system 4 and the common system 5) is transmitted to the upper system.
The detailed functional configuration of the management office 3 will be described later.
The communication point 2 shown in FIG. 1 directly transmits the billing detail data D to the host system without passing through the management office 3.

The central system 4 is a system owned by each road operator and corresponds to a higher-level system for the communication point 2 and the management office 3. The central system 4 receives the billing statement data D from a plurality of communication points 2 and a plurality of management offices 3 belonging to the entire business area (eg, one or more “prefectures”) under the control of each road operator. Calculate the total.
As shown in FIG. 1, the central system 4 includes a station system 40 and a computing system 41.

The station system 40 receives and stores the charging detail data D from the communication point 2 and the management office 3 belonging to the business area. Further, the station system 40 matches the billing detail data D of the same vehicle, and performs a process of determining the final billing amount for each vehicle.
For example, depending on the operation mode of the toll road, 1000 yen may be charged at the entrance toll gate, and 200 yen may be refunded (-200 yen charge) at the exit toll gate. In this case, the station system 40 collates the “vehicle-mounted device ID” and the like included in the billing detail data D with the billing detail data D (billing amount 1000 yen) acquired by the tollgate aggregation device 20 at the entrance tollgate. The billing detail data D (billing amount-200 yen) acquired by the tollgate aggregation device 20 at the exit tollgate is matched. Then, the station system 40 creates new billing detail data D indicating the final billing amount of 800 yen.

The calculation system 41 processes the billing detail data D accumulated and generated by the station system 40 according to the circumstances of the road operator. For example, when it is desired to reflect an exceptional billing process for a system failure or the like or a special discount service for a limited period in the billing amount, the road operator appropriately bills the billing detail data D through the calculation system 41. To process.

The common system 5 corresponds to a host system for the communication point 2, the management office 3, and the central system 4, and in particular, billing details from a plurality of road operators (a plurality of central systems 4 provided for a plurality of business areas). Data D is received and aggregated. The common system 5 refers to the received billing detail data D and immediately creates a Web page that reflects the information (travel route, billing amount, etc.) included in the billing detail data D. Thereby, the user can confirm the usage history of the toll road, that is, the travel route, the charge amount, etc. in real time by accessing the Web page through his/her own terminal device or the like.

The log collection device 6 is a device independent of the communication point 2, the management office 3, the central system 4, etc., and accesses a plurality of toll gate servers 21 installed at each of the plurality of communication points 2 to obtain the charge. Information relating to the travel route is extracted and collected from the billing detail data D accumulated in the location server 21. The travel route information collected by the log collection device 6 is used for detecting illegally traveling vehicles, collecting statistical data of the road traffic network, and the like.

(Functional configuration of tollgate aggregation device)
FIG. 2 is a diagram showing a functional configuration of the tollgate aggregation device according to the first embodiment.
As shown in FIG. 2, the tollgate aggregation device 20 includes a CPU 200, a display unit 210, an operation unit 211, an external connection interface 212, and a recording medium 213.

The CPU 200 is a processor that controls the entire processing of the tollgate collection device 20. The CPU 200 operates as a billing detail data acquisition unit 201, a billing detail data transmission unit 202, and a format conversion unit 203, which will be described later, by operating according to a dedicated program recorded in advance.

The display unit 210 is a user interface for visually presenting to the operator of the tollgate aggregation device 20 various screens required for confirmation of the billing detail data D (FIG. 1), for example, a liquid crystal display. For example, a display monitor.
The operation unit 211 is a user interface that receives an operation required by an operator, and is, for example, a mouse, a keyboard, a touch sensor, or the like.
The external connection interface 212 is a communication interface capable of transmitting/receiving information to/from a host system or the like through a communication line such as a LAN or the Internet.
The recording medium 213 is, for example, a large capacity hard disk drive or the like. A transmission necessity table T (described later) is recorded on the recording medium 213.

Next, various functions of the CPU 200 will be described.
The billing detail data acquisition unit 201 obtains the billing detail data D indicating the travel route and the billing amount of each vehicle traveling in the lane through the plurality of lane servers 22 installed for each of the plurality of lanes belonging to the communication point 2.

The billing statement data transmission unit 202 transmits the billing statement data D acquired through the billing statement data acquisition unit 201 to a central system 4 provided in a business area including a plurality of communication points 2 (toll gates, junctions). To do.
The billing statement data transmission unit 202 also has a function as a transmission determination unit 202a. The transmission determination unit 202a refers to the transmission necessity table T that defines the necessity of transmission of the billing detail data D to the central system 4 for each lane server 22, and refers to the billing detail data acquired through the plurality of lane servers 22. It is determined whether or not D is transmitted to the central system 4.

The format conversion unit 203 converts each of the billing statement data D acquired through the plurality of lane servers 22 into a data format that can be processed by each of the central system 4 and the common system 5.

(Example of transmission necessity table)
FIG. 3 is a diagram illustrating a transmission necessity table according to the first embodiment.
The transmission necessity table T is recorded on the recording medium 213 (FIG. 2) of the tollgate totaling device 20.
Whether each acquired billing statement data D is transmitted to the host system by the lane number (lane number) in which the lane server 22 that created the billing statement data D is installed in the transmission necessity table T. The rule of whether or not is recorded.
Further, in the transmission necessity table T, rules for whether or not to transmit to the higher-level system are set individually for each of the “day confirmed data” and the “unconfirmed data” in the billing detail data D. ..

Here, the "day confirmation data" is the billing detail data D accumulated in the toll booth server 21 during a certain predetermined time unit (for example, one day unit or the working hours unit of the collection staff), It is the billing detail data D that the tollgate totaling device 20 collectively transmits to the host system at intervals of the predetermined time unit.
The “date confirmation data” is particularly required in the matching process in the central system 4 which is a host system of the tollgate collection device 20. Therefore, the "date confirmation data" is converted by the tollgate aggregation device 20 into a data format that can be processed by the central system 4 and then transmitted (the data format of the "day confirmation data" will be described later).

On the other hand, the “unconfirmed data” is the billing detail data D transmitted from the tollgate aggregation device 20 to the higher-level system immediately after the lane server 22 creates the billing detail data D.
Here, when the lane server 22 wirelessly communicates with a vehicle traveling in the lane and creates the billing detail data D, the content shown in the created billing detail data D is a preliminary value for the user. It should be ready for web browsing immediately. Therefore, the billing detail data D created by the lane server 22 is immediately transmitted from the tollgate aggregation device 20 to the common system 5 as "undetermined data". Therefore, the “undetermined data” is converted by the tollgate aggregation device 20 into a data format that can be processed by the common system 5 and then transmitted (the data format of the “undetermined data” will be described later).

For example, in the transmission necessity table T shown in FIG. 3, “unnecessary data” and “day fixed data” are both recorded as “necessary” for “lane No. 01”.
In this case, the transmission determination unit 202a refers to the transmission necessity table T, and first directs the billing detail data D created by the lane server 22 installed in “lane No. 01” to the common system 5. Determine to send.
Then, the billing statement data transmitting unit 202 sets the billing statement data D created by the lane server 22 installed in “lane No. 01” as “unconfirmed data” to be transmitted immediately after the creation, in the common system 5. To send to. Then, at the time of the transmission, the format conversion unit 203 performs processing of converting the billing detail data D created by the lane server 22 into a data format for the common system 5.
Furthermore, the transmission determination unit 202a refers to the transmission necessity table T and determines that the billing statement data D created by the lane server 22 installed in "lane No. 01" is transmitted to the central system 4. To do.
Then, the billing statement data transmission unit 202 centrally sets the billing statement data D created by the lane server 22 installed in "lane No. 01" as "day confirmation data" that is collectively transmitted in a certain predetermined time unit. Send to system 4. Then, at the time of the transmission, the format conversion unit 203 performs a process of converting the billing detail data D created by the lane server 22 into a data format for the central system 4.

Further, for example, in the transmission necessity table T shown in FIG. 3, “undetermined data” is recorded as “not” and “day confirmed data” is recorded as “necessary” for “lane No. 05”.
In this case, the transmission determination unit 202a refers to the transmission necessity table T, and first directs the billing detail data D created by the lane server 22 installed in “lane No. 01” to the common system 5. Determine to send.
Then, the billing statement data transmitting unit 202 sets the billing statement data D created by the lane server 22 installed in “lane No. 01” as “unconfirmed data” to be transmitted immediately after the creation, in the common system 5. To send to.
On the other hand, the transmission determination unit 202a refers to the transmission necessity table T and must transmit the billing detail data D created by the lane server 22 installed in “lane No. 05” to the central system 4. judge. In this case, the billing statement data transmission unit 202 does not transmit the billing statement data D created by the lane server 22 installed in “lane No. 05” to the central system 4.

(Example of billing detail data)
4 and 5 are a first diagram and a second diagram, respectively, showing the billing detail data according to the first embodiment.
Specifically, FIGS. 4 and 5 show the data structure of the billing detail data D at the stage of being created by the lane server 22.
As shown in FIGS. 4 and 5, the billing detail data D created by the lane server 22 includes route information such as “entrance (interchange) number” and “pre-discount toll” for vehicles traveling in the lane. Etc. is included in the charge amount information indicating the charge amount. Further, it also includes time information indicating the time when each tollgate has passed, “vehicle-mounted device ID”, “vehicle-mounted device vehicle number”, etc. for identifying the traveling vehicle (these are not shown).

The route acquisition billing data D1 shown in FIG. 4 is billing detail data D created by the lane server 22A (lane server 22 installed in the lane for route acquisition and billing) in FIG.
Further, the route acquisition data D2 shown in FIG. 5 is the billing detail data D created by the lane server 22B of FIG. 1 (the lane server 22 installed in the lane for which only route acquisition is performed).
As shown in FIGS. 4 and 5, the route acquisition billing data D1 and the route acquisition data D2 created by each of the lane servers 22A and 22B have the same items.

In the charge amount (“pre-discount toll”) of the route acquisition charge data D1 shown in FIG. 4, the charge amount for the vehicle traveling in the lane, which is defined according to the travel route and the vehicle type category, is recorded. Therefore, the route acquisition billing data D1 is required for the matching process of the billing detail data D in the central system 4 or the utilization history Web page creation process through the common system 5. Therefore, normally, in the transmission necessity table T, it is necessary to transmit to the central system 4 and the common system 5 for a lane for which route acquisition and billing are required (both “day confirmed data” and “unconfirmed data” are “ "Required") is defined.
On the other hand, “zero” (not charged) is recorded in the charge amount (“pre-discount toll”) of the route acquisition data D2 shown in FIG. Since the route acquisition data D2 is not used for the matching process in the central system 4 or the process of creating a web page of the usage history through the common system 5, it does not need to be transmitted to each host system. Therefore, normally, in the transmission necessity table T, it is not necessary to transmit to the central system 4 and the common system 5 for lanes that only acquire routes (“day confirmed data” and “unconfirmed data” are both “ No”) is defined.
However, depending on the operation form of the road operator, it is desired that the billing detail data D generated in the lane of a certain communication point 2 be used only in either the central system 4 or the common system 5. Cases are also envisioned. Therefore, in the transmission necessity table T, the necessity can be set individually for each of the "day confirmed data" transmission to the central system 4 and the "unconfirmed data" transmission to the common system 5. Has been done.

(Function of the format converter)
6 and 7 are a first diagram and a second diagram, respectively, for explaining the function of the format conversion unit according to the first embodiment.

FIG. 6 shows the billing detail data D (unconfirmed data Dt1) converted into a data format that can be processed by the common system 5.
The format conversion unit 203 (FIG. 2) can process in the common system 5 by referring to the billing detail data D (FIGS. 4 and 5) acquired through the lane server 22 that needs to be transmitted to the common system 5. A process of creating the undefined data Dt1 having the data format is performed.
Here, as shown in FIG. 6, the data format that can be processed by the common system 5 is, for example, “entry number”, “traffic amount” indicating a billing amount, and the like, billing details created by the lane server 22. Items common to the items recorded in the data D (FIGS. 4 and 5) are included. The format conversion unit 203 determines, among the items constituting the billing detail data D (FIGS. 4 and 5) created by the lane server 22, items common to the items included in the data format that can be processed by the common system 5. Use the value as is.
Further, among the data formats that can be processed by the common system 5, for items that are not included in the billing detail data D created by the lane server 22, fixed values (dummy) defined in advance are adopted.
In this way, the format conversion unit 203 converts the billing statement data D created by the lane server 22 into a data format that can be processed by the common system 5.
The billing statement data transmission unit 202 transmits the billing statement data D (undetermined data Dt1) converted into a data format that the common system 5 can process to the common system 5 immediately after acquisition.

FIG. 7 shows date fixed data Dt2 having a data format that can be processed by the central system 4.
The format conversion unit 203 (FIG. 2) can be processed by the central system 4 by referring to the billing detail data D (FIGS. 4 and 5) acquired through the lane server 22 that needs to be transmitted to the central system 4. A process of creating the day fixed data Dt2 having a data format is performed.
Here, as shown in FIG. 7, the data format that can be processed by the central system 4 also includes items common to the items recorded in the billing detail data D (FIGS. 4 and 5) created by the lane server 22. Be done. The format conversion unit 203 includes items common to the items included in the data format that can be processed by the central system 4 among the items that form the billing detail data D (FIGS. 4 and 5) created by the lane server 22. Use the value as is.
Further, among the data formats that can be processed by the central system 4, for items and the like that are not included in the billing detail data D created by the lane server 22, fixed values defined in advance are adopted.
In this way, the format conversion unit 203 converts the billing statement data D created by the lane server 22 into a data format that can be processed by the central system 4.
The billing statement data transmission unit 202 transmits the billing statement data D (day confirmation data Dt2) converted into a data format that can be processed by the central system 4 to the central system 4 in predetermined time units.

(Effect)
FIG. 8 is a diagram showing an overall configuration of a detail summarization system relating to the proportional relationship.
Hereinafter, the operation and effect of the detail collecting system 1 according to the first embodiment will be described in comparison with the detail collecting system 9 shown in FIG. 8.

Similar to the detail collecting system 1 (FIG. 1) according to the first embodiment, the detail collecting system 9 illustrated in FIG. 8 includes a communication point 2, a management office 3, a central system 4, and a common system 5, And a log collecting device 6.
As a communication point 2, the detail collection system 9 relating to the proportionality includes a tollgate 2B having only a lane server 22A for route acquisition and billing, and a junction 2C having only a lane server 22B for route acquisition. There is.
The tollgate aggregation device 20a installed in each of the tollgate 2B and the junction 2C sequentially transmits the billing detail data D accumulated in the tollgate server 21 through the lane server 22 to the management office 3.

Here, the management office 3 of the detail collection system 9 relating to the proportional relationship includes a management office collection device 30 and an FF processing device 31.

The management office totalizing device 30 receives the billing detail data D from a plurality of communication points 2 (toll gate 2B, junction 2C) belonging to the management area managed by the management office 3, of which the higher system (central system 4 and Only the billing detail data D required for tabulation by the common system 5) is transmitted to the host system.

Specifically, the management office totaling device 30 determines whether or not it is necessary to transmit the received billing statement data D to the higher-level system, depending on the communication point 2 (tollgate totaling device 20).
For example, as described above, the toll booth 2B related to the present proportionality is configured only with the lane server 22A that performs route acquisition and billing. Then, all the charging detail data D received from the toll booth 2B by the management office totalizing device 30 are recorded with the charging amount for the vehicle. Therefore, when the received billing detail data D is transmitted from the tollgate 2B, the management office tallying device 30 transmits the received billing detail data D to the host system.
In addition, as described above, the junction 2C related to the present proportionality is configured only by the lane server 22B that only acquires the route. Then, all the billing detail data D received from the junction 2C by the management office totalizing device 30 will have "zero" recorded in the billing amount. Therefore, when the received billing detail data D is transmitted from the junction 2C, the management office tallying device 30 does not transmit the received billing detail data D to the upper system.

In this way, in the detail aggregation system 9 related to the proportional relation, the billing detail data D acquired at the communication point 2 (toll gate 2B, junction 2C) is selected by the management office 3 and transmitted to the host system. To be done. Then, the management office 3 determines whether or not the transmission to the host system is required based on the communication point 2.

In this way, in order to determine whether or not the billing detail data D should be transmitted to the host system and to realize the function of transmitting only the required billing data D to the host system, the management office 3 (management office Since the relay by the collection device 30) is indispensable, the hierarchical structure of the communication network becomes complicated.
In addition, in this case, each communication point 2 creates a lane (charge lane for charging) in which the billing detail data D that needs to be transmitted to the host system or the billing detail data D that does not need to be sent to the host system. There is a need to be configured with only one of the lanes (the lanes that do not charge) that are used. Then, for example, it is not possible to set a tollgate where lanes that do not charge and lanes that charge are mixed, and it is possible to select a flexible operation mode according to the geographical and structural characteristics of the tollgate or the junction. Can be limited.

On the other hand, as described above, the tollgate aggregation device 20 according to the first embodiment uses the plurality of lane servers 22 installed for each of the plurality of lanes belonging to the communication point 2 to set the travel route of each vehicle traveling in the lane and A billing detail data acquisition unit 201 that obtains billing detail data D indicating a billing amount, and a higher-level system (central system 4, common system) in which the obtained billing detail data D is provided for each business area including a plurality of communication points 2. 5) The billing statement data transmission unit 202 for sending to 5). Then, the billing detail data transmitting unit 202 (transmission determining unit 202a) refers to the transmission necessity table T that defines the necessity of transmitting the billing detail data D to the host system for each lane server, and obtains the acquired billing. It is determined whether the detailed data D is transmitted to the host system.
By doing so, the tollgate aggregation device 20 determines whether or not to transmit each of the billing statement data D acquired through each lane server 22 belonging to the communication point 2 to the higher-level system. Therefore, it is not necessary to go through the management office 3.
Therefore, it becomes possible to directly transmit the billing detail data D from the tollgate totaling device 20 to the higher-level system, and to simplify the hierarchical structure of the communication network.

In addition, by doing so, the tollgate aggregation device 20 determines whether or not to transmit the billing detail data D acquired for each of a plurality of lanes (lane server 22) belonging to the communication point 2 according to the lane. You can judge. Then, for example, as shown in FIG. 1, it is possible to mix lanes not charged and lanes charged at one communication point 2, which is suitable for the geographical and structural characteristics of the tollgate or junction. As described above, the operation mode can be flexibly selected.

Further, the tollgate aggregation device 20 according to the first embodiment converts each of the billing detail data D acquired through the plurality of lane servers 22 into a data format that can be processed by each of the central system 4 and the common system 5. A format conversion unit 203 for converting is further provided.
Here, the billing detail data D created by the lane server 22 may adopt a unique data format (for example, FIGS. 4 and 5) at the communication point 2 to which the lane server 22 belongs. Therefore, if the billing detail data D created by the lane server 22 is directly transmitted to the higher level system, the higher level system may not be able to interpret the received billing detail data D.
Therefore, by adopting the above-mentioned aspect, even when the billing detail data D is different from the data format defined by the higher-level system of the transmission destination, the higher-level system does not charge the received billing detail data D. Can be processed.

In addition to the central system 4, the tollgate aggregation device 20 according to the first embodiment is directed to the common system 5 that aggregates the billing detail data D from the central systems 4 provided for the business areas. And the billing detail data D is transmitted.
By doing so, since the billing detail data D is directly transmitted from the tollgate aggregation device 20 to the common system 5 which is located further above the central system 4, the billing performed by the common system 5 is performed. The processing (for example, the Web page creation processing) on the detailed data D is quickly performed.

As described above, according to the tollgate aggregation device 20 according to the first embodiment, it is possible to simplify the structure of the communication network and flexibly select the operation mode of each lane.

(Modification of the first embodiment)
Although the tollgate aggregation device 20 according to the first embodiment has been described above in detail, the specific aspect of the tollgate aggregation device 20 according to the first embodiment is not limited to the above. It is possible to add various design changes and the like without departing from the scope of the invention.

For example, the transmission necessity table T (FIG. 3) according to the first embodiment may be appropriately editable by the operation of the operator of the tollgate aggregation device 20. Specifically, the CPU 200 has a function of changing the necessity of transmission for each “lane number” according to the table editing operation of the operator through the operation unit 211.
By doing this, for example, when there is a change in the operation mode of the lane (when changing from a lane that has been charged to a lane that is not charged), it is possible to determine whether or not transmission to the host system is necessary. , Can be changed flexibly.

Further, the format conversion processing performed by the format conversion unit 203 is not limited to the above-described aspect, and may be appropriately changed depending on the function of the higher level system.
For example, in the first embodiment, the billing amount included in the billing detail data D created by the lane server 22 that performs route acquisition and billing is directly adopted as the unconfirmed data Dt1 after the format conversion. However, it is not limited to this aspect in other embodiments.
For example, when the common system 5 has a function of independently calculating the charging amount from the entrance information, the exit information and the like indicated in the received billing detail data D (unconfirmed data Dt1), the received unconfirmed It is not necessary that the charge amount is recorded in the data Dt1. Therefore, in this case, the format conversion unit 203 does not have to directly adopt the charging amount shown in the charging detail data D created by the lane server 22 as the unconfirmed data Dt1 after the format conversion (for example, to “0”). It may be fixed, etc.).

Moreover, in each of the above-described embodiments, a program for realizing various functions of the tollgate totaling device 20 is recorded in a computer-readable recording medium, and the program recorded in the recording medium is read by the computer system. By executing the above, various processes are performed. Here, the various processes of the tollgate totaling device 20 described above are stored in a computer-readable recording medium in the form of a program, and the various processes are performed by the computer reading and executing the program. .. The computer-readable recording medium refers to a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Further, the computer program may be distributed to the computer via a communication line, and the computer that receives the distribution may execute the program.
Further, the tollgate aggregation device 20 is not limited to a mode in which various functional configurations are housed in a single device housing, and various functional configurations of the tollgate aggregation device 20 are spread over a plurality of devices connected by a network. It may be an aspect provided with.

Although some embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope of the invention and the scope of the invention, and are also included in the scope of the invention described in the claims and the scope of equivalents thereof.

1, 9 Detail collection system 2 Communication points 20, 20a Tollgate collection device (communication point information processing device)
200 CPU
201 billing detail data acquisition unit 202 billing detail data transmission unit 202a transmission determination unit 203 format conversion unit 210 display unit 211 operation unit 212 external connection interface 213 recording medium 21 tollgate server 22 lane server 3 management office 30 management office tallying device 31 FF processing device 4 Central system 40 Station system 41 Calculation system 5 Common system 6 Log collection device D Billing detail data T Transmission necessity table

Claims (6)

A communication point information processing device installed at each communication point on a toll road,
A billing detail data acquisition unit that obtains billing detail data indicating a travel route and a billing amount of each vehicle traveling in the lane, through a plurality of lane servers installed for each of a plurality of lanes belonging to the communication point,
A billing statement data transmission unit for transmitting the obtained billing statement data to a central system provided for each predetermined business area including a plurality of communication points;
Equipped with
The billing detail data transmission unit refers to a transmission necessity table that defines the necessity of transmitting the billing detail data to the central system for each lane server, and refers to the obtained billing detail data by the central system. A communication point information processing device that determines whether or not to transmit to a communication point. The communication point information processing device according to claim 1, further comprising a format conversion unit that converts each of the billing statement data acquired through the plurality of lane servers into a data format that can be processed by the central system. The billing statement data transmission unit,
The communication point information processing according to claim 1 or 2, further comprising: transmitting the billing detail data to a common system that aggregates the billing detail data from the plurality of central systems provided for each of the plurality of business areas. apparatus. A communication point information processing device according to any one of claims 1 to 3,
A plurality of the lane servers,
The central system,
A detailed tabulation system including. A communication point information processing method at each communication point of a toll road by a communication point information processing device ,
A billing statement data acquisition unit of the communication point information processing device, through a plurality of lane servers installed for each of a plurality of lanes belonging to the communication point, billing statement data indicating a traveling route and a billing amount of each vehicle traveling in the lane. A billing detail data acquisition step of acquiring
A billing statement data transmitting step in which the billing statement data transmitting unit of the communication point information processing device transmits the obtained billing statement data to a central system provided for each predetermined business area including the plurality of communication points. When,
Have
The billing statement data transmitting unit is acquired in the billing statement data transmitting step by referring to a transmission necessity table that defines the necessity of transmitting the billing statement data to the central system for each lane server. A communication point information processing method for determining whether or not to transmit the billing detail data to the central system. The computer of the communication point information processing device installed at each communication point of the toll road,
A billing detail data acquisition unit that obtains billing detail data indicating a traveling route and a billing amount of each vehicle traveling in the lane, through a plurality of lane servers installed for each of the lanes belonging to the communication point.
Billing statement data transmitting means for transmitting the obtained billing statement data to a central system provided for each predetermined business area including a plurality of communication points.
Function as
The billing statement data transmitting means refers to a transmission necessity table that defines the necessity of transmitting the billing statement data to the central system for each lane server, and acquires the obtained billing statement data from the central system. A program that determines whether or not to send to.