Map updating method and device

Abstract

The application relates to the technical field of electronic maps, and provides a map updating method and device, a map updating method for a server end comprises the following steps: acquiring target map data which does not conform to a current map in a real scene; updating first to-be-updated map data corresponding to the target map data in the server end according to the target map data, and generating a release file comprising an updating data field according to a data type to which the target map data belongs; and issuing the release file to a terminal device according to a corresponding release period of the release file, so as to update second to-be-updated map data corresponding to the target map data in the terminal device. Since the release files corresponding to different data types are released according to different release periods, the dynamic data type only involves improvement of data attributes, the data amount is small, bandwidth is not wasted, the release period can be realized according to days, high-precision maps can be updated in time, and the safety of automatic driving is ensured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronic map, and in particular to a map updating method and device. BACKGROUND

[0002] In recent years, the automatic driving technology has entered a stage of rapid development, and the high-precision map has become an important link in the automatic driving solution. However, the map data updating has always been defined as a systematic problem. With the rapid development of China's economy, the frequency of road information change is much higher than before, and the frequency of map data updating has reached the daily update requirement.

[0003] At present, the map data updating is a recognized systematic problem in the industry, and for the high-precision map used in the automatic driving industry, this problem is further magnified, mainly reflected in the following several dimensions:

[0004] 1. Due to the special situation of map data generation process, the map data release needs to complete data collection, data production, data inspection, data compilation and data release, etc. The result is that the data release cycle is long, which does not meet the expectation of automatic driving.

[0005] 2. A set of full-amount high-precision map data has reached the level of GB or more. If the existing map updating method is used, the traffic bandwidth of the vehicle end is also a very high test. If the full-amount update reaches the daily update level, it will cause serious waste of network bandwidth.

[0006] Due to the high safety requirement of the automatic driving technology, how to update the map data in time and without wasting bandwidth is a technical problem to be solved at present. SUMMARY

[0007] The present application provides a map updating method and device to solve the above technical problems existing in the prior art.

[0008] The first aspect of the present application provides a map updating method for a server end, comprising:

[0009] obtaining target map data which does not conform to the current map in the real scene;

[0010] updating the first to-be-updated map data corresponding to the target map data in the server end according to the target map data, and generating a release file including update data field according to the data type to which the target map data belongs;

[0011] downloading the release file to the terminal device according to the corresponding release period of the release file, so as to update the second to-be-updated map data corresponding to the target map data in the terminal device,

[0012] The data types include a dynamic data type and a non-dynamic data type, only the map data of the dynamic data type is updated in data attributes, and the map data of the non-dynamic data type is modified in geometric shapes, and the release cycle of the map data of the dynamic data type is shorter than that of the map data of the non-dynamic data type.

[0013] According to the map updating method provided by the application, the first to-be-updated map data corresponding to the target map data in the server side is updated according to the target map data, and a release file including updated data fields is generated according to the data type to which the target map data belongs, comprising:

[0014] The work material of the work area where the target map data is located is generated, and the work material includes the target map data and the first to-be-updated map data.

[0015] The work task is created according to the work material of the work area.

[0016] For each different work task, it is judged whether the operation of updating the map involves geometric shape modification according to the target map data and the first to-be-updated map data.

[0017] In the case of not involving geometric shape modification, the release file of the dynamic data type is generated according to the updated data attributes, the release file of the dynamic data type is written into the master library to update the first to-be-updated map data, and the release file of the dynamic data type is written into the dynamic release library.

[0018] In the case of involving geometric shape modification, the release file of the non-dynamic data type is generated at least according to the modified geometric shape, and the release file of the non-dynamic data type is written into the master library to update the first to-be-updated map data.

[0019] According to the map updating method provided by the application, the work material of the work area where the target map data is located is generated, comprising:

[0020] The target map data is de-duplicated.

[0021] The de-duplicated target map data is compared with the corresponding first to-be-updated map data in the master library.

[0022] In the case of inconsistent comparison results, the work material is generated.

[0023] According to the map updating method provided by the application, the work task is created according to the work material of the work area, comprising:

