JP7631098B2 - Toll collection system, toll collection method, toll collection program - Google Patents

Description

Embodiments of the present invention relate to an information processing system, an information processing method, and an information processing program.

Each expressway company that manages the operation of toll roads is an independent business. However, for the convenience of the drivers, the expressway companies are not completely independent. In other words, each expressway company has built a system so that drivers can drive on toll roads managed by different expressway companies without being aware of this, and they do not have to pay tolls to each company separately. Specifically, each expressway company shares a single basic toll table, and the toll, which is determined at the toll gate where the vehicle enters and exits, is distributed to each company at a specific rate. Here, the method of sharing the same information is generally to use database synchronization.

The ETC (Electronic Toll Collection) (registered trademark) system, which is widely used on toll roads, enables non-stop toll collection without having to stop the vehicle at the toll gate by wirelessly communicating between the onboard unit of the vehicle traveling in the lane of the toll gate and the roadside equipment installed at the toll gate.

JP 2020-107111 A

Synchronizing databases requires each expressway company to have the same information (the same toll table), which creates the problem of increasing the amount of data held and used for communication when viewed as a whole system.

In addition, national policy needs currently require flexible and rapid changes to tolls. However, the current system cannot meet this need. Therefore, each expressway company must quickly share its own toll change measures with other expressway companies, and quickly apply the changes all the way to the toll gates at the end of the line, thereby building a system that allows for flexible and rapid changes to tolls.

The object of the present invention is to provide an information processing system, an information processing method, and an information processing program that can reduce the amount of data held by the entire system and communication charges, and can change tolls quickly and flexibly.

In an embodiment, an information processing system includes a centralized collaboration server, a first fare table management server connected to the centralized collaboration server, and a server connected to the centralized collaboration server. The centralized collaboration server includes a first communication unit that receives a query from the server and transmits the query to the first fare table management server. The first fare table management server includes a memory unit that stores an extended fare table in which a toll can be calculated from a driving route traveled by a vehicle on a toll road and in which a fare adjustment is set for a predetermined section, a second processor that acquires a partial extended fare table from the extended fare table related to a toll gate under the jurisdiction of the server based on the query, and a second communication unit that transmits the partial extended fare table to the centralized collaboration server. The first communication unit transmits the partial extended fare table to the server.

FIG. 1A is a diagram showing an example of a schematic configuration of an information processing system according to the first embodiment. FIG. 1b is a diagram showing an example of a schematic configuration of an information processing system according to the first embodiment. FIG. 2 is a block diagram showing an example of a central collaboration server that constitutes the information processing system according to the first embodiment. FIG. 3 is a block diagram illustrating an example of a first fee table management server according to the first embodiment. FIG. 4 is a block diagram illustrating an example of a first global management server according to the first embodiment. FIG. 5 is a block diagram illustrating an example of a first area management server according to the first embodiment. FIG. 6 is a block diagram illustrating an example of the first toll gate server according to the first embodiment. FIG. 7 is a block diagram showing an example of a schematic configuration of the first management IF device according to the first embodiment. FIG. 8 is a block diagram illustrating an example of the first lane server according to the first embodiment. FIG. 9 is a block diagram showing an example of a schematic configuration of the first roadside device according to the first embodiment. FIG. 10 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers according to the first embodiment. FIG. 11 is a diagram showing an example of creating a local area extended fee table from the extended fee table. FIG. 12 is a diagram showing an example of creating a tollgate extended fee table corresponding to each tollgate server from the local area extended fee table. FIG. 13 is a diagram showing an example of creating a tollgate extended fee table corresponding to each tollgate server from the local area extended fee table. FIG. 14 is a sequence diagram showing an example of a process for sharing the extended fee table application conditions among the wide area management servers according to the first embodiment. FIG. 15 is a sequence diagram showing an example of a process for sharing the extended fee table application conditions among the wide area management servers according to the first embodiment. FIG. 16 is a sequence diagram showing an example of a process for sharing an extended fee table among each lane server according to the second embodiment. FIG. 17 is a sequence diagram showing an example of a process for sharing an extended fee table among each lane server according to the second embodiment. FIG. 18 is a sequence diagram illustrating an example of an occasional process according to the fourth embodiment. FIG. 19 is a sequence diagram illustrating an example of an occasional process according to the fifth embodiment.

The information processing system, information processing device, and information processing program will be described in detail below with reference to the drawings. Note that in the following embodiments, parts with the same numbers perform similar operations, and will not be described repeatedly.

[First embodiment]
(composition)
1a and 1b are diagrams showing an example of a schematic configuration of an information processing system according to the first embodiment.
As shown in Fig. 1a, the information processing system according to the first embodiment includes a centralized cooperation server 1, a first expressway company 2, a second expressway company 3, a third expressway company 4, and a vehicle 5. In the example of Fig. 1a, three expressway companies are shown, but there may be four or more expressway companies, or there may be only one or two expressway companies. In other words, there may be any number of expressway companies.

The integrated cooperation server 1 is connected to the first expressway company 2, the second expressway company 3, and the third expressway company 4. The integrated cooperation server 1 relays various information to be exchanged between the first expressway company 2, the second expressway company 3, and the third expressway company.

The first expressway company 2 includes a first toll table management server 20, a first wide area management server 21, a first regional management server 22, a first toll gate server 23, a first management interface (IF) device 24, a first lane server 25, a first roadside device 26, and a first traffic control central office 28. Similarly, the second expressway company 3 includes a second toll table management server 30, a second wide area management server 31, a second regional management server 32, a second toll gate server 33, a second management IF device 34, a second lane server 35, a second roadside device 36, and a second traffic control central office 38. Furthermore, the third expressway company 4 includes a third toll table management server 40, a third wide area management server 41, a third regional management server 42, a third toll gate server 43, a third management IF device 44, a third lane server 45, a third roadside device 46, and a third traffic control central office 48.

Here, the first toll gate server 23, the first management IF device 24, the first lane server 25, and the first roadside equipment 26 are arranged in the first toll gate 29. Similarly, the second toll gate server 33, the second management IF device 34, the second lane server 35, and the second roadside equipment 36 are arranged in the second toll gate 39, and the third toll gate server 43, the third management IF device 44, the third lane server 45, and the third roadside equipment 46 are arranged in the third toll gate 49. Here, the first toll gate 29, the second toll gate 39, and the third toll gate 49 include not only entrance toll gates and exit toll gates, but also cases where route free flow or area border free flow is used.

The first fee table management server 20 is connected to the first wide area management server 21. The first fee table management server 20 exchanges various information between the centralized coordination server 1 and the first wide area management server 21. In addition, the second fee table management server 30 and the third fee table management server 40 have the same configuration as the first fee table management server 20, so their explanations are omitted.

The first wide-area management server 21 is connected to the first regional management server 22 and the first traffic control central office 28. The first wide-area management server 21 exchanges various information with the integrated coordination server 1 and the first regional management server 22. Furthermore, the first wide-area management server 21 receives various information including traffic congestion information from the first traffic control central office 28. Furthermore, the second wide-area management server 31 and the third wide-area management server 41 have the same configuration as the first wide-area management server 21, so their explanations are omitted.

The first regional management server 22 is connected to the first toll gate server 23 and the first management IF device 24. The first regional management server 22 exchanges various information between the first toll gate server 23 and the first management IF device 24. The first regional management server 22 is also connected to the centralized linkage server 1. The first regional management server 22 exchanges various information between the centralized linkage server 1. For simplification, only the first regional management server 22 is shown as the regional management server in FIG. 1a, but there may be multiple regional management servers connected to the first fare table management server 20 and the first wide area management server 21. The second regional management server 32 and the third regional management server 42 have the same configuration as the first regional management server 22, so their explanations are omitted.

The first toll gate server 23 is connected to the first management IF device 24 and the first lane server 25. The first toll gate server 23 exchanges various information between the first management IF device 24 and the first lane server 25. The first toll gate server 23 is also connected to the centralized linkage server 1. The first toll gate server 23 exchanges various information with the centralized linkage server 1. For simplification, in FIG. 1a, only the first regional management server 22 is shown as the regional management server, but the number of toll gate servers connected to the first regional management server 22 (i.e., each regional management server) may be multiple. Furthermore, the number of toll gate servers connected to each regional management server may be different or the same. Furthermore, the second toll gate server 33 and the third toll gate server 43 have the same configuration as the first toll gate server 23, so their explanations are omitted.

The first lane server 25 is connected to the first roadside equipment 26. The first lane server 25 exchanges various information with the first roadside equipment 26. For simplicity, FIG. 1a shows only the first lane server 25 as a lane server, but there may be multiple lane servers connected to the first toll gate server 23 (i.e., each toll gate server). Furthermore, the number of lane servers connected to each toll gate server may be different or the same. The second lane server 35 and the third lane server 45 have the same configuration as the first lane server 25, so their explanations are omitted.

The first roadside equipment 26 is placed at an entrance toll gate, an exit toll gate, a route free flow (FF) installed at a predetermined location on the toll road, or an area boundary FF installed at the boundary of an area divided by a first expressway company. The first roadside equipment 26 detects a vehicle 5 using an ETC toll collection system passing through a toll gate, a route FF, or an area boundary FF, and connects to an on-board device 50 mounted on the vehicle 5. The first roadside equipment 26 exchanges various information with the on-board device 50. For simplicity, only the first toll gate server 23 is shown as the toll gate server in FIG. 1a, but the lane server connected to the first toll gate server 23 (i.e., each toll gate server) may be multiple. Furthermore, the number of toll gate servers connected to each regional management server may be different or the same.

The vehicle 5 is equipped with an on-board unit 50 for using the ETC toll collection system. The on-board unit 50 transmits vehicle information, including an on-board unit identifier (ID), card information of the ETC card inserted in the on-board unit 50, entry or exit information, etc., to the first lane server 25 by communicating with the first lane server 25, and receives various information from the first lane server 25.

Here, the first toll gate server 23 is responsible for multiple lane servers. Therefore, the first toll gate server 23, which is responsible for the first lane server 25, is responsible for more lane servers than the first lane server 25. And the first regional management server 22, which is responsible for the first toll gate server 23, is responsible for more lane servers than the first lane server 25. And the first wide area management server 21 is responsible for more lane servers than the first regional management server 22.

