JP2002333324A - Method for version-up of navigation data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a version up method for data for navigation capable of surely remaining user data of customers in non-volatile memory means loaded on a navigation apparatus. SOLUTION: In a hard disk 11 being a non-volatile memory means loaded on a navigation apparatus 10, data for navigation and user data are stored in rewritable form. The hard disk 11 removed for version up is rewritten into data for navigation in the rewriting center of an 3 and the user data is tentatively saved during the rewriting, and the saved user data is written back on the bard disk 11 to make a version up. In this manner, work load of the user is suppressed, and navigation data can be updated with the important user data remaining on the hard disk 11 as they are.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of upgrading navigation data necessary for realizing the function of a navigation device, and more particularly to a method of upgrading the navigation data which is detachably attached to the navigation device. The present invention relates to a method of upgrading navigation data for sex storage means.

[0002]

2. Description of the Related Art Hitherto, optical disks such as DVDs and CDs have been widely used as storage means for reading navigation data such as map data in navigation equipment. A navigation device equipped with an optical disk detects the current position when performing a navigation operation,
The guidance display is performed using a map image generated based on the map data read from the optical disk.

On the other hand, navigation data such as map data recorded on an optical disc is desirably updated after it has been used for a certain period of time in order to respond to changes in road conditions and the like. Therefore, by providing the customer with an optical disk on which the upgraded navigation data is recorded, and mounting the optical disc on the navigation device, the navigation can be realized in a state in which changes in road conditions and the like are appropriately reflected. it can.

[0004]

In recent years, hard disks have become widespread as large-capacity nonvolatile storage means. It is also conceivable that the hard disk is mounted on a navigation device and used as a storage unit for navigation data. By using such a hard disk, the storage capacity of navigation data can be greatly increased, and music data collected by a customer can be stored in an empty area of the hard disk, which is convenient for navigation equipment. Is improved.

When a hard disk is used in a navigation device, the process of upgrading the navigation data as described above becomes complicated. In other words, instead of replacing the recording medium itself like an optical disk, it is necessary for the provider of the hard disk to collect the hard disk from the customer and upgrade the version by rewriting the contents.

However, there are cases where a customer who uses a navigation device wants to keep the user data recorded on the hard disk even when the user desires to update the navigation data. In this case, it is troublesome for the customer to perform the work of backing up the user data before the version upgrade.

[0007] Further, if the business operator performs the version upgrade work itself, it is expected that the intermediate cost will increase due to operations such as collection and return of the target hard disk. On the other hand, at the time of version upgrade, it is not preferable to always require the customer to remove or attach the hard disk to the navigation device in view of the fact that some customers are unfamiliar with handling the hard disk.

In view of the above, the present invention has been made in view of such a problem. When upgrading the navigation data in the nonvolatile storage means mounted on the navigation device, the present invention suppresses the burden on the customer and reduces the burden on the customer. It is an object of the present invention to provide a method for upgrading navigation data, which can surely leave the user data and improve the business efficiency as a whole when the business operator responds to the version upgrade.

[0009]

According to a first aspect of the present invention, there is provided a method for upgrading navigation data, wherein the navigation data is removably attached to a navigation device so that the navigation data and the user data can be rewritten. A method for upgrading the navigation data by rewriting the navigation data with respect to the nonvolatile storage means for storing the data in the nonvolatile storage means. Data is rewritten, the user data is temporarily saved at the time of the rewriting, and the saved user data is written back to the non-volatile storage means after the rewriting is completed to perform a version upgrade. I do.

According to the present invention, when the navigation data is upgraded in the nonvolatile storage means of the navigation device, after the navigation data is rewritten while the user data in the nonvolatile storage means is temporarily saved, The saved user data is written back to the non-volatile storage means, and the version is upgraded. Here, the navigation data includes map data required for the navigation function of the navigation device,
The user data is other related data, and the user data is various data such as music data collected or created by the user. Therefore, while the navigation data on the hard disk is upgraded, the user data unique to each customer can be maintained without being deleted, and the customer can enjoy the advantage without increasing the burden.

According to a second aspect of the present invention, there is provided a navigation data version upgrading method according to the first aspect, wherein the version upgrade is performed by a customer who owns the navigation device. An application is received, and is performed on the non-volatile storage unit that has received the collection request. The execution of the version upgrade is managed based on a customer database that holds customer information, and a series of processes accompanying the version upgrade are performed. It is characterized by managing the operations of