[0024] Create a job task, determine whether the job area overlaps with the job area corresponding to the currently executing job task, and merge the job tasks if they overlap.

[0025] According to a map update method provided by the present invention, before writing the release file of the dynamic data type into the dynamic release library, the method further includes: performing deduplication processing on the release file of the dynamic data type.

[0026] According to a map update method provided by the present invention, the release file further includes: a binary string, wherein the binary string has a first character bit representing each data field in the map data and a second character bit representing the update operation, wherein the first character bit corresponding to the field to be updated is 1, and the first character bit corresponding to the other fields is 0.

[0027] According to a map update method provided by the present invention, non-dynamic data types include: patch data types, revision data types, and basic data types.

[0028] The update content of the map data of the patch data type involves only one map area;

[0029] The updated map data of the revised data type involves multiple map areas;

[0030] The update content of the map data of the basic data type involves the entire map area;

[0031] The map data of the dynamic data type is updated based on the patch data type of the previous version, the map data of the patch data type is updated based on the revision data type of the previous version, and the map data of the revision data type is updated based on the base data type of the previous version.

[0032] A second aspect of the present invention provides a map updating method for a terminal device, comprising:

[0033] The release file containing updated data is obtained from the server. The release file is generated based on the data type of the target map data, which is data in the real scene that does not match the current map.

[0034] Update the map data in the terminal device according to the release document.

[0035] The data types include: dynamic data types and non-dynamic data types. Map data that only updates data attributes is the dynamic data type, and map data that modifies geometry is the non-dynamic data type. The release cycle of map data of the dynamic data type is shorter than that of map data of the non-dynamic data type.

[0036] The third aspect of the present application provides a map updating device for a server side, comprising:

[0037] a target data acquisition module configured to acquire target map data that does not conform to a current map in a real scene;

[0038] a release file generation module configured to update first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generate a release file including update data fields according to a data type to which the target map data belongs;

[0039] a release file delivery module configured to deliver the release file to a terminal device according to a release period corresponding to the release file, so as to update second to-be-updated map data corresponding to the target map data in the terminal device,

[0040] wherein the data type includes a dynamic data type and a non-dynamic data type, the map data that only updates data attributes is the dynamic data type, the map data that modifies a geometric shape is the non-dynamic data type, and a release period of the map data of the dynamic data type is less than a release period of the map data of the non-dynamic data type.

[0041] The fourth aspect of the present application provides a map updating device for a terminal device, comprising:

[0042] a release file acquisition module configured to acquire a release file including update data from a server side, the release file being generated according to a data type to which target map data belongs, the target map data being data that does not conform to a current map in a real scene;

[0043] a map data updating module configured to update map data in the terminal device according to the release file,

[0044] wherein the data type includes a dynamic data type and a non-dynamic data type, the map data that only updates data attributes is the dynamic data type, the map data that modifies a geometric shape is the non-dynamic data type, and a release period of the map data of the dynamic data type is less than a release period of the map data of the non-dynamic data type.

[0045] The fifth aspect of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the map updating method according to any one of the above aspects when executing the program.

[0046] The sixth aspect of the present application provides a non-transitory computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the map updating method according to any one of the above aspects.

[0047] The map updating method provided by the application, by acquiring target map data which does not conform to the current map in the real scene; updating the first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a release file including update data fields according to the data type to which the target map data belongs; issuing the release file to the terminal device according to its corresponding release cycle to update the second to-be-updated map data corresponding to the target map data in the terminal device, wherein the data type includes: dynamic data type and non-dynamic data type, only the map data of the dynamic data type is updated in the data attribute, the map data of the non-dynamic data type is modified in the geometric shape, and the release cycle of the map data of the dynamic data type is less than the release cycle of the map data of the non-dynamic data type. Since the release files corresponding to different data types are released according to different release cycles, the dynamic data type only involves the improvement of the data attribute, and the data amount is small, which will not waste bandwidth, and the release cycle can realize daily release, which can update the high-precision map in time and ensure the safety of automatic driving. BRIEF DESCRIPTION OF DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the application or prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0049] Figure 1 is a flow diagram of the map updating method for the server side provided by the application;

