Road-state evaluation system

Abstract

The present invention makes it possible to evaluate the state of a road at a low cost.　A road-state evaluation system 10 comprises: an acquisition unit 11 that acquires evaluation-use information that includes information related to paving a road to be evaluated; and an evaluation unit 12 that, on the basis of the evaluation-use information acquired by the acquisition unit 11, evaluates the state of the road to be evaluated.

Description

Road Condition Assessment System

[0001] The present invention relates to a road condition evaluation system for evaluating the condition of a road.

[0002] Social infrastructure, which was developed intensively during the period of high economic growth, is rapidly aging and posing an increasing safety risk. Roads are the largest part of social infrastructure. Municipal roads, which account for 97.2% of roads, are facing a growing sense of crisis regarding repairs due to cost reductions and labor shortages. Preventive maintenance is important to ensure that roads can be used for a long time in a cost-effective manner, and it is essential to determine the optimal timing for repairs by predicting deterioration.

[0003] Conventionally, it has been proposed to evaluate the condition of a road for preventive maintenance of the road, etc. For example, Patent Document 1 proposes detecting the condition of a road based on information from a vehicle.

[0004] Japanese Patent Application Laid-Open No. 2021-36455

[0005] In the method disclosed in Patent Document 1, in order to evaluate road conditions, a device for acquiring information to be used for the evaluation must be installed in a vehicle at the time of evaluation, and the vehicle must be driven. Furthermore, other conventional road condition evaluations also require the accumulation of road inspection data to be used for the evaluation. Thus, conventional road condition evaluations have required high costs.

[0006] An embodiment of the present invention has been made in view of the above, and has an object to provide a road condition evaluation system that can evaluate the condition of a road at low cost.

[0007] In order to achieve the above-mentioned object, a road condition evaluation system according to one embodiment of the present invention comprises an acquisition unit that acquires evaluation information including information related to the paving implementation of the road to be evaluated, and an evaluation unit that evaluates the condition of the road to be evaluated based on the evaluation information acquired by the acquisition unit.

[0008] In a road condition evaluation system according to one embodiment of the present invention, the condition of a road to be evaluated is evaluated based on evaluation information including information related to the paving implementation of the road to be evaluated. Information related to the paving implementation of a road is usually prepared when the road is paved, and therefore can be obtained at low cost. Therefore, the road condition evaluation system according to one embodiment of the present invention makes it possible to evaluate the condition of a road at low cost.

[0009] According to one embodiment of the present invention, road conditions can be evaluated at low cost.

[0010] It is a diagram showing the configuration of a road condition evaluation system according to an embodiment of the present invention. It is a table showing an example of information used in the road condition evaluation system. It is a flowchart showing processing executed in the road condition evaluation system according to an embodiment of the present invention. It is a diagram showing the hardware configuration of the road condition evaluation system according to an embodiment of the present invention.

[0011] Hereinafter, an embodiment of a road condition evaluation system according to the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals and duplicated explanations will be omitted.

[0012] FIG. 1 shows a road condition evaluation system 10 according to this embodiment. The road condition evaluation system 10 is a system (device) that evaluates the condition of a road. The evaluation of the road condition also includes prediction of the road condition. The roads that are the subject of evaluation by the road condition evaluation system 10 are paved roads. The road condition evaluation system 10 evaluates, for example, the deterioration of the road (pavement), more specifically, the lifespan (expected lifespan) of the road (pavement). The evaluation results by the road condition evaluation system 10 are used, for example, by local governments or road administrators to make decisions regarding road repairs, specifically, to determine whether or not repairs are necessary and when. The evaluation results by the road condition evaluation system 10 may also be used for purposes other than those described above.

[0013] The road condition evaluation system 10 is configured by a computer such as a PC (personal computer) or a server device. The road condition evaluation system 10 may be configured by multiple computers. The road condition evaluation system 10 may be capable of transmitting and receiving information to and from other devices via a network in order to obtain information necessary to realize its functions.

[0014] Next, the functions of the road condition evaluation system 10 according to this embodiment will be described. As shown in FIG.

