JP7659755B2 - Database Management Systems - Google Patents

Description

The present invention relates to a database management system.

In recent years, safe vehicle driving and autonomous driving assistance have been put into practical use, and autonomous driving is also being developed. In these systems, for example, high-precision map information required for the system is distributed from the cloud to the vehicle via a mobile base station, and is realized as a communication system that combines an on-board computer and communications. This data is stored in databases possessed by the mobile base station and the vehicle.

In safe vehicle driving, autonomous driving assistance, and autonomous driving, for example, static map data for car navigation systems that is collected, edited, and distributed once every few months to years by dedicated data collection vehicles is overlaid with data on nearby vehicles, pedestrians, and traffic signals, accident information, traffic regulation information, and other constantly changing information that is necessary for advanced safe driving assistance and autonomous driving, known as dynamic maps.

In autonomous driving and other vehicle control, the information that changes in the dynamic map is often data on a relatively small local area, since the vehicle is mainly controlled based on information in the vicinity of the vehicle. In addition, to obtain a dynamic map with higher accuracy, i.e. with more information, it is effective to expand the data by sharing the information acquired by a mobile body moving within a local area with other mobile bodies. Looking at this from the perspective of a single vehicle, it will search for and acquire the information it needs from a database distributed across a network owned by other mobile bodies.

A search method using a response accumulation device has been proposed as a method for efficiently searching database resources distributed across a network and efficiently searching for data with high evaluation value without placing a heavy load on the network or database (see JP 2000-235583 A). In this search method, a search process is first performed on a database located in a small area, and the response data accumulated in the response accumulation device, i.e., the number of valid pieces of information, is counted by a response counter. Then, if it is determined that the predetermined number of response data cannot be obtained from this small area, a search of a wider range is performed from the search device via a communication device.

JP 2000-235583 A

For example, in the case of an autonomous vehicle, if there is a fallen object on the road in the direction in which the vehicle is moving, information about the fallen object is information that the vehicle must obtain before reaching the fallen object. Depending on the distance between the vehicle and the fallen object, the allowable time for searching for information is thought to be on the order of several tens of milliseconds to several tens of minutes. Data with an allowable delivery delay time of several tens of milliseconds to several tens of minutes is called quasi-dynamic data or quasi-static data, depending on the allowable time.

In the above-mentioned conventional search method using a response accumulation device, if the required information is not present in the moving vehicle's own database, it is necessary to search for information on other vehicles or mobile base stations, which necessitates a search via a network. If there are many searches via the network, the time required for the search increases dramatically, and there is a risk that the above-mentioned allowable time cannot be met.

The present invention was made based on the above circumstances, and aims to provide a database management system that can efficiently handle semi-dynamic data and semi-static data required for automatic driving of vehicles, etc.

A database management system according to one aspect of the present invention is a database management system installed in a communication system having one or more local edge networks and a cloud data center, the database management system comprising a hierarchical database and a search means, the local edge networks each including one or more mobile base stations and a plurality of mobile objects connected to each other via a common wireless interface, the cloud data center configured to be able to communicate with at least one of the mobile base stations, the hierarchical database including one main database located in the cloud data center, an intermediate database directly or indirectly connected to the main database and located in the mobile base station, and a search means for ... and a terminal database, the mobile body has a sensor, and sensor information acquired by the sensor is stored as registration data of the hierarchical database in the terminal database located on the mobile body having the sensor, a copy of the registration data stored in the terminal database is stored in at least one of the intermediate databases of the local edge network to which the mobile body belongs, the intermediate database and the terminal database have a local master table including information identifying the database in which the registration data exists in the local edge network to which the mobile body belongs, and the search means identifies the intermediate database and the terminal database in which the registration data required by one mobile body is stored based on the local master table.

The database management system of the present invention can efficiently handle registered data, particularly semi-dynamic and semi-static data required for automated driving of vehicles.

FIG. 1 is a schematic configuration diagram showing a database management system according to an embodiment of the present invention. FIG. 2 is a schematic diagram showing an example of the configuration of a communication system in which the database management system of FIG. 1 is used. FIG. 3 is a schematic diagram showing the configuration of the local edge network of FIG. FIG. 4 is a schematic diagram showing the data structure of a hierarchical database in the database management system of FIG. FIG. 5 is an image diagram showing map data corresponding to a road network. FIG. 6 is a schematic data diagram showing an example of a local master table.