[0050] Figure 2 is a flow diagram of the map updating method for the terminal device provided by the application;

[0051] Figure 3 is a structural diagram of the map updating device for the server side provided by the application;

[0052] Figure 4 is a structural diagram of the map updating device for the terminal device provided by the application;

[0053] Figure 5 is a structural diagram of the electronic device provided by the application. DETAILED DESCRIPTION

[0054] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0055] like Figure 1 As shown, the map update method of the first embodiment of the present invention is used on the server side and includes:

[0056] Step S110: Obtain target map data that does not match the current map in the real-world scenario. Specifically, obtaining this target map data mainly includes the following two methods: automatic perception by the vehicle and user feedback. For vehicles with autonomous driving capabilities, the vehicle perceives the actual map data of the driving area during autonomous driving. When the actual map data differs from the corresponding map data in the current map, the actual map data is used as the target map data and uploaded to the server. Alternatively, when the user discovers that the actual map data of the driving area differs from the current navigation map during navigation, the actual map data is uploaded to the server as the target map data. Map data exists in the form of objects in the program implementation. Each map data has a unique map data ID. For example, the road object will contain: road ID and attributes such as bridge, tunnel, whether it is a motor vehicle lane, road segment length, number of lanes, etc. Lane-level data includes attributes such as whether left or right lane changes are allowed, speed limits, and height limits.

[0057] Step S120: Update the first map data to be updated (i.e., data in the map that differs from the real scene) in the server-side according to the target map data, and generate a release file including updated data fields according to the data type of the target map data. That is, the release file only includes the values ​​of the data fields that need to be updated in the map data, and the data volume is relatively small, especially for data that does not involve geometric modifications.

[0058] Step S130: The release file is sent to the terminal device according to its corresponding release cycle to update the second map data to be updated in the terminal device corresponding to the target map data.

[0059] In the embodiment, the data types include a dynamic data type and a non-dynamic data type, the map data that only updates data attributes is the dynamic data type, the map data that modifies a geometric shape is the non-dynamic data type, and the release cycle of the map data of the dynamic data type is shorter than that of the map data of the non-dynamic data type. For example, the information such as road marking (solid line or dashed line), speed limit, and height limit belongs to the attributes of road map data and does not involve road geometric shape, so only the related data field of the road map data needs to be modified, the amount of data to be modified is small, and the release cycle of the modified map data can be shortened. Because of road repair, the number of lanes is changed from three to two, which belongs to the change of road geometric shape, so when the map data is updated, the picture of three lanes in the map data needs to be modified to the picture of two lanes, especially for high-precision map, the amount of picture data is large, and it is not suitable for frequent update, and the corresponding release cycle is large.

[0060] In the map updating method of the embodiment, the release files corresponding to the map data of different data types are released according to different release cycles, the dynamic data type only involves the improvement of data attributes, the amount of data is small, bandwidth is not wasted, the release cycle can be implemented according to day, the high-precision map can be updated in time, and the safety of automatic driving is ensured.

[0061] In the embodiment, step S120 includes:

[0062] The work material of the work area where the target map data is located is generated, and the work material includes the target map data and the first to-be-updated map data. In step S110, the target map data of multiple areas in a real scene is obtained within a period of time, a work area is generated for each target map data, so as to update the map data according to areas.

[0063] The work task is created according to the work material of the work area, that is, a work task is created for each target map data.

[0064] For each different work task, it is judged whether the operation of updating the map involves geometric shape modification according to the target map data and the first to-be-updated map data.

[0065] In the case where the geometric shape modification is not involved, the release file of the dynamic data type is generated according to the updated data attributes, the release file of the dynamic data type is written into the master library to update the first to-be-updated map data, and the release file of the dynamic data type is written into the dynamic release library, and the release cycle of the dynamic release library can be set to daily release, so that the timeliness of map updating is improved.