According to the present invention, when the customer who owns the nonvolatile storage means of the navigation device applies for version upgrade and requests collection of the hard disk, the business operator uses the necessary customer information in the customer database to obtain the information. The version of the navigation data is finally upgraded while managing the execution of the version upgrade for the non-volatile storage means of the customer and a series of tasks incidental thereto. Therefore, with the upgrade of the navigation data, the customer, in addition to enjoying the above advantages, centrally manages the business for distributing the non-volatile storage means between the customer and the business, and Work efficiency can be improved.

According to a third aspect of the present invention, there is provided the navigation data version upgrading method according to the second aspect, wherein a series of tasks associated with the version upgrade includes a non-volatile memory. It is characterized in that it includes a collection operation of the storage unit, a return operation of the non-volatile storage unit after the version upgrade, and a fee collection operation associated with the version upgrade.

According to the present invention, in addition to the operation of the invention described in claim 2, the business operator who upgrades the version of the navigation data can collectively collect and return the nonvolatile means or collect the fee. Management
The distribution of the non-volatile storage means becomes smooth, and the intermediate cost required for version upgrade can be suppressed.

According to a fourth aspect of the present invention, in the method for upgrading the navigation data according to the third aspect, after receiving the application for the version upgrade by a customer, the navigation database is updated based on the customer database. The customer manages the delivery work of the upgrade member necessary for the customer to perform the work of upgrading the nonvolatile storage means, and the upgrade is performed by the customer to whom the upgrade member is delivered. The non-volatile storage means receiving the collection request is performed as a target.

According to this invention, in addition to the function of the invention described in claim 3, the business operator who upgrades the navigation data delivers the upgrade member to the customer who has applied for the upgrade, and thereafter, Furthermore, the non-volatile means are collected from the customer who has received the collection request, and a version upgrade operation is performed. Therefore, it is only necessary for the customer to use the version-up member to move to the collection operation in a state where the non-volatile means has been removed, for example, and both the work efficiency of the customer and the work efficiency of the business operator can be improved.

According to a fifth aspect of the present invention, there is provided the navigation data version upgrading method according to the third or fourth aspect, wherein the pickup request from a customer and the nonvolatile storage means are provided. The collection of the non-volatile storage means and the return of the non-volatile storage means after the version upgrade are performed via a business that has contracted to attach and detach the non-volatile means.

According to the present invention, the customer who has applied for the version upgrade requests a specific business entity without removing and attaching the non-volatile storage means by himself / herself, and the various business described above is performed via this business entity. Done. Therefore, when the customer is unfamiliar with the handling of non-volatile storage means,
The burden can be reduced, and the whole upgrade work can be smoothly performed.

According to a sixth aspect of the present invention, there is provided the navigation data version upgrading method according to any one of the first to fifth aspects, wherein the nonvolatile storage means is a hard disk. It is characterized by the following.

According to the present invention, the hard disk is used as the nonvolatile storage means of the navigation device.
In addition to being able to store large volumes of navigation data and customer-specific user data freely on commonly used hard disks, the burden on both customers and businesses due to hard disk rewriting due to version upgrades is reduced. be able to.

[0021]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below with reference to the drawings.

First, the flow of the entire version upgrade business required to apply the version upgrade method according to the present invention will be described with reference to FIGS. FIG.
It is a block diagram explaining the relationship between the customer who actually uses the version upgrade, the company that executes the version upgrade business, and other related businesses. FIG. 2 is a flowchart illustrating the flow of a version upgrade operation.

In FIG. 1, a customer 1 owns a navigation device 10 manufactured and sold by a business 2. The navigation device 10 is a device that is mounted, for example, on the automobile of the customer 1 and performs navigation by detecting the position of the own vehicle and performing guidance display. When performing navigation by the navigation device 10, map data is required. Generally, an optical disc such as a CD or DVD on which the map data is recorded is often used.
In the present embodiment, it is assumed that navigation data such as map data is recorded and used on a hard disk 11 serving as a nonvolatile storage unit. Compared to an optical disk, the hard disk 11 is superior in terms of storage capacity and high-speed access, so that more comfortable navigation can be realized.

The hard disk 11 is detachably attached to the navigation device 10 via a connector.
It has a storage capacity of about 0 Gbytes. Of these, 8
About 0% is allocated to an area for storing navigation data, and user data can be written to the remaining area. The navigation data includes map data and various data related to the navigation function.
As the user data, music data and the like collected by the user himself can be stored and held in the hard disk 11. Also, initially, the navigation device 10 has only one hard disk 11, but a second hard disk 11 can be added to expand the area for user data.

