JP2023030923A - Method, device, and program for managing special vehicle related information - Google Patents

Abstract

To provide a method or the like for managing special vehicle related information capable of automatically updating special vehicle related information related to a special vehicle to latest information, which includes integrally information stored in each of a vehicle layer, a vehicle supplement layer, a special vehicle application related layer, and a detection results layer, and at the same time, centrally managing the special vehicle related information.SOLUTION: A method for managing special vehicle related information that integrates information stored in each of a vehicle layer, a vehicle supplement layer, a special vehicle application related layer, and a detection results layer includes an update step for updating the special vehicle related information based on at least any of initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application related layer, and current probe information acquired from an on-vehicle device mounted on the special vehicle and probe information accumulated in the past.SELECTED DRAWING: None

Description

TECHNICAL FIELD The present invention relates to a special vehicle-related information management method, a special vehicle-related information management device, and a special vehicle-related information management program.

In recent years, with the spread of IoT (Internet of Things), a plurality of vehicle-mounted devices (for example, digital tachograph (digital tachograph), ETC 2.0, etc.) are beginning to be installed in one vehicle. However, many land transportation companies are unable to properly manage the loading status of multiple onboard units, and are unable to fully and effectively utilize the large amount of probe information (big data) acquired from multiple onboard units. There is

In addition, simple on-vehicle devices (such as GPS capture devices) are also installed in the tractor that is the tow vehicle and the towed vehicle that is connected to the head of the container vehicle (such as a trailer, the chassis of the container vehicle, etc.). In the future, it will be necessary to manage the mounting status of such GPS capture devices and utilize probe information obtained from the GPS capture devices.

On the other hand, when a special vehicle specified in Article 47-2 of the Road Act (hereinafter sometimes referred to as a "special vehicle") is to travel on the road, an application for special vehicle traffic permission must be made to the road administrator. , it is necessary to obtain a special vehicle traffic permit. However, many road transport companies do not adequately manage the acquisition of special vehicle permits for tow and towed vehicles, and do not adequately match the optimum tow and towed vehicles. There is a problem that it is not

An object of the present invention is to solve the above-mentioned conventional problems and to achieve the following objects. That is, the present invention can automatically update the special vehicle related information about the special vehicle by integrating the information stored in the vehicle layer, the vehicle supplement layer, the special vehicle application related layer, and the detection result layer to the latest information. An object of the present invention is to provide a special vehicle related information management method, a special vehicle related information management device, and a special vehicle related information management program capable of centrally managing special vehicle related information.

Means for solving the above problems are as follows. Namely
<1> A method of managing special vehicle-related information related to a special vehicle that integrates information stored in a vehicle layer, a vehicle supplemental layer, a special vehicle application related layer, and a detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
An update step of updating the special vehicle-related information based on at least one of the current probe information acquired from the vehicle-mounted device mounted on the special vehicle and the past accumulated probe information,
A method for managing special vehicle-related information, characterized by including
<2> The special vehicle is equipped with a first vehicle-mounted device and a second vehicle-mounted device,
From the current probe information, the first vehicle-mounted ID in the first probe information obtained from the first vehicle-mounted device, and the second vehicle-mounted ID in the second probe information obtained from the second vehicle-mounted device If the first vehicle-mounted ID and the second vehicle-mounted ID exist in the same vehicle table or the same tractor table in the vehicle layer, update the latest verification date and time of the vehicle table or the tractor table. , the method for managing special vehicle-related information according to <1>.
<3> When the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same vehicle table or the same tractor table, the first vehicle-mounted ID and the The second vehicle-mounted ID is identified, and if the first vehicle-mounted ID and the second vehicle-mounted ID exist in the same vehicle table or the same tractor table, the vehicle table or the tractor table Update the latest verification date and time,
When the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same single vehicle table or the same tractor table, mismatch information is output to a mismatch information table in the detection result layer, The method for managing special vehicle-related information according to <2>, wherein matching information is fed back.
<4> The special vehicle is equipped with a first vehicle-mounted device and a third vehicle-mounted device,
From the current probe information, the first vehicle-mounted ID in the first probe information obtained from the first vehicle-mounted device, and the third vehicle-mounted ID in the third probe information obtained from the third vehicle-mounted device The vehicle number of the tractor table in the vehicle layer corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table in the vehicle layer corresponding to the third vehicle-mounted ID are specified in the special vehicle application relation layer. The method for managing special vehicle-related information according to <1> above, wherein when included in the same connectable group ID of the vehicle breakdown table, the latest verification date and time of the consolidation study table in the vehicle supplement layer is updated.
<5> The vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID belong to the same connectable group ID of the vehicle description table. If not included, the first vehicle-mounted ID and the third vehicle-mounted ID are specified from the probe information accumulated in the past, and the vehicle number of the tractor table corresponding to the first vehicle-mounted ID and , if the vehicle number in the trailer table corresponding to the third in-vehicle ID is included in the same connectable group ID in the vehicle description table, updating the latest verification date and time in the consolidation study table;
The vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID are not included in the same connectable group ID of the vehicle description table. In this case, the method for managing special vehicle-related information according to <4>, wherein inconsistent information is output to an inconsistent information table in the detection result layer, and the inconsistent information is fed back.
<6> The special vehicle is equipped with at least one of the first vehicle-mounted device, the second vehicle-mounted device, and the third vehicle-mounted device, and from the current probe information, acquired from the first vehicle-mounted device First in-vehicle ID in the first probe information, the second in-vehicle ID in the second probe information obtained from the second vehicle-mounted device, and the third in the third probe information obtained from the third vehicle-mounted device specifying at least one of three vehicle-mounted IDs, and a vehicle table and a tractor table in the vehicle layer corresponding to at least one of the first vehicle-mounted ID, the second vehicle-mounted ID, and the third vehicle-mounted ID; and the special vehicle-related information management method according to any one of <1> to <5>, including the latest position information acquisition step of acquiring the latest position information from at least one of the position information and the latest date and time of the trailer table. be.
<7> Management of special vehicle-related information according to <6> above, including a matching step of matching a truck and a trailer with the shortest required time and distance from the departure point to the destination based on the latest position information. The method.
<8> A device for managing special vehicle-related information related to a special vehicle that integrates information stored in a vehicle layer, a vehicle supplementary layer, a special vehicle application related layer, and a detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
Updating means for updating the special vehicle related information based on at least one of the current probe information acquired from the vehicle-mounted device mounted on the special vehicle and the past accumulated probe information,
It is a management device for special vehicle related information characterized by having
<9> A program for managing special vehicle-related information related to special vehicles that integrates the information stored in the vehicle layer, vehicle supplement layer, special vehicle application related layer, and detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
Processing of updating the special vehicle related information based on at least one of the current probe information and the past accumulated probe information acquired from the vehicle-mounted device mounted on the special vehicle,
is a management program for special vehicle-related information characterized by causing a computer to perform

According to the present invention, the above-mentioned problems in the conventional art can be solved and the above-mentioned objects can be achieved. Special vehicle-related information management method, special vehicle-related information management device, and special vehicle-related information management program capable of automatically updating special vehicle-related information to the latest information and centrally managing special vehicle-related information can be provided.

