KR101519020B1 - Appatus for partial-updating navigation data in driving and method thereof - Google Patents

Abstract

The present invention relates to an apparatus and a method for performing partial update of navigation data without stopping service while a navigation system based on a database is performing route guidance service, and a partial updating apparatus for navigation data during running according to the present invention includes: The database file to be saved; A log file stored on a storage medium; A core module for supporting recording or accessing data in the database file and the log file; An update manager for storing update data for the database file in the log file using the core module; And a path guide manager accessing the data stored in the database file using the core module to provide a path guide service. The core module performs log file creation and log recording at the request of the update manager And a recovery manager which is activated only during the migration from the log file to the database file and reads the changed data at the request of the path guide manager from the log file.

Description

[0001] Apparatus and method for partial update of navigation data during driving [0002]

The present invention relates to an apparatus and a method for a database-based navigation to partially update navigation data without stopping service while a route guidance service is being performed.

Conventional navigation has a problem in that it takes much time to update the navigation data on a file basis by adopting a block update method in a whole block.

By managing the navigation data on a database basis, update time can be greatly reduced by adopting a partial update method on an object basis.

Further, if the navigation updates the navigation data while the navigation service is in progress, there is a problem that the route guidance service must be stopped in order to maintain the consistency of the data. Particularly, in the partial updating method of the navigation data, data updating frequently occurs while the navigation service is performing the route guidance service, so that the user's discomfort may be increased.

Korean Patent Laid-Open No. 10-2012-0095552 (Aug. 29, 2012)

SUMMARY OF THE INVENTION The present invention is conceived to solve the above problems, and it is an object of the present invention to provide a route guidance service And to partially update the navigation data without stopping the service while performing the navigation service.

In order to achieve the above object, a partial updating apparatus for navigation data during running according to the present invention includes: a database file stored in a storage medium; A log file stored on a storage medium; A core module for supporting recording or accessing data in the database file and the log file; An update manager for storing update data for the database file in the log file using the core module; And a path guide manager accessing the data stored in the database file using the core module to provide a path guide service. The core module performs log file creation and log recording at the request of the update manager And a recovery manager which is activated only during the migration from the log file to the database file and reads the changed data at the request of the path guide manager from the log file.

1. A partial update apparatus for navigation data during traveling, the core module comprising: a user callback function for communicating between the route guidance manager and the route guidance manager, the start time point (MIGCB_MIGRATION_BEFORE) and the end point (MIGCB_MIGRATION_AFTER) And a restartupSystem user API that provides the same effect that the core module is rebooted by a call of the route guide manager at a start time and an end time of the migration.

The partial update device for navigation data during traveling may further comprise a setUserCallbackFunc user API for registering the user callback function after the update manager is activated.

According to another aspect of the present invention, there is provided a partial updating method of navigation data during driving, comprising: providing a route guidance service by accessing data stored in a database file using a core module driven by a route guidance manager; An update manager is activated to perform an update operation on the database file to activate a recovery manager of the core module, the recovery manager generates a log file and records a log in the generated log file; The recovery manager of the update manager requests the route guidance manager to change the state to 'MIGCB_MIGRATION_BEFORE' before migration from the log file to the database file starts; Reading the changed data from the log file by activating the recovery manager of the path guide manager; After the migration from the log file to the database file is completed, the recovery manager of the update manager requests the path guide manager to change the state to 'MIGCB_MIGRATION_AFTER'; And a step of providing a route guidance service by directly accessing the data stored in the database file using the core module when the recovery manager of the route guidance manager is inactivated.

A method for partially updating navigation data during driving, the method comprising: performing communication between the update manager and the route guidance manager when the recovery manager of the update manager requests the route guidance manager to change the state to 'MIGCB_MIGRATION_BEFORE' or 'MIGCB_MIGRATION_AFTER' And a user callback function is used.

The partial update method of navigation data during driving is characterized in that the update manager registers the user callback function in the core module using the setUserCallbackFunc user API configured in the core module after being driven.

In the partial update method of navigation data during running, when the route guidance manager changes state to 'MIGCB_MIGRATION_BEFORE' or 'MIGCB_MIGRATION_AFTER', a restartupSystem user API is called to provide the same effect as rebooting the core module.