[Description of the embodiments of the present invention]
First, the embodiments of the present invention will be listed and described.

A database management system according to one aspect of the present invention is a database management system installed in a communication system having one or more local edge networks and a cloud data center, the database management system comprising a hierarchical database and a search means, the local edge networks each including one or more mobile base stations and a plurality of mobile objects connected to each other via a common wireless interface, the cloud data center configured to be able to communicate with at least one of the mobile base stations, the hierarchical database including one main database located in the cloud data center, an intermediate database directly or indirectly connected to the main database and located in the mobile base station, and a search means for ... and a terminal database, the mobile body has a sensor, and sensor information acquired by the sensor is stored as registration data of the hierarchical database in the terminal database located on the mobile body having the sensor, a copy of the registration data stored in the terminal database is stored in at least one of the intermediate databases of the local edge network to which the mobile body belongs, the intermediate database and the terminal database have a local master table including information identifying the database in which the registration data exists in the local edge network to which the mobile body belongs, and the search means identifies the intermediate database and the terminal database in which the registration data required by one mobile body is stored based on the local master table.

Since the database management system uses a local master table, when the search means identifies the intermediate database and the terminal database in which the registration data required by one mobile body is stored, there is no need to access a cloud data center. In addition, in the database management system, one or more mobile base stations and multiple mobile bodies are connected to each other by a common wireless interface, so the intermediate database and the terminal database can be accessed without going through a cloud data center or a mobile base station. Furthermore, in the database management system, a copy of the registration data based on the sensor information acquired by the sensor of the mobile body is present at least in the intermediate database 20 of the mobile base station 110. Therefore, it is possible to access either the terminal database in which the registration data to be acquired is present or the intermediate database. With the above configuration, the database management system can access the registration data required by one mobile body in a short time, so that the registration data, particularly the quasi-dynamic data and quasi-static data required for automatic driving of a vehicle, can be efficiently handled.

The intermediate database and the terminal database may have a data table that stores the registration data of the intermediate database or the terminal database identified by the search means. By providing the intermediate database and the terminal database with the above-mentioned data table in this way, the registration data required for each mobile unit or mobile base station can be selectively copied to this data table, thereby reducing the amount of access via the network and further improving efficiency.

The main database may have an overall master table including information identifying the database in which the registered data for the entire one or more local edge networks exists. By providing the main database with the overall master table in this way, it becomes easier to optimize the local master table. Furthermore, when there are multiple local edge networks, searches can be efficiently performed across local edge networks.

It is preferable that the system includes a communication speed estimation means for estimating the communication speed between the intermediate database and the terminal database identified by the search means, the sensor information includes metadata for estimating the communication speed, and the communication speed estimation means estimates the communication speed based on the metadata. By estimating the communication speed using the communication speed estimation means in this manner, it is possible to access the required registered data in an even shorter time.

The metadata may include at least one of the position, speed, radio wave shielding level, communication traffic, and actual communication result speed of the one mobile unit. In this way, by including at least one of the position, speed, radio wave shielding level, communication traffic, and actual communication result speed of the one mobile unit in the metadata, the accuracy of estimating the communication speed can be improved.

The moving object may include a vehicle. The database management system is particularly suitable for use in a system including a vehicle.

[Details of the embodiment of the present invention]
Hereinafter, a database management system according to an embodiment of the present invention will be described with reference to the accompanying drawings.

The database management system 1 shown in FIG. 1 includes a hierarchical database 1a, a search unit 1b, and a communication speed estimation unit 1c.

As shown in FIG. 2, the database management system 1 is installed in a communication system that includes one or more local edge networks 100 and a cloud data center 200. The following describes a communication system in which the database management system 1 is used.

[Local Edge Network]
3, each local edge network 100 includes one or more mobile base stations 110 and a plurality of moving objects 120 connected to each other via a common wireless interface. The local edge network 100 may also include a roadside unit 130.

The mobile base station 110, the multiple moving objects 120, and the roadside unit 130 are connected by a wireless interface. The wireless interface may be 5G, local 5G, 4G, DSRC (Dedicated Short Range Communications), LPWA (Low Power Wide Area), Wi-Fi, IEEE 802.11 series, ITS (Intelligent Transport System) communication interfaces, etc.