FIG. 1 is a schematic diagram illustrating specific aspects (1) to (4) of the "connectable group ID" in the vehicle description table of the special vehicle application related layer. FIG. 2 is a schematic diagram showing an example of the mounting position of the in-vehicle D or in-vehicle G1 in each vehicle. FIG. 3 is a diagram showing the container chassis and container head classified according to the presence/absence of vehicle-mounted equipment. FIG. 4 is a schematic diagram showing an example of the mounting position of the in-vehicle D or in-vehicle G2 in each vehicle. FIG. 5 is a diagram in which motorcycles and heads are classified according to the presence or absence of on-vehicle equipment. FIG. 6 is a schematic diagram for explaining the so-called "set" state in the present invention. FIG. 7 is a diagram showing an example of special vehicle-related information in a special vehicle. FIG. 8 is a diagram for explaining the relationship between the information in the motorcycle/tractor/trailer table, the information in the vehicle inspection table, and the information in the consolidation examination document table. FIG. 9 is a flow chart showing an example of the flow of processing for updating special vehicle related information by the special vehicle related information management method of the present invention. FIG. 10 is a diagram showing an example of the hardware configuration of the special vehicle-related information management device of the present invention. FIG. 11 is a diagram showing an example of the functional configuration of the special vehicle-related information management device of the present invention. FIG. 12A is a flowchart showing the flow of processing for matching an optimum truck and trailer in the first embodiment (No. 1). FIG. 12B is a flowchart showing the flow of processing for matching an optimum truck and trailer in the first embodiment (No. 2). FIG. 13 is a diagram showing a delivery method using an optimum combination of trucks and trailers from a factory in Miyazaki Prefecture to Miyazaki Port in the first embodiment. FIG. 14 is a diagram showing a delivery method using an optimal combination of trucks and trailers from factories in Miyazaki Prefecture and prefecture border municipalities to Miyazaki Port in Example 2. In FIG.

(Management method of special vehicle-related information and management device of special vehicle-related information)
A method for managing special vehicle-related information according to the present invention is a method for managing special vehicle-related information related to a special vehicle by integrating information stored in a vehicle layer, a vehicle supplement layer, a special vehicle application-related layer, and a detection result layer. and initial registration information in the table included in the vehicle layer, the table included in the vehicle supplement layer, and the table included in the special vehicle application relationship layer, and the current acquired from the vehicle-mounted device mounted on the special vehicle At least one of the probe information and the past accumulated probe information, and an update step of updating the special vehicle related information based on and other steps.

A special vehicle related information management device of the present invention is a device for managing special vehicle related information related to a special vehicle that integrates information stored in a vehicle layer, a vehicle supplement layer, a special vehicle application related layer, and a detection result layer. and initial registration information in the table included in the vehicle layer, the table included in the vehicle supplement layer, and the table included in the special vehicle application relationship layer, and the current acquired from the vehicle-mounted device mounted on the special vehicle based on at least one of the probe information and past accumulated probe information, update means for updating the special vehicle related information, and the latest position information acquisition means and matching means. have other means as necessary.

The special vehicle-related information management method of the present invention can be preferably carried out by the special vehicle-related information management device of the present invention, the updating step can be performed by the updating means, and the latest position information acquiring step can be performed by the latest position information acquisition means, the matching step can be performed by the matching means, and the other steps can be performed by the other means.

In the special vehicle-related information management method and the special vehicle-related information management device of the present invention, the information stored in the vehicle layer, the vehicle supplement layer, the special vehicle application relation layer, and the detection result layer are integrated. The special vehicle related information can be automatically updated to the latest information, and the special vehicle related information can be centrally managed.

<<Special vehicle>>
A special vehicle (special vehicle) is a vehicle that has a special structure or a vehicle that transports cargo that exceeds the general limits of any of width, length, height and gross weight. , bridges, elevated roads, tunnels, etc., vehicles that exceed either gross weight or height limits.

Vehicles with special structures include, for example, self-propelled construction machines such as truck cranes, five special types of trailer-coupled vehicles (van type, tank type, hood frame type, for containers, for transporting automobiles), Additional 3 types of type, stanchion type, ship bottom type etc. can be mentioned. The special 5 car models and the additional 3 car models are called the 8 special car models.
Examples of vehicles that transport special cargo include construction machinery, large generators, train bodies, utility poles, and the like that exceed any of the general limit values because they cannot be divided.

<< Special vehicle related information >>
The special vehicle related information integrates the information stored in the four layers of <Vehicle Layer>, <Vehicle Supplementary Layer>, <Special Vehicle Application Layer>, and <Detection Result Layer> shown in Table 1 below. This is information about special vehicles that
The four layers have respective tables shown in Table 1 below.

(1) Vehicle Layer The vehicle layer stores various information related to special vehicles.
Tables included in the vehicle layer include, for example, [single vehicle table], [tractor (towing vehicle) table], and "trailer table (hereafter referred to as a trailer on behalf of the towed vehicle)". The tables may be collectively referred to as [motorcycle/tractor/trailer table].

(2) Vehicle Supplementary Layer The vehicle supplementary layer stores information about special vehicles other than the information stored in the vehicle layer.
Tables included in the vehicle supplemental layer include, for example, [vehicle inspection table] and [consolidated examination document table].

(3) Special vehicle application-related layer Tables included in the special vehicle application-related layer include, for example, [special vehicle application main table], [special vehicle application (vehicle breakdown) (hereinafter referred to as "vehicle breakdown" ) table].

(4) Detection Result Layer Tables included in the detection result layer include, for example, [mismatch information table].

<Vehicle layer>
As a vehicle layer, the following Table 2 shows a [motorcycle/tractor/trailer table] in which information about a motor vehicle, a tractor, and a trailer is summarized. These pieces of information are statically registered at the initial stage (operation start, vehicle addition, special vehicle application/change).

[motorcycle, tractor, trailer table]

The features of the digital tachograph (digital tachograph), GPS capture device, and ETC 2.0 as onboard equipment in Table 2 are as shown in Table 3 below.

Digital tachographs (sometimes abbreviated as "digi tachographs") are developed by the Automobile Bureau of the Ministry of Land, Infrastructure, Transport and Tourism and the Ministry of Health, Labor and Welfare in collaboration to visualize the working conditions of truck and bus operators and make it obligatory to acquire operation records. , certifies equipment. About 20 private companies ship certified equipment, for example, Transtron Co., Ltd., Yazaki Energy System Co., Ltd., and the like. In the present invention, a digital tachograph manufactured by Transtron Co., Ltd., which is strong against the cloud type, is used, but it is not particularly limited as long as it is the cloud type. Note that the digital tachograph is powered, and the GPS acquisition interval is 1 second.

GPS capture devices only work when they are being towed, such as when there is no power supply or when the vehicle being towed (trailer, container car chassis, double connection), etc. In recent years, understanding location information has become an issue for logistics companies. there is Therefore, several private companies have started commercialization. In addition, the GPS capture device is not supplied with power, and the GPS acquisition interval can be changed from 5 seconds to 1 hour for each application in relation to the battery life.

In ETC 2.0, the Road Bureau of the Ministry of Land, Infrastructure, Transport and Tourism has been standardizing ETC on-board equipment since it is subject to tolls on expressways. It is a mechanism that uploads the data accumulated in the on-board unit when the vehicle passes through the area. ETC 2.0 has a power supply, a GPS acquisition interval of 200 m, and a cumulative change in the traveling direction of 45°. About 10 private companies are shipping certified equipment, such as Panasonic Corporation, which is currently promoting the introduction of a highway discount system for logistics companies.

<Vehicle Supplementary Layer>
As vehicle supplementary layers, there are [Vehicle inspection table] in Table 4 below and [Consolidated examination document table] in Table 5 below. The information in these tables is statically registered at the initial stage (operation start, vehicle addition, special vehicle application/change).

[Vehicle inspection table]
The vehicle inspection table shown in Table 4 below has "vehicle number" as a linking key.

＊表５中「連結可能グループＩＤ」は、以下に説明する＜特車申請関係レイヤ＞を管轄するキーである。 [Consolidation study table]
The consolidation review document table shown in Table 5 below has the "chassis number" of the towing vehicle and the "chassis number" of the towed vehicle as a linking key.

* "Connectable group ID" in Table 5 is a key that governs the <special vehicle application related layer> described below.