[0015] The acquisition unit 11 is a functional unit that acquires evaluation information (information used for evaluation) including information related to the paving implementation of the road to be evaluated. The acquisition unit 11 may acquire evaluation information including information indicating at least one of the paving configuration, paving material, and paving contractor of the road to be evaluated, as information related to the paving implementation of the road to be evaluated. The acquisition unit 11 may acquire evaluation information including information indicating the planned traffic volume at the time of paving the road, as information related to the paving implementation of the road to be evaluated.

[0016] The information on road pavement implementation included in the evaluation information is, for example, information on the pavement that became clear when the road pavement was implemented, and is information related to road evaluation (information that can be used to evaluate the road). For example, information stored in a public database related to road pavement can be used as information on road pavement implementation. Specifically, information stored in the National Road Facility Inspection Database, a road data platform developed primarily by the Ministry of Land, Infrastructure, Transport and Tourism, can be used as this information. The National Road Facility Inspection Database is open data. The National Road Facility Inspection Database stores a large amount of data on public roads.

[0017] The information related to this embodiment among the information stored in the national road facility inspection database is shown in Figure 2. As shown in Figure 2, the national road facility inspection database includes an inspection results database, a pavement configuration database, and a pavement design database.

[0018] Of the above databases, the information stored in the pavement configuration DB and the pavement design DB corresponds to information related to the implementation of road paving. The inspection result DB stores information indicating the inspection results of the road. By using the information stored in the inspection result DB, the road condition can be evaluated (using a method different from the evaluation by the road condition evaluation system 10). However, information about all roads is not stored in the inspection result DB. The road condition evaluation system 10 evaluates the condition of roads for which information is not stored in the inspection result DB using the information stored in the pavement configuration DB and the pavement design DB. Note that, as described below, the information stored in the inspection result DB may be used for evaluation by the road condition evaluation system 10.

[0019] The inspection results DB, pavement configuration DB, and pavement design DB store information on a road section (division) basis, such as the latitude and longitude of the section or information for each section identified by the road's kilometer post. In other words, the information stored in the inspection results DB, pavement configuration DB, and pavement design DB corresponds to a road section. The road condition evaluation system 10 can determine the correspondence between the information stored in the inspection results DB, pavement configuration DB, and pavement design DB and the road section. The pavement configuration DB stores the following information: first layer - construction date, first layer - material code, first layer - thickness, contractor name, second layer - material code, and second layer - thickness. Generally, a pavement (asphalt pavement) includes two layers: a first layer (surface layer) and a second layer (base layer).

[0020] The above-mentioned "first layer_laying date" is the date when the first layer was laid. When used in the road condition evaluation system 10, "first layer_laying date" is information in the format of [YYYYMM], for example. "first layer_material code" is a code indicating the material of the first layer. When used in the road condition evaluation system 10, "first layer_material code" is information in the format of a categorical variable or a design matrix, for example. "first layer_thickness" is the thickness of the first layer. When used in the road condition evaluation system 10, "first layer_thickness" is a value in units of [mm], for example. "contractor name" is the name of the contractor who carried out (constructed) the pavement. When used in the road condition evaluation system 10, "contractor name" is information in the format of a categorical variable or a design matrix, for example. "second layer_material code" is a code indicating the material of the second layer. When used in the road condition evaluation system 10, "second layer_material code" is information in the format of a categorical variable or a design matrix, for example. The second layer_thickness is the thickness of the second layer. When used in the road condition evaluation system 10, the second layer_thickness is expressed in units of, for example, mm.

[0021] The pavement design DB stores information on pavement plan traffic volume categories. Normally, when a road is paved, the traffic volume of the road is estimated. The pavement plan traffic volume category is a category (one of a plurality of categories preset according to the level of traffic volume) that indicates the estimated traffic volume of the road. When used in the road condition evaluation system 10, the pavement plan traffic volume category is information in the form of, for example, a categorical variable, a factor variable, or a design matrix.