According to another aspect of the present invention, there is provided a computer-readable recording medium having a path guide manager driven to access data stored in a database file using a core module to provide a path guide service; An update manager is activated to perform an update operation on the database file to activate a recovery manager of the core module, the recovery manager generates a log file and records a log in the generated log file; The recovery manager of the update manager requests the route guidance manager to change the state to 'MIGCB_MIGRATION_BEFORE' before migration from the log file to the database file starts; Reading the changed data from the log file by activating the recovery manager of the path guide manager; After the migration from the log file to the database file is completed, the recovery manager of the update manager requests the path guide manager to change the state to 'MIGCB_MIGRATION_AFTER'; And a step of providing a route guidance service by directly accessing the data stored in the database file using the core module, wherein the recovery manager of the route guidance manager is inactivated to record the program in which the implemented partial navigation method of navigation data is implemented do.

As described above, according to the present invention, the update time can be greatly reduced by managing the navigation data on the basis of the database and adopting the partial update method on an object unit basis, and the navigation service can be continuously received even during the update of the navigation data It is possible to reduce the inconvenience of the navigation user.

1 is a block diagram showing an overall configuration of a partial update apparatus for navigation data during running according to the present invention,
2 is a view showing the operation of the route guidance manager after the navigation boot,
3 shows a driving view of the route guiding and partial update switching 1 stage,
4 shows a driving view of the route guiding and partial update switching 2 steps,
FIG. 5 shows a driving view of three steps of route guidance and partial update switching,
FIG. 6 is a diagram illustrating the operation of the route guidance manager returned to a normal state after partial update.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1, a preferred embodiment of a partial updating device for navigation data during running includes core modules 30a and 30b having a database file 40, a log file 50, recovery managers 32a and 32b, A guidance manager 10 and an update manager 20. [

The database file 40 and the log file 50 which are components of the present invention are each a passive component and are stored in a storage medium separate from the main memory. The storage medium used in the present invention is preferably implemented as a flash memory, but is not limited thereto.

The core modules 30a and 30b, the route guidance manager 10, and the update manager 20, which are components of the present invention, can be actively and independently implemented as a complex of various hardware and software constituting a navigation device provided in a mobile environment, Which is defined by the functional characteristics that each component provides.

The core modules 30a and 30b are data base management systems (DBMSs) that support writing or accessing data in the database file 40 and the log file 50.

The path guide manager 10 accesses the data stored in the database file 40 using the core module 30a to search for a destination selected by the user and transmits a path such as a straight line / Provide guidance services.

The update manager 20 stores the update data for the database file 40 in the log file 50 using the core module 30b and then writes the log data stored in the log file 50 to the database file 40 Migrate.

The route guide manager 10 and the update manager 20 operate in a process based or a thread based manner in the navigation device, each of which uses the core modules 30a and 30b.

The core module 30a and the core module 30b are actually the same files but when they operate, they have independent regions in the state connected to the path guide manager 10 and the update manager 20, And are denoted by different reference numerals.

The core module 30a and the core module 30b each include a user callback function 34, a user API 36 and recovery managers 32a and 32b. However, since the user callback function and the user API provided in the core module 30a do not perform a direct function in connection with the present invention, they are not shown in the drawing in order to avoid confusion. The user callback function 34, the user API 36 and the recovery manager 32b provided in the recovery manager 32a and the core module 30b provided in the core module 30a are components related to the present invention .

The user callback function 34 communicates between the route guide manager 10 and the update manager 20 to notify the route guidance manager of the start point of the migration (MIGCB_MIGRATION_BEFORE) and the end point (MIGCB_MIGRATION_AFTER) Lt; / RTI >

A user API (Application Programming Interface) 36 is an interface that enables the functions provided by the core modules 30a and 30b to be used in an application program, and includes setUserCallbackFunc and restartupSystem.

setUserCallbackFunc is a user API used by the update manager 20 and the update manager 20 must register the user callback function 34 after booting through this user API.

The restartupSystem is a user API used by the path guide manager 10, and has the same effect as the core module 30a rebooted through the user API at the time of state transition (transfer) of its own state.

The recovery manager 32b performs log file creation and log recording at the request of the update manager 20 to perform partial update based on the log file and also the recovery manager 32a reads the database file 40), and the changed data is read from the log file at the request of the route guide manager 10, thereby performing a function of enabling seamless route guidance service. The recovery manager 32a and the recovery manager 32b are also the same as the core module 30a and the core module 30b in reality. However, the recovery manager 32a and the recovery manager 32b are respectively operated by the path guide manager 10 and the update manager 20 ), Which are independent from each other, and thus are denoted by different reference numerals in order to distinguish them.

