Toll collection system and toll collection method

Abstract

To reduce a data holding amount and communication fees of an entire system, and to change tolls promptly and flexibly.SOLUTION: An information processing system according to an embodiment includes: a unified coordination server; a first toll table management server that is connected to the unified coordination server; and a server that is connected to the unified coordination server. The unified coordination server includes a first communication unit that receives a query from the server and transmits the query to the first toll table management server. The first toll table management server includes: a storage unit that stores an extended toll table; a second processor that acquires, in the extended toll table, a partial extended toll 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 toll table to the unified coordination server. The first communication unit transmits the partial extended toll table to the server.SELECTED DRAWING: Figure 1a

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing method, and an information processing program. [Background technology]

[0002] Each expressway company that operates a toll road 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 that allows drivers to drive on toll roads managed by different expressway companies without being aware of this and does not require them to pay tolls to each company separately. Specifically, each expressway company shares a single master toll table, and the toll 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.

[0003] Furthermore, the ETC (Electronic Toll Collection) (registered trademark) system, which is widely used on toll roads, enables non-stop toll collection without the need for vehicles to stop at the toll gate by wirelessly communicating between the onboard unit of a vehicle traveling in the lane of the toll gate and roadside equipment installed at the toll gate. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-107111 Summary of the Invention [Problem to be solved by the invention]

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

[0006] Furthermore, due to current national policy needs, there is a demand for flexible and rapid changes to tolls. However, the current system cannot meet this need. Therefore, each expressway company needs to quickly share its own toll change measures with other expressway companies, and build a system that allows for flexible and rapid changes to tolls by quickly applying the changes all the way to the toll gates at the end of the line.

[0007] An 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. [Means for solving the problem]

[0008] In one 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 sends 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 tolls can be calculated from the route traveled by a vehicle on a toll road and in which fare adjustments are set for specified sections, a second processor that obtains a partial extended fare table from the extended fare table that is relevant 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. [Brief explanation of the drawings]

[0009] [Figure 1a] FIG. 1a is a diagram showing an example of a schematic configuration of an information processing system according to the first embodiment. [Figure 1b] FIG. 1b is a diagram showing an example of a schematic configuration of an information processing system according to the first embodiment. [Figure 2] 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. [Figure 3] FIG. 3 is a block diagram showing an example of the first fee table management server according to the first embodiment. [Figure 4] FIG. 4 is a block diagram showing an example of the first wide area management server according to the first embodiment. [Figure 5] FIG. 5 is a block diagram illustrating an example of a first regional management server according to the first embodiment. [Figure 6] FIG. 6 is a block diagram showing an example of the first toll gate server according to the first embodiment. [Figure 7] FIG. 7 is a block diagram showing an example of a schematic configuration of the first management IF device according to the first embodiment. [Figure 8] FIG. 8 is a block diagram illustrating an example of the first lane server according to the first embodiment. [Figure 9] FIG. 9 is a block diagram showing an example of a schematic configuration of the first roadside device according to the first embodiment. [Figure 10] FIG. 10 is a sequence diagram showing an example of a process for sharing the extended toll table among the lane servers according to the first embodiment. [Figure 11] FIG. 11 is a diagram showing an example of creating a local area extended fee table from the extended fee table. [Figure 12] 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. [Figure 13] 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. [Figure 14] 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. [Figure 15]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. [Figure 16] FIG. 16 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers according to the second embodiment. [Figure 17] FIG. 17 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers according to the second embodiment. [Figure 18] FIG. 18 is a sequence diagram illustrating an example of an occasional process according to the fourth embodiment. [Figure 19] FIG. 19 is a sequence diagram illustrating an example of an occasional process according to the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] The information processing system, the information processing device, and the 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 the same operations, and redundant description will be omitted.