FIG. 1b is a diagram showing an example of a schematic configuration of an information processing system according to the first embodiment.
Fig. 1b shows an example in which there are n first regional management servers 22, whereas Fig. 1a shows only one for simplification, and m first toll gates 29 are connected to each of the first regional management servers 22. As shown in Fig. 1a, the first regional management server 22 and the first toll gate server 23 can be connected to the integrated cooperation server, but are omitted here for simplification. Fig. 1b is merely an example, and the number of first toll gates 29 connected to each first regional management server 22 does not have to be the same, and may of course be different.

As is clear from FIG. 1b, for example, the first toll table management server 20 manages n*m toll gates, and the first regional management server 22a manages m toll gates. The second expressway company 3 and the third expressway company 4 have a similar configuration, but are omitted for simplicity. Also, only one first toll table management server 20 and one first wide area management server 21 are located in the first expressway company 2. A first regional management server 22 is located in each management office of the first expressway company 2, and a first toll gate 29 is located at each toll gate.

FIG. 2 is a block diagram showing an example of the central collaboration server 1 that constitutes the information processing system according to the first embodiment.
The central collaboration server 1 can be configured using a general-purpose computer or the like, and includes a processor 101, a storage unit 102, an interface 103, a display unit 104, and an operation unit 105, etc.

The first processor, processor 101, realizes various processing functions by executing the programs stored in memory unit 102. For example, processor 101 functions as a relay unit that transfers various information to a wide area management server, a fee table management server, etc., by executing the programs stored in memory unit 102.

The storage unit 102 has a program memory that stores programs executed by the processor 101, a working memory that stores working data, and a data memory that stores data files, etc. The storage unit 102 appears to store the basic fee table, extended fee table, extended fee table application conditions, driving history information, etc., using data virtualization technology. However, this information is actually stored in the storage unit of, for example, the first fee table management server 20 or the first wide area management server 21, and when the processor 101 needs this information, it can be used by sending a query to the first fee table management server 20 or the first wide area management server 21 and receiving the data corresponding to the query.

Here, the basic fee table is a fee table for calculating the toll according to the normal driving route of the vehicle 5. Furthermore, the extended fee table is a fee table for calculating the toll of the vehicle 5 when a fee adjustment zone is set. The extended fee table application condition information is information including the application condition indicating the case in which the extended fee table is applied when the extended fee table is set, and the extended fee table number corresponding to the extended fee table at the time of application. Note that the application condition indicates the condition that the vehicle 5 must satisfy, such as what time and what time the toll gate, route FF, and area border FF were passed. Furthermore, the extended fee table number is an identification number for identifying the extended fee table. The driving history information is information indicating the driving route when the vehicle 5 passed the entrance toll gate, route FF, and area border FF. Note that the memory unit 102 may of course actually store various information such as the basic fee table and the extended fee table.

The interface 103 is, for example, a communication interface for connecting to the first fee table management server 20, the first wide area management server 21, the second fee table management server 30, the second wide area management server 31, the third fee table management server 40, and the third wide area management server 41. For example, the interface 103 functions as a communication unit that transmits queries.

The display unit 104 displays the display contents according to the display control from the processor 101, and displays information related to fee table processing. The operation unit 105 is composed of a keyboard and the like. The operation unit 105 accepts information input by an operator and supplies the information to the processor 101.

FIG. 3 is a block diagram showing an example of the first fee table management server 20 according to the first embodiment.
The first fee table management server 20 can be configured by a general-purpose computer or the like, and includes a processor 201, a storage unit 202, an interface 203, a display unit 204, an operation unit 205, and the like.

The processor 201 realizes various processing functions by executing the programs stored in the memory unit 202. For example, the processor 201 functions as a control unit of the first fee table management server 20 by executing the programs stored in the memory unit 202.

The storage unit 202 has a program memory that stores the programs executed by the processor 201, a working memory that stores working data, and a data memory that stores data files, etc. For example, the storage unit 202 can store various information such as a basic fee table and an extended fee table. The extended fee table will be described later.

The interface 203 is a communication interface for connecting to the first wide area management server 21 and the first local management server 22, and functions as a communication unit that transmits various requests, which are queries, to the central coordination server 1 and receives various information from the central coordination server 1.

The display unit 204 displays contents according to display control from the processor 201. The operation unit 205 is composed of a keyboard, etc. The operation unit 205 receives information input by an operator and supplies the information to the processor 201.
The second fee table management server 30 also has a processor 301, a memory unit 302, an interface 303, a display unit 204, and an operation unit 305, etc., and the third fee table management server 40 also has a processor 401, a memory unit 402, an interface 403, a display unit 404, and an operation unit 405, etc., but these are substantially similar to the configuration of the first fee table management server 20, so their explanation is omitted.

FIG. 4 is a block diagram showing an example of the first wide area management server 21 according to the first embodiment.
The first wide area management server 21 can be configured by a general-purpose computer or the like, and includes a processor 211, a storage unit 212, an interface 213, a display unit 214, an operation unit 215, and the like.

The processor 211 realizes various processing functions by executing the programs stored in the memory unit 212. For example, the processor 211 functions as a control unit of the first wide area management server 21 by executing the programs stored in the memory unit 212. For example, the processor 211 can output various requests, which are queries.

The storage unit 212 has a program memory that stores programs executed by the processor 211, a working memory that stores working data, and a data memory that stores data files, etc. For example, the storage unit 212 can store various information such as a basic fee table, extended fee table application condition information, an extended fee table number list, and driving history information. Here, the extended fee table application condition information and the extended fee table number list will be described later.

The interface 213 is a communication interface for connecting to the first fare table management server 20, the first regional management server 22, and the first traffic control central office 28, and functions as a communication unit that transmits various requests, which are queries, to the central cooperation server 1 and receives various information from the central cooperation server 1. The interface 213, which functions as a communication unit, also has the function of receiving various information, such as congestion information, from the first traffic control central office 28.

The display unit 214 displays contents according to display control from the processor 211. The operation unit 215 is composed of a keyboard, etc. The operation unit 215 receives information input by an operator and supplies the information to the processor 211.
The second wide area management server 31 also includes a processor 311, a memory unit 312, an interface 313, a display unit 314, and an operation unit 315, and the third wide area management server 41 also includes a processor 411, a memory unit 412, an interface 413, a display unit 414, and an operation unit 415, etc. However, these are substantially similar to the configuration of the first wide area management server 21, and the description thereof will be omitted.

FIG. 5 is a block diagram showing an example of the first area management server 22 according to the first embodiment.
The first regional management server 22 can be configured by a general-purpose computer or the like, and includes a processor 221, a memory unit 222, an interface 223, a display unit 224, an operation unit 225, and the like.

The processor 221 realizes various processing functions by executing the programs stored in the memory unit 222. For example, the processor 221 functions as a control unit of the first regional management server 22 by executing the programs stored in the memory unit 222. For example, the processor 221 can output various requests, which are queries.

The memory unit 222 has a program memory that stores programs executed by the processor 221, a working memory that stores working data, and a data memory that stores data files, etc. For example, the memory unit 222 can store various information such as a local area basic fee table, a local area extended fee table, local area driving history information that is driving history related to the first area management server 22, and an extended fee table number list. Here, the local area basic fee table is a fee table that is composed of only a basic fee table related to toll gates under the jurisdiction of the first area management server 22, for example. The local area extended fee table will be described later.

The interface 223 is a communication interface for connecting to the centralized coordination server 1, the first management IF device 24, the first tollgate server 23, and the first management IF device 24, and functions as a communication unit that transmits various requests, which are queries, to the centralized coordination server 1 and receives various information from the centralized coordination server 1. The interface 223, which functions as a communication unit, also has the function of receiving various information from the first management IF device 24 and the first lane server 25.

The display unit 224 displays contents according to display control from the processor 221. The operation unit 225 is composed of a keyboard, etc. The operation unit 225 receives information input by an operator and supplies the information to the processor 221.
The second regional management server 32 also includes a processor 321, a storage unit 322, an interface 323, a display unit 324, and an operation unit 325, etc., and the third regional management server 42 also includes a processor 421, a storage unit 422, an interface 423, a display unit 424, and an operation unit 425, etc. However, these are substantially similar in configuration to the first regional management server 22, and therefore description thereof will be omitted.

FIG. 6 is a block diagram showing an example of the first toll gate server 23 according to the first embodiment.
The first tollbooth server 23 can be configured by a general-purpose computer or the like, and includes a processor 231, a memory unit 232, an interface 233, a display unit 234, an operation unit 235, and the like.

The processor 231 realizes various processing functions by executing the programs stored in the memory unit 232. For example, the processor 231 functions as a control unit of the first regional management server 22 by executing the programs stored in the memory unit 232. For example, the processor 221 can output various requests, which are queries.

The storage unit 232 has a program memory that stores programs executed by the processor 231, a working memory that stores working data, and a data memory that stores data files, etc. For example, the storage unit 232 can store various information such as a toll gate basic toll table, a toll gate extended toll table, and toll gate driving history information that is driving history information related to the first toll gate server 23. Here, the toll gate basic toll table is a toll table that is composed only of a basic toll table related to the toll gate under the jurisdiction of the first toll gate server 23, for example. The toll gate extended toll table will be described later.

The interface 233 is a communication interface for connecting to the centralized coordination server 1, the first management IF device 24, and the first lane server 25, and functions as a communication unit that transmits various requests, which are queries, to the centralized coordination server 1 and receives various information from the centralized coordination server 1. The interface 233, which functions as a communication unit, also has the function of receiving various information from the first management IF device 24 and the first lane server 25.

The display unit 234 displays contents according to display control from the processor 231. The operation unit 235 is composed of a keyboard, etc. The operation unit 235 receives information input by an operator and supplies the information to the processor 231.
The second toll gate server 33 also includes a processor 331, a memory unit 332, an interface 333, a display unit 334, an operation unit 335, etc., and the third toll gate server 43 also includes a processor 431, a memory unit 432, an interface 433, a display unit 434, an operation unit 435, etc. However, these are substantially similar to the configuration of the first toll gate server 23, and therefore the description thereof will be omitted.

FIG. 7 is a block diagram showing an example of a schematic configuration of the first management IF device 24 according to the first embodiment.
The first management IF device 24 can be configured by a general-purpose computer or the like, and includes a processor 241, a storage unit 242, an interface 243, a display unit 244, an operation unit 245, and the like.