< Special vehicle application related layer >
In the special vehicle application related layer, as the information registered at the initial stage (at the time of special vehicle application processing or update processing), for the "permission number" assigned to the special vehicle application form, ""connectable group ID" is assigned.
In the special vehicle application related layer, [special vehicle application main table] that manages the main part of the special vehicle application information shown in Table 6 below, and "vehicle number" belonging to the "special vehicle application main part table" shown in Table 7 below Prepare a [vehicle breakdown table] that manages

[Special car application table]
The [special car application main table] shown in Table 6 below uses "connectable group ID" as a jurisdiction key.

[Vehicle breakdown table]
The [Vehicle Description Table] shown in Table 7 below manages the "Vehicle Number" using the "Connectable Group ID" as a jurisdiction key.
In addition, it is also possible to use the "representative vehicle number" of the "special vehicle online application manual" (Ministry of Land, Infrastructure, Transport and Tourism Road Bureau, All Japan Trucking Association) as the jurisdiction key. However, if the "representative vehicle number" is used as a jurisdiction key, the effect of change is large when the corresponding special vehicle is scrapped. was newly established.

Here, a specific aspect of the "connectable group ID" in the [vehicle breakdown table] of the <special vehicle application related layer> will be described.
As shown in FIG. 1, there are four possible forms of the "connectable group ID", namely, "connectable group ID" (1) to "connectable group ID" (4).
There is a [vehicle description table] in which the "tractor" is in the shape of ● or the "trailer" is in the shape of ▲.
Case 1: As a standard case, different groups are formed such as "connectable group ID" (1) and "connectable group ID" (2).
Case 2: There may be partially overlapping tractors or trailers, such as "connectable group ID" (1) and "connectable group ID" (3).
Case 3: It does not matter if there is a complete inclusive relationship between "connectable group ID" (2) and "connectable group ID" (4). However, "connectable group ID" (4) is normally useless, so it is desirable to delete it.

<Detection result layer>
In the detection result layer, inconsistency information detected as inconsistent from the results of analyzing the initially registered information and the probe information acquired during daily operation is shown in Table 8 below [Inconsistency information table] , and feeds back the inconsistency information.

[Inconsistency information table]

表９の不整合情報の検出種が「１」の場合としては、初期登録されている＜車両レイヤ＞の［単車テーブル］上の「車両番号」における「デジタコ－ＩＤ」又は「ＥＴＣ２．０－ＩＤ」と、日常運用時に取得したプローブ情報及び半年毎程度のサイクルで累積したプローブ情報から特定した「デジタコ－ＩＤ」又は「ＥＴＣ２．０－ＩＤ」とが不一致の場合であり、原因として単車の車載器の載替が考えられる。 [Example of remounting the on-board unit of a motorcycle]
Table 9 below shows an example of remounting of on-vehicle equipment (digital tachograph or ETC 2.0) for motorcycles.

If the detection type of the inconsistency information in Table 9 is "1", the "digitacho-ID" or "ETC2.0- ID” and the “digitacho-ID” or “ETC2.0-ID” specified from the probe information acquired during daily operation and the probe information accumulated in a cycle of about half a year do not match, and the cause is the motorcycle. It is possible to replace the on-board equipment.

表１０の不整合情報の検出種が「２」の場合としては、初期登録されている＜車両レイヤ＞の［トラクタテーブル］上の「車両番号」における「デジタコ－ＩＤ」又は「ＥＴＣ２．０－ＩＤ」と、日常運用時に取得したプローブ情報及び半年毎程度のサイクルで累積したプローブ情報から特定した「デジタコ－ＩＤ」又は「ＥＴＣ２．０－ＩＤ」とが不一致の場合であり、原因としてトラクタの車載器の載替が考えられる。 [Example of remounting a tractor on-board unit]
Table 10 below shows an example of remounting of a tractor vehicle-mounted device (digital tachograph or ETC 2.0).

If the detection type of the inconsistency information in Table 10 is "2", the "digitacho-ID" or "ETC2.0- ID” and the “digitacho-ID” or “ETC2.0-ID” specified from the probe information obtained during daily operation and the probe information accumulated in a cycle of about every six months do not match, and the cause is the tractor. It is possible to replace the on-board equipment.

表１１の不整合情報の検出種が「６」の場合としては、日常運用時に取得したプローブ情報及び半年毎程度のサイクルで累積したプローブ情報から特定した「デジタコ－ＩＤ」及び「ＧＰＳ捕捉機－ＩＤ」に対応するトラクタの「車両番号」及びトレーラの「車両番号」の組み合わせが、＜特車申請関係レイヤ＞の［車両内訳書テーブル］上の「連結可能グループＩＤ」に含まれない場合であり、原因として特車申請漏れが考えられる。 [Example of failure to apply for a special car]
Table 11 below shows an example of omission of a special car application.

In the case where the detection type of inconsistency information in Table 11 is "6", the "digitacho-ID" and "GPS capture device- If the combination of the tractor's "vehicle number" and the trailer's "vehicle number" corresponding to the "ID" is not included in the "connectable group ID" on the [vehicle breakdown table] of the <special vehicle application related layer> There is, and the omission of special car application can be considered as the cause.

<Renewal process and means of renewal>
The update process includes initial registration information in the table included in the vehicle layer, the table included in the vehicle supplement layer, and the table included in the special vehicle application related layer, and the on-vehicle equipment installed in the special vehicle. A step of updating the special vehicle-related information based on at least one of current probe information and past accumulated probe information, and is performed by an updating means.

The current probe information is real-time probe information acquired at predetermined transmission intervals from each vehicle-mounted device mounted on a special vehicle.
The past accumulated probe information is big data in which current probe information acquired in real time is accumulated for a predetermined period. The predetermined period is not particularly limited and can be appropriately selected according to the purpose, and is, for example, about half a year.

In one aspect of the present invention, the special vehicle is equipped with a first vehicle-mounted device and a second vehicle-mounted device, and from the current probe information, in the first probe information acquired from the first vehicle-mounted device A first vehicle-mounted ID and a second vehicle-mounted ID in the second probe information acquired from the second vehicle-mounted device are specified, and the first vehicle-mounted ID and the second vehicle-mounted ID are the vehicle layer When existing in the same vehicle table or the same tractor table in , it is preferable to update the latest verification date and time of the vehicle table or the tractor table. According to this aspect, from the current probe information, it is determined that the specified first vehicle-mounted ID and second vehicle-mounted ID exist in the same single vehicle table or the same tractor table in the vehicle layer, that is, they are "integral". can be verified.

Examples of the first vehicle-mounted device include a digital tachograph.
Examples of the second vehicle-mounted device include ETC 2.0.
The same single vehicle table or the same tractor table in the vehicle layer is as shown in Table 2 above.

In one aspect of the present invention, when the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same vehicle table or the same tractor table, the first vehicle-mounted ID is determined from past accumulated probe information. The vehicle-mounted ID and the second vehicle-mounted ID are identified, and if the first vehicle-mounted ID and the second vehicle-mounted ID exist in the same vehicle table or the same tractor table, the vehicle table or updating the latest verification date and time of the tractor table, and if the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same motorcycle table or the same tractor table, inconsistency information in the detection result layer; It is preferable to output inconsistency information to a table and feed back said inconsistency information. According to this aspect, from the probe information accumulated in the past, the specified first vehicle-mounted ID and second vehicle-mounted ID exist in the same single vehicle table or the same tractor table in the vehicle layer ("integral"), or Non-existence (not “same”) can be verified.

The mismatch information table in the detection result layer is as shown in Table 8 above.
Feedback of inconsistency information includes, for example, displaying a warning message on the screen, outputting a warning sound, and outputting a warning message.