The mobile base station 110 and the multiple moving objects 120 are connected to each other via a common wireless interface. In other words, the mobile base station 110 and the multiple moving objects 120 can communicate directly between any two of them. Furthermore, communication can also be performed using one or more moving objects 120 as a repeater, such as vehicle 121-drone 122-mobile base station 110. Note that in FIG. 3, in order to avoid cluttering the drawing, only a representative portion of the communication between the two above is shown, and not all of it is shown.

<Mobile base station>
The mobile base station 110 is a base station that manages and controls a geographical area in which wireless communication is possible in the local edge network 100. Specifically, the mobile base station 110 performs data management processing and distribution control processing for a plurality of moving objects 120, for example.

The mobile base station 110 includes a main base station 111 and a local base station 112, and can communicate with mobile base stations 110 in other local edge networks 100 or with a cloud data center 200, forming a backbone network for communications.

(Main base station)
The master base station 111 supervises and controls the entire geographical range. The master base station 111 has a communication function, an intermediate database 20, and a processor. The master base station 111 may also have a sensor. By having the sensor in this way, information acquired by the master base station 111 can be used as dynamic data.

(Local base station)
The local base station 112 belongs to a lower layer than the main base station 111, and subdivides and controls the geographical area controlled by the main base station 111. For this reason, a plurality of local base stations 112 are usually provided. Conversely, if there is no need to subdivide the geographical area, the local base station 112 can be omitted, and the mobile base station 110 is composed only of the main base station 111, and directly controls the entire geographical area.

The local base station 112 has a communication function, an intermediate database 20, and a processor. The local base station 112 may also have a sensor. By having the local base station 112 have a sensor in this way, information acquired by the local base station 112 can be used as dynamic data. The local base station 112 can be, for example, a local 5G base station.

<Mobile>
The multiple mobile objects 120 are devices that move within a data sharing area (a geographical area in which wireless communication can be performed) managed by the local edge network 100 .

The multiple moving bodies 120 may include a vehicle 121, a drone 122, a mobile robot 123, a portable device 124, a bicycle 125, etc. Among these, it is preferable that the moving body 120 includes a vehicle 121. The database management system 1 can be particularly suitably used for a system including a vehicle 121, for example, a V2X communication system used for automatic driving and MaaS business. "V2X" is an abbreviation for Vehicle to X, and is a technology that collectively refers to the connection and mutual cooperation between a vehicle 121 and something (another vehicle 121, a pedestrian, infrastructure, a network, etc.). This V2X is essential for, for example, automatic driving of the vehicle 121. In the above V2X communication system, it is necessary to handle time series data having a large dynamic range in time and space acquired by the vehicle 121. The database management system 1 can handle such time series data particularly efficiently. The following description is based on the assumption that the moving body 120 includes a vehicle 121, but this does not mean that the database management system 1 requires the vehicle 121 to be a required component of the moving body 120.

The multiple moving bodies 120 each have a communication function, a terminal database 30, a processor, and a sensor 120a. Note that a "sensor" refers to an element or device that detects a phenomenon in the real world and converts the detected phenomenon into a signal that can be processed by a computer. In FIG. 1, the drone 122 is shown as having a sensor 120a, but the other moving bodies 120 also have sensors 120a, although they are not shown in the figure.

Each mobile object 120 is connected to each other, and the information collected by each other's sensor 120a is processed by the above processor and stored in the terminal database 30. The above information can include any natural phenomenon such as weather and temperature, phenomena caused by man-made objects such as traffic congestion, human vital signs such as heart rate, respiratory rate, and blood pressure, people approaching the vehicle, information on objects fallen on the road, and any information that can be detected by a sensor such as time, travel speed, and position. In the database management system 1, for example, camera images taken by the mobile robot 123, map data for driving, photographic data taken by the drone 122, and 3D shape data generated from the data are assumed.

<Roadside unit>
The roadside devices 130 are devices that are installed on roads and control and monitor the traffic of the vehicles 121. The roadside devices 130 include traffic lights, street lights, etc., and are connected to the local base station 112 via the wireless interface.

The roadside unit 130 has a communication function. In addition, it is preferable that the roadside unit 130 has a database (the intermediate database 20 or the terminal database 30), a processor, and a sensor. By having this configuration, the information acquired by the roadside unit 130 can be used as dynamic data.

The roadside unit 130 may also function as a mobile base station 110. In other words, the roadside unit 130 can function as a stationary mobile unit 120, a mobile base station 110, or both.

