KR20090056061A - Mobile database system for navigation and method therefor - Google Patents

Abstract

A mobile database system for navigation and a method therefore are provided to improve the performance of a navigation system by generating mobile data through loading of an original map and network data. A data loader(330) loads an original map and network data and produces a mobile database. A navigation database system engine(350) generates more than one network table by using the mobile database. The navigation database system engine set a connection link between more than one network tables and stores it. An original data loader(331) processes the input-output of the original map / network data. A data converter(333) converts the original map/ network data into a memory structure for building a mobile database. A data builder uses the memory structure and generates the mobile database.

Description

Mobile database system for navigation and method therefor {Mobile Database System for Navigation and Method Therefor}

The present invention relates to a mobile database system and a method for navigation. More particularly, the present invention relates to a system and method for providing storage / retrieval of road network data and map data in a navigation system.

The present invention is derived from a study conducted as part of the IT growth engine technology development project of the Ministry of Information and Communication and the Ministry of Information and Communication Research and Development. [Task Management Number: 2006-S-025-02, Title: Map Air Update Technology for Telematics] Development].

The navigation system currently on the market stores road network data and map data in the form of a file using a unique physical storage format (PSF) for each company in the terminal.

Since the conventional navigation system as described above stores data using a unique physical storage format for each company, the following problems occur.

First, when a part of the road network data and the map data is changed, the conventional navigation system needs to replace the entire file with a new file to update the data. Here comes the problem of replacing the entire data file.

Second, in the conventional navigation system, it is difficult to define or insert / delete additional data schemas other than the fixed data schema created by the map provider, and because the format of the file is fixed, it is difficult to create and store and manage data specialized for each navigation application. there is a problem.

Third, the conventional navigation system is difficult to develop when the program developer does not know the format of the physical storage format because the format of the physical storage format is diverse and the structure is complicated.

Although the relational database system for mobile can be used to solve the problems of the above-mentioned conventional navigation system, the following problems arise in the conventional mobile relational database system.

First, since the conventional relational database system for mobile devices does not basically provide a function of storing and retrieving map data, spatial data type, spatial index, and query processing for storing spatial data in binary form in order to store map data. A problem arises that requires functionality.

Second, since a conventional relational database system for mobile performs a search process every time for a path search in a navigation application, a performance degradation occurs in the process of finding a connected node or link.

1 is a diagram illustrating a network configuration of a conventional mobile relational database. Here, it is assumed that node N1 is a starting point and that N6 is a destination.

Referring to FIG. 1, the conventional mobile relational database method uses a representative path search algorithm such as Dijkstra or A * to obtain {L1, L2, L3} by searching N1 in the node table to obtain a link associated with N1. do. At this time, it is assumed that there is ID information of links connected to the node table.

However, L1, L2, and L3 are logical IDs, so to get the record corresponding to L1, we have to query the link table again. In this way, we continue to search the connected nodes and links through the query until we find the destination N6. You must search.

Therefore, the conventional mobile relational database method causes a problem of degrading the performance of the navigation system because the mobile relational database method performs a query to find the connected link continuously to find the destination N6.

In order to solve this problem, it is an object of the present invention to provide a system and method for providing efficient storage / retrieval of road network data and map data in a mobile database system for navigation.

In order to achieve the above technical problem, the present invention provides a mobile database system for navigation, comprising: a data loader for generating a mobile database by loading raw map / network data; And a navigation database system engine that generates one or more network tables using the mobile database created by the data loader, and sets and stores a connection link between the one or more network tables.

In addition, the present invention provides a method for creating a network table in a mobile database system for navigation, comprising the steps of: a) if there is a network table creation call, determining whether there is a definition of a link in addition to the definition of the network table column; And b) if there is a definition for the connection link in the step a), generating an additional physical connection column by the number of the connection links in the network table.

In addition, the present invention provides a method for providing road network data retrieval in a mobile database system for navigation, a) if a request for information on a node or link connected to a particular record, whether or not the connection link for the particular record is defined Confirming; And b) returning a record using a record ID stored in the physical connection column if a connection link to the specific record is defined in step b).