In one aspect of the present invention, the special vehicle is equipped with a first vehicle-mounted device and a third vehicle-mounted device, and from the current probe information, in the first probe information acquired from the first vehicle-mounted device A first vehicle-mounted ID and a third vehicle-mounted ID in third probe information acquired from the third vehicle-mounted device are identified, and a vehicle number of a tractor table in the vehicle layer corresponding to the first vehicle-mounted ID. and the vehicle number in the trailer table in the vehicle layer corresponding to the third in-vehicle ID are included in the same connectable group ID in the vehicle description table in the special vehicle application relation layer, the vehicle supplement layer It is preferable to update the latest verification date and time of the consolidated consideration document table in . According to this aspect, from the current probe information, the vehicle number of the tractor table and the vehicle number of the trailer table corresponding to the specified first vehicle-mounted ID and the third vehicle-mounted ID are the vehicle breakdown table in the special vehicle application relationship layer It can be verified that they are included in the same connectable group ID, that is, they are a "set".

Examples of the first vehicle-mounted device include a digital tachograph.
Examples of the third vehicle-mounted device include a GPS capture device.
The single vehicle table or tractor table in the vehicle layer is as shown in Table 2 above.
The vehicle description table in the special vehicle application related layer is as shown in Table 7 above.

In one aspect of the present invention, the vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID are identically linked in the vehicle description table. If not included in the possible group IDs, the first vehicle-mounted ID and the third vehicle-mounted ID are specified from past accumulated probe information, and the tractor table corresponding to the first vehicle-mounted ID is identified. and the vehicle number in the trailer table corresponding to the third in-vehicle ID are included in the same connectable group ID in the vehicle description table, the latest verification date and time in the consolidation study table is updated. death,
The vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID are not included in the same connectable group ID of the vehicle description table. In this case, it is preferable to output mismatch information to a mismatch information table in the detection result layer and feed back the mismatch information. According to this aspect, from the probe information accumulated in the past, the vehicle number of the tractor table and the vehicle number of the trailer table corresponding to the specified first vehicle-mounted ID and the third vehicle-mounted ID are vehicle breakdowns in the special vehicle application related layer. It can be verified that it is contained ("set") or not contained (not "set") in the same connectable group ID of the table.

The mismatch information table in the detection result layer is as shown in Table 8 above.
Feedback of inconsistency information includes, for example, displaying a warning message on the screen, outputting a warning sound, and outputting a warning message.

As the first to third probe information, for example, as shown in Table 12 below, "vehicle ID", "travel route ID", "position (longitude, latitude)", "speed", " It includes data items such as departure date and time, departure point (longitude, latitude), arrival date and time, destination (longitude, latitude), travel distance, and required time.

The data item "vehicle ID" is data for identifying the vehicle in which the vehicle-mounted device is mounted, and is set in advance.
The data item "travel route ID" is used to identify a travel route, which is a unit of movement from a starting point to a destination with a purpose.
The data items of "date and time" and "position (longitude, latitude)" are acquired by a GPS (Global Positioning System) unit mounted on each vehicle-mounted device.
The "speed" data item is obtained from the vehicle's axles using a speed sensor that the vehicle-mounted device has, synchronized with the GPS unit.
The data items of "date and time of departure" and "place of departure (longitude, latitude)" are the date and time of departure of the travel route and the longitude and latitude of the place of departure.
The data items of "arrival date and time" and "destination (longitude, latitude)" are the arrival date and time of the travel route and the longitude and latitude of the destination.
The data item of "moving distance" is the moving distance from the starting point to the current position.
The data item "required time" is the required time from the departure point to the current location.

Here, the special vehicle is equipped with a plurality of vehicle-mounted devices, and is equipped with at least one of the first vehicle-mounted device, the second vehicle-mounted device, and the third vehicle-mounted device, and from the first vehicle-mounted device The 1st acquired probe information and the 2nd probe information acquired from the 2nd vehicle-mounted device, or the 1st probe information acquired from the 1st vehicle-mounted device and the 3rd probe information acquired from the 3rd vehicle-mounted device and are probe information related to the same special vehicle.

In order to accurately grasp the state of the above "set", as shown in FIG. are substantially identical (nearby).
The case of [a] among [a], [b], [c], and [d] in FIG. 3 is defined as "set". That is, the above-mentioned "set" means that the container head and the container chassis are combined, and the container head is equipped with an on-board D (digital tachograph), and the container chassis is equipped with an on-board G1 (GPS capture device). means if
The above "set" is said to be operated as a "set" because the container head and container chassis, which are originally separate vehicles, can be associated with the digital tachograph D and the GPS capture device G1 mounted on each. Meaning.

On the other hand, the above-mentioned "same body" can be associated with the digital tachograph (D) and ETC 2.0 (G2), which are different on-vehicle units mounted on a container head or a single car, which is originally a single car. It means that they are in the same state.
As shown in FIG. 4, each vehicle (head or motorcycle) is equipped with an on-board device D (digital tachograph) and an on-board device G2 (ETC2.0). Among [a], [b], [c], and [d] in FIG. 5, the case [a] is defined as "same body".

In the "set" or "integral" determination method, the first probe information obtained from the first vehicle-mounted device and the second probe information obtained from the second vehicle-mounted device, or the first vehicle-mounted device It is determined that the first probe information and the third probe information obtained from the third vehicle-mounted device are probe information relating to the same moving body. For example, when there are "first probe information D" and "second probe information G1 or G2", the installation position is generally on-board due to the purpose and characteristics of the on-board probe that acquires the probe information. It is usually determined by the design of the vessel. Specifically, in-vehicle D is generally mounted on the head of a container car or the front part in front of the seat of a ready-mixed concrete car, and in-vehicle G1 or G2 is generally mounted near the front of the chassis of a dump truck or container car. , and its mounting position is generally as shown in FIG.

Here, "substantially the same time" and "substantially the same position information" of the vehicle will be described.
As shown in FIG. 6, the head portion of the container car is positioned in front of the chassis portion of the container car in the traveling direction. Therefore, in the moving state, vehicle G1 passes after vehicle D passes. In addition, in the case of the head part of the container car alone, it often happens that it moves backward and joins the chassis part of the container car, but when the head part of the container car and the chassis part of the container car are combined rarely occur.

In order to fuse multiple types of probe information, it is a prerequisite to grasp the substantially same (neighborhood) of multiple vehicles. In the present invention, substantial identity (neighborhood) is determined by "spatio-temporal distance" as described below.
In probe D and probe G, which are multiple types of probes, the head part of the container car is located in front of the chassis part of the container car in the traveling direction, and when probe D is in front of probe G , the difference between probe acquisition times (time G-time D) does not take a negative value.
Therefore, the spatio-temporal distance is defined by Equation 1 below. One second of longitude and latitude is approximately 25 m.

[Formula 1]

For example, the position information X1 at the time X in the first probe information and the position information X2 at substantially the same time as the time X in the second probe information different from the second probe information are substantially and the position information Y1 at the time Y sampled next to the time X in the first probe information and the time Y in the second probe information are substantially the same When the position information Y2 at time is substantially the same is represented by a spatiotemporal distance, the spatiotemporal distance between the first probe information and the second probe information is positive or zero, and the spatiotemporal distance are considered to be substantially identical (neighboring). Specifically, the spatio-temporal distance between the first probe information and the second probe information in the moving state is preferably 1.5 (seconds/seconds) or less, and is 1.0 (seconds/seconds) or less. It is more preferable to have

Next, the information stored in the special vehicle related information includes, for example, (i) static information registered at the beginning, (ii) dynamic information verified in daily operation, (iii) There are information updated in near-real time, and (iv) information fed back as correction information candidates as detection results in a cycle of about every six months.