The processor 241 realizes various processing functions by executing the programs stored in the memory unit 242. For example, the processor 241 functions as a control unit of the first management IF device 24 by executing the programs stored in the memory unit 242.

The memory unit 242 has a program memory that stores the programs executed by the processor 241, a working memory that stores working data, and a data memory that stores data files, etc.

The interface 243 is a communication interface for connecting to the first regional management server 22 and the first toll gate server 23, and functions as a relay unit that transfers various information received from the first regional management server 22 to the first toll gate server 23.

The display unit 244 displays contents according to display control from the processor 241. The operation unit 245 is composed of a keyboard, etc. The operation unit 245 receives information input by an operator and supplies the information to the processor 241.
The second management IF device 34 also includes a processor 341, a storage unit 342, an interface 343, a display unit 344, and an operation unit 345, etc., and the third management IF device 44 also includes a processor 441, a storage unit 442, an interface 443, a display unit 444, and an operation unit 445, etc. However, these are substantially similar in configuration to the management IF device 24, and therefore description thereof will be omitted.

FIG. 8 is a block diagram showing an example of the first lane server 25 according to the first embodiment.
The first lane server 25 can be configured using a general-purpose computer or the like, and includes a processor 251, a memory unit 252, an interface 253, a display unit 254, and an operation unit 255, etc.

The processor 251 realizes various processing functions by executing the programs stored in the memory unit 252. For example, the processor 251 functions as a control unit of the first lane server 25 by executing the programs stored in the memory unit 252.

The memory unit 252 has a program memory that stores the programs executed by the processor 251, a working memory that stores working data, and a data memory that stores data files, etc. For example, the memory unit 252 can store various information such as a lane basic toll table, a lane expansion toll table, and an expansion toll table number list. Here, the lane basic toll table is, for example, a toll table consisting only of a basic toll table related to the toll gate under the jurisdiction of the first lane toll gate. The lane expansion toll table will be described later.

The interface 253 is a communication interface for connecting to the centralized cooperation server 1 and the first roadside equipment 26, and functions as a communication unit that transmits and receives various information to and from the first tollgate server 23. The interface 253, which functions as a communication unit, also has the function of receiving various information from the first roadside equipment 26.

The display unit 254 displays contents according to display control from the processor 251. The operation unit 255 is composed of a keyboard, etc. The operation unit 255 receives information input by an operator and supplies the information to the processor 251.
The second lane server 35 also includes a processor 351, a memory unit 352, an interface 353, a display unit 354, an operation unit 355, etc., and the third lane server 45 also includes a processor 451, a memory unit 452, an interface 453, a display unit 454, an operation unit 455, etc. However, these are substantially similar in configuration to the first lane server 25, and therefore description thereof will be omitted.

FIG. 9 is a block diagram showing an example of a schematic configuration of the first roadside equipment 26 according to the first embodiment.
As shown in FIG. 9, the first roadside equipment 26 includes an interface aggregation unit 261 , a vehicle detector 262 , a camera 263 , an antenna 264 , a roadside display 265 , and a departure controller 266 .

The interface aggregation unit 261 aggregates information from each unit and outputs it to the first lane server 25. The interface aggregation unit 261 also outputs information from the first roadside equipment 26 to each unit. For example, the interface aggregation unit 261 outputs a vehicle detection signal ON or OFF from the vehicle detector 262 etc. to the first lane server 25. The first lane server 25 detects the position (movement) of the vehicle based on the vehicle detection signal ON or OFF from the vehicle detector 262 etc., and controls the operation of the first roadside equipment 26.

The camera 263 captures an image of the vehicle 5 that has entered the first lane server 25. The captured image is sent to the first lane server 25 via the interface aggregation unit 261. Under the control of the processor 251, the first lane server 25 identifies the license plate of the vehicle 5 from the captured image and obtains the vehicle number. The first lane server 25 may also obtain other information related to the vehicle 5, such as the model of the vehicle 5, from the captured image.

The antenna 264 communicates with the vehicle-mounted device 50 of the vehicle 5, receives various information transmitted from the vehicle-mounted device 50, and transmits various information to the vehicle-mounted device 50. For example, the vehicle-mounted device 50 of the vehicle 5 traveling on a toll road on which the first lane server 25 is installed transmits vehicle information including the vehicle-mounted device ID, card number information of the ETC card, entry or exit records, records of passing through route FF and/or area border FF, etc. to the antenna 264 via wireless communication with the antenna 264. Furthermore, the vehicle-mounted device 50 of the vehicle 5 receives the entry or exit records, records of passing through route FF and/or area border FF, and tolls from the antenna 264 via wireless communication with the antenna 264.

The roadside display 265 displays information output from the interface aggregation unit 261 to the driver of the vehicle 5. For example, the roadside display 265 displays the toll calculated by the first lane server 25. The departure controller 266 controls the opening and closing of a departure control bar based on the departure control information (permission to pass or temporary stop) from the interface aggregation unit 261. Note that the roadside display 265 and the departure controller 266 can be omitted when the first roadside device 26 is installed on the route FF or the area boundary FF.
The second roadside device 36 also includes an interface aggregation unit 361, a vehicle detector 362, a camera 363, an antenna 364, a roadside display 365, and a departure controller 366, and the third roadside device 46 also includes an interface aggregation unit 461, a vehicle detector 462, a camera 463, an antenna 464, a roadside display 465, and a departure controller 466. However, these are substantially similar in configuration to the first lane server 25, and therefore description thereof will be omitted.

[Preparation process]
Next, the advance preparation process according to the first embodiment will be described. When congestion occurs on a toll road or the like, and it becomes necessary to adjust the toll, the extended toll table, which is the adjusted toll table, must be shared by the lane servers of each expressway company. This is because if the lane server does not have the extended toll table, the extended toll table cannot be applied when a vehicle 5 passes through. In addition, extended toll table application condition information, including the extended toll table application conditions, must be shared by the wide area management server or the local management server of each expressway company.

(Sharing of extended fee tables)
First, the operation for sharing the extended fare table among the lane servers will be described.
FIG. 10 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers according to the first embodiment.
In the first embodiment, each regional management server that receives a change notification transmits a query (a table request) to the central cooperation server 1 to obtain the extended fee table.

First, assume that a traffic jam occurs on a toll road under the jurisdiction of the first expressway company 2.

The processor 211 of the first wide-area management server 21 receives traffic congestion information indicating that congestion has occurred on a specific toll road from the first traffic control central office 28 (step ST101). The first traffic control central office 28 observes the condition of the toll road using cameras, etc., and immediately transmits traffic congestion information to the first wide-area management server 21 when traffic congestion occurs. The traffic congestion information includes information such as how many kilometers the congestion is from the point where the congestion has occurred and the current date and time.

The processor 211 creates extended fare table application condition information (step ST102). The processor 211 receives traffic congestion information through the interface 213, which is a communication unit. In the first embodiment, the processor 211 determines whether the traffic congestion information matches the extended fare table operation conditions stored in the memory unit 212. Here, the extended fare table operation conditions are conditions for starting to create an extended fare table, such as a certain number of kilometers of congestion on a specific toll road, a specific date and time, etc. This extended fare table operation condition may be stored in the memory unit 212 of the first wide area management server 21.

When it is determined that the traffic congestion information matches the extended fare table operating conditions, the processor 211 determines the extended fare table application conditions so that a discount (extended fare) can be received when the vehicle 5 detours around a congested area, or a surcharge (extended fare) is charged when the vehicle proceeds through a congested area. The extended fare table application conditions include the start time and end time when the extended fare table becomes effective, the route pattern to be applied, the vehicle type, the presence or absence of a discount for disabled people, etc. The processor 211 creates an extended fare table number (identifier) that corresponds to the extended fare table when these tolls are changed. The processor 211 then creates extended fare table application condition information that includes the extended fare table application conditions and the extended fare table number.

In addition, if the traffic congestion information does not meet the conditions for applying the extended fare table, the first lane server 25 continues to use the basic fare table, which is the normal fare table, until traffic congestion information is transmitted again from the first traffic control central station 28.

The processor 211 may display the traffic congestion information to the administrator who manages the first wide area management server 21 via the display unit 214, and the administrator may determine whether the traffic congestion information complies with the operational regulations. If it does, the administrator inputs an instruction to the first wide area management server 21 to create extended fee application conditions. Then, the processor 211 may create extended fee application condition information according to the input.

The processor 211 can also display, via the display unit 214, that the traffic congestion information matches the extended fare table operating conditions, display a group of candidate extended fare table application conditions that can be applied based on the traffic congestion information, or display to the administrator operating regulations that the administrator can apply. Semi-automatic operation is also possible, in which the administrator selects an appropriate option from the presented information.

The processor 211 transmits variable fee setting information, including instructions to create an extended fee table, to the first fee table management server 20 (step ST103). If it is determined that the traffic congestion information matches the extended fee table operation conditions, the processor 211 transmits the variable fee setting information to the first fee table management server 20 via the interface 213. Here, the variable fee setting information includes instructions on how to process the basic fee table, i.e., which sections the extended fee applies to, etc.

The processor 201 of the first fee table management server 20 creates an extended fee table (step ST104). The processor 201 receives variable fee setting information through the interface 203. The processor 201 creates an extended fee table to which changes from the basic fee table have been applied in accordance with instructions included in the variable fee setting information, and stores the created extended fee table in the memory unit 202.

The processor 201 transmits a change notification to the centralized cooperation server 1 and the first regional management server 22 (step ST105). In order to collect tolls using the extended toll table, the extended toll table must be stored in each lane server under the jurisdiction of the first expressway company 2, the second expressway company 3, and the third expressway company 4. Therefore, the processor 201 transmits a change notification indicating that a new extended toll table has been created to the first regional management server 22 and the centralized cooperation server 1 via the interface 203 in order to distribute the extended toll table to each toll gate server.

The processor 101 of the integrated cooperation server 1 transfers the received change notification to the second toll table management server 30 of the second expressway company 3 (step ST106). The processor 101 receives the change notification through the interface 103. The processor 101 then transmits the change notification to the second toll table management server 30 through the interface 213. Note that in FIG. 10, for the sake of simplicity, the change notification is transmitted to the second toll table management server 30 of the second expressway company 3, but the change notification is also transmitted to the third toll table management server 40 of the third expressway company 4. In addition, the processing of the third expressway company 4 after receiving the change notification is similar to the processing of the second expressway company 3, so the explanation here is omitted. Note that if there are expressway companies other than the third expressway company 4, it goes without saying that the processing of those expressway companies is similar to the processing of the second expressway company 3.