[0011] [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 Figure 1a, the information processing system according to the first embodiment includes an integrated cooperation server 1, a first expressway company 2, a second expressway company 3, a third expressway company 4, and a vehicle 5. While the example in Figure 1a shows three expressway companies, 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.

[0012] The integrated cooperation server 1 is connected to a first expressway company 2, a second expressway company 3, and a 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.

[0013] The first expressway company 2 comprises a first toll table management server 20, a first wide area management server 21, a first regional management server 22, a first toll booth 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 station 28. Similarly, the second expressway company 3 comprises a second toll table management server 30, a second wide area management server 31, a second regional management server 32, a second toll booth server 33, a second management IF device 34, a second lane server 35, a second roadside device 36, and a second traffic control central station 38. Furthermore, the third expressway company 4 is equipped with a third toll table management server 40, a third wide area management server 41, a third regional management server 42, a third toll booth server 43, a third management IF device 44, a third lane server 45, a third roadside equipment 46, and a third traffic control central station 48.

[0014] Here, the first toll booth server 23, the first management IF device 24, the first lane server 25, and the first roadside equipment 26 are located within the first toll booth 29. Similarly, the second toll booth server 33, the second management IF device 34, the second lane server 35, and the second roadside equipment 36 are located within the second toll booth 39, and the third toll booth server 43, the third management IF device 44, the third lane server 45, and the third roadside equipment 46 are located within the third toll booth 49. Here, the first toll booth 29, the second toll booth 39, and the third toll booth 49 are not only entrance and exit toll booths, but also include cases where the toll booths are route free-flow or area boundary free-flow.

[0015] 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 with the integrated cooperation server 1 and the first wide area management server 21. 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, and therefore their explanation will be omitted.

[0016] The first wide-area management server 21 is connected to the first regional management server 22 and the first traffic control central station 28. The first wide-area management server 21 exchanges various types of information with the integrated cooperation server 1 and the first regional management server 22. Furthermore, the first wide-area management server 21 receives various types of information, including traffic congestion information, from the first traffic control central station 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, and therefore their explanation will be omitted.

[0017] The first regional management server 22 is connected to the first toll booth server 23 and the first management IF device 24. The first regional management server 22 exchanges various types of information with the first toll booth server 23 and the first management IF device 24. The first regional management server 22 is also connected to the general cooperation server 1. The first regional management server 22 exchanges various types of information with the general cooperation server 1. For simplicity, FIG. 1a shows only the first regional management server 22 as the regional management server, but multiple regional management servers may be 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, and therefore their description will be omitted.

[0018] 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 types of 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 central cooperation server 1. The first toll gate server 23 exchanges various types of information with the central cooperation server 1. For simplicity, FIG. 1a shows only the first regional management server 22 as the regional management server, but multiple toll gate servers may be connected to the first regional management server 22 (i.e., each regional management server). Furthermore, the number of toll gate servers connected to each regional management server may be different or the same. 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 description will be omitted.

[0019] The first lane server 25 is connected to the first roadside equipment 26. The first lane server 25 exchanges various types of 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 tollgate server 23 (i.e., each tollgate server). Furthermore, the number of lane servers connected to each tollgate 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 description will be omitted.

[0020] The first roadside equipment 26 is installed 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 the toll gate, route FF, or area boundary FF, and connects to an on-board device 50 installed on the vehicle 5. The first roadside equipment 26 exchanges various information with the on-board device 50. For simplicity, FIG. 1a shows only the first toll gate server 23 as the toll gate server, but multiple lane servers may be connected to the first toll gate server 23 (i.e., each toll gate server). Furthermore, the number of toll gate servers connected to each regional management server may be different or the same.

[0021] 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 an ETC card inserted into 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.

[0022] Here, the first tollgate server 23 is in charge of a plurality of lane servers. Therefore, the first tollgate server 23 that is in charge of the first lane server 25 is in charge of more lane servers than the first lane server 25. The first regional management server 22 that is in charge of the first tollgate server 23 is in charge of more lane servers than the first lane server 25. The first wide area management server 21 is in charge of more lane servers than the first regional management server 22.

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

[0024] As is clear from FIG. 1b, for example, the first toll table management server 20 is responsible for n*m toll gates, and the first regional management server 22a is responsible for m toll gates. The second expressway company 3 and the third expressway company 4 have similar configurations, 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 at each management office of the first expressway company 2, and a first toll gate 29 is located at each toll gate.

[0025] FIG. 2 is a block diagram showing an example of the general 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, an operation unit 105, and the like.

[0026] Processor 101, which is the first processor, realizes various processing functions by executing programs stored in storage unit 102. For example, processor 101 executes programs stored in storage unit 102 to function as a relay unit that transfers various information to a wide-area management server, a fee table management server, etc.

[0027] 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 fare table, extended fare table, extended fare table application conditions, driving history information, etc. using data virtualization technology. However, this information is actually stored in a storage unit of, for example, the first fare table management server 20 or the first wide-area management server 21, and when the processor 101 needs this information, it can use it by sending a query to the first fare table management server 20 or the first wide-area management server 21 and receiving data corresponding to the query.

[0028] Here, the basic toll table is a toll table for calculating tolls according to the normal driving route of the vehicle 5. Furthermore, the extended toll table is a toll table for calculating tolls for the vehicle 5 when a toll adjustment zone is set. The extended toll table application condition information is information including application conditions indicating the cases in which the extended toll table is applied when the extended toll table is set, and the extended toll table number corresponding to the extended toll table at the time of application. Note that the application conditions indicate the conditions that the vehicle 5 must satisfy, such as the time and date at which toll gates, routes FFs, and area borders FFs were passed. Furthermore, the extended toll table number is an identification number for identifying the extended toll table. The driving history information is information indicating the driving route when the vehicle 5 passed through 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 toll table and extended toll table.

[0029] The interface 103 is a communication interface for connecting to, for example, 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.

[0030] The display unit 104 displays information relating to fee table processing in accordance with display control from the processor 101. The operation unit 105 is composed of a keyboard, etc. The operation unit 105 receives information input by an operator and supplies the information to the processor 101.

[0031] 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.

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

[0033] The storage unit 202 has a program memory that stores 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.

[0034] The interface 203 is a communication interface for connecting to the first wide area management server 21 and the first regional management server 22, and functions as a communication unit that sends various requests, which are queries, to the central collaboration server 1 and receives various information from the central collaboration server 1.

[0035] The display unit 204 displays content 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 fare 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 fare 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 the same as the configuration of the first fare table management server 20, so their explanation will be omitted.

[0036] 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.

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

[0038] The storage unit 212 has a program memory for storing programs executed by the processor 211, a working memory for storing working data, and a data memory for storing 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. The extended fee table application condition information and the extended fee table number list will be described later.

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

[0040] The display unit 214 displays the display content according to the 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. However, these are substantially the same as the configuration of the first wide area management server 21, and therefore a description thereof will be omitted.

[0041] 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 storage unit 222, an interface 223, a display unit 224, an operation unit 225, and the like.

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

[0043] The storage unit 222 has a program memory for storing programs executed by the processor 221, a working memory for storing working data, and a data memory for storing data files, etc. For example, the storage unit 212 can store various information such as a local area basic fee table, a local area extended fee table, local area driving history information which 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, for example, a fee table consisting only of basic fee tables related to toll gates under the jurisdiction of the first area management server 22. The local area extended fee table will be described later.

[0044] Interface 223 is a communications interface for connecting to the centralized cooperation server 1, the first management IF device 24, the first tollbooth server 23, and the first management IF device 24, and functions as a communications unit that transmits various requests, which are queries, to the centralized cooperation server 1 and receives various information from the centralized cooperation server 1. Interface 223, which functions as a communications unit, also has the function of receiving various information from the first management IF device 24 and the first lane server 25.

[0045] The display unit 224 displays display content 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 comprises a processor 321, a memory unit 322, an interface 323, a display unit 324, an operation unit 325, etc., and the third regional management server 42 also comprises a processor 421, a memory unit 422, an interface 423, a display unit 424, an operation unit 425, etc. However, these are substantially similar in configuration to the first regional management server 22, and therefore a description thereof will be omitted.

[0046] 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 storage unit 232, an interface 233, a display unit 234, an operation unit 235, and the like.

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

[0048] The storage unit 232 has a program memory for storing programs executed by the processor 231, a working memory for storing working data, and a data memory for storing 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, which is driving history information related to the first toll gate server 23. Here, the toll gate basic toll table is a toll table consisting of only the 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.

[0049] The interface 233 is a communication interface for connecting to the central collaboration server 1, the first management IF device 24, and the first lane server 25, and functions as a communication unit that sends various requests, which are queries, to the central collaboration server 1 and receives various information from the central collaboration 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.

[0050] The display unit 234 displays the display content according to the 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 the same as the configuration of the first toll gate server 23, and therefore a description thereof will be omitted.

[0051] 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.

[0052] The processor 241 realizes various processing functions by executing the programs stored in the storage 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 storage unit 242.

[0053] The storage unit 242 has a program memory that stores programs executed by the processor 241, a working memory that stores working data, and a data memory that stores data files and the like.

[0054] 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.

[0055] The display unit 244 displays the display content according to the 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 a description thereof will be omitted.

[0056] 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 by a general-purpose computer or the like, and includes a processor 251, a storage unit 252, an interface 253, a display unit 254, an operation unit 255, and the like.

[0057] The processor 251 realizes various processing functions by executing the programs stored in the storage 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 storage unit 252.

[0058] The storage unit 252 has a program memory for storing programs executed by the processor 251, a working memory for storing working data, and a data memory for storing data files, etc. For example, the storage 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 the 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.

[0059] Interface 253 is a communications interface for connecting to central cooperation server 1 and first roadside device 26, and functions as a communications unit that transmits and receives various types of information to and from first tollgate server 23. Interface 253, which functions as a communications unit, also has the function of receiving various types of information from first roadside device 26.

[0060] The display unit 254 displays the display content according to the 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, and an operation unit 355, and the third lane server 45 also includes a processor 451, a memory unit 452, an interface 453, a display unit 454, and an operation unit 455. However, these are substantially similar in configuration to the first lane server 25, and therefore a description thereof will be omitted.

[0061] FIG. 9 is a block diagram showing an example of a schematic configuration of the first roadside device 26 according to the first embodiment. As shown in FIG. 9, the first roadside device 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.

[0062] 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 or the like 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 or the like, and controls the operation of the first roadside equipment 26.

[0063] The camera 263 captures an image of the vehicle 5 that has entered the first lane server 25. The captured image is transmitted 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 acquires the vehicle number. The first lane server 25 may also acquire other information related to the vehicle 5, such as the model of the vehicle 5, from the captured image.

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

[0065] 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.

[0066] [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, making it necessary to adjust the toll, the extended toll table, which is the adjusted toll table, must be shared among 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 among the wide-area management server or local management server of each expressway company.

[0067] (Shared extended fee table) First, the operation for sharing the extended fee table among the lane servers will be described. FIG. 10 is a sequence diagram showing an example of a process for sharing the extended toll 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 acquire the extended fee table.

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

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

[0070] The processor 211 creates extended toll 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 toll table operation conditions stored in the memory unit 212. Here, the extended toll table operation conditions are conditions for starting to create an extended toll table, such as the number of kilometers of traffic congestion on a specific toll road, or a specific date and time. The extended toll table operation conditions may be stored in the memory unit 212 of the first wide area management server 21.

[0071] If it is determined that the traffic congestion information matches the extended toll table operating conditions, the processor 211 determines the extended toll table application conditions so that a discount (extended toll) can be received if the vehicle 5 detours around a congested area, or a surcharge (extended toll) can be incurred if the vehicle 5 proceeds through a congested area. The extended toll table application conditions include the start time and end time at which the extended toll table becomes effective, the route pattern to be applied, the vehicle type, and whether or not a discount for persons with disabilities is available. The processor 211 creates an extended toll table number (identifier) ​​corresponding to the extended toll table when these tolls are changed. The processor 211 then creates extended toll table application condition information including the extended toll table application conditions and the extended toll table number.

[0072] Furthermore, 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.

[0073] Alternatively, 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 operating regulations. If it does, the administrator may input an instruction to create extended fee application conditions to the first wide-area management server 21. Then, the processor 211 may create extended fee application condition information in accordance with the input.

[0074] 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 operating regulations that the administrator can apply. Semi-automatic operation is also possible, in which the administrator selects an appropriate option from the displayed information.

[0075] 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., instructions on which sections the extended fee will be applied to.

[0076] 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.

[0077] Processor 201 transmits a change notification to the central 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 each of the first expressway company 2, the second expressway company 3, and the third expressway company 4. Therefore, 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 central cooperation server 1 via interface 203 in order to distribute the extended toll table to each tollgate server.

[0078] 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). Processor 101 receives the change notification via interface 103. Processor 101 then transmits the change notification to the second toll table management server 30 via interface 213. Note that for simplicity's sake, in FIG. 10 , 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 performed by the third expressway company 4 after receiving the change notification is similar to the processing performed by the second expressway company 3, and therefore will not be described here. Note that if there are expressway companies other than the third expressway company 4, the processing performed by those expressway companies will of course be similar to the processing performed by the second expressway company 3.

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

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

[0081] Here, it is sufficient for the first regional management server 22 to have extended toll tables for the first toll gate servers 23 under its jurisdiction, i.e., the toll gates under the jurisdiction of the first regional management server 22. Therefore, the processor 221 sends, for example, a table request to the general cooperation server 1, requesting only the extended toll tables related to the toll gates 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. The processor 321 then learns from the received change notification that a new extended toll table has been created. Therefore, the processor 321 sends a table request to the general cooperation server 1, which is a query requesting only the extended toll tables related to the toll gates under the jurisdiction of the second regional management server 32.

[0082] It is not necessary for the processor 221 and the processor 321 to send the table requests at the same time. For example, the processor 221 or the processor 321 may send a table request immediately after receiving a change notification.

[0083] The processor 101 transmits a table request to the first fee table management server 20 (step ST109). The processor 101 receives the table request from each regional management server via the interface 103. Using data virtualization technology, the processor 101 of the integrated collaboration server 1 makes 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 acquire 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 the converted table request.

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

[0085] The processor 101 transmits the local area extended fee table information to the first local area management server 22 and the second local area 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. Then, the processor 101 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 local area management server 22 and the second local area management server 32 from the acquired local area extended fee table, through the interface 103 to the first local area management server 22 and the second local area management server 32.

[0086] FIG. 11 is a diagram showing an example of creating a local area tollgate extended fee table from the extended fee table. Figure 11(a) shows an example of a portion of the extended toll table stored in the memory unit 202 of the first toll table management server 20. For example, the first regional management server is composed of an A regional management server, a B regional management server, and a C regional management server. The A regional management server is responsible for the first toll gates to the third toll gate on Expressway A, the B regional management server is responsible for the fourth toll gates to the sixth toll gate on Expressway B, and the C regional management server is responsible for the seventh toll gates to the eighth toll gate on Expressway C. The extended toll table in Figure 11(a) shows the tolls between each toll gate. The top, middle, and bottom rows of the toll table are tolls for light vehicles, standard vehicles, medium-sized vehicles, etc., respectively.

[0087] Figures 11(b) and (c) show examples of the local area extended fee table of the A area management server and the B area management server, respectively. When the A area management server sends a table request to the general collaboration server 1, the A area management server receives, for example, a local area extended fee table such as that shown in Figure 11(b). Similarly, when the B area management server sends a table request to the general collaboration server 1, the B area management server receives, for example, a local area extended fee table such as that shown in Figure 11(c). Note that, although not shown in Figure 11 for simplicity, the C home area management server also receives the local area extended fee tables related to the seventh toll gate and the eighth toll gate from the general collaboration server 1.

[0088] 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 via interface 223. Then, processor 221 creates a tollgate extended fee table that contains only the fee tables related to each tollgate server provided in first tollgate server 23 from the local area extended fee table included in the local area extended fee table information. Similarly, processor 321 receives local area extended fee table information via interface 323. Then, processor 321 creates a tollgate extended fee table that contains only the fee tables related to each tollgate server provided in second tollgate server 33 from the local area extended fee table included in the local area extended fee table information.

[0089] FIG. 12 is a diagram showing an example in which the processor 221 creates a tollgate extended fee table corresponding to each tollgate server from the local area extended fee table.

[0090] Figure 12(a) is the local area extended toll table of the A area management server shown in Figure 11(b). Here, for example, it is assumed that the first toll gate server 23 includes an A toll gate server, a B toll gate server, a C toll gate server, etc. It is also assumed that 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.

[0091] Figure 12(b) is a tollgate extended fee table for tollgate server A that has jurisdiction over the first tollgate, Figure 12(c) is a tollgate extended fee table for tollgate server B that has jurisdiction over the second tollgate, and Figure 12(d) is a tollgate extended fee table for tollgate server C that has jurisdiction over the third tollgate. As shown in Figures 12(a) to (d), processor 221 creates a tollgate extended fee table that includes only fee tables related to each tollgate server from its own area extended fee table.

[0092] FIG. 13 is a diagram showing an example in which the processor 221 creates a tollgate extended fee table corresponding to each tollgate server from the local area extended fee table. Figure 13(a) is the local area extended toll table of the B area management server shown in Figure 11(c). Here, for example, the first toll gate server 23 is assumed to include, in addition to the toll gate server described in Figure 12, a D toll gate server that has jurisdiction over the fourth toll gate, an E toll gate server that has jurisdiction over the fifth toll gate, and an F toll gate server that has jurisdiction over the sixth toll gate.

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

[0094] The processor 321 also creates the tollgate extended fee table in the same manner as described with reference to FIGS.

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

[0096] The processor 231 of the first tollgate server 23 and the processor 331 of the second tollgate server 33 create a lane expansion fee table (step ST114). The processor 231 receives the tollgate expansion fee table information through the interface 233. The processor 231 creates the tollgate expansion fee table included in the tollgate expansion fee table information as the lane expansion fee table. 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 the lane expansion fee table.

[0097] Processor 231 and processor 331 transmit lane expansion fee table information including the lane expansion fee table to the first lane server 25 and second lane server 35 (step ST115). 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 among the first lane server 25 via interface 233. Similarly, 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 among the second lane server 35 via interface 333.

[0098] 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 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 included 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.

[0099] Here, the delivery notice may be sent directly to the first wide area management server 21, or may be sent via a relay through the first tollgate server 23 and / or the first regional management server 22. Similarly, the processor 331 receives lane expansion fee table information via 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 notice indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 sends the delivery notice to the second wide area management server 31 via the interface 353, which is a communication unit. Here, the delivery notice may be sent directly to the second wide area management server 31, or may be sent via a relay through the second tollgate server 33 and / or the second regional management server 32.

[0100] Processor 211 and processor 311 each transmit a delivery notification to the central collaboration server 1 (step ST117). 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 storage 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 313. Processor 311 may store the received delivery notification in storage unit 312.

[0101] The processor 101 transmits 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 via the interface 103. When the processor 101 receives a delivery notification from all wide-area management servers, it determines that the extended fare table has been shared among 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 be configured to use the extended fare table by an administrator managing the lane server via the operation unit. In this case, the extended fare table application conditions do not need to be transmitted to the lane server. Furthermore, each lane server may use the extended fare table upon receiving an instruction from any server (wide-area management server, fare table management server, regional management server, etc.) or any other device.

[0102] It is possible to omit steps ST117 and ST118. 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 toll table has been shared by all lane servers and start operation.

[0103] (Extended fee table applicable conditions shared) Next, the operation for sharing the extended fee table application conditions among the wide area management servers will be described.

[0104] 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 will be omitted.

[0105] The processor 101 transmits a change notification to the second wide area management server 31 (step ST121). The processor 101 receives the change notification through the interface 103. Then, the processor 101 transmits the change notification to the second wide area management server 31 through the interface 103.

[0106] Processor 311 transmits a condition information request to central collaboration server 1 (step ST122). Processor 311 receives the change notification via interface 313. Processor 311 learns from the received change notification that an extended fee table application condition has been created. Processor 311 then outputs a condition information request requesting the extended fee table application condition, and transmits the condition information request to central collaboration server 1 via interface 313.

[0107] 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 via the interface 103. Using data virtualization technology, the processor 101 of the integrated collaboration server 1 makes 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 acquire 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.

[0108] Processor 211 transmits the extended fee table application condition information to central collaboration server 1 (step ST124). Processor 211 receives the table request via interface 213. Then, processor 211 acquires the extended fee table application conditions stored in memory unit 202 in accordance with the received table request. Then, processor 211 transmits the extended fee table application condition information including the extended fee table application conditions to central collaboration server 1 via interface 213.

[0109] 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. Then, the processor 101 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.

[0110] As a result, the extended fee table application conditions are shared among the wide area management servers.

[0111] (Modification of the 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 among the regional management servers according to the first embodiment. The extended fee table application conditions may be shared among the respective regional management servers, i.e., the first regional management server 22, the second regional management server 32, and the third regional management server 42. Therefore, Fig. 15 shows an example of a process for sharing the extended fee table application conditions among the respective regional management servers.

[0112] Steps ST101 to ST105 are the same as the operations described with reference to FIG. 10, and therefore the description will be omitted.

[0113] The processor 101 transmits a change notification to the second wide area management server 31 (step ST131). The processor 101 receives the change notification through the interface 103. Then, the processor 101 transmits the change notification to the second wide area management server 31 through the interface 103.

[0114] The processor 311 transmits a change notification to the second regional management server 32 (step ST132). The processor 311 receives the change notification through the interface 313. Then, the processor 311 transmits the change notification to the second regional management server 32 through the interface 313.

[0115] 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 to the central collaboration server 1 through interface 223. 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 to the central collaboration server 1 through interface 323.

[0116] 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 via 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 acquire 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) compatible with the memory unit 212 of the first wide area management server 21 and transmits it.

[0117] Processor 211 transmits the extended fee table application condition information to central collaboration server 1 (step ST135). Processor 211 receives the table request via interface 203. Then, processor 211 acquires the extended fee table application conditions stored in memory unit 212 in accordance with the received table request. Then, processor 211 transmits the extended fee table application condition information including the extended fee table application conditions to central collaboration server 1 via interface 213.

[0118] 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.

[0119] As a result, the extended fee table application conditions are shared among the respective regional management servers.

[0120] (Operation and effect of the first embodiment) According to the first embodiment described above, by using data virtualization technology, it is no longer necessary for each fee table management server to synchronize the extended fee tables in real time. This simplifies the system and reduces costs when viewed from the perspective of the entire system. Furthermore, data management is simplified because there is less need to share data created by other companies with one's own storage unit.

[0121] [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.

[0122] (Shared extended fee table) FIG. 16 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers 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 acquire the extended fee table.

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

[0124] Steps ST201 to ST204 are the same as steps ST101 to ST104 described with reference to FIG. 10, and therefore a description of these steps will be omitted.

[0125] Processor 201 sends a change notification to central 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 first expressway company 2, second expressway company 3, and third expressway company 4. Therefore, processor 201 sends a change notification to central cooperation server 1 via 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.

[0126] 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). Processor 101 receives the change notification via interface 103. Processor 101 then transmits the change notification to the second toll table management server 30 via 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 performed by the third expressway company 4 after receiving the change notification is similar to the processing performed by the second expressway company 3, and therefore will not be described here.

[0127] Processor 301 of second fare table management server 30 transmits a table request to central collaboration server 1 (step ST207). Processor 301 receives the change notification via interface 303. Processor 301 then learns from the received change notification that a new extended fare table has been created. Therefore, processor 301 transmits a table request, which is a query to central collaboration server 1, via interface 303 to obtain the new extended fare table. Here, it is sufficient for the second fare table management server 30 to have an extended fare table for the second regional management server 32 under its jurisdiction. Therefore, processor 301 transmits, for example, a table request to central collaboration server 1, which is a query requesting only extended fare tables related to the second regional management server 32 under the jurisdiction of the second fare table management server 30 (i.e., the toll gates under the jurisdiction of the second fare table management server 30).

[0128] 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, it is stored in the memory unit 202 of the first fee table management server 20. Therefore, in order to acquire 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.

[0129] The processor 201 transmits the extended fee table information to the general collaboration server 1 (step ST209). The processor 201 receives a table request via the interface 203. Then, the processor 201 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) associated with a 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 general collaboration server 1 via the interface 203. The processor 201 may also acquire only the extended fee table associated with the second regional management server 32 under the jurisdiction of the second fee table management server 30 from the extended fee tables stored in the memory unit 202 and transmit it to the second fee table management server 30.