Static information that is initially registered is the table included in the <Vehicle layer>, the table included in the <Vehicle supplement layer>, the <Special are stored in the table included in the <vehicle application relation layer> and the table included in the <detection result layer>.
Information verified in daily operations is dynamically collected and automatically updated in order to ensure and verify the consistency and up-to-dateness of special vehicle-related information integrated during daily operations. In addition, in order to grasp the latest position information of the vehicle, the "position information" and "latest date and time" in the [motorcycle/truck/trailer table] of the <vehicle layer> are sequentially updated during daily operation.

Here, in the special vehicle related information shown in FIG. > to statically register information.

As shown in FIG. 7, during verification during daily operation, information is automatically updated in the <vehicle layer> and the <special vehicle application-related layer> based on the acquired probe information. Specifically, in the probe information acquired during daily operation, the digital tachograph and ETC 2.0 in the motorcycle and tractor are in the same state, and the tractor and trailer are in the same connectable group ID of the [vehicle breakdown table]. Collect and verify information on the "set" state of the GPS capture device, and if it is verified that it is properly in the "integrated" state or "set" state, automatically enter the [single vehicle table] of the <vehicle layer> Alternatively, update the "latest verification date and time" of the "Tractor table" and the [Consolidated review document table] of the <special vehicle application related layer>.

In addition, during daily operation, the "location information" and "latest date and time" of the probe information acquired by each on-vehicle device of the digital tacho, ETC 2.0, and GPS capture device are displayed as "latest date and time" as shown in FIG. location information”.

In addition, as shown in FIG. 7, past probe information accumulated in a cycle of about half a year is analyzed to detect and feed back inconsistent information such as not in the "integrated" state or in the "set" state.
For example, in the [motor vehicle table] or [tractor table] in the <vehicle layer>, if the digitach-ID and the ETC2.0-ID are registered on the same vehicle but they are not in the "same" state, then as inconsistent information Visualize and give feedback.
Also, as shown in FIG. 7, it was detected that the digitachor-ID and GPS capture device-ID were not registered on the [vehicle description table] of the <special vehicle application-related layer>, but that they were in a "set" state. In this case, it is output as inconsistency information of <detection result layer> and fed back.

<Integration and automatic updating of special vehicle-related information>
Referring to FIG. 8, the information of the "motorcycle/tractor/trailer table" in Table 2 in the above <vehicle layer> and the [vehicle inspection table] in Table 4 and Table 5 [consolidation review document in the <vehicle supplementary layer> Table] information and processing will be described.

As shown in FIG. 8, the vehicle number in the [motorcycle/tractor/trailer table] of Table 2 that matches the "vehicle number" of "Miyazaki 100 or 1111" in the [vehicle inspection table] of Table 4 is retrieved. Then, "Miyazaki 100 or 1111" is found for the "vehicle number" in the [tractor table] of Table 2, and from the [tractor table], the "vehicle number" is "Miyazaki 100 or 1111" and the "chassis number" is "SH1EDX-1234.""It can be seen that it is.
Next, when searching for the "chassis number" in the [Consolidation study table] in Table 5, where the "chassis number" matches "SH1EDX-1234", the chassis number "SH1EDX-1234" of the "towing vehicle" is found. From the [Consolidated review table] in 5, it can be seen that the chassis number of the "towed vehicle" is "CTB34003-666", and the chassis number of the "towed vehicle" is "SH1EDX-1234" and the chassis number of the "towed vehicle". It can be seen that the “connectable group ID” with “CTB34003-666” is “T-00001-12345”.

<Update processing of special vehicle related information>
FIG. 9 is a flowchart showing an example of the flow of processing for updating special vehicle-related information. Hereinafter, with reference to Table 2, Table 5, Table 7, Table 8, etc., the flow of processing for updating the special vehicle related information will be described.

In step S1, when each probe information is collected and analyzed from a plurality of vehicle-mounted devices mounted on a special vehicle during daily operation, the process proceeds to S2.

In step S2, it is determined whether or not each acquired probe information is digital tachograph and ETC 2.0. shifts the process to S8.

In step S3, "digitacho-ID" is specified from the acquired probe information of the digitacho, and "ETC2.0-ID" is specified from the acquired probe information of ETC2.0, and then the process proceeds to S4.

In step S4, it is determined whether or not the specified "digitacho-ID" and "ETC2.0-ID" both exist in the same [motorcycle table] or the same [tractor table] of the <vehicle layer>, If it exists in the same [motorcycle table] or the same [tractor table], the process goes to S5, and if it does not exist in the same [motorcycle table] or the same [tractor table], the process goes to S6. Transition.

In step S5, when the "latest verification date and time" in the [motorcycle table] or [tractor table] is updated, this processing is completed. Therefore, in the "latest verification date and time", the latest date and time when the proper state of the combination of the "digitacho-ID" and "ETC2.0-ID" in the [motorcycle table] or the [tractor table] is verified is stored.

In step S6, from the probe information accumulated in the cycle of half a year, whether the specified "digitacho-ID" and "ETC2.0-ID" both exist in the same [motorcycle table] or the same [tractor table] It is determined whether or not it exists, and if it exists, the process proceeds to S5, and if it does not exist, the process proceeds to S7.

In step S7, when the "mismatch information" in the "mismatch information table" is updated with "1" or "2", this processing ends.

In step S8, it is determined whether or not each acquired probe information is a digital tachograph and a GPS capturing device. terminates this process.

In step S9, when the "digitacho-ID" is specified from the acquired digitacho information, and the "GPS capture device-ID" is specified from the acquired GPS capture information, the process proceeds to S10.

In step S10, the specified "digitachor-ID" and "GPS capture device-ID" exist in the [tractor table] and [trailer table], and the "vehicle number" in the [tractor table] corresponding to the "digitachor-ID" , it determines whether the "vehicle number" of the [trailer table] corresponding to the "GPS capture device-ID" is included in the same "connectable group ID" of the [vehicle description table], and the same " If it is included in the "connectable group ID", the process proceeds to S11, and if it is not included in the same "connectable group ID", the process proceeds to S12.

In step S11, when the "latest verification date and time" in the [consolidated examination document table] is updated, this processing is completed. Therefore, the latest date and time when the proper state was verified is stored in the "latest verification date and time" of the [Consolidated Proposal Table].

In step S12, the specified "digitachor-ID" and "GPS capture device-ID" exist in the [tractor table] and [trailer table] from each probe information accumulated in half-year cycles, and the "digitachor-ID" The "vehicle number" of the [tractor table] corresponding to the , and the "vehicle number" of the [trailer table] corresponding to the "GPS capture device-ID" are the same "connectable group ID" of the [vehicle description table]. If it is included in the same "connectable group ID", the process proceeds to S11, and if it is not included in the same "connectable group ID", the process proceeds to S13. transition to

In step S13, when the "mismatch information" in the "mismatch information table" is updated with "6", this processing ends.

<Latest Position Information Acquisition Step and Latest Position Information Acquisition Means>
In the latest position information acquisition step, the special vehicle is equipped with at least one of the first vehicle-mounted device, the second vehicle-mounted device, and the third vehicle-mounted device, and from the current probe information, the first 1st vehicle-mounted ID in the 1st probe information acquired from vehicle-mounted device, 2nd vehicle-mounted ID in the 2nd probe information acquired from said 2nd vehicle-mounted device, and 3rd acquired from said 3rd vehicle-mounted device identifying at least one of a third in-vehicle ID in the probe information of the vehicle layer in the vehicle layer corresponding to at least one of the first in-vehicle ID, the second in-vehicle ID, and the third in-vehicle ID This is a step of acquiring the latest position information from the position information and the latest date and time of at least one of the table, tractor table, and trailer table, and is carried out by the latest position information acquisition means.

Examples of the first vehicle-mounted device include a digital tachograph.
Examples of the second vehicle-mounted device include ETC 2.0.
Examples of the third vehicle-mounted device include a GPS capture device.
A single vehicle table, a tractor table, or a trailer table in the vehicle layer is as shown in Table 2.