[0022] The acquisition unit 11 acquires, as evaluation information for the road to be evaluated, information on the first layer material code and contractor name from the pavement configuration DB, as well as information on the pavement plan traffic volume classification from the pavement design DB. The acquisition unit 11 may acquire this information, for example, from a national road facility inspection database, or may acquire this information by accepting input of this information into the road condition evaluation system 10 by a user who has acquired this information from the national road facility inspection database. The acquisition unit 11 may also acquire information other than the above as evaluation information for the road to be evaluated. For example, the acquisition unit 11 may acquire information on the first layer thickness, second layer material code, and second layer thickness from the pavement configuration DB.

[0023] Of the above information, the information on first layer_thickness and second layer_thickness corresponds to information indicating the pavement configuration of the road being evaluated. The information on first layer_material code and second layer_material code corresponds to information indicating the pavement material of the road being evaluated. The information on contractor name corresponds to information indicating the contractor of the road being evaluated. The information on pavement plan traffic volume category is information indicating the planned traffic volume when the road being evaluated is paved.

[0024] When acquiring information from the nationwide road facility inspection database, the acquisition unit 11 may convert each piece of information into the above-described format used in the road condition evaluation system 10. Alternatively, the acquisition unit 11 may acquire information whose format has already been converted. The conversion of the information format may be performed by a conventional method.

[0025] The acquisition unit 11 also acquires information on the first layer_date of construction from the pavement configuration DB for the road to be evaluated. The acquisition unit 11 also acquires information indicating the timing of the evaluation. The information indicating the timing of the evaluation is, for example, in the same format as the first layer_date of construction (year and month in the above example). The acquisition unit 11 acquires information indicating the timing of the evaluation by, for example, accepting an input operation from a user to the road condition evaluation system 10. Alternatively, the acquisition unit 11 may use a time-lapse function provided in the road condition evaluation system 10 to acquire information indicating the current time as information indicating the timing of the evaluation. From this information, the acquisition unit 11 calculates the elapsed time (for example, the number of years elapsed, expressed in years) from the time the road was paved to the time of the evaluation as evaluation information for the road to be evaluated. The acquisition unit 11 sets the elapsed time as the timing of the evaluation minus the first layer_date of construction.

[0026] The acquisition unit 11 may acquire the above-mentioned information by a method other than the above. Furthermore, the information related to the implementation of paving of the road to be evaluated, which is included in the evaluation information acquired by the acquisition unit 11, does not necessarily have to be the above-mentioned information, and may be information related to the implementation of paving other than the above.

[0027] The acquisition unit 11 may also acquire information other than the above as the evaluation information. The acquisition unit 11 may also acquire information related to the road other than information related to the implementation of road paving as the evaluation information in addition to information related to the implementation of road paving. For example, the acquisition unit 11 may acquire information on the 24-hour traffic volume [vehicles] and large vehicle inclusion rate [%] of the road at the time of evaluation as the evaluation information. Furthermore, the traffic volume information may be traffic volume information estimated using base station statistical data (spatial statistical data from mobile communications) owned by a telecommunications carrier.

[0028] Furthermore, the (type of) information used as evaluation information may be selected in advance using existing technology so as to increase the accuracy of the evaluation. Furthermore, when evaluation is performed for multiple roads, the acquisition unit 11 acquires evaluation information for each road to be evaluated. The acquisition unit 11 outputs the acquired evaluation information to the evaluation unit 12.

[0029] The evaluation unit 12 is a functional unit that evaluates the condition of the road to be evaluated based on the evaluation information acquired by the acquisition unit 11. The evaluation unit 12 may evaluate the lifespan of the road as the condition of the road to be evaluated. The evaluation unit 12 may evaluate the condition of each of multiple roads included in the area to be evaluated, and evaluate the condition of the roads in the entire area from the conditions of each of the multiple evaluated roads. The evaluation unit 12 performs the evaluation, for example, as follows.