The processor 301 of the second fare table management server 30 transmits a change notification to the second regional management server 32 (step ST107). The processor 301 transmits the change notification to the second regional management server 32 via the interface 303. Here, the processor 301 may transmit the change notification to only the regional management servers that have jurisdiction over the lane servers affected by the extended fare table. Also, in steps ST107 and ST108, an example is described in which the centralized linkage server 1 transmits the change notification to the second regional management server 32 via the second fare table management server 30. However, the centralized linkage server 1 may transmit the change notification directly to the second regional management server 32.

The processor 221 of the first regional management server 22 and the processor 321 of the second regional management server 32 send a table request to the central coordination server 1 (step ST108). The processor 221 receives the change notification through the interface 223. The processor 221 then learns from the received change notification that a new extended fee table has been created. The processor 221 then sends a table request, which is a query, to the central coordination server 1 through the interface 223 to obtain the new extended fee table.

Here, it is sufficient for the first regional management server 22 to have an extended toll table for the first toll gate server 23 under its jurisdiction, i.e., the toll gate under the jurisdiction of the first regional management server 22. Therefore, the processor 221, for example, sends a table request to the centralized linkage server 1, requesting only the extended toll table related to the toll gate under the jurisdiction of the first regional management server 22. Similarly, the processor 321 of the second regional management server 32 under the jurisdiction of the second expressway company 3 receives a change notification from the second toll table management server 30. Then, the processor 321 knows from the received change notification that a new extended toll table has been created. Therefore, the processor 321 sends a table request to the centralized linkage server 1, which is a query requesting only the extended toll table related to the toll gate under the jurisdiction of the second regional management server 32.

Note that the table requests sent by processor 221 and processor 321 do not need to be sent at the same time. For example, processor 221 or processor 321 may each send a table request immediately after receiving a change notification.

The processor 101 transmits a table request to the first fee table management server 20 (step ST109). The processor 101 receives table requests from each regional management server through the interface 103. The processor 101 of the integrated collaboration server 1 uses data virtualization technology to make it appear as if the extended fee table is stored in the memory unit 102. However, in reality, the extended fee table is stored in the memory unit 202 of the first fee table management server 20. Therefore, in order to obtain the extended fee table, the processor 101 uses a Foreign Data Wrapper function to convert the received table request into a table request compatible with the memory unit 202 of the first fee table management server 20 and transmits it.

The processor 201 transmits the extended fee table information to the unified cooperation server 1 (step ST110). The processor 201 receives a table request through the interface 203. Then, the processor 201 acquires the local area extended fee table, which is a partial extended fee table related to the toll gate under the jurisdiction of the first regional management server 22 or the second regional management server 32, from the extended fee table stored in the memory unit 202 in accordance with the received table request. Then, the processor 201 transmits the extended fee table information including the local area extended fee table and the extended fee table application conditions to the unified cooperation server 1 through the interface 203. Here, the local area extended fee table generated based on the table request transmitted by the first regional management server 22 includes only the extended fee table related to the toll gate under the jurisdiction of the first regional management server 22. And the local area extended fee table generated based on the table request transmitted by the second regional management server 32 includes only the extended fee table related to the toll gate under the jurisdiction of the second regional management.

The processor 101 transmits the local area extended fee table information to the first regional management server 22 and the second regional management server 32 (step ST111). The processor 101 receives the local area extended fee table information through the interface 103. The processor 101 converts the received extended fee table into data that the processor 101 can handle using the external data wrapper function. The processor 101 then transmits the local area extended fee table information, including the local area extended fee table and extended fee table application conditions corresponding to the first regional management server 22 and the second regional management server 32 from the acquired local area extended fee table, to the first regional management server 22 and the second regional management server 32 through the interface 103.

FIG. 11 is a diagram showing an example of creating a local area tollgate extended fee table from the extended fee table.
FIG. 11(a) shows an example of a part of the extended fee table stored in the memory unit 202 of the first fee table management server 20. For example, the first area management server is composed of an A area management server, a B area management server, and a C area management server. The A area management server is responsible for the first toll gate to the third toll gate on the A motorway, the B area management server is responsible for the fourth toll gate to the sixth toll gate on the B motorway, and the C area management server is responsible for the seventh toll gate to the eighth toll gate on the C motorway. The extended fee table in FIG. 11(a) shows the tolls between each toll gate. The upper, middle, and lower rows of the fee table are tolls for light vehicles, ordinary vehicles, medium-sized vehicles, etc., respectively.

Figures 11 (b) and (c) respectively show examples of the local area extended fee table of the A-area management server and the local area extended fee table of the B-area management server. When the A-area management server sends a table request to the centralized coordination server 1, the A-area management server receives, for example, a local area extended fee table as shown in Figure 11 (b). Similarly, when the B-area management server sends a table request to the centralized coordination server 1, the B-area management server receives, for example, a local area extended fee table as shown in Figure 11 (c). Although not shown in Figure 11 for simplicity, the C-area management server also naturally receives the local area extended fee table related to the seventh toll gates to the eighth toll gates from the centralized coordination server 1.

Processor 221 and processor 321 each create a tollgate extended fee table from the local area extended fee table included in the local area extended fee table information (step ST112). Processor 221 receives the local area extended fee table through interface 223. Then, processor 221 creates a tollgate extended fee table that contains only the fee tables related to each tollgate server provided in the first tollgate server 23 from the local area extended fee table included in the local area extended fee table information. Similarly, processor 321 receives the local area extended fee table information through interface 323. Then, processor 321 creates a tollgate extended fee table that contains only the fee tables related to each tollgate server provided in the second tollgate server 33 from the local area extended fee table included in the local area extended fee table information.

Figure 12 shows an example of the processor 221 creating a toll gate extended fee table corresponding to each toll gate server from the local area extended fee table.

Figure 12 (a) is the local area extended toll table of the A area management server shown in Figure 11 (b). Here, for example, the first toll gate server 23 is assumed to include an A toll gate server, a B toll gate server, a C toll gate server, etc. The A toll gate server is in charge of the first toll gate, the B toll gate server is in charge of the second toll gate, and the C toll gate server is in charge of the third toll gate server.

Figure 12(b) is a toll gate extended fee table for toll gate server A which has jurisdiction over the first toll gate, Figure 12(c) is a toll gate extended fee table for toll gate server B which has jurisdiction over the second toll gate, and Figure 12(d) is a toll gate extended fee table for toll gate server C which has jurisdiction over the third toll gate. As shown in Figures 12(a) to (d), processor 221 creates a toll gate extended fee table that has only the fee tables related to each toll gate server from the local area extended fee table.

FIG. 13 is a diagram showing an example in which the processor 221 creates a toll gate extended fee table corresponding to each toll gate server from the local area extended fee table.
Fig. 13(a) is the local area extended toll table of the B area management server shown in Fig. 11(c). Here, for example, the first toll gate server 23 includes a D toll gate server that manages the fourth toll gate, an E toll gate server that manages the fifth toll gate, and an F toll gate server that manages the sixth toll gate, in addition to the toll gate servers described in Fig. 12.

Figure 13(b) is a toll gate extended fee table for the D toll gate server in charge of the fourth toll gate, and Figure 13(c) is a lane extended fee table for the E toll gate server in charge of the fifth toll gate. For simplicity, the toll gate extended fee table for the F toll gate server in charge of the sixth toll gate is omitted from Figure 13. As shown in Figures 13(a) to (c), the processor 221 creates a toll gate extended fee table that has only the fee tables related to each toll gate from the local area extended fee table.

The processor 321 also creates the tollgate extended fee table in the same manner as described with reference to Figures 12 and 13.

The processor 221 and the processor 321 respectively transmit toll gate extended fee table information including the toll gate extended fee table to the first toll gate server 23 and the second toll gate server 33 (step ST113). The processor 231 of the first toll gate server 23 transmits the toll gate extended fee table information including the toll gate extended fee table and the extended fee table application conditions via the interface 233. Similarly, the processor 331 transmits the toll gate extended fee table information including the toll gate extended fee table and the extended fee table application conditions via the interface 333.

The processor 231 of the first toll gate server 23 and the processor 331 of the second toll gate server 33 create a lane expansion fee table (step ST114). The processor 231 receives the toll gate expansion fee table information through the interface 233. The processor 231 creates the toll gate expansion fee table included in the toll gate expansion fee table information as the lane expansion fee table. Similarly, the processor 331 receives the toll gate expansion fee table information through the interface 333. The processor 331 creates the toll gate expansion fee table included in the toll gate expansion fee table information as the lane expansion fee table.

The processor 231 and the processor 331 transmit lane expansion fee table information including the lane expansion fee table to the first lane server 25 and the second lane server 35 (step ST115). The processor 231 transmits the lane expansion fee table information including the lane expansion fee table and the extension fee table application conditions to the corresponding lane server of the first lane server 25 through the interface 233. Similarly, the processor 331 transmits the lane expansion fee table information including the lane expansion fee table and the extension fee table application conditions to the corresponding lane server of the second lane server 35 through the interface 333.

The processor 351 of the first lane server 25 and the processor 351 of the second lane server 35 respectively transmit a delivery notification to the first wide area management server 21 and the second wide area management server 31 (step ST116). The processor 251 receives the lane expansion fee table information through the interface 253. Then, the processor 251 stores the lane expansion fee table and the expansion fee table application conditions contained in the received lane expansion fee table information in the memory unit 252. When the lane expansion fee table is stored in the memory unit 252, the processor 251 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 transmits the delivery notification to the first wide area management server 21 through the interface 253, which is a communication unit.

Here, the delivery notification may be sent directly to the first wide area management server 21, or may be relayed through the first toll gate server 23 and/or the first regional management server 22. Similarly, the processor 331 receives lane expansion fee table information through the interface 333. Then, the processor 351 stores the lane expansion fee table and the expansion fee table application conditions included in the received lane expansion fee table information in the memory unit 352. When the lane expansion fee table is stored in the memory unit 252, the processor 351 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 sends the delivery notification to the second wide area management server 31 through the interface 353, which is a communication unit. Here, the delivery notification may be sent directly to the second wide area management server 31, or may be relayed through the second toll gate server 33 and/or the second regional management server 32.