On the other hand, the route guide manager 10 operates on a read basis and the update manager 20 operates on a write basis. If these two administrators are working at the same time, the original database stored in the database file 40 is shared. At this time, a device is required to maintain consistency of data with respect to a specific time domain (a period in which the original database is changed). In the present invention, this problem is solved through a state transition (transfer) method.

The transfer proceeds in three steps.

Step 1 is simply a matter of sharing the two administrators without changing the original database.

Step 2 is a state in which the status of the route guidance manager 10 is changed by the update manager 20 so that the consistency of data is maintained immediately before the original database is changed.

Step 3 is a state in which the state of the route guidance manager 10 is returned to the original state immediately after the update of the original database by the update manager 20 is completed.

Hereinafter, the partial updating process of the navigation data during running will be described in detail with reference to FIGS. 2 to 6. FIG.

FIG. 2 shows a state in which the route guide manager 10 is operated after navigation booting.

First, FIG. 2 shows a connection relationship of components for the route guidance manager 10 to provide route guidance after setting the destination of the user after the initial navigation boot.

Only the route guidance manager 10 is driven here, and the update manager 20 is not driven. At this time, the recovery manager 32a is in an inactive state, and the route guide manager 10 fetches the data necessary for route guidance from the original database of the database file 40. [

FIG. 3 is a diagram illustrating a route guiding and partial update switching one-step driving mode.

The route guide manager 10 fetches the necessary data from the original database and performs the service without changing any state.

After the update manager 10 is driven, the user callback function 34 is first registered in the core module 30b (S101). The registration method uses the setUserCallbackFunc user API provided by the core module 30b.

Thereafter, the update manager 20 performs an update operation configured with a Long Transaction (S103). At this time, the recovery manager 32b is activated, and the activated recovery manager 32b generates the log file 50 and records the log in the generated log file 50. [

In this state, no changes are made to the original database.

FIG. 4 is a diagram showing a route guiding and partial update switching two-step driving mode.

The recovery manager 32b of the update manager 20 is in a state in which all the change operations are recorded in the log and only the work to be reflected (migrated) to the original database remains.

Here, the recovery manager 32b calls the user callback function 34 to request the state transition of the route guidance manager (S201). Set the state value of the user callback function parameter to 'MIGCB_MIGRATION_BEFORE'.

The user callback function 34 takes charge of communication with the route guidance manager 10 and requests the route guidance manager 10 to switch to the two-step state and waits for a response (S203).

The route guide manager 10 calls the restartupSystem user API. At this time, the value of the parameter 'state' is set to 'MIGCB_MIGRATION_BEFORE' (S205). Additionally, the core module 30a of the path guide manager 10 retrieves from the original database of the database file 40 and initializes all data that was cached.

At this time, the recovery manager 32a of the path guide manager 10 is activated, and the changed state is changed to read the changed data from the log file 50 (S207). It is natural that the unchanged data is read in the database file 40.

When the user callback function 34 is thus returned (S209, S211, S213), the recovery manager 32b of the update manager 20 starts to reflect the change data recorded in the log to the original database of the database file 40 (S215).

Thus, the route guide manager 10 can retrieve the updated data from the log file 50 without interruption of the service before the migration to the original database is completed, and can serve the user.

FIG. 5 is a diagram illustrating a route guidance and a partial update switching three-step driving mode.

The recovery manager 32b of the update manager 20 reflects all of the change data recorded in the log file 50 to the original database and is in a state of being ready to complete the commit (S301).

The recovery manager 32b of the update manager 20 calls the user callback function 34 to request the state change of the route guide manager 10 (S303). The state of the callback function's parameter state is set to 'MIGCB_MIGRATION_AFTER', which tells it to return to its original state.

The user callback function 34 takes charge of communication with the route guidance manager 10 and requests the route guidance manager 10 to switch to the three-step state and waits for a response (S305).

The route guide manager 10 calls the restartupSystem user API (S307). The value of the parameter state is set to 'MIGCB_MIGRATION_AFTER'.

At this time, the recovery manager 32a of the route guide manager 10 is deactivated, and the data is changed to read from the original database.

When the user callback function 34 is thus returned (S311, S313, S315), the recovery manager 32b of the update manager 20 completes the commit and all the operations are terminated.

Thereby, the route guide manager 10 can retrieve the data necessary for route guidance from the updated original database without interruption of the route guidance service, and can provide service.

FIG. 6 is a view illustrating the operation of the route guidance manager, which is returned to a normal state after the update is completed.

The update manager 20 has finished all tasks and is finished.

The route guide manager 10 has returned to the initial boot state.

However, the user is not aware of all the processes that occur internally and can continuously receive the route guidance service continuously by the updated data.

Meanwhile, the embodiment of the present invention described above can be recorded in a medium used in a general-purpose computer including a mobile terminal. The medium may be a magnetic recording medium (e.g., ROM, floppy disk, hard disk, etc.), an optical reading medium (e.g. CD ROM or DVD), an electrical recording medium (e.g. flash memory, memory stick, And a carrier wave (e.g., transmission over the Internet).

The present invention has been described with reference to the preferred embodiments. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

10: Path Guide Manager 20: Update Manager
30a, 30b: core module 32a, 32b: recovery manager
34: User Callback Function 36: User API
40: Database file 50: Log file

Claims (8)

delete A database file stored on a storage medium;
A log file stored on a storage medium;
A core module for supporting recording or accessing data in the database file and the log file;
An update manager for storing update data for the database file in the log file using the core module; And
And a route guidance manager for accessing data stored in the database file using the core module and providing a route guidance service,
Wherein the core module performs log file creation and log recording at the request of the update manager and is activated only during the migration from the log file to the database file, And a recovery manager for reading the data from the recovery manager,
The core module
(MIGCB_MIGRATION_BEFORE) and an end point (MIGCB_MIGRATION_AFTER) to the route guidance manager by performing communication between the route guidance manager and the route guidance manager,
Further comprising a restartupSystem user API for providing the same effect that the core module is rebooted by a call of the route guide manager at a start time and an end time of the migration. 3. The apparatus of claim 2, wherein the core module
Further comprising a setUserCallbackFunc user API for registering the user callback function after the update manager is activated. Providing a route guide service by accessing data stored in a database file using a core module by being driven by a route guide manager;
An update manager is activated to perform an update operation on the database file to activate a recovery manager of the core module, the recovery manager generates a log file and records a log in the generated log file;
The recovery manager of the update manager requests the route guidance manager to change the state to 'MIGCB_MIGRATION_BEFORE' before migration from the log file to the database file starts;
Reading the changed data from the log file by activating the recovery manager of the path guide manager;
After the migration from the log file to the database file is completed, the recovery manager of the update manager requests the path guide manager to change the state to 'MIGCB_MIGRATION_AFTER'; And
And a step of providing a route guidance service by directly accessing the data stored in the database file using the core module when the recovery manager of the route guide manager is inactivated and providing the route guidance service. 5. The method of claim 4,
Wherein the update manager uses a user callback function that performs communication between the update manager and the route guidance manager when the recovery manager of the update manager requests the route guidance manager to switch the state to 'MIGCB_MIGRATION_BEFORE' or 'MIGCB_MIGRATION_AFTER' A method for partially updating navigation data. 6. The method of claim 5,
Wherein the update manager registers the user callback function in the core module using the setUserCallbackFunc user API configured in the core module after being driven. 5. The method of claim 4,
If the path guide manager switches to 'MIGCB_MIGRATION_BEFORE' or 'MIGCB_MIGRATION_AFTER', the restartupSystem user API is called to provide the same effect as rebooting the core module. A computer-readable recording medium on which a program embodying the method of any one of claims 4 to 7 is recorded.

Images