[0030] The evaluation unit 12 inputs the evaluation information from the acquisition unit 11. The evaluation unit 12 evaluates the road's lifespan, for example, as described above, from the input evaluation information. The road's lifespan is, for example, the length of time from the time of evaluation to the time when the road being evaluated needs repair. Specifically, for example, the road's lifespan is the length of time (for example, a value in years) from the time of evaluation to the time when the road's MCI (Maintenance and Control Index) reaches a value that requires repair. The MCI has a maximum value of 10.0 and is a value that decreases as the road condition deteriorates. Note that the road condition evaluated by the evaluation unit 12 may be something other than the road's lifespan, as long as it can be evaluated from the evaluation information.

[0031] MCI is calculated, for example, by the following formula and method: Flatness=(IRIValue-0.24) / 1.33 mci1=10.0-1.48×CrackValue ０．３ -0.29 x Root Value ０．７ -0.47 x Flatness ０．２ mci2=10.0-1.51×CrackValue ０．３ -0.30 x Root Value ０．７ mci3=10.0-2.23×CrackValue ０．３ mci4=10.0-0.54×RutValue ０．７ The minimum value among mci1 to mci4 is defined as MCI.

[0032] In the above, Flatness is the value of the flatness of the road. IRIValue is the value of the IRI (International Roughness Index) of the road. CrackValue is the value of the crack rate of the road. RutValue is the value of the rutting of the road. The calculation of the MCI above is based on the method shown in Ueno Shinichiro, 7. Survey on IRI (International Roughness Index) on Prefectural Roads, 2014, Annual Report of the Tokyo Metropolitan Civil Engineering Technical Support and Human Resources Development Center, pp. 73-84.

[0033] Even if it is not possible to obtain values ​​for calculating the MCI for the road to be evaluated, such as the IRI value, crack rate value, and rutting value of the above-mentioned road, the evaluation unit 12 can evaluate the condition of the road from the evaluation information.

[0034] The evaluation unit 12 stores evaluation criteria for evaluation using evaluation information in advance, and performs evaluation using the evaluation criteria. For example, the evaluation unit 12 stores an evaluation model that inputs evaluation information, which is an explanatory variable, and outputs an evaluation result, which is a target variable. The evaluation model is, for example, a model (learning and prediction model) that is an ANN (artificial neural network) generated by machine learning. The ANN may be a feedforward neural network. The ANN may be multi-layered, i.e., generated by deep learning.

[0035] For example, in the evaluation model, the input layer is provided with neurons for inputting each piece of evaluation information acquired by the acquisition unit 11. In addition, in the evaluation model, the output layer is provided with neurons for outputting the value of the road lifespan, which is the evaluation result.

[0036] An evaluation model is generated by machine learning, for example, as follows. First, learning data (teacher data) to be used for machine learning is acquired. The learning data is data about roads from which a lifespan corresponding to the evaluation result, which is the output of the evaluation model, can be calculated and from which information corresponding to the evaluation information can be acquired. As described above, the road lifespan is calculated based on the MCI. The MCI can be calculated using information stored in the inspection result DB shown in FIG. 2. Therefore, the road related to the learning data can be a road whose information is stored in the inspection result DB.

[0037] The inspection result DB stores information such as the inspection date and year, crack measurement values, rutting measurement values, and IRI measurement values. The inspection date and year is the date and year when the road inspection was performed. When used to generate an evaluation model, the inspection date and year is information in the format of [YYYYMM], for example. The crack measurement value is the measurement value of the crack rate of the road measured by inspection. When used to generate an evaluation model, the crack measurement value is a value in units of [%], for example. The rutting measurement value is the measurement value of rutting of the road measured by inspection. When used to generate an evaluation model, the rutting measurement value is a value in units of [mm], for example. The IRI measurement value is the measurement value of the IRI of the road measured by inspection. When used to generate an evaluation model, the IRI measurement value is a value in units of [mm / m], for example.

[0038] To generate an evaluation model, each piece of information from the inspection result DB is acquired for the road related to the learning data. Furthermore, information similar to the evaluation information acquired by the acquisition unit 11 is acquired for the road related to the learning data. However, the elapsed time in the evaluation information acquired by the acquisition unit 11 for the road related to the learning data is the elapsed time from the time the road was paved to the time the inspection was performed (for example, the number of years elapsed, expressed in years). In this case, the elapsed time is the inspection date - first layer installation date.