Processor 211 and processor 311 each send a delivery notification to the central collaboration server 1 (step ST117). Processor 211 receives the delivery notification via interface 213. Processor 211 sends the received delivery notification to the central collaboration server 1 via interface 213. Processor 211 may store the received delivery notification in memory unit 212. Processor 311 receives the delivery notification via interface 313. Processor 311 sends the received delivery notification to the central collaboration server 1 via interface 313. Processor 311 may store the received delivery notification in memory unit 312.

The processor 101 transmits the operation start information to the first wide area management server 21 and the second wide area management server 31 (step ST117). The processor 101 receives a delivery notification from each wide area management server through the interface 103. Then, when the processor 101 receives the delivery notification from all the wide area management servers, it determines that the extended fee table has been shared by all the lane servers, and transmits the operation start information to each wide area management server. Each lane server will use the extended fee table according to the start time included in the extended fee table application conditions. Here, each lane server may use the extended fee table by the administrator who manages the lane server via the operation unit. In this case, the extended fee table application conditions do not need to be transmitted to the lane server. Also, each lane server may use the extended fee table by receiving an instruction from any server (wide area management server, fee table management server, regional management server, etc.) or any other device.

Note that steps ST117 and ST118 can be omitted. That is, when the first wide area management server 21 and the second wide area management server 31 receive the delivery notification, the first wide area management server 21 and the second wide area management server 31 may determine that the extended fee table has been shared by all lane servers and may start operation.

(Sharing of extended fee table application conditions)
Next, an operation for sharing the extended fee table application conditions among the respective global management servers will be described.

FIG. 14 is a sequence diagram showing an example of a process for sharing the extended fee table application conditions among the wide area management servers according to the first embodiment.
Steps ST101 to ST105 are the same as the operations described with reference to FIG. 10, and therefore the description thereof will be omitted.

The processor 101 transmits a change notification to the second wide area management server 31 (step ST121). The processor 101 receives the change notification via the interface 103. The processor 101 then transmits the change notification to the second wide area management server 31 via the interface 103.

The processor 311 sends a condition information request to the central collaboration server 1 (step ST122). The processor 311 receives the change notification through the interface 313. The processor 311 learns from the received change notification that an extended fee table application condition has been created. The processor 311 then outputs a condition information request requesting the extended fee table application condition, and sends the condition information request to the central collaboration server 1 through the interface 313.

The processor 101 transmits a condition information request to the first wide area management server 21 (step ST123). The processor 101 receives the condition information request through the interface 103. The processor 101 of the integrated collaboration server 1 uses data virtualization technology to make it appear as if the extended fee table application conditions are stored in the memory unit 102. However, in reality, they are stored in the memory unit 212 of the first wide area management server 21. Therefore, in order to obtain the extended fee table application conditions, the processor 101 uses an external data wrapper function to convert the received condition information request into a condition information request that is compatible with the memory unit 212 of the first wide area management server 21 and transmits it.

The processor 211 transmits the extended fee table application condition information to the centralized collaboration server 1 (step ST124). The processor 211 receives the table request via the interface 213. The processor 211 then acquires the extended fee table application condition stored in the memory unit 202 in accordance with the received table request. The processor 211 then transmits the extended fee table application condition information including the extended fee table application condition to the centralized collaboration server 1 via the interface 213.

The processor 101 transmits the extended fee table application condition information to the second wide area management server 31 (step ST125). The processor 101 receives the extended fee table application condition information through the interface 103. The processor 101 uses the external data wrapper function to convert the received extended fee table application condition information into data that the processor 101 can handle. The processor 101 then transmits the extended fee table application condition information to the second wide area management server 31 through the interface 103. The processor 311 of the second wide area management server 31 that has received the extended fee table application condition information stores the extended fee table application conditions from the received extended fee table application condition information in the memory unit 312.

As a result, the conditions for applying the extended fee table will be shared among all global management servers.

(Modification of sharing of extended fee table application conditions)
FIG. 15 is a sequence diagram showing an example of a process for sharing the extended fee table application conditions according to the first embodiment among the regional management servers.
The extended fee table application conditions may be shared among the regional management servers, i.e., the first regional management server 22, the second regional management server 32, and the third regional management server 42. FIG. 15 shows an example of a process for sharing the extended fee table application conditions among the regional management servers.

Steps ST101 to ST105 are the same as the operations described with reference to Figure 10, so the explanation will be omitted.

The processor 101 transmits a change notification to the second wide area management server 31 (step ST131). The processor 101 receives the change notification via the interface 103. The processor 101 then transmits the change notification to the second wide area management server 31 via the interface 103.

The processor 311 transmits a change notification to the second regional management server 32 (step ST132). The processor 311 receives the change notification via the interface 313. The processor 311 then transmits the change notification to the second regional management server 32 via the interface 313.

Processor 221 and processor 321 each send a condition information request to the central collaboration server 1 (step ST133). Processor 221 receives the change notification through interface 223. Processor 221 learns from the received change notification that an extended fee table application condition has been created. Processor 221 then outputs a condition information request requesting the extended fee table application condition, and sends the condition information request through interface 223 to central collaboration server 1. Similarly, processor 221 receives the change notification through interface 323. Processor 321 learns from the received change notification that an extended fee table application condition has been created. Processor 321 then outputs a condition information request requesting the extended fee table application condition, and sends the condition information request through interface 323 to central collaboration server 1.

The processor 101 transmits a condition information request to the first wide area management server 21 (step ST134). The processor 101 receives the condition information request through the interface 103. The processor 101 of the integrated collaboration server 1 uses data virtualization technology to make it appear that the extended fee table application conditions are stored in the memory unit 102. However, in reality, they are stored in the memory unit 212 of the first wide area management server 21. Therefore, in order to obtain the extended fee table application conditions, the processor 101 uses an external data wrapper function to convert the received condition information request into SQL (Structured Query Language) that is compatible with the memory unit 212 of the first wide area management server 21 and transmits it.

The processor 211 transmits the extended fee table application condition information to the centralized collaboration server 1 (step ST135). The processor 211 receives the table request via the interface 203. The processor 211 then acquires the extended fee table application condition stored in the memory unit 212 in accordance with the received table request. The processor 211 then transmits the extended fee table application condition information including the extended fee table application condition to the centralized collaboration server 1 via the interface 213.

The processor 101 transmits the extended fee table application condition information to the second regional management server 32 (step ST136). The processor 101 receives the extended fee table application condition information through the interface 103. The processor 101 converts the received extended fee table application condition information into data that the processor 101 can handle using the external data wrapper function. The processor 101 then transmits the extended fee table application condition information to the first regional management server 22 and the second regional management server 32 through the interface 103. The processor 221 of the first regional management server 22 and the processor 321 of the second regional management server 32 that have received the extended fee table application condition information store the extended fee table application conditions from the received extended fee table application condition information in the memory unit 222 and the memory unit 322, respectively.

As a result, the conditions for applying the extended fee table will be shared among all regional management servers.

(Effects of the First Embodiment)
According to the first embodiment described above, by using data virtualization technology, it becomes unnecessary for each fee table management server to synchronize the extended fee table in real time. This makes it possible to simplify the system, which leads to cost reduction when viewed from the perspective of the entire system. Furthermore, since there is less need to share data created by other companies with one's own storage unit, data management is simplified.

Second Embodiment
(composition)
The configuration according to the second embodiment is similar to the configuration according to the first embodiment, and therefore a description of the configuration will be omitted.

(Sharing of extended fee tables)
FIG. 16 is a sequence diagram showing an example of a process for sharing an extended fee table among each lane server according to the second embodiment.
In the second embodiment, each fee table management server transmits a query (a table request) to the central cooperation server 1 to obtain an extended fee table.

First, assume that a traffic jam occurs on a toll road under the jurisdiction of the first expressway company 2.

Steps ST201 to ST204 are the same as steps ST101 to ST104 described with reference to FIG. 10, so the description of these steps will be omitted.

The processor 201 sends a change notification to the centralized cooperation server 1 (step ST205). In order to collect tolls using the extended toll table, the extended toll table must be stored in each toll gate server under the jurisdiction of the first expressway company 2, the second expressway company 3, and the third expressway company 4. Therefore, the processor 201 sends a change notification to the centralized cooperation server 1 via the interface 203 indicating that a new extended toll table has been created, in order to distribute the extended toll table to each toll gate server.

The processor 101 of the integrated cooperation server 1 transfers the received change notification to the second toll table management server 30 of the second expressway company 3 (step ST206). The processor 101 receives the change notification through the interface 103. The processor 101 then transmits the change notification to the second toll table management server 30 through the interface 213. Note that for simplicity's sake, in FIG. 16, the change notification is transmitted to the second toll table management server 30 of the second expressway company 3, but the change notification is also transmitted to the third toll table management server 40 of the third expressway company 4. Furthermore, the processing of the third expressway company 4 after receiving the change notification is similar to that of the second expressway company 3, and therefore will not be described here.

The processor 301 of the second fee table management server 30 transmits a table request to the central linkage server 1 (step ST207). The processor 301 receives the change notification through the interface 303. The processor 301 then knows from the received change notification that a new extended fee table has been created. The processor 301 then transmits a table request, which is a query, to the central linkage server 1 through the interface 303 to obtain the new extended fee table. Here, it is sufficient for the second fee table management server 30 to have an extended fee table for the second regional management server 32 under its jurisdiction. The processor 301 then transmits a table request, which is a query requesting only the extended fee table related to the second regional management server 32 under its jurisdiction (i.e., the toll gate under the jurisdiction of the second fee table management server 30), to the central linkage server 1, for example.

The processor 101 transmits a table request to the first fee table management server 20 (step ST208). The processor 101 receives the table request from the second fee table management server 30 via the interface 103. The processor 101 uses data virtualization technology to make it appear as if the extended fee table is stored in the memory unit 102. However, in reality, the extended fee table is stored in the memory unit 202 of the first fee table management server 20. Therefore, in order to obtain the extended fee table, the processor 101 uses an external data wrapper function to convert the received table request into SQL compatible with the memory unit 202 of the first fee table management server 20 and transmits it.