[0066] In the case of involving geometry modification, at least according to the modified geometry, a release file of the non-dynamic data type is generated, the release file of the non-dynamic data type is written into the master library to update the first to-be-updated map data, and the release file of the non-dynamic data type is written into a non-dynamic release library. The release cycle of the non-dynamic release library can be determined according to the specific non-dynamic data type.

[0067] Specifically, the work materials of the work area where the target map data is located are generated, including:

[0068] The target map data is de-duplicated. In a period of time, multiple vehicles may have passed through the same area and uploaded target map data that does not conform to the current map in the real scene of the area, so de-duplication is needed.

[0069] The de-duplicated target map data is compared with the corresponding first to-be-updated map data in the master library. In actual situations, the vehicle-side map may be an older version, and the server-side is always the latest version, so the first to-be-updated map data in the master library needs to be compared to avoid repeated updates.

[0070] In the case where the comparison result is inconsistent, the work materials are generated, and if the comparison result is consistent, the target map data is ignored.

[0071] In this embodiment, the work tasks are created according to the work materials of the work area, including:

[0072] The work tasks are created, and it is judged whether the work area overlaps with the work area corresponding to the work task being executed. In the case of overlap, the work tasks are merged. For example, a road section is being repaired and needs to adjust the number of lanes. The first target map data uploaded by the vehicle side is related to the data of adjusting the number of lanes. The work materials of the work area where the first target map data is located are generated according to the first target map data, and the first work task is created according to the work materials of the work area. The second intelligence finds that the speed limit of this road section has changed, and the second target map data uploaded by the vehicle side is related to the data of adjusting the speed limit attribute of the lane, and the second work task is created. Because the two intelligence are transmitted to the cloud through two intelligence respectively, two work tasks are generated, and it can be judged from the latitude and longitude coordinates in the first target map data and the second target map data that the two work tasks belong to the same work area, that is, the two work areas overlap.

[0073] In this embodiment, before the release file of the dynamic data type is written into the dynamic release library, the release file of the dynamic data type is de-duplicated. It is avoided that the same target map data is uploaded by two different vehicle sides in succession before release on the same day, and the same release file is generated in succession.

[0074] In the present embodiment, the release file further includes a binary string, the binary string is provided with a first character bit representing each data field in the map data and a second character bit representing an update operation (such as modification, deletion or addition), the first character bit corresponding to the data field to be updated is 1, and the first character bit corresponding to the remaining data field is 0. In this way, the release file only needs to include the map data ID of the target map data and the specific content of the data field to be updated, and the remaining data field can be empty, thereby further reducing the data size of the release file. When the terminal device receives the release file, the map data to be updated can be located through the map data ID, the specific update operation can be obtained through the second character bit in the binary string, and the data field to be updated can be located through the first character bit.

[0075] In the present embodiment, the non-dynamic data type includes a patch data type, a revision data type and a basic data type.

[0076] The update content of the map data of the patch data type relates to and only relates to one map region, the map region is a region obtained by dividing the map according to a grid, and the work region is the map region. For the map data of the patch data type, the updated release period can be set to one week.

[0077] The update content of the map data of the revision data type relates to multiple map regions. For the map data of the revision data type, the updated release period can be set to one month.

[0078] The update content of the map data of the basic data type relates to all map regions. For the map data of the basic data type, the updated release period can be set to one quarter.

[0079] The map data of the dynamic data type is updated based on the patch data type of the previous version, the map data of the patch data type is updated based on the revision data type of the previous version, and the map data of the revision data type is updated based on the basic data type of the previous version. Thus, each update is performed on the basis of the latest version, for example: the dynamic that has been released can only be modified based on the most recent patch that has been released, if there is no patch that has been released recently, the dynamic is modified based on the most recent revision that has been released, and the revision is always available (because the basic data is usually provided by a third party, the revision data cannot be released at the same time as the basic data, and the basic data will have errors that need to be supplemented by the revision, even if a new version of the basic data is released, the errors need to be detected and supplemented by the revision).