[0039] The MCI at the time of inspection is calculated using the above formula and method from the crack measurement values, rutting measurement values, and IRI measurement values ​​in the acquired inspection result DB. Note that the MCI calculation may be performed using a method other than the above formula and method depending on the information used for the calculation. Next, assuming that the MCI at the time the road was paved was 10.0, the MCI change rate (MCI change rate) (e.g., the value of MCI decrease per year) is calculated from the above elapsed time and the MCI at the time of inspection. Next, using the MCI change rate, the length of time from the time of inspection to the time when repair is necessary as the road's lifespan (e.g., a value in years) is calculated as the road's lifespan. For example, the MCI value at the time when repair is necessary is set as a threshold, and the length of time from the MCI value at the time of inspection until the MCI value reaches the threshold is calculated. The threshold is set to, for example, 4.5. That is, when the MCI changes according to the calculated MCI change rate, the length of time (e.g., a value in years) from the value at the time of inspection until the MCI value reaches the threshold value is calculated as the road lifespan. Note that the assumed MCI value at the time the road is paved does not need to be 10.0 as described above, and may be any reasonable assumed value (e.g., 9.0).

[0040] As learning data, information similar to the evaluation information and the road lifespan are acquired and calculated for each road. In addition, a sufficient number of pieces of such information are acquired and calculated to generate an evaluation model.

[0041] In addition, data cleansing may be performed when acquiring and calculating the learning data. For example, outliers may be excluded. Specifically, for example, for the first layer_laying year and month, values ​​before January 1950 are excluded. For crack measurement values, values ​​equal to or greater than 100.0 are excluded. For rutting measurement values, values ​​equal to or greater than 50.0 are excluded. For IRI measurement values, values ​​equal to or greater than 50.0 are excluded. For elapsed time, values ​​equal to or less than 0 are excluded. For MCI values, values ​​equal to or less than 0 are excluded. For MCI change rates, values ​​less than 0.22 or greater than 2.2 are excluded. For road lifespan, values ​​equal to 0 are excluded. Information about roads that include excluded information may not be included in the learning data. In addition, data cleansing may be performed in a similar manner to that described above when the evaluation unit 12 evaluates roads. In this case, roads related to the excluded information may be excluded from the evaluation targets.

[0042] Next, to generate an evaluation model, information similar to the evaluation information as learning data is input to the evaluation model, and information on the road lifespan is used as the output of the evaluation model to perform machine learning. The above machine learning is performed for each combination of information similar to the evaluation information and the road lifespan, i.e., for each road. The machine learning itself, i.e., the updating of the ANN parameters, is performed in the same manner as conventional machine learning.

[0043] The above-mentioned evaluation model, which is a trained model used in the road condition evaluation system 10, is expected to be used as a program module that is part of artificial intelligence software. The model is used, for example, in a computer having a CPU (Central Processing Unit) and memory, and the CPU of the computer operates according to instructions from the model stored in the memory. For example, the CPU of the computer operates to input information to the evaluation model in accordance with the instructions, perform calculations according to the evaluation model, and output results from the evaluation model. Specifically, the CPU of the computer operates to input information to the input layer of the ANN in accordance with the instructions, perform calculations based on trained weighting coefficients in the ANN, and output results from the output layer of the ANN.

[0044] The above is the generation of an evaluation model by machine learning. The generation of an evaluation model by machine learning may be performed by the road condition evaluation system 10 or by a system (apparatus) other than the road condition evaluation system 10.

[0045] The evaluation unit 12 inputs the evaluation information received from the acquisition unit 11 into the evaluation model, performs calculations according to the evaluation model, and obtains a value indicating the lifespan of the road, which is output from the evaluation model. Note that the evaluation criteria for evaluation using the evaluation information do not necessarily have to be the evaluation model described above, and may be anything that can evaluate the condition of the road to be evaluated based on the evaluation information.