The processor 201 transmits the extended fee table information to the unified linkage server 1 (step ST209). The processor 201 receives a table request through the interface 203. The processor 201 then acquires the extended fee table stored in the memory unit 202 in accordance with the received table request. The acquired extended fee table is an extended fee table (partial extended fee table) related to the toll gate under the jurisdiction of the second fee table management server 30. However, the processor 201 may acquire the extended fee table stored in the memory unit 202. The processor 201 then transmits the extended fee table information including the extended fee table and the extended fee table application conditions to the unified linkage server 1 through the interface 203. The processor 201 may acquire only the extended fee table related to the second regional management server 32 under the jurisdiction of the second fee table management server 30 from the extended fee table stored in the memory unit 202 and transmit it to the second fee table management server 30.

The processor 101 transmits the extended fee table information to the second fee table management server 30 (step ST210). The processor 101 receives the extended fee table information through the interface 103. The processor 101 converts the received extended fee table into data that the processor 101 can handle using the external data wrapper function. The processor 101 then transmits the acquired extended fee table and the extended fee table information including the extended fee table application conditions to the second fee table management server 30 through the interface 103.

Processor 201 and processor 301 each create a local area extended fee table from the extended fee table included in the area extended fee table information (step ST211). Processor 201 creates a local area extended fee table from the extended fee table stored in memory unit 202, with only extended fee tables related to toll booths under the jurisdiction of each regional management server of the first fee table management server 20. Similarly, processor 301 receives extended fee table information through interface 303. Then, processor 301 creates a local area extended fee table from the extended fee table included in the extended fee table information, with only fee tables related to toll booths under the jurisdiction of each regional management server of the second fee table management server 30.

The processor 201 and the processor 301 respectively transmit the local area extended fee table information to the first regional management server 22 and the second regional management server 32 (step ST212). The processor 201 transmits the local area extended fee table information including the created local area extended fee table and the extended fee table application conditions to the first regional management server 22. Similarly, the processor 301 transmits the local area extended fee table information including the created local area extended fee table and the extended fee table application conditions to the second regional management server 32.

The processor 221 and the processor 321 transmit the toll gate extended fee table information to the first toll gate server 23 and the second toll gate server 33, respectively (step ST213). The processor 221 receives the local area extended fee table information through the interface 223. The processor 221 then creates a toll gate extended fee table related to each toll gate under the jurisdiction of the first regional management server 22 from the local area extended fee table included in the local area extended fee table information. The processor 221 then transmits the toll gate extended fee table information including the created toll gate extended fee table and the extended fee table application conditions to the first toll gate server 23. Similarly, the processor 321 receives the local area extended fee table information through the interface 323. The processor 321 then creates a toll gate extended fee table related to each toll gate under the jurisdiction of the second regional management server 32 from the local area extended fee table included in the local area extended fee table information. Then, the processor 321 transmits the toll gate extended fee table information, including the created toll gate extended fee table and the extended fee table application conditions, to the second toll gate server 33.

The processor 231 and the processor 331 transmit the lane expansion fee table information to the first lane server 25 and the second lane server 35, respectively (step ST214). The processor 231 receives the toll gate expansion fee table information through the interface 233. The processor 231 then creates the toll gate expansion fee table included in the toll gate expansion fee table information as a lane expansion fee table. The processor 231 then transmits the created lane expansion fee table and the lane expansion fee table information including the conditions for applying the expansion fee table to the first lane server 25.

Similarly, the processor 331 receives the tollgate expansion fee table information through the interface 333. The processor 331 then creates the tollgate expansion fee table included in the tollgate expansion fee table information as a lane expansion fee table. The processor 331 then transmits the created lane expansion fee table and the lane expansion fee table information including the conditions for applying the expansion fee table to the second lane server 35.

The processor 351 of the first lane server 25 and the processor 351 of the second lane server 35 respectively send a delivery notification to the first wide area management server 21 and the second wide area management server 31 (step ST215). The processor 251 receives the lane expansion fee table information through the interface 253. Then, the processor 251 stores the lane expansion fee table and the expansion fee table application conditions contained in the received lane expansion fee table information in the memory unit 252. When the lane expansion fee table is stored in the memory unit 252, the processor 251 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 sends the delivery notification to the first wide area management server 21 through the interface 253, which is a communication unit.

Here, the delivery notification may be sent directly to the first wide area management server 21, or may be sent via relay through the first toll gate server 23 and/or the first regional management server 22. Similarly, the processor 331 receives lane expansion fee table information through the interface 333. Then, the processor 351 stores the lane expansion fee table and the expansion fee table application conditions included in the received lane expansion fee table information in the memory unit 352. When the lane expansion fee table is stored in the memory unit 252, the processor 351 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 sends the delivery notification to the second wide area management server 31 through the interface 353, which is a communication unit. Here, the delivery notification may be sent directly to the second wide area management server 31, or may be sent via relay through the second toll gate server 33 and/or the second regional management server 32.

Processor 211 and processor 311 each transmit a delivery notification to the central collaboration server 1 (step ST216). Processor 211 receives the delivery notification via interface 213. Processor 211 transmits the received delivery notification to the central collaboration server 1 via interface 213. Processor 211 may store the received delivery notification in memory unit 212. Processor 311 receives the delivery notification via interface 313. Processor 311 transmits the received delivery notification to the central collaboration server 1 via interface 213. Processor 311 may store the received delivery notification in memory unit 312.

The processor 101 transmits the operation start information to the first wide area management server 21 and the second wide area management server 31 (step ST217). The processor 101 receives a delivery notification from each wide area management server through the interface 103. Then, when the processor 101 receives the delivery notification from all the wide area management servers, it determines that the extended fee table has been shared by all the lane servers, and transmits the operation start information to each wide area management server. Each lane server will use the extended fee table according to the start time included in the extended fee table application conditions. Here, each lane server may use the extended fee table by the administrator who manages the lane server via the operation unit. In this case, the extended fee table application conditions do not need to be transmitted to the lane server. Also, each lane server may use the extended fee table by receiving an instruction from any server (wide area management server, fee table management server, regional management server, etc.) or any other device.

Note that steps ST216 and ST217 can be omitted. That is, when the first wide area management server 21 and the second wide area management server 31 receive the delivery notification, the first wide area management server 21 and the second wide area management server 31 may determine that the extended fee table has been shared by all lane servers and may start operation.

(Sharing of extended fee table application conditions)
The operation for sharing the extended fee table application information among the wide area management servers is the same as that in the first embodiment, and therefore a description thereof will be omitted here.

(Effects of the Second Embodiment)
According to the second embodiment described above, by using data virtualization technology, it becomes unnecessary for each fee table management server to perform operations for synchronizing the extended fee tables. This makes it possible to simplify the system, which leads to cost reduction when viewed from the perspective of the entire system.

[Third embodiment]
(composition)
The configuration according to the third embodiment is similar to the configuration according to the first embodiment, and therefore a description of the configuration will be omitted.

(Sharing of extended fee tables)
FIG. 17 is a sequence diagram showing an example of a process for sharing an extended fee table among each lane server according to the second embodiment.
In the third embodiment, each toll gate server transmits a query (a table request) to the general cooperation server 1 to obtain the extended toll table.

First, assume that a traffic jam occurs on a toll road under the jurisdiction of the first expressway company 2.

Steps ST301 to ST307 are the same as steps ST101 to ST107 described with reference to FIG. 10, and therefore a description of these steps will be omitted. Note that, in steps ST306 to ST308, an example is shown in which the second fare table management server 30 and the second area management server 32 relay the change notification, but these steps can be omitted. In other words, the centralized cooperation server 1 may send the change notification directly to the second toll gate server 33.

The processor 221 and the processor 321 transmit a change notification to the first toll gate server 23 and the second toll gate server 33, respectively (step ST308). The processor 221 receives the change notification through the interface 223. The processor 221 transmits the change notification to the first toll gate server 23 through the interface 223. Similarly, the processor 321 receives the change notification through the interface 323. The processor 321 transmits the change notification to the second toll gate server 33 through the interface 323.

The processor 231 and the processor 331 send a table request to the centralized cooperation server 1 (step ST309). The processor 231 receives the change notification through the interface 233. The processor 231 then knows from the received change notification that a new extended fee table has been created. The processor 231 then sends a table request, which is a query, to the centralized cooperation server 1 through the interface 233 to obtain the new extended fee table. Here, it is sufficient for the first toll gate server 23 to have an extended fee table for its own toll gate. The processor 231 then sends a table request to the centralized cooperation server 1, for example, requesting only the extended fee table related to the first toll gate server 23.

Similarly, the processor 331 of the second tollgate server 33 under the jurisdiction of the second expressway company 3 receives a change notification from the second regional management server 32. The processor 331 then learns from the received change notification that a new extended toll table has been created. The processor 331 then sends a table request, which is a query requesting only the extended toll table related to the second tollgate server 33, to the integrated coordination server 1. Note that the table requests sent by the processor 231 and the processor 331 do not need to be sent simultaneously. For example, the processor 231 or the processor 331 may each send a table request immediately after receiving the change notification.

The processor 101 transmits a table request to the first fare table management server 20 (step ST310). The processor 101 receives table requests from each toll booth server through the interface 103. The processor 101 of the integrated cooperation server 1 uses data virtualization technology to make it appear as if the extended fare table is stored in the memory unit 102. However, in reality, the extended fare table is stored in the memory unit 202 of the first fare table management server 20. Therefore, in order to obtain the extended fare table, the processor 101 uses an external data wrapper function to convert the received table request into a table request compatible with the memory unit 202 of the first fare table management server 20 and transmits it.

The processor 201 transmits the toll gate extended fee table information to the centralized cooperation server 1 (step ST311). The processor 201 receives a table request via the interface 203. Then, in accordance with the received table request, the processor 201 acquires a toll gate extended fee table, which is a partial extended fee table related to the first toll gate server 23 or the second toll gate server 33, from the extended fee table stored in the memory unit 202. Then, the processor 201 transmits the toll gate extended fee table information, including the toll gate extended fee table and the extended fee table application conditions, to the centralized cooperation server 1 via the interface 203.

Here, the toll gate extended fee table generated based on the table request sent by the first toll gate server 23 includes only the extended fee table related to the toll gate under the jurisdiction of the first toll gate server 23. And, the toll gate extended fee table generated based on the table request sent by the second toll gate server 33 includes only the extended fee table related to the toll gate under the jurisdiction of the second toll gate server 33.