When the customer 1 purchases the navigation device 10, navigation data is already recorded on the hard disk 11. However, if the navigation device 10 is used for a predetermined period, the navigation data becomes old, so that it is necessary to upgrade the version to cope with the latest road conditions and the like. In this case, for example, in the case of a recording medium such as an optical disk, it is only necessary to obtain and replace the upgraded disk, but in the case of the hard disk 11,
The work for upgrading the navigation data becomes complicated. In the present embodiment, the operator 2 provides a series of operations related to version upgrade as described later so that the navigation data on the hard disk 11 can be upgraded without increasing the burden on the customer 1.

Next, the business 2 carries out a business relating to the manufacture and sale of the navigation device 10 and also carries out a version upgrade of the hard disk 11. The company 2 stores customer information on customers who have purchased the navigation device 10 in the customer database 3 in order to manage the upgrade work. The customer information stored in the customer database 3 includes, for example, the customer's name, address, purchase date, model of the navigation device 10, version information, etc., and is referred to as necessary in a series of version upgrade operations. can do.

As shown in FIG. 2, the departments involved in the version upgrade work in the business 2 include a reception center 2a, an inquiry center 2b, and a service center 2.
c, a collection center 2d, and a rewriting center 2e.
The role of each section will be described later. In the example of FIG. 2, each department is provided inside the business entity 2, but a part of the business may be outsourced by outsourcing. Also, in FIG. 2, a carrier 4 and a dealer 5 are shown as businesses to which the business 2 undertakes related work, and the roles of each will be described later.

Next, a description will be given of the flow of a version upgrade operation performed in cooperation with each department inside the enterprise 2 and an external enterprise. There are a plurality of forms of version upgrade work according to the present embodiment according to the intention of the customer 1.
FIG. 2 is a flowchart showing the flow of version upgrade work corresponding to the basic mode in chronological order. In the flowchart of FIG. 2, it is assumed that the customer 1 has already purchased the navigation device 10 including the hard disk 11.

First, when it is time to upgrade the navigation data recorded on the hard disk 11, the business entity 2 refers to the customer database 3 to determine the customer 1 who owns the navigation device 10, and determines the navigation data. Is updated (step S1). The notification of the version upgrade to the customer 1 may be, for example, by sending an e-mail via the Internet in addition to sending a direct mail.

The notification in step S1 shows the contents of the version upgrade of the navigation data and the application method, information on the delivery of the version upgrade kit necessary for performing the version upgrade work, information on the fee accompanying the version upgrade, and the like. . Then, the reception center 2a confirms whether or not an application for version upgrade based on the judgment of the customer 1 has been received (step S).
2). The application for version upgrade from the customer 1 may be received by e-mail via the Internet, for example, in addition to receiving the request by telephone or fax.

When the application for the version upgrade from the customer 1 is not received (step S2; NO), the process ends without performing the subsequent version upgrade. On the other hand, when an application for version upgrade is received from the customer 1 (step S2; YES), the above-described version upgrade kit is delivered to the customer 1 (step S3).
It should be noted that the actual delivery in step S3 is entrusted to the carrier 4 in FIG. 1, and is associated with the customer information in the customer database, for example, to centrally manage the slip number.
Manage the entire delivery of the upgrade kit.

Here, the version upgrade kit includes the hard disk 1 removed from the navigation device 10.
1 and a member for protecting the terminals and the like of the hard disk 11 during transportation. The customer 1 first removes the hard disk 11 attached to the navigation device 10, and then packs the hard disk 11 using the members included in the version upgrade kit, and collects the hard disk 11 based on a pickup request as described later. Will wait until.

When the version upgrade kit is delivered in step S3, a fee is collected for the customer 1 in accordance with the version upgrade (step S4). Specifically, as a payment method for the customer 1, the carrier 4
The customer 1 can select a method desired by the customer 1, such as using cash on delivery via a credit card or paying a fee using a credit card. The company 2 can properly use the slips according to the fee payment method of the customer 1 and integrally manage the sales accounting of the entire upgrade business. In addition, as a method of paying the fee of the customer 1, an electronic billing form via the Internet may be used.

Next, it is confirmed at the collection center 2d whether or not a request for collection of the hard disk 11 for version upgrade has been received from the customer 1 (step S).
5). The collection request from the customer 1 may be received by e-mail via the Internet in addition to receiving the request by telephone or fax, for example. In this case, for example, at the stage of step S3, it is necessary to inform the customer 1 of the method of collection request and the request destination. The collection center 2d obtains necessary customer information with reference to the customer database 3 for the customer 1 that has received the collection request, and manages the number of received collections daily.