From the current probe information, the "location information" and "latest date and time" of the probe information acquired by the first to third on-board equipment mounted on the special vehicle are added to the special vehicle-related Save to "Latest location information" in <vehicle layer> of information. Table 13 below shows the correspondence between each vehicle-mounted device and each table of <vehicle layer>.

"Latest location information" is specified from the probe information obtained from the digital tachograph, ETC2.0, and GPS capture device, and Based on this, "location information" and "latest date and time" in "digital tacho-ID" of the [motorcycle/tractor/trailer table] shown in Table 1, "location information" and "latest date and time" in "ETC2.0-ID", " The "location information" and "latest date and time" in "GPS capture device-ID" are updated in near-real time at the transmission intervals shown in Table 13.
Note that the "positional information" in the [motorcycle/tractor/trailer table] in Table 2, for example, (32.5924072032, 131.659943987) is expressed as (32.59, 131.66) in relation to the number of digits. . Also, the "latest date and time" in the [motorcycle/tractor/trailer table] in Table 1 is expressed as (yyyymmdd.hhmmss).

<Matching step and matching means>
The matching step is a step of matching a truck and a trailer that minimize the required time and distance from the starting point to the destination based on the latest positional information obtained in the latest positional information obtaining step, and is carried out by the matching means. be.
Note that the matching process will be described in detail in Examples 1 and 2, which will be described later.

<Other steps and other means>
The other steps are not particularly limited and can be appropriately selected according to the purpose. Examples thereof include a communication step and an input step.
The other means are not particularly limited and can be appropriately selected according to the purpose. Examples thereof include communication means and input means.

The communication unit is not particularly limited as long as it can communicate with the special vehicle-related information management device, and can be appropriately known, and examples thereof include a transceiver, an information communication network, and the Internet. .

The input unit is not particularly limited as long as it can receive various requests to the special vehicle-related information management device, and any known input unit can be used as appropriate. Examples include a keyboard, mouse, touch panel, and microphone.

(Special vehicle-related information management program)
A program for managing special vehicle-related information of the present invention is a program for managing special vehicle-related information related to a special vehicle that integrates information stored in a vehicle layer, a vehicle supplement layer, a special vehicle application-related layer, and a detection result layer. and initial registration information in the table included in the vehicle layer, the table included in the vehicle supplement layer, and the table included in the special vehicle application relationship layer, and the current acquired from the vehicle-mounted device mounted on the special vehicle and at least one of the probe information and the past accumulated probe information, and causes the computer to perform a process of updating the special vehicle related information.

The special vehicle-related information management program of the present invention can be, for example, a program that causes a computer to execute the special vehicle-related information management method of the present invention. Moreover, a preferred aspect of the special vehicle-related information management program of the present invention can be the same as a suitable aspect of the special vehicle-related information management method of the present invention, for example.

The special vehicle-related information management program of the present invention can be created using various known program languages according to the configuration of the computer system to be used and the type and version of the operating system.

The special vehicle-related information management program of the present invention may be recorded on a recording medium such as an internal hard disk or an external hard disk, or may be recorded on a recording medium such as a CD-ROM, DVD-ROM, MO disk, or USB memory. You may keep a record.
Furthermore, when recording the special vehicle related information management program of the present invention on the above recording medium, it can be used directly or by installing it on a hard disk through a recording medium reading device of the computer system as necessary. can do. Further, the management program for special vehicle-related information of the present invention may be recorded in an external storage area (another computer, etc.) accessible from the computer system through an information communication network. In this case, the special vehicle-related information management program of the present invention recorded in the external storage area can be used directly from the external storage area through an information communication network or by installing it on a hard disk if necessary. .
The special vehicle-related information management program of the present invention may be divided and recorded on a plurality of recording media for each arbitrary process.

<Computer-readable recording medium>
A computer-readable recording medium relating to the present invention records the special vehicle-related information management program of the present invention.
The computer-readable recording medium related to the present invention is not particularly limited and can be appropriately selected according to the purpose. memory and the like.
Further, the computer-readable recording medium according to the present invention may be a plurality of recording media in which the special vehicle-related information management program of the present invention is divided for each arbitrary process and recorded.

An example of the technology disclosed in the present invention will be described below in further detail using an example of the configuration of an apparatus.
FIG. 10 shows a hardware configuration example of the special vehicle-related information management device of the present invention.
In the special vehicle related information management device 100 of the present invention, for example, the control unit 101, the main storage device 102, the auxiliary storage device 103, the I/O interface 104, the communication interface 105, the input device 106, the output device 107, the display device 108 are connected via a system bus 109 .

The control unit 101 performs operations (four arithmetic operations, comparison operations, etc.), operation control of hardware and software, and the like. The control unit 101 may be, for example, a CPU (Central Processing Unit), a part of a machine used in the method of managing special vehicle-related information of the present invention, or a combination thereof.
The control unit 101 implements various functions by executing a program (for example, a special vehicle-related information management program according to the present invention) read into the main storage device 102 or the like.
The processing performed by the update means (update unit) in the special vehicle related information management apparatus of the present invention can be performed by the control unit 101, for example.

The main storage device 102 stores various programs, as well as data necessary for executing the various programs. As the main memory device 102, for example, one having at least one of ROM (Read Only Memory) and RAM (Random Access Memory) can be used.
The ROM stores, for example, various programs such as BIOS (Basic Input/Output System). Moreover, the ROM is not particularly limited and can be appropriately selected according to the purpose. Examples thereof include mask ROM and PROM (Programmable ROM).
The RAM functions, for example, as a working range in which various programs stored in the ROM, auxiliary storage device 103, etc. are developed when the control unit 101 executes them. The RAM is not particularly limited and can be appropriately selected depending on the purpose. Examples thereof include DRAM (Dynamic Random Access Memory) and SRAM (Static Random Access Memory).

The auxiliary storage device 103 is not particularly limited as long as it can store various types of information, and can be appropriately selected according to the purpose. Examples thereof include a solid state drive (SSD) and a hard disk drive (HDD). Further, the auxiliary storage device 103 may be a portable storage device such as a CD drive, DVD drive, BD (Blu-ray (registered trademark) Disc) drive.
A management program for special vehicle-related information of the present invention is stored in, for example, the auxiliary storage device 103 , loaded into the RAM (main memory) of the main storage device 102 , and executed by the control unit 101 .

The I/O interface 104 is an interface for connecting various external devices. The I/O interface 104 is, for example, CD-ROM (Compact Disc ROM), DVD-ROM (Digital Versatile Disk ROM), MO disk (Magneto-Optical disk), USB memory [USB (Universal Serial Bus) flash drive], etc. data input/output.

The communication interface 105 is not particularly limited, and any known one can be used as appropriate, such as a wireless or wired communication device.

The input device 106 is not particularly limited as long as it can receive various requests and information input to the special vehicle related information management device 100 of the present invention, and can be appropriately known devices such as a keyboard, mouse, A touch panel, a microphone, etc. are mentioned. Also, when the input device 106 is a touch panel (touch display), the input device 106 can also serve as the display device 108 .

The output device 107 is not particularly limited, and any known device can be used as appropriate, such as a printer.
The display device 108 is not particularly limited, and any known device can be used as appropriate. Examples thereof include a liquid crystal display and an organic EL display.

FIG. 11 shows an example of the functional configuration of the special vehicle-related information management device of the present invention.
As shown in FIG. 11, the special vehicle-related information management device 100 of the present invention includes a communication function unit 120, an input function unit 130, an output function unit 140, a display function unit 150, a storage function unit 160, and a control function unit 170 .