[Cloud Data Center]
The cloud data center 200 includes a router 210, a server 220, and a main database 10. The cloud data center 200 is configured to be able to communicate with at least one mobile base station 110.

The cloud data center 200 collects information from the mobile base stations 110 in each data sharing area via the router 210. The server 220 manages the collected information, and the main database 10 stores the information under the control of the server 220. Note that the information stored in the main database 10 is the necessary information among the information collected and processed by the mobile base stations 110. Not all data is necessarily stored.

[Communication Systems]
As shown in FIG. 2, a plurality of local edge networks 100 are installed according to the geographical range (data sharing area) in which wireless communication is possible, covering a wide area.

In the network configuration shown in FIG. 2, first, in the local edge network 100, the sensor 120a of the mobile unit 120 acquires information, which is processed by the mobile unit 120 and stored in the terminal database 30 of the mobile unit 120. A part of the above information, i.e., information about which mobile unit 120 acquired what information, is collected by the local base station 112 included in the mobile base station 110 together with information acquired by the roadside unit 130. After all the collected information is processed by the local base station 112, it is further collected and processed by the main base station 111, and the necessary information is relayed to the cloud data center 200 as appropriate using the main base station 111 as a gateway (GW).

[Hierarchical Database]
As already mentioned, the mobile base station 110, the mobile body 120, etc. have an intermediate database 20 and an end database 30, but from the perspective of the hierarchical database 1a, the hierarchical database 1a has one main database 10 located in the cloud data center 200, an intermediate database 20 connected directly or indirectly to the main database 10 and located in the mobile base station 110, and an end database 30 connected to the intermediate database 20 and located in the mobile body 120.

<Registered data>
In the database management system 1, sensor information acquired by a sensor 120a of a mobile object 120 is stored as registered data of a hierarchical database 1a in a terminal database 30 disposed in the mobile object 120 having the sensor 120a.

In addition, in the database management system 1, a copy of the above-mentioned registration data stored in the end database 30 is stored in at least one intermediate database 20 of the local edge network 100 to which the mobile unit 120 belongs. Specifically, for example, the local base station 112 periodically checks the end database 30 of the mobile unit 120 within the geographical range it manages, and if new registration data within the geographical range it manages is registered in the end database 30, it copies the registration data to its own intermediate database 20. Similarly, the main base station 111 periodically checks the intermediate databases 20 of multiple local base stations 112, and if new registration data is registered in the intermediate database 20, it copies the registration data to its own intermediate database 20. Note that this is just one example, and other methods may be used.

The mobile unit 120 may stop and be turned off. Or, the mobile unit 120 may move outside the geographical range governed by one local edge network 100. In such a case, other mobile units 120 may not be able to access the terminal database 30 held by this mobile unit 120 through the local edge network 100, and may not be able to obtain the necessary registered data. In the database management system 1, a copy of the above registered data is stored in the intermediate database 20, which is in principle always in operation, so that the necessary registered data can, in principle, be obtained at all times.

Furthermore, in the database management system 1, other mobile objects 120 may have copies of the above registered data. Details will be described later.

In the database management system 1, the search means 1b identifies the intermediate database 20 and the end database 30 in which the registration data required by one mobile unit 120 is stored, based on the local master table 50 described later (see FIG. 4). The intermediate database 20 and the end database 30 preferably have a data table 40 that stores the registration data of the intermediate database 20 or the end database 30 identified by the search means 1b.

The data table 40 will be described with reference to FIG. 4. FIG. 4 shows one local base station 112 included in the local edge network 100 and a number of vehicles 121 (five in FIG. 4) controlled by this local base station 112. For simplicity, the terminal databases 30 (first terminal database 31 and second terminal database 32, respectively) for two of the five vehicles 121 (first vehicle 121a and second vehicle 121b) are shown. The local base station 112 also has an intermediate database 20.

For example, if the search unit 1b identifies the intermediate database 20 of the local base station 112 as the database storing the registration data a required by the first vehicle 121a, the registration data a is stored in the data table 40 of the first vehicle 121a. On the other hand, if the second vehicle 121b does not require the registration data a, the registration data a is not stored in the data table 40 of the second vehicle 121b.

The data table 40 also stores sensor information acquired by the sensor 120a of the vehicle 121. The data table 40 of the intermediate database 20 also stores a copy of the above-mentioned registered data stored in the terminal database 30.