If the collection request from the customer 1 is not received (step S5; NO), the process in FIG. 2 ends without performing the subsequent version-up operation, but is terminated based on another mode as described later ( (See FIG. 3 or FIG. 4) There is a possibility that a version upgrade operation is performed. On the other hand, when a pickup request from the customer 1 is received (step S5;
YES), the collection center 2d issues an instruction to the transport company 4 and performs a collection operation of the hard disk 11 (step S).
6). Prior to collecting the hard disk 11, it is desirable to ask the customer 1 about the desired date and time of collection. At the desired date and time, the carrier 4 visits an address matching the customer information and collects the hard disk 11 to be upgraded.

Next, the hard disk 11 collected from the customer 1 is delivered to the rewriting center 2e, and the hard disk 11 is upgraded (step S7). In the present embodiment, in order to improve the work efficiency because a large number of hard disks 11 are handled, a series of version upgrade processes in which a number of processes are combined on a line is executed, and details thereof will be described later.
The rewriting center 2e always manages the quantity of the hard disks 11 that have been updated on a daily basis, and performs a management operation so as to keep the delivery date and quality appropriately.

When the version upgrade in step S7 is completed, the collection center 2d once picks up the upgraded hard disk 11 and issues an instruction to the carrier 4 to return the hard disk 11 to the customer 1 (step S7). S8). The hard disk 1
Prior to returning 1, it is desirable to confirm the home presence of the customer 1 by telephone or the like. Then, the carrier 4 visits the address corresponding to the customer information, returns the upgraded hard disk 11, and completes the version upgrade business of FIG. In the basic form of FIG. 2, the returned hard disk 11 is stored by the customer 1 by the navigation device 10 by himself / herself.
It is assumed to be attached to.

Here, in the series of version upgrade work shown in FIG. 2, if the customer 1 has any questions, he can make an inquiry to the inquiry center 2b. For example, it is possible to inquire how to remove or attach the hard disk 11 to the navigation device 10, or to inquire about the version upgrade schedule. The inquiry center 2b provides appropriate advice for inquiries from the customer 1, but if it is difficult to respond by itself,
The service center 2c described later may be introduced to the customer 1.

With the above-described version-up operation, a series of operations such as a collection operation and a return operation of the hard disk 11 and a charging operation associated with the version-up are smoothly advanced for the customer 1 who wants to upgrade the navigation data. In addition to this, the entire business can be centrally managed based on the customer database 3. In addition, since the provider 3 plays a central role in performing the version upgrade business and the business incidental thereto, the intermediate cost required for upgrading the navigation data can be suppressed. In addition to the cost of upgrading the version for the customer 1, as described later, the collected hard disk 11 has user data unique to the user, which is a great advantage.

Next, with regard to the version upgrade work of this embodiment, there are variations other than the basic form of FIG. Hereinafter, a variation form in the version upgrade work will be described with reference to FIGS. 3 and 4.

FIG. 3 is a flowchart showing a flow in the case where a store 5 is interposed between the customer 1 and the business 2 in the above-described upgrade work. In FIG. 3, steps S1 to S4 proceed in a flow similar to the basic mode of FIG. However, it is also assumed that the customer 1 who has received the above-mentioned hardening kit in step S4 is unfamiliar with the handling of the hard disk 11 and wants to entrust the removal of the hard disk 11 from the navigation device 10 to a third party. In such a case, as shown in FIG. 3, the customer 1 visits the store 5 and requests removal of the hard disk 11 for the purpose of upgrading (step S101).

On the other hand, in the store 5, for example, after the work of removing the hard disk 11 from the navigation device 10 installed in the automobile of the customer 1, the hard disk is transferred to the collection center 2d of the company 1 in order to cope with the upgrade. Eleven pickup requests are made (step S102).
In this case, the cost for removing the hard disk 11 is paid directly from the customer 1 to the store 5, but this cost is separate from the cost of the version upgrade itself.

When the collection center 2d receives the collection request in step S102, it issues an instruction to the carrier 4 and collects the hard disk 11 of the customer 1 from the store 5 (step S103). Subsequently, as in step S7 (FIG. 2), the hard disk 11 is upgraded in the rewriting center 2e (step S104).