The processor 101 transmits the tollgate extended fee table information to the first tollgate server 23 and the second tollgate server 33 (step ST312). The processor 101 receives the tollgate extended fee table information through the interface 103. The processor 101 converts the received tollgate extended fee table into data that the processor 101 can handle using the external data wrapper function. The processor 101 then transmits the tollgate extended fee table information, including the tollgate extended fee table and extended fee table application conditions corresponding to the first tollgate server 23 and the second tollgate server 33, respectively, through the interface 103 to the first tollgate server 23 and the second tollgate server 33, respectively.

The processor 231 and the processor 331 transmit lane expansion fee table information including the lane expansion fee table to the first lane server 25 and the second lane server 35, respectively (step ST313). The processor 231 receives the toll gate expansion fee table information through the interface 233. The processor 231 creates the toll gate expansion fee table included in the toll gate expansion fee table information as a lane expansion fee table. The processor 231 then transmits the lane expansion fee table information including the lane expansion fee table and the conditions for applying the expansion fee table to the corresponding lane server among the first lane server 25.

Similarly, the processor 331 receives the tollgate expansion fee table information through the interface 333. The processor 331 creates the tollgate expansion fee table included in the tollgate expansion fee table information as a lane expansion fee table. The processor 331 then transmits the lane expansion fee table information including the lane expansion fee table and the conditions for applying the expansion fee table to the corresponding lane server among the second lane servers 35.

The processor 351 of the first lane server 25 and the processor 351 of the second lane server 35 transmit a delivery notification to the first wide area management server 21 and the second wide area management server 31, respectively (step ST314). The processor 251 receives the lane expansion fee table information through the interface 253. Then, the processor 251 stores the lane expansion fee table and the expansion fee table application conditions contained in the received lane expansion fee table information in the memory unit 252. When the lane expansion fee table is stored in the memory unit 252, the processor 251 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 transmits the delivery notification to the first wide area management server 21 through the interface 253, which is a communication unit. Here, the delivery notification may be transmitted directly to the first wide area management server 21, or may be transmitted via the first toll gate server 23 and/or the first regional management server 22.

Similarly, the processor 331 receives lane expansion fee table information through the interface 333. The processor 351 then stores the lane expansion fee table and the expansion fee table application conditions contained in the received lane expansion fee table information in the memory unit 352. When the lane expansion fee table is stored in the memory unit 252, the processor 351 outputs a delivery notification indicating that the lane expansion fee table has been stored in the memory unit 252. The processor 251 then transmits the delivery notification to the second wide area management server 31 through the interface 353, which is a communication unit. Here, the delivery notification may be transmitted directly to the second wide area management server 31, or may be transmitted via the second toll gate server 33 and/or the second regional management server 32.

Processor 211 and processor 311 each transmit a delivery notification to the central collaboration server 1 (step ST315). Processor 211 receives the delivery notification via interface 213. Processor 211 transmits the received delivery notification to the central collaboration server 1 via interface 213. Processor 211 may store the received delivery notification in memory unit 212. Processor 311 receives the delivery notification via interface 313. Processor 311 transmits the received delivery notification to the central collaboration server 1 via interface 213. Processor 311 may store the received delivery notification in memory unit 312.

The processor 101 transmits operation start information to the first wide area management server 21 and the second wide area management server 31 (step ST316). The processor 101 receives delivery notifications from each wide area management server via the interface 103. Then, when the processor 101 receives delivery notifications from all wide area management servers, it determines that the extended fare table has been shared by all lane servers, and transmits operation start information to each wide area management server. Each lane server will use the extended fare table according to the start time included in the extended fare table application conditions.

Here, each lane server may use the extended fare table via the operation unit, by an administrator who manages the lane server. In this case, it is not necessary to transmit the extended fare table application conditions to the lane server. Also, each lane server may use the extended fare table upon receiving instructions from any server (wide area management server, fare table management server, regional management server, etc.) or any other device.

Note that steps ST315 and ST316 can be omitted. That is, when the first wide area management server 21 and the second wide area management server 31 receive the delivery notification, the first wide area management server 21 and the second wide area management server 31 may determine that the extended fee table has been shared by all lane servers and may start operation.

(Sharing of extended fee table application conditions)
The operation for sharing the extended fee table application information among the wide area management servers is the same as that in the first embodiment, and therefore a description thereof will be omitted here.

(Effects of the Third Embodiment)
According to the third embodiment described above, by using data virtualization technology, it becomes unnecessary for each fee table management server to perform operations for synchronizing the extended fee tables, which makes it possible to simplify the system and leads to cost reduction when viewed from the perspective of the entire system.

In addition, since the first toll gate server 23 and the second toll gate server 33 make a table request and obtain the toll gate extended fee table, there is no need for the regional management server to obtain its own regional extended fee table. Therefore, fewer devices are involved in distributing the extended fee table to the lane server, which leads to reduced processing when viewed from the perspective of the entire system.

[Fourth embodiment]
[composition]
The configuration according to the fourth embodiment is similar to the configuration according to the first embodiment, and therefore a description of the configuration will be omitted.

(Processing at any time)
In the fourth embodiment, the advance preparations described in the first to third embodiments are performed so that the lane server holds the extended fare table and each wide area management server holds the conditions for applying the extended fare table, and thus processing at any time using the extended fare table becomes possible (operational stage).

FIG. 18 is a sequence diagram illustrating an example of an occasional process according to the fourth embodiment.
First, it is assumed that the toll is adjusted due to congestion or the like, and operation using the extended toll table is started. In other words, it is assumed that the advance preparation process according to the first embodiment is completed, and operation using the extended toll table is started.

The vehicle 5 enters or travels on a toll road under the jurisdiction of the first expressway company 2, and passes through a first lane server 25 installed at either the entrance toll, main line FF, or area boundary FF.

The processor 251 receives vehicle information from the vehicle-mounted device 50 (step ST401). The processor 251 receives the vehicle information through the interface 253. The first roadside equipment 26 managed by the first lane server 25 detects the vehicle 5 using the vehicle detector 262, the camera 263, etc. Then, based on the detection, the antenna 264 starts communication with the vehicle-mounted device 50. Then, the processor 251 receives the vehicle information including the vehicle-mounted device ID, the card number information of the ETC card, the entry or exit record, etc.

The processor 251 transmits the route information to the first wide area management server 21 (step ST402).

The processor 251 receives vehicle information through the interface 253. The processor 251 determines the route that the vehicle 5 will take based on the toll booth ID and vehicle information assigned to the processor 251. The processor 251 then outputs route information including vehicle information and driving history information indicating the driving route of the vehicle 5, and transmits the route information to the first wide area management server 21 via the interface 253, relaying the first toll booth server 23 and the first regional management server 22.

The processor 211 determines whether the vehicle 5 is passing through a route that is eligible for a discount (step ST403). The processor 211 receives route information through the interface 213. The processor 211 links the vehicle ID included in the vehicle information in the route information with the driving history information, and outputs driving route information indicating the driving route for each vehicle 5. The processor 211 then compares the driving route information with the extended fare table application condition information stored in the memory unit 212, and determines whether the extended fare table is to be applied to the vehicle 5. For example, if the vehicle's driving route satisfies the application conditions included in the extended fare table application information, the processor 211 determines that the extended fare table is to be applied to the vehicle 5.

When the processor 211 determines that the extended fee table is to be applied to the vehicle 5, it creates an extended fee table number list (step ST404). The processor 211 creates an extended fee table number list that includes the extended fee table number of the extended fee table to be applied and the vehicle-mounted device ID of the vehicle 5.

The processor 211 transmits the extended fare table number list to the first regional management server 22 (step ST405). The processor 211 transmits the created extended fare table number list to the first regional management server 22 that is the target. The extended fare table number list only needs to be held by the first lane server 25 through which the vehicle 5 may pass. Therefore, the processor 211 transmits the extended fare table number list only to the first regional management server 22 that is the target among the first regional management servers 22.

The processor 221 transmits the extended fee table number list to the first management IF device 24 (step ST406). The processor 221 receives the extended fee table number list via the interface 223. The processor 221 then transmits the extended fee table number list to the target first management IF device 24.

The processor 241 transmits the extended fare table number list to the first toll gate server 23 (step ST407). The processor 241 receives the extended fare table number list via the interface 243. The processor 241 then transmits the extended fare table number list to the target first toll gate server 23. The processor 241 may also transmit the extended fare table list directly to the first lane server 25. In this case, the following step ST408 is omitted.

The processor 231 transmits the extended fare table number list to the first lane server 25 (step ST408). The processor 231 receives the extended fare table number list via the interface 233. The processor 231 then transmits the extended fare table number list to the target first lane server 25.

The processor 251 registers the extended fee table number list in the memory unit 252 (step ST409). The processor 251 receives the extended fee table number list through the interface 253. The processor 251 then registers the extended fee table number list in the memory unit 252.

Then, the vehicle 5 passes through the first lane server 25 installed at the main line FF, the area boundary FF, or the exit toll gate.

The processor 251 receives vehicle information from the vehicle-mounted device 50 (step ST410). The processor 251 receives the vehicle information through the interface 253. The first roadside equipment 26 managed by the first lane server 25 detects the vehicle 5 using a vehicle detector 262, a camera 263, etc. Then, based on the detection, the antenna 264 starts communication with the vehicle-mounted device 50. The processor 251 then receives the vehicle information.

The processor 251 checks whether the vehicle 5 is a vehicle registered in the extended fee table list based on the vehicle-mounted device ID included in the vehicle information (step ST411). The processor 251 checks whether the vehicle-mounted device ID included in the vehicle information corresponds to an onboard device ID in the extended fee table number list stored in the memory unit 252. If they correspond, the processor 251 determines that the vehicle 5 is a vehicle 5 to which the extended fee table applies.

The processor 251 performs a toll allocation process (step ST412). The processor 251 determines the toll for the vehicle 5 using the lane extension toll table corresponding to the extension toll table number included in the extension toll table number list, and transmits information about the determined toll to the vehicle-mounted device 50. The vehicle-mounted device 50 may also announce to the driver via a speaker or the like how much the toll was.

For simplicity, FIG. 18 only uses the first expressway company 2 for explanation, but the same operation will occur if the vehicle 5 enters the second expressway company 3 and the third expressway company 4 and then exits through the lane server (exit toll booth). Of course, route information is handed over between the wide area management servers that have jurisdiction over the toll roads on which the vehicle 5 has traveled.