The communication function unit 120, for example, transmits and receives various data to and from an external device. For example, the communication function unit 120 may receive data such as vehicle attribute data and travel performance data from an external device.
The input function unit 130 receives, for example, various instructions to the special vehicle-related information management device 100 of the present invention. Also, the input function unit 130 receives, for example, a plurality of pieces of probe information.
The output function unit 140 prints out, for example, the result of determining that the probe information is related to the special vehicle related information.
The display function unit 150 displays, for example, the result of determination as probe information related to special vehicle-related information on the display.

The storage function unit 160 stores various programs, for example, and has a special vehicle related information DB 161 and a matching result DB 162 .
Special vehicle related information DB161 is DB which preserve|saves the information currently preserve|saved at the table of a vehicle layer, a vehicle supplement layer, a special vehicle application relation layer, and a detection result layer. Specifically, it is a DB that stores the information shown in Tables 2 and 4 to 8.

The matching result DB 162 is a DB that stores the results of matching performed by the special vehicle-related information management device.

The control function unit 170 has an updating unit 171 as updating means and a matching unit 172 as matching means. The control function unit 170 executes, for example, various programs stored in the storage function unit 160, and controls the operation of the entire special vehicle-related information management device 100 of the present invention.

The update unit 171 updates initial registration information in the vehicle layer, the vehicle supplement layer, the special vehicle application related layer, and the detection result layer, probe information acquired from the current special vehicle, and past accumulated special vehicles. Based on at least one of the probe information, a process for automatically updating the special vehicle related information is performed.
The matching unit 172 performs matching processing of the towing vehicle and the towed vehicle that minimize the required time and distance to the destination. Details of the matching process will be described in first and second embodiments.

Examples of the present invention will be described below, but the present invention is not limited to these examples.

(Example 1)
<Matching process for optimum combination of tractor and trailer>
12A and 12B are flowcharts showing the flow of processing for matching the optimum combination of truck and trailer in the first embodiment. Hereinafter, the flow of processing for matching the optimum combination of truck and trailer will be described with reference to FIG. 13, Tables 2, 4, 5 and 6.

First, based on a prior contract, a trailer with a "trailer table" "type" of "CTB34003" is to be used from the factory in Miyazaki prefecture shown in FIG. 13 to Miyazaki Port (ferry terminal).

In step S11, a trailer whose "model" is "CTB34003" in the [trailer table] of <vehicle layer> is searched to determine whether or not there is a trailer with a status of "0" (waiting). If there is a trailer with a status of "0" (standby) and a "type" of "CTB34003", the trailer is specified and the process proceeds to S12. On the other hand, if there is no trailer with a status of "0" (standby) and a model of "CTB34003", matching is not possible, and this process ends.

In step S12, based on the "vehicle number" of the [trailer table] of the specified trailer, it is determined whether or not the "valid period" of the [vehicle inspection table] of the <vehicle supplement layer> is before n days before the vehicle inspection expires. If it is before n days before vehicle inspection expires, the process proceeds to S13, and if it is after n days before vehicle inspection expires, the process returns to S1. It should be noted that the setting of n days before the end of vehicle inspection can be appropriately determined by operation, and is, for example, n=6.

In step S13, based on the "chassis number" of the [trailer table] of the identified trailer, the "connectable group ID" (for example, T-000001-12345) of the [consolidation study table] of the <vehicle supplement layer> is set. Once specified, the process proceeds to S14.

In step S14, based on the "connectable group ID" (T-000001-12345) specified in step 13, the "traffic end date" of the [special vehicle application main table] of the <special vehicle application related layer> , it is determined whether or not it is before m days before the passage permit expires. Processing ends.
It should be noted that the setting of m days before m days before the passage permit expires can be appropriately determined by operation, for example, m=30.

In step S15, based on the "connectable group ID" (T-000001-12345) specified in step S13, the "shape" of the "vehicle breakdown table" of the <special vehicle application related layer> and the "tractor" It is determined whether an object exists or not, and if an object whose "shape" is "tractor" exists, the process proceeds to S16. On the other hand, if there is no object whose "shape" is "tractor", matching is not possible, so this process ends.

In step S16, the tractors selected in step S15 are listed, and if this is designated as "tractor list 1", the process proceeds to step S17.

In step S17, based on the "connectable group ID" (T-000001-12345) specified in step S13, the "shape" of the "vehicle breakdown table" of the <special vehicle application related layer> is "trailer". exists, and if there is one whose "shape" is "trailer", the process proceeds to S18.
On the other hand, if the "shape" is "trailer" does not exist, matching is not possible, so this processing ends.

In step S18, the trailers selected in step S17 are listed, and if this is designated as "trailer list 1", the process proceeds to step S19.

In step S19, for the "tractors" existing in the "tractor list 1" created in step S16, based on the "vehicle number", the "status" of the [tractor table] of <vehicle layer> is set to "0" (waiting ) and whether or not there is a tractor whose vehicle inspection expired before n days before exists in the "valid period" of the [Vehicle Supplementary Layer] [Vehicle Inspection Table]. to S20. It should be noted that the setting of n days before the end of vehicle inspection can be appropriately determined by operation, and is, for example, n=6.
On the other hand, if the "status" is "0" (waiting) and there is no tractor before n days before the vehicle inspection expires in the "valid period" of the [vehicle inspection table] of the <vehicle supplement layer>, matching is not possible. Therefore, this processing ends.

In step S20, the tractors selected in step S19 that are n days before the expiration of the vehicle inspection are listed.

In step S21, for the "trailer" existing in the "trailer list 1" created in step S18, based on the "vehicle number", the "status" of the [trailer table] of <vehicle layer> is set to "0" (waiting ), and in the "Validity Period" of the [Vehicle Supplementary Layer] [Vehicle Inspection Table], it is determined whether or not there is a trailer whose vehicle inspection expires n days ago or earlier. The process proceeds to S22. It should be noted that the setting of n days before the end of vehicle inspection can be appropriately determined by operation, and is, for example, n=6.
On the other hand, if the "status" is "0" (waiting) and the "validity period" of the [vehicle inspection table] of the <vehicle supplement layer> does not include a trailer before n days before the vehicle inspection expires, matching is not possible. Therefore, this processing ends.

In step S22, the trailers selected in step S21 that are n days before the expiration of the vehicle inspection are listed.

In step S23, for the "tractor" existing in the "tractor list 2" created in step S20, based on the "vehicle number", from the "digitacho-ID position information" in the [tractor table] of <vehicle layer> to " It is determined whether or not the tractor exists in "Miyazaki Prefecture", and if the tractor exists in "Miyazaki Prefecture", the process proceeds to S24.
On the other hand, if the tractor does not exist within "Miyazaki Prefecture" based on the "positional information of the digitacho-ID", matching is not possible, and this process ends.

In step S24, the tractors existing in "Miyazaki Prefecture" selected in step S23 are listed.

In step S25, for the "trailer" existing in the "trailer list 2" created in step S22, based on the "vehicle number", "position information of GPS capture device-ID" in the [trailer table] of <vehicle layer> If the trailer exists in "Miyazaki Prefecture", the process proceeds to S26.
On the other hand, if the trailer does not exist in "Miyazaki Prefecture" based on the "GPS capture device-ID position information", this process ends because matching is not possible.

In step S26, trailers existing in "Miyazaki Prefecture" selected in step S25 are listed, and if this is designated as "trailer list 3", the process proceeds to S27.

In step S27, from the combination of the "tractor list 3" created in step S24 and the "trailer list 3" created in step S26, the required time and distance from the factory in "Miyazaki Prefecture" to "Miyazaki Port" are calculated. When the shortest tractor-trailer combination is identified, this process ends.

At the beginning of steps S15 and S17, all tractors and trailers that have a special vehicle application permit that is the "connectable group ID" (T-000001-12345) are extracted as list 1. List 2 and List 3 are obtained by narrowing down List 1 with each extraction condition. Specific results are shown in Table 14.