Hard disk 11 after version upgrade
Is first returned to the store 5 by the carrier 4 instructed by the collection center 2d (step S105).
When the customer 1 who has been contacted by the store 5 visits the store 5 again, the upgraded hard disk 1
1 is installed, and finally the hard disk 1
1 is returned to the customer 1 (step S106).

Next, FIG. 4 shows a service center 2 between the customer 1 and the business 2 in the above-mentioned version upgrade work.
It is a flowchart which shows the flow at the time of the serviceman of c. In FIG. 4, the customer 1 that has been notified of the version upgrade in step S1 (FIG. 2) directly consults or inquires about the version upgrade to the inquiry center 2b (step S201). At this time, the customer 1 uses the inquiry center 2b to
The above serviceman who removes and attaches the equipment is introduced, and the subsequent work proceeds.

Based on the request from the inquiry center 2b to the service center 2c, a specific service person visits the customer 1 (step S202). The serviceman, for example, removes the hard disk 11 from the navigation device 10 installed in the car of the customer 1 and then collects the hard disk 11 (step S203) and stores it at the service center 2c.

Next, from the service center 2c to the business 1
A request for collection of the hard disk 11 is made to the collection center 2d (step S204). Receiving this, the collection center 2d issues an instruction to the carrier 4 and collects the hard disk 11 of the customer 1 from the service center 2c (step S205). Subsequently, as in step S7 (FIG. 2), the hard disk 11 is upgraded in the rewriting center 2e (step S206).

Hard disk 11 after version upgrade
Is carried to the service center 2c by the carrier 4 instructed from the collection center 2d, and the serviceman in charge of receiving the visit again visits the customer 1 (step S207). Then, the serviceman performs the work of installing the hard disk 11 after the version upgrade, and finally the hard disk 11 is returned to the customer 1 (step S208). Thereafter, similarly to step S4 in FIG. 2, a fee is collected for the customer 1 in accordance with the version upgrade (step S209).

As described above, in the version upgrade business shown in FIGS. 3 and 4, unlike FIG. 2, it is not necessary for the customer 1 to remove or attach the hard disk 11 to the navigation device 10 at the time of version upgrade. . Therefore, the customer 1 may select the mode of FIG. 2 when performing the work of removing and attaching the hard disk 11, and select the mode of FIG. 3 or 4 when the work is difficult. it can. Therefore, it is possible to reduce the work load on the customer 1 due to the upgrade of the navigation data.

Next, the details of the version upgrade process performed in the rewriting center 2e corresponding to step S7 in FIG. 2 (step S104 in FIG. 3, step S206 in FIG. 4) will be described with reference to FIGS. I do. FIG. 5 is a flowchart showing an outline of the entire version upgrade process performed in the rewriting center 2e. The feature of the version upgrade process in the present embodiment is that the navigation data recorded on the hard disk 11 is rewritten and the user data recorded by the user is left as it is.

As shown in FIG. 5, the whole version upgrade process of this embodiment is composed of four large processes. First, in step S11, a check process of each hard disk 11 delivered as a target for version upgrade is executed. That is, the target hard disk 1
In step 1, the storage state of the hard disk 11 is checked to determine whether there is navigation data to be upgraded and to determine whether there is user data data to be saved.

FIG. 6 is a flowchart for explaining the step of checking the hard disk 11 in step S11. FIG.
When the target hard disk 11 is put into the line of the rewriting center 2e, the hard disk 1
It is checked whether or not 1 and the backup hard disk are normally connected to the user data saving device (step S21). The user data saving device is provided exclusively for this line, and includes a backup hard disk for saving user data recorded on the hard disk 11.

FIG. 7 shows the external structure of the user data saving device. As shown in FIG. 7, two connectors 22 and 23 are provided on the user data evacuation device main body 21, and one of the connectors 22 is connected to the backup hard disk 24. And the other connector 2
2 is connected to the target hard disk 11, and a check in step S21 is performed. The user data evacuation device main body 21 is connected to a power supply unit 25 for supplying power and a display 2 for performing various displays.
6 is connected. The display 26 is used for displaying a caution to an operator when a failure during the process is detected.

As the user data saving device shown in FIG. 7, the navigation device 10 can be used.
That is, the control program for the actual device in the navigation device 10 is replaced with the program for the process, and the structure is modified so that each of the above components can be connected.
What is necessary is just to comprise a user data saving device. As the backup hard disk 24, the same type as the hard disk 11 to be upgraded is used. As a result, when a large number of user data evacuation devices are installed to improve work efficiency, the cost burden can be reduced.