[0046] The evaluation unit 12 may also evaluate the condition of each of a plurality of roads. In this case, the evaluation unit 12 may evaluate the condition of the roads in the entire area to be evaluated based on the condition of each of the evaluated roads. The area to be evaluated is, for example, an administrative division such as a prefecture or a city, ward, town, or village. The area to be evaluated may also be something other than that. In this case, the evaluation unit 12 is configured to know to which area the road to be evaluated belongs. For example, the evaluation unit 12 acquires information relating to the association between roads and areas.

[0047] For example, the evaluation unit 12 may calculate the sum or average of the evaluation results of the roads included in the area to determine the road condition of the entire area. The evaluation unit 12 may also calculate the average of the evaluation results weighted according to the length of the road to determine the road condition of the entire area. Alternatively, the evaluation unit 12 may evaluate the road condition of the entire area to be evaluated from the conditions of each of the multiple roads using a method other than those described above.

[0048] The evaluation unit 12 outputs information indicating the evaluation result of the road condition. For example, the evaluation unit 12 transmits the information to the user's terminal. Alternatively, the evaluation unit 12 may output the information in a format that the user can recognize (for example, display or audio output). The evaluation unit 12 may also output the condition of each road or the condition of each area on a map (for example, a national map, a prefectural map, or a city, ward, town, or village map). By providing such information on a map, it is possible to visualize the road conditions across Japan, for example. The road condition evaluation system 10 according to this embodiment has been described above. The evaluation unit 12 may also output information indicating the evaluation result using a method other than the above.

[0049] Next, the process executed by the road condition evaluation system 10 according to this embodiment (the operation method performed by the road condition evaluation system 10) will be described using the flowchart of FIG. 3 . In this process, first, the acquisition unit 11 acquires evaluation information including information related to the paving implementation of the road to be evaluated (S01). Next, the evaluation unit 12 evaluates the condition of the road to be evaluated based on the evaluation information (S02). Next, the evaluation unit 12 evaluates the road condition of the entire area based on the condition of each of the multiple roads included in the area to be evaluated (S03). Next, the evaluation unit 12 outputs information indicating the evaluation result (S04). This concludes the process executed by the road condition evaluation system 10 according to this embodiment.

[0050] As described above, in this embodiment, the condition of a road to be evaluated is evaluated based on evaluation information including information related to the paving implementation of the road to be evaluated. Information related to the paving implementation of a road is usually prepared when the road is paved, and can be obtained at low cost. Therefore, according to this embodiment, the condition of a road can be evaluated at low cost. Specifically, this embodiment can evaluate the condition of a road without requiring expensive inspection data such as road surface property surveys, as in conventional deterioration prediction, and without requiring data spanning long periods such as several years. Therefore, it is possible to evaluate the condition of large-scale roads at low cost, even for municipal roads that do not have sufficient inspection data accumulated.

[0051] Furthermore, as in this embodiment, the information regarding the pavement implementation of the road to be evaluated may be information indicating at least one of the pavement structure, pavement material, and pavement contractor of the road. Alternatively, the information regarding the pavement implementation of the road to be evaluated may be information indicating the planned traffic volume at the time of paving the road. These configurations make it possible to reliably acquire evaluation information. For example, evaluation information can be reliably acquired from the above-mentioned national road facility inspection database. Furthermore, this information is appropriate for evaluating the road condition. Therefore, these configurations make it possible to appropriately and reliably evaluate the road condition. However, the information regarding the pavement implementation of the road to be evaluated does not necessarily have to be the above-mentioned information; it may be any information related to the pavement implementation of the road and usable for evaluating the road condition.

[0052] Furthermore, as in this embodiment, the condition of the road to be evaluated may be the road's lifespan. The road's lifespan is useful information for long-term repair plans to achieve preventive maintenance. Therefore, with this configuration, it can be appropriately and easily used to determine, for example, whether or not repairs are necessary or when, resulting in a highly convenient evaluation result. However, the condition of the road to be evaluated does not necessarily have to be the road's lifespan.