[0080] The second embodiment of the present application also provides a map updating method for a terminal device, such as a vehicle-mounted device. The specific flow is as shown in Figure 2 The specific flow is as shown in

[0081] In step S210, a release file including update data is obtained from a server side. The release file is generated according to a data type to which target map data belongs. The target map data is data in a real scene that does not conform to a current map. Specifically, the release file is the release file generated in the first embodiment.

[0082] In step S220, the map data in the terminal device is updated according to the release file.

[0083] The data type includes a dynamic data type and a non-dynamic data type. The map data that only updates data attributes is the dynamic data type, and the map data that modifies a geometric shape is the non-dynamic data type. The release period of the map data of the dynamic data type is shorter than the release period of the map data of the non-dynamic data type.

[0084] Since the server side can send the release file to the terminal device as a daily release period, the map in the terminal device can be updated in time. The data amount of the release file released daily is small, and the waste of bandwidth is avoided.

[0085] Specifically, step S220 includes:

[0086] The original data is loaded in the order of first loading the non-dynamic data type and then loading the dynamic data type. For the non-dynamic data type, the data is loaded in the order of basic data type-> revision data type-> patch data type, that is, the map data in the terminal device is loaded in the order of basic data-> revision-> patch-> dynamic. Of course, only the latest version of each data type is loaded, and the version of the data type loaded later is not lower than the version of the data type loaded earlier.

[0087] The update order is dynamic-> patch-> revision-> basic database, and the data is updated according to the update order. This order only indicates the priority of the data to be updated. Dynamic has the highest priority. If there is no patch at the time, dynamic will update revision. Revision is definitely available.

[0088] The map updating device provided by the present application is described below. The map updating device described below can be correspondingly referred to the map updating method described above.

[0089] As shown in Figure 3As shown, the map updating device of the third embodiment of the present application is used for a server side and comprises:

[0090] The target data acquisition module 310 is configured to acquire target map data that does not conform to the current map in the real scene.

[0091] The release file generation module 320 is configured to update first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generate a release file including update data fields according to a data type to which the target map data belongs.

[0092] The release file delivery module 330 is configured to deliver the release file to a terminal device according to a release period corresponding to the release file, so as to update second to-be-updated map data corresponding to the target map data in the terminal device.

[0093] The data type includes a dynamic data type and a non-dynamic data type, only the map data of the dynamic data type is updated in terms of data attributes, only the map data of the non-dynamic data type is modified in terms of geometric shapes, and the release period of the map data of the dynamic data type is shorter than the release period of the map data of the non-dynamic data type.

[0094] In the map updating device, the release files corresponding to the map data of different data types are released according to different release periods, the dynamic data type only involves improvement of data attributes, and the data volume is small, so that bandwidth is not wasted, the release period can be implemented as daily release, and high-precision maps can be updated in time, thereby ensuring the safety of autonomous driving.

[0095] Optionally, the release file generation module 320 comprises:

[0096] The work material generation module is configured to generate work materials of a work area where the target map data is located, and the work materials include the target map data and the first to-be-updated map data.

[0097] The work task creation module is configured to create work tasks according to the work materials of the work area.

[0098] The shape modification judgment module is configured to, for each different work task, judge whether the operation of updating the map involves geometric shape modification according to the target map data and the first to-be-updated map data.

[0099] The dynamic release file generation module is configured to, in the case where the geometric shape modification is not involved, generate the release file of the dynamic data type according to the updated data attributes, write the release file of the dynamic data type into a master database to update the first to-be-updated map data, and write the release file of the dynamic data type into a dynamic release database.

[0100] The non-dynamic publishing file generation module is configured to generate a publishing file of the non-dynamic data type according to at least the modified geometry shape in a case involving geometry shape modification, write the publishing file of the non-dynamic data type into the master database to update the first to-be-updated map data, and write the publishing file of the non-dynamic data type into a non-dynamic publishing database.

[0101] Optionally, the job material generation module is specifically configured to:

[0102] De-duplicate the target map data.

[0103] Compare the de-duplicated target map data with the corresponding first to-be-updated map data in the master database.