As a result of the check in step S21, if the hard disk 11 and the backup hard disk 24 are not properly connected to the user data saving device (step S21; NO), a caution display to that effect is displayed on the display 26 (step S22). ), No further processing is performed. Since the backup hard disk 24 can store user data of a plurality of hard disks 11 according to the storage capacity, once connected to the connector 22, the state is maintained until the storage capacity becomes insufficient.

On the other hand, by checking in step S21,
If a normal connection is confirmed (step S21; YE
S), it is checked whether there is free space in the backup hard disk 24 (step S23). As described above, due to the limitation of the storage capacity of the backup hard disk 24, it is necessary to exchange a certain number of user data of the hard disk 11 for recording. For example, storage capacity is allocated so that user data of eight hard disks 11 can be saved. At this time, since one directory is provided for user data of one hard disk 11, a check in step S23 can be performed based on the number of directories of the backup hard disk 24.

If the result of the check in step S23 is that there is no free space in the backup hard disk 24 (step S23; NO), a message to that effect and a caution display urging the replacement of the backup hard disk 24 are displayed on the display 26 (step S24). ), No further processing is performed. On the other hand, if there is free space in the backup hard disk 24 (step S23; YE
S), the user password set in the hard disk 11 is released using the master password (step S25). That is, a unique user password is set on the hard disk 11 of the present embodiment so as to permit access to only the navigation device 10 of the specific customer 1. Therefore, the process of step S25 is necessary to release the user password so that the hard disk 11 can be read.

Next, the hard disk 11 is accessed,
The storage state is confirmed (step S26). In particular,
It is determined whether or not navigation data is stored in the hard disk 11 and whether or not a user data directory for recording user data exists. Accordingly, it is possible to confirm in advance the steps to be performed subsequently, such as whether to rewrite the navigation data or save the user data in the subsequent processing.

Then, the processing of steps S27 to S29 is executed according to the result of the determination in step S26. If it is determined in step S27 that the navigation data is not recorded on the hard disk 11 (step S27; NO), a caution display to that effect is displayed on the display 26 (step S28), and the subsequent processing is not performed. On the other hand, when it is determined that the navigation data is recorded (step S27; YES), the process proceeds to step S29.

In step S29, the hard disk 1
If it is determined that the directory for user data exists in step 1 (step S29; YES), the process proceeds to the user data saving step of step S12 (FIG. 5). On the other hand, if it is determined that the user data directory does not exist on the hard disk 11 (step S29; NO), there is no need to save the user data, so step S13 (FIG. 5)
Move to the navigation data rewriting process. Instead of providing the determination in step S29, even if the user data directory does not exist, the process may be shifted to the user data saving process, and the actual user data saving may not be performed.

Next, returning to FIG. 5, in step S12,
A saving process of the user data recorded on the hard disk 11 is executed. That is, the entire user data directory is temporarily saved on the backup hard disk 24 so that the user data uniquely recorded by the customer 1 is not deleted by the upgrade of the hard disk 11.

FIG. 8 is a flowchart for explaining the user data saving process in step S12. In FIG. 8, the production number and the manufacturer code assigned to the target hard disk 11 are extracted (step S31). The serial number and the manufacturer code are stored as management information in the backup hard disk 24 in association with the user data of the target hard disk 11. As will be described later, a directory for storing evacuation data of a specific hard disk 11 is provided. For example, if a name including a production number and a manufacturer code is given to this directory, the evacuation of user data can be easily performed. Can be identified.

Next, the backup hard disk 24
To check if there is an evacuation directory associated with the serial number and manufacturer code of the target hard disk 11 (step S32). That is, the user data of the target hard disk 11 is
This is a process for avoiding useless processing beforehand, assuming that the data has already been saved to the backup hard disk 24. As a result of the check, if the evacuation directory for the target hard disk 11 already exists (step S32; YES), a message to that effect and a caution display urging replacement of the hard disk 11 are displayed on the display 26 (step S33), and thereafter. Is not performed.

On the other hand, if there is no evacuation directory for the target hard disk 11 (step S32;
NO), a backup directory to which a name including a serial number and a manufacturer code corresponding to the target hard disk 11 is assigned is created in the backup hard disk 24 before the user data is saved (step S34).

Subsequently, in order to save the user data, the user accesses the target hard disk 11 to read the user data from the user data directory and writes it as the save data in the corresponding save directory of the backup hard disk 24 (step S35). As a result, saved data similar to the user data to be saved is held in the backup hard disk 24. It is desirable to display on the display 26 that copying is in progress during the processing of step S35. Also, when copying is interrupted due to a problem during the processing in step S35, it is desirable to display a caution display to that effect on the display 26. In this case, no further processing is performed.