[0130] 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. Then, the processor 101 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.

[0131] 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, which contains only extended fee tables related to toll gates under the jurisdiction of each regional management server of 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, which contains only fee tables related to toll gates under the jurisdiction of each regional management server of second fee table management server 30.

[0132] The processor 201 and the processor 301 transmit the local area extended fee table information to the first local area management server 22 and the second local area management server 32, respectively (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 local area management server 22. Similarly, the processor 301 transmits the created local area extended fee table and 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 local area management server 32.

[0133] The processor 221 and the processor 321 transmit the tollgate extended fee table information to the first tollgate server 23 and the second tollgate 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 tollgate extended fee table associated with each tollgate under the jurisdiction of the first area 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 tollgate extended fee table information including the created tollgate extended fee table and the extended fee table application conditions to the first tollgate server 23. Similarly, the processor 321 receives the local area extended fee table information through the interface 323. The processor 321 then creates a tollgate extended fee table associated with each tollgate under the jurisdiction of the second area 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 created tollgate extended fee table and tollgate extended fee table information including the extended fee table application conditions to the second tollgate server 33.

[0134] 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 tollgate expansion fee table information through the interface 233. The processor 231 then creates the tollgate expansion fee table included in the tollgate 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 extension fee table application conditions to the first lane server 25.

[0135] Similarly, the processor 331 receives the tollgate expansion fee table information through the interface 333. Then, the processor 331 creates the tollgate expansion fee table included in the tollgate expansion fee table information as a lane expansion fee table. Then, the processor 331 transmits the created lane expansion fee table and the lane expansion fee table information including the expansion fee table application conditions to the second lane server 35.

[0136] 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 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 included 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.

[0137] Here, the delivery notice may be sent directly to the first wide area management server 21, or may be sent via a relay through the first tollgate server 23 and / or the first regional management server 22. Similarly, the processor 331 receives lane expansion fee table information via 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 notice indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 sends the delivery notice to the second wide area management server 31 via the interface 353, which is a communication unit. Here, the delivery notice may be sent directly to the second wide area management server 31, or may be sent via a relay through the second tollgate server 33 and / or the second regional management server 32.

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

[0139] The processor 101 transmits 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 via the interface 103. When the processor 101 receives a delivery notification from all wide-area management servers, it determines that the extended fare table has been shared among 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 be configured to use the extended fare table by an administrator managing the lane server via the operation unit. In this case, the extended fare table application conditions do not need to be transmitted to the lane server. Furthermore, each lane server may use the extended fare table upon receiving an instruction from any server (wide-area management server, fare table management server, regional management server, etc.) or any other device.

[0140] It is possible to omit steps ST216 and ST217. 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 toll table has been shared by all lane servers and start operation.

[0141] (Extended fee table applicable conditions shared) The operation for sharing the extended fee table application information among the wide area management servers is the same as in the first embodiment, and therefore a description thereof will be omitted here.

[0142] (Effects of the second embodiment) According to the second embodiment described above, by using data virtualization technology, it is no longer necessary for each fee table management server to synchronize the extended fee tables, which simplifies the system and reduces costs when viewed from the perspective of the entire system.

[0143] [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.

[0144] (Shared extended fee table) FIG. 17 is a sequence diagram showing an example of a process for sharing the extended fee table among the lane servers according to the second embodiment. In the third embodiment, each tollgate server transmits a query (a table request) to the general cooperation server 1 to acquire the extended toll table.

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

[0146] Steps ST301 to ST307 are the same as steps ST101 to ST107 described with reference to Figure 10, and therefore a description of these steps will be omitted. Note that, although steps ST306 to ST308 show an example in which the change notification is relayed by the second fare table management server 30 and the second regional management server 32, these steps can be omitted. In other words, the general cooperation server 1 may send the change notification directly to the second toll gate server 33.

[0147] Processor 221 and processor 321 transmit change notifications to the first toll booth server 23 and the second toll booth server 33, respectively (step ST308). Processor 221 receives the change notification through interface 223. Processor 221 transmits the change notification to the first toll booth server 23 through interface 223. Similarly, processor 321 receives the change notification through interface 323. Processor 321 transmits the change notification to the second toll booth server 33 through interface 323.

[0148] Processor 231 and processor 331 transmit a table request to general cooperation server 1 (step ST309). Processor 231 receives the change notification via interface 233. Processor 231 then learns from the received change notification that a new extended fee table has been created. Processor 231 then transmits a table request, which is a query to general cooperation server 1 via interface 233, to acquire 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. Therefore, processor 231 transmits a table request to general cooperation server 1, for example, requesting only the extended fee table associated with the first toll gate server 23.

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

[0150] The processor 101 transmits a table request to the first fare table management server 20 (step ST310). The processor 101 receives the table request from each toll booth server via the interface 103. Using data virtualization technology, the processor 101 of the integrated cooperation server 1 makes 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 acquire 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 the converted table request.

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

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

[0153] 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.

[0154] 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 tollgate expansion fee table information through the interface 233. The processor 231 creates the tollgate expansion fee table included in the tollgate expansion fee table information as a lane expansion fee table. Then, 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.

[0155] 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.

[0156] The processor 351 of the first lane server 25 and the processor 351 of the second lane server 35 transmit a delivery notice 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 included 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 notice indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 transmits the delivery notice to the first wide-area management server 21 through the interface 253, which is a communication unit. Here, the delivery notice may be transmitted directly to the first wide-area management server 21, or may be transmitted via the first tollgate server 23 and / or the first regional management server 22.

[0157] 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 notice indicating that the lane expansion fee table has been stored in the memory unit 252. Then, the processor 251 transmits the delivery notice to the second wide area management server 31 through the interface 353, which is a communication unit. Here, the delivery notice 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.

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

[0159] 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 a delivery notification from each wide area management server via the interface 103. When the processor 101 receives a delivery notification from all wide area management servers, it determines that the extended toll 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 toll table according to the start time included in the extended toll table application conditions.

[0160] Here, each lane server may use the extended fare table via the operation unit under the control of an administrator who manages the lane server. In this case, the extended fare table application conditions do not need to be transmitted 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, local management server, etc.) or any other device.

[0161] It is possible to omit steps ST315 and ST316. 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 toll table has been shared by all lane servers and start operation.

[0162] (Extended fee table applicable conditions shared) The operation for sharing the extended fee table application information among the wide area management servers is the same as in the first embodiment, and therefore a description thereof will be omitted here.

[0163] (Operation and effect of the third embodiment) According to the third embodiment described above, by using data virtualization technology, it is no longer necessary for each fee table management server to synchronize the extended fee tables, which simplifies the system and reduces costs when viewed from the perspective of the entire system.

[0164] In addition, since the first tollgate server 23 and the second tollgate server 33 request a table and obtain the tollgate extended fee table, the regional management server does not need to obtain its own regional extended fee table. Therefore, fewer devices are required to distribute the extended fee table to the lane server, which reduces the processing load in the entire system.

[0165] [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.

[0166] (Processed on an ongoing basis) In the fourth embodiment, the processing when it becomes possible to perform processing at any time 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 wide area management server holds the extended fare table application conditions.

[0167] 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 has been adjusted due to congestion or the like, and operation using the extended toll table has begun. In other words, it is assumed that the advance preparation process according to the first embodiment has ended, and operation using the extended toll table has begun.

[0168] Then, 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.

[0169] 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.

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

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

[0172] 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 that indicates 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.

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

[0174] The processor 211 transmits the extended toll table number list to the first area management server 22 (step ST405). The processor 211 transmits the created extended toll table number list to the target first area management server 22. The extended toll 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 toll table number list only to the target first area management server 22 among the first area management servers 22.

[0175] 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 through the interface 223. Then, the processor 221 transmits the extended fee table number list to the target first management IF device 24.

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

[0177] The processor 231 transmits the extended toll table number list to the first lane server 25 (step ST408). The processor 231 receives the extended toll table number list via the interface 233. Then, the processor 231 transmits the extended toll table number list to the target first lane server 25.

[0178] The processor 251 registers the extended fee table number list in the storage unit 252 (step ST409). The processor 251 receives the extended fee table number list through the interface 253. Then, the processor 251 registers the extended fee table number list in the storage unit 252.

[0179] Thereafter, 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.

[0180] 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 a 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.

[0181] The processor 251 checks whether the vehicle 5 is a vehicle registered in the extended fare table list based on the on-board device ID included in the vehicle information (step ST411). The processor 251 checks whether the on-board device ID included in the vehicle information corresponds to the on-board device ID in the extended fare table number list stored in the storage unit 252. If they correspond, the processor 251 determines that the vehicle 5 is a vehicle 5 to which the extended fare table applies.

[0182] 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 in-vehicle device 50. The in-vehicle device 50 may also announce the amount of the toll to the driver via a speaker or the like.

[0183] 18, for simplicity, only the first expressway company 2 is used for explanation, but the same operation occurs even if the vehicle 5 exits through a lane server (exit toll gate) after entering the second expressway company 3 and the third expressway company 4. 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.

[0184] (Operation and effect 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 storage capacity and processing load on the lane server and on the vehicle-mounted device.

[0185] [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.

[0186] (Processed on an ongoing basis) In the fifth embodiment, we will explain the processing that occurs when, through the advance preparations described in the first to third embodiments, the lane server holds the extended fare table and each regional server holds the extended fare table application conditions, making it possible to perform processing using the extended fare table at any time (operational stage).

[0187] 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 has been adjusted due to congestion or the like, and operation using the extended toll table has begun. In other words, it is assumed that the advance preparation process according to the first embodiment has ended, and operation using the extended toll table has begun.

[0188] Then, 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.

[0189] 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 a 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.

[0190] The processor 251 transmits the route information to the first area management server 22 (step ST502).

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

[0192] 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 that indicates 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 should 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 should be applied to the vehicle 5.

[0193] When 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 including the extended fee table number of the extended fee table to be applied and the vehicle-mounted device ID of the vehicle 5.

[0194] Steps ST505 to ST513 are the same as steps ST406 to ST414 described in the fourth embodiment, and therefore a description thereof will be omitted here.

[0195] 19, for simplicity, only the first expressway company 2 is used for explanation, but the same operation occurs even if the vehicle 5 exits through a lane server (exit toll gate) after entering the second expressway company 3 and the third expressway company 4. 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.

[0196] (Operation and effect 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, thereby reducing the storage capacity and processing load on the lane server and on the vehicle-mounted device.

[0197] [Other embodiments] It should be noted that the present invention is not limited to the above-described embodiments. 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.

[0198] Furthermore, it is possible to combine the fourth embodiment with the fifth embodiment. That is, the server that holds the extended toll table application conditions may be different for each expressway company.

[0199] In short, this invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in combination as appropriate as possible, and in such cases, the combined effects can be obtained. Furthermore, the above-described embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining the disclosed multiple constituent elements. [Explanation of symbols]

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

Claims

1. In the toll collection system, a first wide-area management server that is under the jurisdiction of a first road operator among a plurality of wide-area management servers provided for each of a plurality of road operators, and that creates application condition information including a toll adjustment section for the adjusted toll when it becomes necessary to adjust the toll based on traffic congestion information; a first fee table management server that receives application condition information of the extended fee table created by the first wide area management server from the first wide area management server, and creates an extended fee table for collecting adjusted fees based on the application condition information; a first toll booth server that is installed at a first toll booth under the jurisdiction of the first road operator, that stores an extended toll table distributed from the first toll table management server, and that uses the extended toll table to collect tolls from passing vehicles via a first roadside device installed at the first toll booth; a second toll booth server that is installed at a second toll booth under the jurisdiction of a second road operator different from the first road operator, that stores an extended toll table distributed from the toll table management server via an integrated cooperation server connected to the first wide area management server, and that uses the extended toll table to collect tolls from passing vehicles via a second roadside device installed at the second toll booth; A toll collection system comprising:

2. When the first wide-area management server determines that the traffic congestion information matches the extended fare table operating conditions stored in the storage unit of the wide-area management server, the first wide-area management server determines the application condition information of the extended fare table so that the vehicle can receive a discount if it detours around the congested area, or so that the vehicle can receive a surcharge if it proceeds through the congested area. The toll collection system according to claim 1.

3. The integrated collaboration server is connected to the first fare table management server and a second fare table management server under the jurisdiction of the second road operator, The central collaboration server when receiving a change notification indicating that the extended fee table has been created from the first fee table management server, transmitting the change notification to a second wide area management server or a second fee table management server connected to the second wide area management server; The toll collection system according to claim 1.

4. the toll collection system further includes a second regional management server connected to the centralized cooperation server and the second fare table management server, the second rate table management server, upon receiving the change notification from the centralized cooperation server, forwards the change notification to the second regional management server; The second regional management server receiving the change notification, transmitting a query to the central cooperation server for a request to distribute the extended fee table, and obtaining from the central cooperation server an extended fee table for the local area corresponding to the jurisdiction of the central cooperation server; The toll collection system according to claim 3.

5. the second tollgate server is connected to the second regional management server, and creates a tollgate extended fee table corresponding to the tollgate as the extended fee table from its own regional extended fee table acquired from the second regional management server; The toll collection system according to claim 4.

6. The central collaboration server When receiving a change notification to apply the extended fee table from the first fee table management server, the change notification is transferred to the second wide area management server, and when receiving a query for requesting the application condition information of the extended fee table acquired from the second wide area management server, the query is sent to the first wide area management server, and the application condition information is acquired from the first wide area management server. The toll collection system according to claim 3.

7. the toll collection system further includes a second regional management server connected to the central cooperation server and the second wide area management server, The second global management server Upon receiving the change notification, forward the change notification to the second regional management server; The second regional management server requesting the application condition information of the extended fee table from the central collaboration server; acquiring the application condition information from the first wide area management server via the central collaboration server; The toll collection system according to claim 3.

8. The second fee table management server Upon receiving a change notification to apply the extended fee table from the central collaboration server, the central collaboration server transmits a query to the central collaboration server to acquire the extended fee table from the first fee table management server via the central collaboration server, creates a self-extended fee table from the acquired extended fee table, and distributes the self-extended fee table to a second regional management server connected to the second fee table management server. The toll collection system according to claim 3.

9. The toll collection system includes: a second toll table management server connected to the centralized cooperation server and managed by the second road operator; a second regional management server connected to the central collaboration server and the second fee table management server; Further provided with The second fee table management server When a change notification for applying the extended fee table is received from the central cooperation server, the change notification is transferred to the second regional management server; The second regional management server transfers the change notification to the second toll booth server; Upon receiving the change notification, the second toll booth server transmits a query to the central cooperation server, acquires the extended fee table from the first fee table management server via the central cooperation server, and stores the extended fee table. The toll collection system according to claim 1.

10. The toll collection system further includes a first lane server connected to the first toll booth server; When the first lane server receives vehicle information from an on-board device of a passing vehicle, the first lane server inquires about route information from the first wide area management server; the first wide area management server identifies an extended toll table number to be applied based on the route information of the vehicle and the application condition information of the extended toll table, and transmits the identified extended toll table number to the first lane server via the first toll booth server; the first lane server collects tolls from the passing vehicles using the extended fare table of the received extended fare table number from among the extended fare tables; The toll collection system according to claim 1.

11. the toll collection system further includes a first area management server and a first lane server connected to the first toll booth server; When the first lane server receives vehicle information from an on-board device of a passing vehicle via the first toll gate server, it inquires about route information from the first regional management server, the first regional management server identifies an extended fare table number to be applied based on the route information of the vehicle and the application condition information of the extended fare table, and transmits the extended fare table number to the first lane server via the first toll gate server; the first lane server collects tolls from the passing vehicles using the extended fare table of the received extended fare table number from among the extended fare tables; The toll collection system according to claim 1.

12. When it becomes necessary to adjust tolls based on traffic congestion information, a first wide-area management server under the jurisdiction of a first road operator among a plurality of wide-area management servers provided for each of a plurality of road operators creates application condition information including toll adjustment sections for the adjusted tolls, a first fee table management server connected to the first wide area management server receives application condition information of the extended fee table created by the first wide area management server, and creates an extended fee table for collecting the adjusted fee based on the application condition information; a first toll booth server installed at a first toll booth under the jurisdiction of the first road operator stores the extended toll table distributed from the first toll table management server, and collects tolls from passing vehicles using the extended toll table via a first roadside device installed at the first toll booth; a second toll gate under the jurisdiction of a second road operator different from the first road operator, which holds an extended toll table distributed from the toll table management server via an integrated cooperation server connected to the first wide area management server, and collects tolls from passing vehicles using the extended toll table via a second roadside device installed at the second toll gate; Toll collection method.

Images