In this way, the data table 40 in which the registration data is stored will have different registration data stored between the local base station 112 and the multiple vehicles 121. That is, for example, there is registration data a stored only in the first vehicle 121a and the local base station 112, registration data b stored only in the second vehicle 121b and the local base station 112, registration data c stored in all, and registration data d stored only in the first vehicle 121a and the second vehicle 121b. Hereinafter, in order to distinguish between the three data tables 40 shown in FIG. 4, the data tables 40 of the first vehicle 121a and the second vehicle 121b may be referred to as the first data table 41 and the second data table 42, respectively.

By providing the intermediate database 20 and the terminal database 30 with the above-mentioned data table 40 in this way, the registration data required for each mobile unit 120 or mobile base station 110 can be selectively replicated in this data table 40, thereby reducing the amount of access via the network and further improving efficiency.

<Local master table>
As shown in FIG. 4, the database management system 1 has a local master table 50 including information for identifying the database in which the intermediate database 20 and the end database 30 in the local edge network 100 to which the intermediate database 20 and the end database 30 belong, in which the registered data exists. The local master table 50 has the same information in the intermediate database 20 and the end database 30 in the local edge network 100. Specifically, for example, when new registered data is stored in the end database 30 in each mobile unit 120, the information is collected in the main base station 111 via the local base station 112 or directly. The main base station 111 updates the local master table 50 and distributes the updated local master table 50 to the intermediate database 20 and the end database 30 in the local edge network 100. In this way, the identity of the local master table 50 is ensured. Alternatively, when new registered data is stored in the mobile unit 120, the information can be shared among the mobile units 120, including other mobile units 120, by using a communication means that allows sharing at the same time.

A specific example of the local master table 50 will be described below, taking as an example a case where the subject of sensor information is a "falling object." For "falling object" information, it is advisable to label the data to link it to a road (road link, see Figure 5), and update the information for each road link. For example, in Figure 5, the first vehicle 121a (label V1) is traveling between a0 and a1 (road link a01). Note that a similar configuration can be used for sensor information other than that of a falling object.

Figure 6 is an example of a local master table 50 corresponding to this road link a01. In Figure 6, time* (* is a number) indicates the time when the data was updated. After that, the second column separated by "/" is the label of the vehicle 121 etc. that updated the fallen object data, the third column is the position and speed of the vehicle 121 (although in Figure 6 it is written in km, it means km/h), and the fourth column represents the vehicle 121 etc. that stores the corresponding registered data. Note that "φ" means that there is no change. Also, by using GPS as the sensor 120a for the position, and the speedometer of the vehicle 121 for the speed, it is possible to obtain sensor information.

For example, record R1 at time 1 shows that at time 1, the first vehicle 121a with label V1 obtained registration data of a fallen object while traveling at a speed of 20 km/h at a position 10 m away, and that only V1 has this registration data at the stage of time 1. Record R2 at time 2 shows that the local base station 112 with label B1 duplicated the registration data at time 2, and that the registration data is held by V1 and B1. At time 3 (record R3), a vehicle 121 with label V3 passed by the same location and discovered the same fallen object, so that the registration data is held by V1, V3, and B1. These three are linked because they are for the same fallen object.

When a new fallen object is discovered on road link a01, it is registered as a new record as shown in record R4 at time time4. This record R4 indicates that it is shared with V4 at the same time as it is registered by V1. This registered data is also deleted at time time5 (record R5) by making the vehicles 121 etc. that have the above registered data into an empty set (number 0). Deleting unnecessary data in this way prevents the data table 40 and local master table 50 from becoming too large, and allows the registered data to be handled more efficiently. Examples of registered data to be deleted include data that has been there for a certain amount of time, data that has not been rediscovered even though multiple vehicles 121 have passed through the same location, etc.

In addition, record R6 at time time6 means that there was no particular change when the first vehicle 121a with label V1 passed, meaning that nothing new was discovered. At the same time, it can also be data that identifies the position and speed of V1 at time time6.

<Overall master table>
In the database management system 1, the main database 10 of the cloud data center 200 has an overall master table that includes information for identifying the database in which the above-mentioned registered data of the entire one or more local edge networks 100 exists.

The above overall master table is a collection of records from the local master tables 50 of each local edge network 100.

The local master table 50 of each local edge network 100 is updated sequentially, but the overall master table does not need to be updated every time there is an update to each local master table 50. For example, it may be updated periodically at a relatively long interval.