[0104] In a case where the comparison result is inconsistent, generate the job material.

[0105] Optionally, the job task creation module is specifically configured to create a job task, judge whether the job area and a job area corresponding to a job task being executed overlap, and in a case of overlap, merge the job tasks.

[0106] Optionally, the dynamic publishing file generation module is further configured to de-duplicate the publishing file of the dynamic data type.

[0107] Optionally, the publishing file further includes a binary string, the binary string is provided with a first character bit representing each data field in the map data and a second character bit representing an update operation, and a first character bit corresponding to a field that needs to be updated is 1 and first character bits corresponding to the remaining fields are 0.

[0108] Optionally, the non-dynamic data type includes a patch data type, a revision data type, and a base data type.

[0109] The update content of the map data of the patch data type involves and only involves one map area.

[0110] The update content of the map data of the revision data type involves multiple map areas.

[0111] The update content of the map data of the base data type involves all map areas.

[0112] The map data of the dynamic data type is updated based on the patch data type of the previous version, the map data of the patch data type is updated based on the revision data type of the previous version, and the map data of the revision data type is updated based on the base data type of the previous version.

[0113] As Figure 4As shown, the map updating device of the fourth embodiment of the present application is used for a terminal device and comprises:

[0114] The release file acquisition module 410 is configured to acquire a release file including update data from a server side, the release file being generated according to a data type to which target map data belongs, the target map data being data in a real scene that does not conform to a current map.

[0115] The map data updating module 420 is configured to update map data in the terminal device according to the release file.

[0116] The data type includes a dynamic data type and a non-dynamic data type, map data that only updates data attributes is the dynamic data type, map data that modifies a geometric shape is the non-dynamic data type, and a release period of the dynamic data type is shorter than a release period of the non-dynamic data type.

[0117] Figure 5 An example of a schematic diagram of a physical structure of an electronic device is shown in FIG. 5. Figure 5 As shown, the electronic device can include a processor 510, a communications interface 520, a memory 530, and a communications bus 540, wherein the processor 510, the communications interface 520, and the memory 530 can communicate with each other through the communications bus 540. The processor 510 can invoke a logical instruction in the memory 530 to execute a map updating method for a server side, the method comprising:

[0118] Acquiring target map data in a real scene that does not conform to a current map.

[0119] Updating first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a release file including update data fields according to a data type to which the target map data belongs.

[0120] Distributing the release file to a terminal device according to a release period corresponding to the release file, to update second to-be-updated map data corresponding to the target map data in the terminal device.

[0121] The data type includes a dynamic data type and a non-dynamic data type, map data that only updates data attributes is the dynamic data type, map data that modifies a geometric shape is the non-dynamic data type, and a release period of the dynamic data type is shorter than a release period of the non-dynamic data type.

[0122] Or executing a map updating method for a terminal device, the method comprising:

[0123] obtaining a release file including update data from a server side, the release file being generated according to a data type to which target map data belongs, the target map data being data in a real scene that does not conform to a current map;

[0124] updating map data in a terminal device according to the release file,

[0125] wherein the data type includes a dynamic data type and a non-dynamic data type, only map data of a data attribute being the dynamic data type, and map data of a geometric shape being the non-dynamic data type, a release period of the dynamic data type being less than a release period of the non-dynamic data type.

[0126] In addition, the logic instructions in the memory 530 described above can be implemented in the form of a software function unit and sold or used as an independent product, and can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0127] On the other hand, the present application also provides a computer program product, the computer program product includes a computer program, the computer program can be stored on a non-transitory computer readable storage medium, when the computer program is executed by a processor, the computer can execute the map update method for the server side provided by the above-mentioned methods, the method includes:

[0128] obtaining target map data in a real scene that does not conform to a current map.

[0129] updating first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a release file including an update data field according to a data type to which the target map data belongs.

[0130] downloading the release file to a terminal device according to a corresponding release period of the release file, to update second to-be-updated map data corresponding to the target map data in the terminal device.