According to the present invention, by providing efficient storage and retrieval of road network data and map data in a mobile database system for navigation, there is an effect of improving the performance of the navigation system.

In addition, according to the present invention, when a part of the road network data and the map data is changed, the insertion / deletion / update of the changed part is provided, thereby improving the data update speed.

In addition, according to the present invention, it is possible to quickly find the connected node / link through the connection link without having to query each time to find the connected node / link when performing the path search algorithm, thereby reducing the path search time.

In addition, according to the present invention, by providing a database structure, there is an effect of providing flexibility for defining a new schema and inserting data.

In addition, according to the present invention, it is possible to easily develop a navigation application by providing an extended database interface regardless of the physical storage format.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

In addition, when a part is said to "include" a certain component, this means that it may further include other components, except to exclude other components unless otherwise stated.

2 is a diagram illustrating a relationship between logical structure tables for explaining a logical structure of a table and a link used for storing / retrieving road network data according to an embodiment of the present invention. Here, in the embodiment of the present invention will be described with reference to Figure 1 used in the background for convenience of description.

Referring to FIGS. 1 and 2, the logical structure table may include a node table N as shown in 2a of FIG. 2, a mapping table of node table N as shown in 2b of FIG. 2, and a mapping table as shown in 2c of FIG. 2. It consists of a plurality of tables including a link table L, a mapping table of the link table L as shown in FIG. 2D, a geometry table G as shown in FIG. 2E, and the like.

Here, the node table N is a table for storing information about the connection links of the nodes of the road network, the logical ID (ID), the number of links associated with the logical ID (#) and the logical IDs of the connected links (L1 ~) L8) consists of a schema. When defining a node table N, if a connection link such as 2b of FIG. 2 is specified along with a column definition, a physical connection column can be automatically stored in the system. Will generate

The mapping table of the node table N consists of a source column and a target column, a source column consists of a source table name and a source column name, and a target column consists of a target table name and a target column name, respectively.

Referring to the first row in 2b of FIG. 2 as an example, the mapping table of the node table N indicates that the L1 column of the node table N is a linking column and points to an ID of the link table L as a target. If additional data is inserted, find the record in the link table L that has the same value as the value in the L1 column, and specify the record ID as _L1, which is a physical connection column. Or '_' before the source column name).

The link table L has a link definition that points to the geometry in the same way as the node table N.

3 is a diagram showing the configuration of a mobile database system for navigation according to an embodiment of the present invention. Here, in the embodiment of the present invention, for convenience of description, 'road network data' will be referred to as 'network data'.

In addition, among the terms described below, the network table is a concept including a table having information on a link, such as the node table N and the link table N described above.

Referring to FIG. 3, the mobile database system 300 for navigation includes a data loader 330, a navigation database system engine 350, and a navigation application 360.

The data loader 330 performs a function of batch loading raw map data such as DXF (Drawing Exchange Format), SHP (Shape), etc. into a mobile database, and includes a raw data loader 331, a map / network data converter 333, and Map / network data builder 335.

The raw data loader 331 processes input / output for the raw map / network data.

The map / network data converter 333 converts the raw map / network data input through the raw data loader 331 into a memory structure before constructing the mobile database.

The map / network data builder 335 generates the raw map / network data converted by the map / network data converter 333 into a mobile database using the memory structure and provides the generated map / network data to the navigation database system engine 350.