Next, the original user data of the hard disk 11 and the save data in the save directory of the backup hard disk 24 are compared with each other to determine whether or not they match (step S3).
6). This makes it possible to check whether or not data has been lost due to the evacuation processing in step S35. As a result, when the total data sizes of the user data and the save data match (step S36; YES), a message indicating that copying has been completed normally and a message prompting replacement of the hard disk 11 are displayed on the display 26 (step S37). The process proceeds to the navigation data rewriting step of S13 (FIG. 5). On the other hand, when the total data sizes of the user data and the save data do not match (step S36; N
O), a caution display to that effect is displayed on the display 26 (step S38), and the subsequent processing is not performed.

Next, returning to FIG. 5, in step S13,
A rewriting process of the navigation data recorded on the hard disk 11 is executed. That is, the upgraded navigation data is newly written in place of the old navigation data on the hard disk 11. In the rewriting process of step S13, after the hard disk 11 is once removed from the user data saving device main body 21, a general initialization process is performed by the recording device, and a new navigation data writing process is performed. At this point, the upgraded navigation data is recorded on the hard disk 11, and all the original user data is deleted.

Next, in step S14, a write-back step for the saved data in the backup hard disk 24 is executed. As described above, since it is necessary to return the user data deleted in step S13 to the original state,
The processing is the reverse of that in step S12.

FIG. 9 is a flowchart for explaining the user data write-back step of step S14. In FIG. 9, it is necessary to connect the upgraded hard disk 11 to the user data saving device again, so it is checked whether the hard disk 11 and the backup hard disk 24 are normally connected (step S41). As a result, when the hard disk 11 and the backup hard disk 24 are not normally connected to the user data saving device (step S411; N
O), a caution display to that effect is displayed on the display 26 (step S42), and the subsequent processing is not performed.

If a normal connection is confirmed by the check in step S41 (step S41; YES),
As in step S31 of FIG. 8, the serial number and manufacturer code assigned to the hard disk 11 are extracted (step S43). Next, the backup hard disk 24 is accessed, and it is checked whether or not there is an evacuation directory in which the serial number and the manufacturer code of the hard disk 11 are associated (step S4).
4). That is, since the save data corresponding to the saved user data is held in the save directory created in step S34 of FIG. 8, its existence is confirmed.

As a result of the check in step S44, if the corresponding save directory 24 does not exist in the backup hard disk 24 (step S44; N
O) Since the user data cannot be written back, a message to that effect and a caution display urging the replacement of the hard disk 11 are displayed on the display 26 (step S45), and the subsequent processing is not performed. On the other hand, if the corresponding save directory 24 exists on the backup hard disk 24 (step S44; YES), the user data is written back (step S46).

More specifically, the backup hard disk 24 is accessed, the save data is read from the corresponding save directory, and written back to the user data directory created on the hard disk 11. As a result, the hard disk 11 is again written with the original user data in addition to the upgraded navigation data. It is desirable to display on the display 26 that copying is in progress during the process of step S46. Also, when copying is interrupted due to a problem during the processing of step S46, it is desirable to display that fact on the display 26. In this case,
No further processing is performed.

Next, the total data size of the user data written back to the hard disk 11 and the save data in the save directory of the backup hard disk 24 are compared to determine whether or not they match (see FIG. 1). Step S47). This is a process similar to step S36 in FIG. If the result of the determination in step S47 is that the total data sizes of the user data and the save data do not match (step S47; NO), a caution display to that effect is displayed on the display 26 (step S48), and the subsequent processing is performed. Absent.

On the other hand, if the result of determination in step S47 is that the total data sizes of the user data and the save data match (step S47; YES), an upgrade password is set in the hard disk 11 (step S49). This version upgrade password is a password for permitting access only once after the upgraded hard disk 11 is attached to the navigation device 10. In other words, the originally set user password has been released, but if the hard disk 11 is attached to the navigation device 10 as it is, access is not possible. Therefore, the upgrade password allows access once only when the hard disk 11 is attached to the navigation device 10, and thereafter, the navigation device 10
This is effective when automatically setting the original user password.

Finally, a message indicating that the processing in the write-back process has been completed and a message prompting replacement of the hard disk 11 are displayed on the display 26 (step S50), and the upgrade process for the hard disk 11 is completed. Thereafter, the processes shown in FIGS. 5 to 9 are repeatedly performed on the other hard disks 11 on the line, so that many hard disks 11 can be upgraded.