[0131] The data type includes a dynamic data type and a non-dynamic data type, map data only updating data attributes is the dynamic data type, map data modifying geometric shapes is the non-dynamic data type, and the release cycle of the dynamic data type is shorter than that of the non-dynamic data type.

[0132] Or a map updating method for a terminal device is executed, and the method includes:

[0133] A release file including update data is obtained from a server side, the release file is generated according to a data type to which target map data belongs, and the target map data is data in a real scene that does not conform to a current map.

[0134] The map data in the terminal device is updated according to the release file.

[0135] The data type includes a dynamic data type and a non-dynamic data type, map data only updating data attributes is the dynamic data type, map data modifying geometric shapes is the non-dynamic data type, and the release cycle of the dynamic data type is shorter than that of the non-dynamic data type.

[0136] In another aspect, the application also provides a non-transitory computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement a map updating method for a server side provided by the above-mentioned methods, and the method includes:

[0137] Target map data in a real scene that does not conform to a current map is obtained.

[0138] First to-be-updated map data corresponding to the target map data in the server side is updated according to the target map data, and a release file including update data is generated according to a data type to which the target map data belongs.

[0139] The release file is sent to a terminal device according to a corresponding release cycle of the release file, so as to update second to-be-updated map data corresponding to the target map data in the terminal device.

[0140] The data type includes a dynamic data type and a non-dynamic data type, map data only updating data attributes is the dynamic data type, map data modifying geometric shapes is the non-dynamic data type, and the release cycle of the dynamic data type is shorter than that of the non-dynamic data type.

[0141] Or a map updating method for a terminal device is executed, and the method includes:

[0142] Obtain a release file including update data from a server side, the release file being generated according to a data type to which target map data belongs, the target map data being data in a real scene that does not conform to current map data.

[0143] Update the map data in the terminal device according to the release file.

[0144] The data type includes a dynamic data type and a non-dynamic data type, only the map data of the dynamic data type is updated in terms of data attributes, and only the map data of the non-dynamic data type is modified in terms of geometric shapes, and a release cycle of the map data of the dynamic data type is shorter than a release cycle of the map data of the non-dynamic data type.

[0145] The above-described apparatus embodiments are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed on multiple network units. Part or all of the modules can be selected to achieve the purpose of the embodiment scheme according to actual needs. Those skilled in the art can understand and implement without creative labor.

[0146] From the above description of the embodiments, those skilled in the art can clearly understand that the embodiments can be realized by means of software plus a necessary general hardware platform, and of course can also be realized by hardware. Based on such understanding, the above technical solutions, essentially or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments.

[0147] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A map update method characterized by comprising: For the server side, comprising: acquiring target map data in a real scene that does not conform to a current map; updating first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a release file including update data fields according to a data type to which the target map data belongs; downloading the release file to a terminal device according to a corresponding release cycle thereof to update second to-be-updated map data corresponding to the target map data in the terminal device, wherein the data type includes a dynamic data type and a non-dynamic data type, only map data of a data attribute is the dynamic data type, map data of a geometric shape is the non-dynamic data type, a release cycle of the dynamic data type is less than a release cycle of the non-dynamic data type, the release file of the dynamic data type is stored in a dynamic release library, and the release file of the non-dynamic data type is stored in a non-dynamic release library.

2. The map update method according to claim 1, characterized by, updating first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a release file including update data fields according to a data type to which the target map data belongs, comprises: generating work materials of a work area in which the target map data is located, the work materials including the target map data and the first to-be-updated map data; creating a work task according to the work materials of the work area; for each different work task, judging whether an operation of updating a map involves geometric shape modification according to the target map data and the first to-be-updated map data; in a case where the operation does not involve geometric shape modification, generating a release file of the dynamic data type according to an updated data attribute, writing the release file of the dynamic data type into a master library to update the first to-be-updated map data, and writing the release file of the dynamic data type into a dynamic release library; in a case where the operation involves geometric shape modification, generating a release file of the non-dynamic data type according to at least a modified geometric shape, writing the release file of the non-dynamic data type into the master library to update the first to-be-updated map data, and writing the release file of the non-dynamic data type into a non-dynamic release library.