The navigation database system engine 350 functions as an engine that stores and manages map data and road network data for navigation applications, and includes a storage engine 351 and a spatial query executor ( 353, a connection link creator 355, a connection link handler 357, and a path manager 359.

The storage engine 351 is responsible for input / output for the map / network database and map / network data, and performs a management function and a buffering function for each page.

The spatial query executer 353 processes the spatial query and the attribute query, and provides a record unit management function.

The link generator 355 defines a table schema to automatically generate meta information when specifying link information.

The link link handler 357 automatically updates the physical link information when an insert / delete / update occurs in the network table in which the link is defined, and provides an external interface for immediately finding a connected node or link. .

The path manager 359 provides a function of a path searching algorithm and externally provides navigation related common interfaces.

The navigation application 360 implements a path searching function using an interface provided by the navigation database system engine 350.

4 is a flowchart illustrating a process of generating a road network table according to an embodiment of the present invention.

Hereinafter, a process of generating a road network table including a connection link according to an embodiment of the present invention will be described with reference to FIG. 4.

First, if there is a network table creation call (S410), it is determined whether there is a definition for the link in addition to the definition of the network table column (S430). In this case, the presence or absence of the definition of the connection link is determined by whether or not a connection column is defined in the table. If the connection column exists, it is determined that the connection link is defined.

If there is a definition for the connection link in step S430, a physical connection column is additionally generated by the number of connection link definitions in the table (S440), and meta information about the table is generated (S450).

If there is no definition for the link in step S430, meta information about the table is generated (S450).

5 is a flowchart illustrating a process of collectively constructing road network data including a connection link according to an embodiment of the present invention.

Hereinafter, a process of collectively constructing road network data including a connection link according to an embodiment of the present invention will be described. Here, the batch building of the road network data including the connection link is largely composed of an insert phase and a build phase.

First, if there is a batch construction call for road network data including a connection link (S510), a layer included in the source data is opened (S531), and it is determined whether the next layer exists (S533). Here, the layer refers to an aggregate of one or more spatial objects constituting the road network.

If it is determined in step S533 that the next layer exists, the next record is fetched from the source layer (S535), and it is determined whether a record to be inserted exists (S537).

If it is determined in step S537 that the record to be inserted exists, the remaining column values except the connection column are inserted into the generated network table as shown in FIG. 3, and the flow proceeds to step S535.

If no record to insert exists in step S537, the flow advances to step S531.

If it is determined in step S533 that the next layer does not exist, the process proceeds to the building step, and the network table is opened after the insertion is completed in the inserting step (S551).

Through the insertion steps S531 to S539 as described above, loops are performed on all layers included in the source data, and values are inserted into the remaining columns except the physical connection column.

Subsequently, after the insertion is completed in the insertion step, the next network table is opened (S551), and it is determined whether the next network table exists (S553).

If it is determined in step S553 that the next network table exists, the next record is read from the inserted network table (S553), and it is determined whether the next record exists (S555).

If it is determined in step S555 that the next record exists, the RID (Record ID) which is the ID of the connected network record is searched (S557), the connection column is updated (S559), and the flow proceeds to step S554.

If it is determined in step S553 that the next network table does not exist, the building step ends.

If it is determined in step S555 that the next record does not exist, the flow advances to step S551.

6 is a conceptual diagram of a connection link according to an embodiment of the present invention, Figure 7 is a flow chart illustrating a process of gradually building a road network data including a connection link according to an embodiment of the present invention.

Referring to FIG. 6, a connection link according to an embodiment of the present invention includes an inbound link and an outbound link. Here, the link pointing to the current record N1 is an inbound link, and the link pointing to the current record N1 is called an outbound link. In this case, the inbound link mainly refers to a link pointing to the current network table in another network table, and the outbound link mainly refers to a link pointing to another network table in the current network table.

Hereinafter, a process of gradually building road network data including a connection link according to an embodiment of the present invention will be described. In this case, the gradual construction process means a gradual construction of road network data when the navigation application uses the data that has been collectively constructed and wants to partially change the data.

First, if there is an insert command for a network table, a record is inserted into a corresponding network table (S710), and a search is performed for a record having an inbound link indicated by the inserted record (S720).

Subsequently, if a record having a search result inbound link exists in step S720, the physical connection column of the corresponding record is updated with the RID of the inserted record (S730), and the record having the outbound link indicated by the connection link in the inserted record is updated. Search (S740).

Subsequently, if a record having a search result outbound link exists in step S740, the physical connection column of the current network table is updated with the RID of the record (S750).

8 is a flowchart illustrating a process of searching road network data according to an embodiment of the present invention.

Hereinafter, a process of searching road network data according to an embodiment of the present invention will be described with reference to FIG. 8.

If there is a request for a node or link connected to the current record, a record connected to a specific column value is searched (S810), and it is determined whether a link is defined (S820).

Subsequently, if it is determined in step S820 that the connection link is defined, the RID stored in the physical connection column of the network table is read (S830), and the record is returned using the RID stored in the physical connection column (S850).

If it is determined in step S820 that the link is not defined, the record is searched and retrieved by the logical ID (S840), and the result is returned (S850).

The embodiments of the present invention described above are not implemented only through the apparatus and the method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. Implementation may be easily implemented by those skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a road network diagram for explaining the principle of the conventional mobile relational database method.

2 is a diagram illustrating a relationship between logical structure tables for explaining a logical structure of a table and a link used for storing / retrieving road network data according to an embodiment of the present invention.

3 is a diagram showing the configuration of a mobile database system for navigation according to an embodiment of the present invention.

4 is a flowchart illustrating a process of generating a road network table according to an embodiment of the present invention.

5 is a flowchart illustrating a process of collectively constructing road network data including a connection link according to an embodiment of the present invention.

6 is a conceptual diagram for a connection link according to an embodiment of the present invention.

7 is a flowchart illustrating a process of gradually building road network data including a connection link according to an embodiment of the present invention.

8 is a flowchart illustrating a process of searching road network data according to an embodiment of the present invention.

Claims (11)

In the mobile database system for navigation, A data loader for loading raw map / network data to create a mobile database; And A navigation database system engine that generates one or more network tables using the mobile database created by the data loader and sets and stores a connection link between the one or more network tables. Mobile database system comprising a. The method of claim 1, The data loader is A raw data loader that processes input and output for the raw map / network data; A data converter for converting the raw map / network data input through the raw data loader into a memory structure for constructing a mobile database; And A data builder for generating the map / network data converted by the data converter into a mobile database using the memory structure Mobile database system comprising a. The method of claim 2, The data builder If there is a definition of the connection link in addition to the definition of the column of the network table, the mobile database system to create additional physical connection columns as many as the number of the connection link definition set in the network table. The method of claim 3, wherein The data builder Checks records of all layers included in the raw map / network data, inserts column values into the remaining columns except the connection column of the columns of the network table, and loops through the records in the network table where the column values are inserted. A mobile database system that searches a target record of each column defined by a connection link and sets the record ID of the corresponding record as a value. The method of claim 4, wherein The navigation database system engine A link link handler for automatically updating physical connection information of the network table when an insertion / deletion / update occurs in a network table in which the link is defined; And Link generator for automatically generating meta information when defining link information by defining the schema of the network table Mobile database system comprising a. The method of claim 5, wherein The navigation database system engine If there is a request for information about a node or a link connected to a specific record, check whether the connection link for the specific record is defined, And a link is defined for the particular record, and returns the record using the record ID stored in the physical connection column. In the method for creating a network table in a mobile database system for navigation, a) if there is a network table creation call, determining whether there is a definition for a link other than the definition of the network table column; And b) if there is a definition for the connection link in step a), generating additional physical connection columns in the network table by the number of the connection links. Network table generation method comprising a. The method of claim 7, wherein c) looping all layers included in the network data in the network table in which the physical connection column is generated, and inserting column values into the remaining columns except the physical connection column; And d) retrieving the target record of each column defined as a link by looping the record in the network table into which the column value is inserted in step c) and setting the record ID of the corresponding record as a value; Network table generation method comprising a. The method according to claim 7 or 8, If there is an insert command for the network table, inserting a record into the network table and searching for the existence of a record having an inbound link pointed to by the inserted record; Updating the physical connection column of the corresponding record with the record ID of the inserted record if the record having the inbound link exists in the searching; Retrieving a record having an outbound link pointed to by a link in the inserted record; And Updating a physical connection column of the corresponding network table with a record ID of a record having the retrieved outbound link Network table generation method comprising a. The method of claim 9, If there is a request for information about a node or a link connected to a specific record, checking whether the connection link for the specific record is defined; And In the step of checking whether the connection link for the specific record is defined, returning a record using the record ID stored in the physical connection column if the connection link for the specific record is defined. Road network data search providing method comprising a. In the method for providing road network data retrieval in a mobile database system for navigation, a) if there is a request for information on a node or link connected to a particular record, checking whether the link for the particular record is defined; And b) if a connection link for the specific record is defined in step b), returning the record using the record ID stored in the physical connection column; Road network data search providing method comprising a.

Images