表１４の結果から、リスト３では、トラクタが１台、トレーラが３台該当する。これらの４台が、図１３に示す位置に存在しており、その詳細な位置情報は表１５に示すとおりである。

From the results in Table 14, List 3 corresponds to one tractor and three trailers. These four units exist at the positions shown in FIG. 13, and their detailed position information is shown in Table 15.

Here, in FIG. 13, for example, the flow of the case where the trailer 3 is used is indicated by a solid line. First, travel from Miyazaki City, Miyazaki Prefecture, where the tractor 1 exists, to Nichinan City, Miyazaki Prefecture, where the trailer 3 exists [I], pull the trailer 3 to Nobeoka City, Miyazaki Prefecture, where the factory is located [II], and load. After that, it becomes a flow of [III] to transport to Miyazaki Port, and Table 13 shows the required time and distance. The required time and distance can be calculated using a commonly used route search engine.
Similar to Trailer 3, Trailer 1 and Trailer 2 were also tested, and the required time and distance were obtained. The results are shown in Table 16.

表１６の結果から、所要時間及び距離が最も少ないトレーラ１とトラック１とが最適な組み合わせであるとしてマッチングされる。

From the results of Table 16, the trailer 1 and the truck 1, which require the shortest required time and distance, are matched as the optimum combination.

(Example 2)
In Example 1, the matching result required more than 2 hours and 30 minutes. Specifically, steps after step S23 were performed again.
In steps S23 and S25, as shown in FIG. 14, the matching target area "within Miyazaki Prefecture" is expanded to include "Miyazaki Prefecture and prefectural border municipalities" to create list 3. As shown in Table 17, the tractor 2 and 3 trailers.

From the results of Example 1, the trailer is narrowed down to trailer 1, so the case where tractor 2 (Saiki City, Oita Prefecture; border city between Oita Prefecture and Miyazaki Prefecture) is used is indicated by a solid line in FIG.
As shown in FIG. 14, the vehicle travels from Saiki City, Oita Prefecture, where the tractor 2 is present, to Nobeoka City, Miyazaki Prefecture, where the trailer 1 is present [I], and travels to a factory in Nobeoka City, Miyazaki Prefecture by pulling the trailer 1 [I]. II], and then transport it to Miyazaki Port after loading [III]. Detailed location information is shown in Table 18. In addition, Table 19 shows the results of obtaining the required time and distance.

表１９の結果から、所要時間が２時間３０分間以内となる、大分県佐伯市内に存在するトラクタ２と宮崎県延岡市内に存在するトレーラ１とが最適な組み合わせであるとマッチングされる。

From the results of Table 19, the tractor 2 located in Saiki City, Oita Prefecture and the trailer 1 located in Nobeoka City, Miyazaki Prefecture are matched as the optimum combination, which requires less than 2 hours and 30 minutes.

100 special vehicle related information management device 101 control unit 102 main storage device 103 auxiliary storage device 104 I/O interface 105 communication interface 106 input device 107 output device 108 display device 109 system bus 120 communication function unit 130 input function unit 140 output function Part 150 Display function part 160 Storage function part 161 Special car related information DB
162 Matching result DB
170 control function unit 171 update unit 172 matching unit

Claims (9)

A method for managing special vehicle-related information about a special vehicle that integrates information stored in a vehicle layer, a vehicle supplement layer, a special vehicle application related layer, and a detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
An update step of updating the special vehicle-related information based on at least one of the current probe information acquired from the vehicle-mounted device mounted on the special vehicle and the past accumulated probe information,
A method for managing special vehicle-related information, comprising: The special vehicle is equipped with a first vehicle-mounted device and a second vehicle-mounted device,
From the current probe information, the first vehicle-mounted ID in the first probe information obtained from the first vehicle-mounted device, and the second vehicle-mounted ID in the second probe information obtained from the second vehicle-mounted device If the first vehicle-mounted ID and the second vehicle-mounted ID exist in the same vehicle table or the same tractor table in the vehicle layer, update the latest verification date and time of the vehicle table or the tractor table. , The method for managing special vehicle-related information according to claim 1. When the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same vehicle table or the same tractor table, the first vehicle-mounted ID and the second vehicle-mounted ID are determined from past accumulated probe information. is specified, and if the first vehicle ID and the second vehicle ID exist in the same motorcycle table or the same tractor table, the latest verification date and time of the motorcycle table or the tractor table and update
When the first vehicle-mounted ID and the second vehicle-mounted ID do not exist in the same single vehicle table or the same tractor table, mismatch information is output to a mismatch information table in the detection result layer, 3. The method for managing special vehicle-related information according to claim 2, wherein matching information is fed back. The special vehicle is equipped with a first vehicle-mounted device and a third vehicle-mounted device,
From the current probe information, the first vehicle-mounted ID in the first probe information obtained from the first vehicle-mounted device, and the third vehicle-mounted ID in the third probe information obtained from the third vehicle-mounted device The vehicle number of the tractor table in the vehicle layer corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table in the vehicle layer corresponding to the third vehicle-mounted ID are specified in the special vehicle application relation layer. 2. The method of managing special vehicle-related information according to claim 1, wherein, when included in the same connectable group ID of the vehicle breakdown statement table, the latest verification date and time of the consolidated examination statement table in the vehicle supplement layer is updated. The vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID are not included in the same connectable group ID of the vehicle description table. In this case, from the probe information accumulated in the past, the first vehicle-mounted ID and the third vehicle-mounted ID are identified, and the vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the third vehicle-mounted ID are identified. if the vehicle number of the trailer table corresponding to the in-vehicle ID of No. 3 is included in the same connectable group ID of the vehicle description table, updating the latest verification date and time of the consolidated examination document table;
The vehicle number of the tractor table corresponding to the first vehicle-mounted ID and the vehicle number of the trailer table corresponding to the third vehicle-mounted ID are not included in the same connectable group ID of the vehicle description table. 5. The management method of special vehicle-related information according to claim 4, wherein inconsistent information is output to an inconsistent information table in said detection result layer, and said inconsistent information is fed back. The special vehicle is equipped with at least one of the first vehicle-mounted device, the second vehicle-mounted device, and the third vehicle-mounted device, and from the current probe information, the first acquired from the first vehicle-mounted device The first vehicle-mounted ID in the probe information, the second vehicle-mounted ID in the second probe information obtained from the second vehicle-mounted device, and the third vehicle-mounted in the third probe information obtained from the third vehicle-mounted device A single vehicle table, a tractor table, and a trailer table in the vehicle layer that specify at least one of the IDs and correspond to at least one of the first vehicle-mounted ID, the second vehicle-mounted ID, and the third vehicle-mounted ID. 6. The method for managing special vehicle-related information according to any one of claims 1 to 5, comprising a latest position information acquiring step of acquiring the latest position information from at least one of the position information and the latest date and time. 7. The method for managing special vehicle-related information according to claim 6, further comprising a matching step of matching a truck and a trailer that minimize the required time and distance from the departure point to the destination based on the latest position information. A device for managing special vehicle-related information related to a special vehicle that integrates information stored in a vehicle layer, a vehicle supplemental layer, a special vehicle application related layer, and a detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
Updating means for updating the special vehicle related information based on at least one of the current probe information acquired from the vehicle-mounted device mounted on the special vehicle and the past accumulated probe information,
A management device for special vehicle-related information, comprising: A program for managing special vehicle-related information about a special vehicle that integrates information stored in a vehicle layer, a vehicle supplement layer, a special vehicle application related layer, and a detection result layer,
Initial registration information in a table included in the vehicle layer, a table included in the vehicle supplement layer, and a table included in the special vehicle application relationship layer;
Processing of updating the special vehicle related information based on at least one of the current probe information and the past accumulated probe information acquired from the vehicle-mounted device mounted on the special vehicle,
A management program for special vehicle-related information, characterized by causing a computer to perform.

Images