3. The map update method according to claim 2, characterized by, generating work materials of a work area in which the target map data is located, comprises: performing deduplication processing on the target map data; comparing the deduplicated target map data with corresponding first to-be-updated map data in a master library; in a case where a comparison result is inconsistent, generating the work materials.

4. The map update method according to claim 2, characterized by, creating a work task according to the work materials of the work area, comprises: creating the work task, judging whether the work area overlaps with a work area corresponding to a work task being executed, and merging the work tasks in a case of overlap.

5. The map update method according to claim 2, characterized by, Before writing the release file of the dynamic data type into the dynamic release library, further comprising: performing deduplication processing on the release file of the dynamic data type.

6. The map update method according to claim 1, characterized by, The publishing file further includes a binary string, the binary string is provided with a first character bit representing each data field in the map data and a second character bit representing an update operation, the first character bit corresponding to a field that needs to be updated is 1, and the first character bit corresponding to the remaining fields is 0.

7. The map update method according to any one of claims 1 to 6, characterized by, The non-dynamic data type includes a patch data type, a revision data type and a base data type, The update content of the map data of the patch data type relates to and only relates to one map region; The update content of the map data of the revision data type relates to multiple map regions; The update content of the map data of the base data type relates to all map regions; The map data of the dynamic data type is updated based on the patch data type of the previous version, the map data of the patch data type is updated based on the revision data type of the previous version, and the map data of the revision data type is updated based on the base data type of the previous version.

8. A map update method characterized by comprising: For a terminal device, comprising: Obtaining a publishing file including update data from a server side, the publishing file is generated according to the data type to which the target map data belongs, and the target map data is data in a real scene that does not conform to the current map; Updating the map data in the terminal device according to the publishing file, Wherein, the data type includes: dynamic data type and non-dynamic data type, only updating the data attribute of the map data is the dynamic data type, modifying the geometric shape of the map data is the non-dynamic data type, the publishing period of the dynamic data type map data is less than the publishing period of the non-dynamic data type map data, the publishing file of the dynamic data type is stored in the dynamic publishing library, and the publishing file of the non-dynamic data type is stored in the non-dynamic publishing library.

9. A map update device characterized by comprising: For a server side, comprising: A target data acquisition module for acquiring target map data in a real scene that does not conform to the current map; A publishing file generation module for updating first to-be-updated map data corresponding to the target map data in the server side according to the target map data, and generating a publishing file including an update data field according to the data type to which the target map data belongs; A publishing file delivery module for delivering the publishing file to a terminal device according to its corresponding publishing period to update second to-be-updated map data corresponding to the target map data in the terminal device, Wherein, the data type includes: dynamic data type and non-dynamic data type, only updating the data attribute of the map data is the dynamic data type, modifying the geometric shape of the map data is the non-dynamic data type, the publishing period of the dynamic data type map data is less than the publishing period of the non-dynamic data type map data, the publishing file of the dynamic data type is stored in the dynamic publishing library, and the publishing file of the non-dynamic data type is stored in the non-dynamic publishing library.

10. A map update device characterized by comprising: For a terminal device, comprising: A publishing file acquisition module for obtaining a publishing file including update data from a server side, the publishing file is generated according to the data type to which the target map data belongs, and the target map data is data in a real scene that does not conform to the current map; A map data updating module is configured to update map data in a terminal device according to the release file, The data types include dynamic data types and non-dynamic data types, map data only updating data attributes is the dynamic data type, and map data modifying geometric shapes is the non-dynamic data type. The release cycle of the dynamic data type is shorter than that of the non-dynamic data type. The release file of the dynamic data type is stored in a dynamic release library, and the release file of the non-dynamic data type is stored in a non-dynamic release library.

11. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor implements the map updating method in any one of claims 1-7 or the map updating method in claim 8 when executing the program.

12. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program implements the map updating method in any one of claims 1-7 or the map updating method in claim 8 when executed by the processor.

Images