(Functions and Effects of the Fourth Embodiment)
According to the fourth embodiment described above, route understanding is performed by the wide-area management server, so there is no need for the vehicle to understand a large amount of route information and perform lane server processing using that information, thereby reducing the memory capacity and processing load on the lane server and on the vehicle-mounted device.

[Fifth embodiment]
[composition]
The configuration according to the fifth embodiment is similar to the configuration according to the first embodiment, and therefore a description of the configuration will be omitted.

(Processing at any time)
In the fifth embodiment, the processing when it becomes possible to perform processing on an ongoing basis using the extended fare table (operational stage) due to the advance preparations described in the first to third embodiments, in which the lane server holds the extended fare table and each regional server holds the conditions for applying the extended fare table, will be described.

FIG. 19 is a sequence diagram illustrating an example of an occasional process according to the fifth embodiment.
First, it is assumed that the toll is adjusted due to congestion or the like, and operation using the extended toll table is started. In other words, it is assumed that the advance preparation process according to the first embodiment is completed, and operation using the extended toll table is started.

The vehicle 5 enters or travels on a toll road under the jurisdiction of the first expressway company 2, and passes through a first lane server 25 installed at either the entrance toll, main line FF, or area boundary FF.

The processor 251 receives vehicle information from the vehicle-mounted device 50 (step ST501). The processor 251 receives the vehicle information through the interface 253. The first roadside equipment 26 managed by the first lane server 25 detects the vehicle 5 using a vehicle detector 262, a camera 263, etc. Then, based on the detection, the antenna 264 starts communication with the vehicle-mounted device 50. Then, the processor 251 receives the vehicle information.

The processor 251 transmits the route information to the first regional management server 22 (step ST502).

The processor 251 determines the route that the vehicle 5 will take based on the toll gate ID and vehicle information assigned to the processor 251. The processor 251 then outputs route information including vehicle information and driving history information indicating the driving route of the vehicle 5, and transmits the route information to the first regional management server 22 via the interface 253 and the first toll gate server 23.

The processor 221 determines whether the vehicle 5 is passing through a route that is eligible for a discount (step ST503). The processor 221 receives route information through the interface 223. The processor 201 links the vehicle ID included in the vehicle information in the route information with the driving history information, and outputs driving route information indicating the driving route for each vehicle 5. The processor 201 then compares the driving route information with the extended fare table application condition information stored in the memory unit 202, and determines whether the extended fare table is to be applied to the vehicle 5. For example, if the vehicle's driving route satisfies the application conditions included in the extended fare table application information, the processor 201 determines that the extended fare table is to be applied to the vehicle 5.

If it is determined that the extended fee table is to be applied to the vehicle 5, the processor 221 creates an extended fee table list (step ST504). The processor 201 creates an extended fee table number list that includes the extended fee table number of the extended fee table to be applied and the vehicle-mounted device ID of the vehicle 5.

Steps ST505 to ST513 are similar to steps ST406 to ST414 described in the fourth embodiment, so their explanation will be omitted here.

In addition, in FIG. 19, for simplicity, only the first expressway company 2 is used for explanation, but the same operation will occur even if the vehicle 5 enters the second expressway company 3 and the third expressway company 4 and then exits from the lane server (exit toll booth). Of course, route information is handed over between the regional management servers that have jurisdiction over the toll roads on which the vehicle 5 has traveled.

(Functions and Effects of the Fifth Embodiment)
According to the fifth embodiment described above, route understanding is performed by the regional management server, so there is no need for the vehicle to understand a large amount of route information and perform lane server processing using that information, and the storage capacity and processing load on the lane server and on the vehicle-mounted device are reduced.

[Other embodiments]
It should be noted that the present invention is not limited to the above-described embodiment. For example, the first to third embodiments can be combined with each other. For example, the second expressway company 3 may have a regional management server send a table request to the general cooperation server 1 as in the first embodiment, and the third expressway company 4 may have a toll table management server send a table request.

Furthermore, the fourth and fifth embodiments can be combined. That is, the server that holds the extended toll table application conditions may be different for each expressway company.

In short, this invention is not limited to the above-described embodiment, and various modifications can be made in the implementation stage without departing from the gist of the invention. Furthermore, the embodiments may be implemented in combination as appropriate as possible, in which case the combined effects can be obtained. Furthermore, the above-described embodiment includes inventions at various stages, and various inventions can be extracted by appropriate combinations of the multiple constituent elements disclosed.

1... General cooperation server 101, 201, 301... Processor 102, 202, 302... Memory unit 103, 202, 302... Interface 104, 204, 304... Display unit 105, 205, 305... Operation unit 2, 3, 4... Expressway company 20, 30, 40... Toll table management server 201, 301, 401... Processor 202, 302, 402... Memory unit 203, 303, 403... Interface 204, 304, 404... Display unit 205, 305, 405... Operation unit 21, 31, 41... Wide area management server 211, 311, 411... Processor 212, 312, 412... Memory unit 213, 313, 413... Interface 214, 314, 414...display unit 215, 315, 415...operation unit 22, 32, 42...regional management server 221, 321, 421...processor 222, 322, 422...storage unit 223, 323, 423...interface 224, 324, 424...display unit 225, 325, 425...operation unit 23, 33, 43...toll gate server 231, 331, 431...processor 232, 332, 432...storage unit 233, 333, 433...interface 234, 334, 434...display unit 235, 335, 435...operation unit 24, 34, 44...management IF device 241, 341, 441...processor 242, 342, 442...storage unit 243, 343, 443... interface 244, 344, 444... display unit 245, 345, 445... operation unit 25, 35, 45... lane server 251, 351, 451... processor 252, 352, 452... storage unit 253, 353, 453... interface 254, 354, 454... display unit 255, 355, 455... operation unit 26, 36, 46... roadside equipment 261, 361, 461... interface aggregation unit 262, 362, 462... vehicle detector 263, 363, 463... camera 264, 364, 464... antenna 265, 365, 465... roadside display 266, 366, 466... departure controller 28, 38, 48...Traffic control central station 5...Vehicle 50...In-vehicle device

Claims (10)

A fee collection system including a centralized cooperation server, a first fee table management server connected to the centralized cooperation server, and a server connected to the centralized cooperation server,
the central cooperation server includes a first communication unit that receives a query from the server and transmits the query to the first fee table management server;
The first fee table management server
A storage unit that stores an extended fare table that allows a toll to be calculated from a travel route of a vehicle on a toll road and in which a fare adjustment is set for a predetermined section;
a second processor for obtaining a partial extended fare table of the extended fare table related to a toll booth under the jurisdiction of the server based on the query;
a second communication unit that transmits the partial extended fee table to the centralized cooperation server;
Equipped with
The first communication unit transmits the partial extended fee table to the server.
Toll collection system. the server is a first regional management server connected to the central coordination server,
a third processor for generating a toll booth extended fare table from the partial extended fare table , the toll booth extended fare table including an extended fare table associated with each of the toll booths managed by the server;
a third communication unit that transmits the toll gate extended fee table corresponding to each of the toll gates under the jurisdiction of the server;
The toll collection system according to claim 1 . 3. The fee collection system according to claim 1, wherein the query is generated in response to receiving a change notification from the first fee table management server, the change notification indicating that the extended fee table has been generated. The toll collection system further includes a first wide area management server connected to the first toll table management server, and the first wide area management server
a fourth processor that generates extended fee table application condition information including an application condition for applying the extended fee table and an extended fee table number for identifying the extended fee table, and variable fee setting information including an instruction to create the extended fee table;
a fourth communication unit that transmits the variable fee setting information to the first fee table management server;
The toll collection system of claim 3 , further comprising: a second processor configured to generate the extended fee table based on the variable fee setting information and to generate a change notification indicating that the extended fee table has been generated. the fee collection system further includes a second wide-area management server connected to the central cooperation server, and the second communication unit transmits the change notification to the second wide-area management server via the central cooperation server;
The fee collection system of claim 4, wherein the second wide area management server comprises: a fifth processor that generates a condition information request requesting extended fee table application condition information in response to the change notification; and a fifth communication unit that transmits the condition information request to the first wide area management server via the centralized coordination server and receives the extended fee table application condition information from the first wide area management server in response to the condition information request. the fee collection system further includes a second wide area management server connected to the central cooperation server and a second regional management server connected to the second wide area management server, the second communication unit transmits the change notification to the second regional management server via the central cooperation server and the second wide area management server,
The fee collection system of claim 4, wherein the second regional management server comprises: a sixth processor that generates a condition information request requesting extended fee table application condition information in response to the change notification; and a sixth communication unit that transmits the condition information request to a first wide area management server via the centralized coordination server and the second wide area management server, and receives the extended fee table application condition information from the first wide area management server in response to the condition information request. the server is a second fare table management server connected to the centralized cooperation server, and the fee collection system includes a second regional management server connected to the second fare table management server,
the server comprises a seventh processor which creates a local area extended fee table for a toll gate under the jurisdiction of the second regional management server from the partial extended fee table , and a seventh communication unit which transmits the local area extended fee table to the second regional management server;
The toll collection system of claim 1, wherein the second regional management server comprises: an eighth processor that creates a toll gate extended fee table from the local region extended fee table, the toll gate extended fee table including extended fee tables related to each toll gate under the jurisdiction of the second regional management server; and an eighth communication unit that transmits the toll gate extended fee table corresponding to each toll gate under the jurisdiction of the second regional management server. The toll collection system according to claim 1 , wherein the server is a first toll gate server connected to the centralized cooperation server. A fee collection method executed by a centralized collaboration server, comprising:
Receiving a first query from a server;
sending the first query to a first tariff table management server;
receiving from the first toll table management server a partial extended toll table related to a toll gate under the jurisdiction of the server, the partial extended toll table being included in an extended toll table in which a toll can be calculated based on a travel route traveled by a vehicle on a toll road and toll adjustments are set for a predetermined section;
sending the partial extended fee table to the server;
A method of collecting fees . A fee collection program having instructions to be executed by a processor of a centralized coordination server , the instructions comprising:
Receiving a first query from a server;
sending the first query to a first tariff table management server;
receiving from the first toll table management server a partial extended toll table related to a toll gate under the jurisdiction of the server, the partial extended toll table being included in an extended toll table in which a toll can be calculated based on a travel route traveled by a vehicle on a toll road and toll adjustments are set for a predetermined section;
sending the partial extended fee table to the server;
A toll collection program that includes :