The server 220 of the cloud data center 200 may optimize this overall master table. That is, the server 220 resolves inconsistencies within one local master table 50 or between multiple local master tables 50, erases old registered data, corrects duplicate registrations, and so on. The optimized overall master table is divided into local master tables 50 corresponding to each local edge network 100 and transmitted to each local edge network 100. Each local edge network 100 updates the local master table 50 in each local edge network 100 based on the information of the received local master table 50.

The mobile unit 120 can also use the local master table 50 to obtain information about the adjacent local edge network 100 in advance when moving to the adjacent local edge network 100. Using only the local master table 50, only the local edge network 100 to which the mobile unit 120 belongs can be searched, but using the overall master table makes it possible to search for information about adjacent local edge networks 100.

[Search methods]
The search unit 1b identifies the intermediate database 20 and the end database 30 in which registration data required by one mobile unit 120 is stored, based on the local master table 50 as described above.

For example, in FIG. 5, assume that the second vehicle 121b with label V2 is planning to pass through road link a01. In this case, for the second vehicle 121b, the fallen object information for road link a01 corresponds to the required registered data.

The search means 1b uses the processor of the second vehicle 121b to refer to the local master table 50 of the second vehicle 121b. In the case of the local master table 50 shown in FIG. 6, it can be seen that there is a fallen object at a position 10 m from record R3 at time 3, and it can be determined that the registered data is stored in three databases, V1, V3, and B1, that is, two terminal databases 30 and one intermediate database 20. On the other hand, it can be seen that there is no longer an object at a position 30 m from record R5 at time 5, and that there is no change in the position 50 m from record R6 at time 6.

In the database management system 1, the above search is performed by using the processor of the second vehicle 121b and by referencing the local master table 50 of the second vehicle 121b, so there is no need to search via the network. Therefore, it is possible to quickly identify the intermediate database 20 and the end database 30 in which the registered data is stored without placing a load on the network.

The second vehicle 121b can access either the identified intermediate database 20 or the end database 30 (in this case, the end databases 30 of V1 and V3 and the intermediate database 20 of B1) to obtain the required registration data. Which database to access can be determined using the communication speed estimation means 1c.

[Communication speed estimation means]
The communication speed estimation unit 1c estimates the communication speed with the intermediate database 20 and the end database 30 identified by the search unit 1b.

The sensor information acquired by the sensor 120a of the mobile unit 120 includes metadata for estimating the communication speed, and the communication speed estimation means 1c is configured to estimate the communication speed based on the metadata.

It is preferable that the metadata includes at least one of the position, speed, radio wave shielding degree, communication traffic, and speed of the actual communication result of the mobile unit 120. For example, the local master table 50 in FIG. 6 includes the position and speed (direction and speed) of the mobile unit 120. When the position of the mobile unit 120 is used, it is preferable to also use the position of the mobile base station 110.

In the local edge network 100 of the communication system in which the database management system 1 is used, there is a path for acquiring registered data between end databases 30, i.e., between mobile units 120 directly without going through the mobile base station 110. In this case, the distance to the mobile unit 120 with which the communication is to be made, the speed, radio wave shielding degree, communication traffic, and the communication speed of the actual communication result change from moment to moment, and these may cause the communication speed to change. Therefore, by including at least one of the position, speed, radio wave shielding degree, communication traffic, and communication speed of the actual communication result of the mobile unit 120 in the above metadata, the accuracy of estimating the communication speed can be improved.

Then, the communication speed estimation means 1c accesses the database that is estimated to have a faster communication speed to obtain the required registered data. By estimating the communication speed in this way using the communication speed estimation means 1c, it becomes possible to access the required registered data in an even shorter time.

<Advantages>
Since the database management system 1 uses the local master table 50, when the search unit 1b specifies the intermediate database 20 and the end database 30 in which the registration data required by one mobile unit 120 is stored, there is no need to access the cloud data center 200. Furthermore, in the database management system 1, one or more mobile base stations 110 and multiple mobile units 120 are connected to each other via a common wireless interface, so the intermediate database 20 and the end database 30 can be accessed without going through the cloud data center 200 or the mobile base station 110. Furthermore, in the database management system 1, a copy of the registration data based on the sensor information acquired by the sensor 120a of the mobile unit 120 exists at least in the intermediate database 20 of the mobile base station 110. Therefore, it is possible to access either the end database 30 or the intermediate database 20 of the mobile unit 120 in which the registration data to be acquired exists. With the above configuration, the database management system 1 can access the registration data required by one mobile unit 120 in a short time, so that the registration data, particularly the quasi-dynamic data and quasi-static data required for the automatic driving of the vehicle 121, can be efficiently handled.