[0053] Furthermore, as in the present embodiment, the condition of each of the multiple roads included in the area to be evaluated may be evaluated, and the road condition of the entire area may be evaluated based on the evaluated conditions of each of the multiple roads. With this configuration, it is possible to grasp the road condition of the entire area, for example, a prefecture. Furthermore, even if the accuracy of the evaluation results for individual roads is not high, the evaluation result for the entire area can be used as information that allows understanding of the road conditions for each area, resulting in a highly convenient evaluation result.

[0054] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0055] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0056] For example, the road condition evaluation system 10 according to an embodiment of the present disclosure may function as a computer that performs information processing according to the present disclosure. Fig. 4 is a diagram showing an example of the hardware configuration of the road condition evaluation system 10 according to an embodiment of the present disclosure. The above-described road condition evaluation system 10 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0057] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the road condition evaluation system 10 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0058] Each function in the road condition evaluation system 10 is realized by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via a communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0059] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, each function in the road condition evaluation system 10 described above may be realized by the processor 1001.

[0060] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, each function of the road condition evaluation system 10 may be implemented by a control program stored in the memory 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0061] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for performing information processing according to an embodiment of the present disclosure.

[0062] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The storage medium provided in road condition evaluation system 10 may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0063] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0064] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0065] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0066] The road condition evaluation system 10 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0067] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0068] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0069] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0070] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0071] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0072] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0073] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0074] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0075] Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information.

[0076] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0077] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0078] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0079] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0080] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0081] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0082] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0083] The road condition evaluation system disclosed herein has the following configuration. [1] A road condition evaluation system comprising: an acquisition unit that acquires evaluation information including information related to the paving implementation of a road to be evaluated; and an evaluation unit that evaluates the condition of the road to be evaluated based on the evaluation information acquired by the acquisition unit. [2] The road condition evaluation system described in [1], wherein the acquisition unit acquires evaluation information including information indicating at least one of the pavement configuration, paving material, and paving contractor of the road to be evaluated as information related to the paving implementation of the road to be evaluated. [3] The road condition evaluation system described in [1] or [2], wherein the acquisition unit acquires evaluation information including information indicating the planned traffic volume at the time of paving the road to be evaluated as information related to the paving implementation of the road to be evaluated. [4] The road condition evaluation system described in any of [1] to [3], wherein the evaluation unit evaluates the lifespan of the road as the condition of the road to be evaluated. [5] The road condition evaluation system described in any of [1] to [4], wherein the evaluation unit evaluates the condition of each of multiple roads included in the area to be evaluated and evaluates the condition of the roads in the entire area from the conditions of each of the evaluated roads.

[0084] 10...road condition evaluation system, 11...acquisition unit, 12...evaluation unit, 1001...processor, 1002...memory, 1003...storage, 1004...communication device, 1005...input device, 1006...output device, 1007...bus.

Claims

1. A road condition evaluation system comprising: an acquisition unit that acquires evaluation information including information related to the pavement implementation of the road to be evaluated; and an evaluation unit that evaluates the condition of the road to be evaluated based on the evaluation information acquired by the acquisition unit.

2. A road condition evaluation system as described in claim 1, wherein the acquisition unit acquires evaluation information including information indicating at least one of the pavement structure, pavement material, and pavement contractor of the road to be evaluated as information relating to the pavement implementation of the road to be evaluated.

3. A road condition evaluation system as described in claim 1, wherein the acquisition unit acquires evaluation information including information indicating the planned traffic volume at the time of paving the road to be evaluated as information relating to the implementation of paving of the road to be evaluated.

4. A road condition evaluation system according to claim 1, wherein the evaluation unit evaluates the lifespan of the road as the condition of the road to be evaluated.

5. A road condition evaluation system as described in claim 1, wherein the evaluation unit evaluates the condition of each of a plurality of roads included in the area to be evaluated, and evaluates the road condition of the entire area from the evaluated conditions of each of the plurality of roads.