As described above, the rewriting center 2
According to the version upgrade step e, when the user data of the customer 1 is recorded on the hard disk 11 to be upgraded, only the navigation data can be rewritten while leaving the user data. Therefore, the customer 1 has a great advantage in that the customer 1 can surely leave his / her user data on the hard disk 11 and continuously use it without performing a backup operation by himself before the version upgrade.

[0077]

As described above, according to the present invention, when updating the navigation data in the nonvolatile storage means mounted on the navigation device, the user data is saved and the navigation data is rewritten. Since the user data is written back, when the user data important to the customer is stored in the non-volatile storage means, the navigation data can be upgraded while securely deleting the user data without deleting it.

Further, according to the present invention, when upgrading the navigation data, the business operator can manage various tasks based on the customer database and provide the customer with various options as the version upgrade task.
While reducing the work load of the customer, the business efficiency of the business can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a relationship between a customer, a business operator, and other related business operators regarding version upgrade work according to the present invention.

FIG. 2 is a flowchart illustrating a flow of a version upgrade operation.

FIG. 3 is a flowchart showing a flow in a case where a dealer intervenes between a customer and a business in a version upgrade operation.

FIG. 4 is a flowchart showing a flow in a case where a service man of a service center intervenes between a customer and a business operator in the version upgrade work.

FIG. 5 is a flowchart showing an outline of an entire upgrade process performed in the rewriting center.

FIG. 6 is a flowchart illustrating a hard disk confirmation process.

FIG. 7 is a diagram illustrating an external configuration of a user data saving device.

FIG. 8 is a flowchart illustrating a user data saving process.

FIG. 9 is a flowchart illustrating a user data write-back step.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Customer 2 ... Business 2a ... Reception center 2b ... Inquiry center 2c ... Service center 2d ... Collection center 3 ... Customer database 4 ... Carrier 5 ... Sales shop 10 ... Navigation equipment 11 ... Hard disk 21 ... User data evacuation device main body 22 Reference numerals 23, Connector 24, Backup hard disk 25, Power supply 26, Display

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Kenichiro Yano 25-1, Nishimachi, Yamada-ji, Kawagoe-shi, Saitama Prefecture Pioneer Corporation Inside the Kawagoe Plant (72) Inventor Satoshi Saito 25-1, Nishi-machi, Yamada, Kawagoe-shi, Saitama Pioneer F-term in Kawagoe Factory Co., Ltd. (reference) 2C032 HB02 HC08 2F029 AA02 AC02 AC14 AC20 AD01 5H180 AA01 BB13 FF03 FF22 FF27

Claims (6)

[Claims] 1. A non-volatile storage means which is detachably attached to a navigation device and rewritably stores navigation data and user data, wherein the navigation data is upgraded by updating the navigation data. The method, for rewriting the navigation data for the non-volatile storage unit removed from the navigation device, temporarily saving the user data at the time of the rewriting, and after the rewriting is completed, A version upgrade method for navigation data, wherein the saved user data is written back to the non-volatile storage means to upgrade the version. 2. The version upgrade is performed on the non-volatile storage unit that receives the application for version upgrade from a customer who owns the navigation device and receives a request for pickup, and stores the customer information. 2. The method for upgrading navigation data according to claim 1, wherein the execution of the version upgrade is managed based on a database, and a series of tasks associated with the version upgrade is managed. 3. A series of tasks accompanying the version upgrade include a task of collecting non-volatile storage means,
3. The navigation data version upgrade method according to claim 2, further comprising a return operation of the non-volatile storage unit after the upgrade, and a fee collection operation associated with the upgrade. 4. 4. After receiving an application for the version upgrade by a customer, delivery of a version upgrade member necessary for the customer to perform a version upgrade operation of the nonvolatile storage means by himself / herself based on the customer database. 4. The navigation system according to claim 3, wherein while managing a business, the upgrade is performed on the non-volatile storage unit that receives a pickup request from a customer to whom the upgrade member has been delivered. 5. How to upgrade the data. 5. The collection request from a customer, the collection of the non-volatile storage means, and the return of the non-volatile storage means after the version upgrade are performed by attaching and detaching the non-volatile means, respectively. The method for upgrading navigation data according to claim 3 or 4, wherein the method is performed via a contracted business operator. 6. The method according to claim 1, wherein the nonvolatile storage unit is a hard disk.