[Other embodiments]
The above-mentioned embodiment does not limit the configuration of the present invention. Therefore, the above-mentioned embodiment may omit, replace or add components of each part of the above-mentioned embodiment based on the description in this specification and common technical knowledge, and it should be understood that all of these are within the scope of the present invention.

In the above embodiment, the intermediate database and the end database have a data table that stores the registered data of the intermediate database or the end database identified by the search means. However, the data table is not an essential component, and the present invention can achieve the same effect even if it is omitted. However, each time registered data is required, the identified database is accessed and the registered data is obtained. For this reason, it is preferable to have the above data table.

In the above embodiment, a case was described in which the main database has an overall master table that includes information identifying a database in which registered data for one or more entire local edge networks exists, but the overall master table is not a required component and can be omitted. The present invention can achieve a certain level of effectiveness even when operated only within a local edge network.

In the above embodiment, a case has been described in which the search means includes a communication speed estimation means for estimating the communication speed with the identified intermediate database and end database, but the communication speed estimation means is not an essential component and can be omitted. For example, access may be made to different databases in a preset order until registered data is obtained from the identified intermediate database and end database.

In the above embodiment, the case where the local base station deletes the registered data has been described, but it is not a necessary constituent requirement for the local base station to delete the registered data. Instead of the local base station, the main base station, a cloud data center, or a mobile body may delete the registered data, or multiple base stations may delete the registered data.

As described above, the database management system of the present invention can efficiently handle registered data, particularly semi-dynamic data and semi-static data required for automated driving of vehicles.

1 Database management system 1a Hierarchical database 1b Search means 1c Communication speed estimation means 10 Main database 20 Intermediate database 30 End database 31 First end database 32 Second end database 40 Data table 41 First data table 42 Second data table 50 Local master table 100 Local edge network 110 Mobile base station 111 Main base station 112 Local base station 120 Mobile body 120a Sensor 121 Vehicle 121a First vehicle 121b Second vehicle 122 Drone 123 Mobile robot 124 Portable device 125 Bicycle 130 Roadside device 200 Cloud data center 210 Router 220 Server R1, R2, R3, R4, R5, R6 Record

Claims (6)

A database management system installed in a communication system including one or more local edge networks and a cloud data center,
A hierarchical database and a search means are provided,
Each of the local edge networks includes one or more mobile base stations and a plurality of mobile units connected to each other via a common wireless interface;
the cloud data center is configured to be in communication with at least one of the mobile base stations;
The hierarchical database is
A primary database located in the cloud data center;
an intermediate database located at said mobile base station and connected directly or indirectly to said main database;
a terminal database connected to the intermediate database and disposed in the mobile unit;
The moving object has a sensor,
The sensor information acquired by the sensor is stored as registration data of the hierarchical database in the terminal database disposed in the mobile body having the sensor,
A copy of the registration data stored in the end database is stored in at least one of the intermediate databases of a local edge network to which the mobile unit belongs;
The intermediate database and the terminal database each have a local master table including information for identifying a database in the local edge network to which the intermediate database and the terminal database belong in which the registration data exists;
A database management system in which the search means identifies an intermediate database and a terminal database in which registration data required by one mobile object is stored based on the local master table. The database management system according to claim 1, wherein the intermediate database and the terminal database have a data table that stores the registered data of the intermediate database or the terminal database identified by the search means. The database management system according to claim 1 or 2, wherein the main database has an overall master table that includes information identifying databases in which the registration data of the entire one or more local edge networks exists. a communication speed estimation means for estimating a communication speed between the intermediate database and the terminal database specified by the search means,
the sensor information includes metadata for estimating the communication speed;
4. The database management system according to claim 1, wherein said communication speed estimating means estimates said communication speed based on said metadata. The database management system according to claim 4, wherein the metadata includes at least one of the location, speed, radio wave shielding degree, communication traffic, and actual communication result speed of the one mobile object. The database management system according to any one of claims 1 to 5, wherein the moving object includes a vehicle.

Images