Map data management method, device and system, electronic equipment and computer program product

Abstract

The invention discloses a map data management method, device and system, electronic equipment and a computer program product, and the method is executed by a map data management client, and comprises the steps: sending a map data pulling request to a map data management server when the client is started, the map data pulling request is used for pulling map data in a specified range or in a total amount; receiving map data returned by the server and performing local caching, wherein the map data is map data containing a map query structure; when the map data is queried, the map data is loaded from the local cache and queried. According to the method and the device, the map data user can flexibly pull the map data according to own service requirements, so that the map data use requirements of different service parties are met; the map data is cached in the local of each user, so that the loading and using efficiency of the map data is improved; a client-server mode is adopted, services irrelevant to services are separated from and decoupled from the services, and the map data management cost is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of map data management, and in particular to a map data management method, device, system, electronic equipment, and computer program product. Background Art

[0002] In the existing technical architecture, the management and use of map data by various business systems mainly rely on a relatively traditional processing process. This process can be roughly divided into the following three core steps:

[0003] First, the original map files are initialized and stored in a specified directory. In particular, when Docker is used for deployment, this directory also needs to be mounted to ensure that the map files can be correctly accessed by the application in the container.

[0004] Secondly, a SDK (Software Development Kit) dedicated to parsing map data is introduced through Maven. As a key component for map data processing, the path of this SDK needs to be clearly specified in the system configuration file.

[0005] Finally, during the project startup process, the parsing module in the SDK will be responsible for reading the map files stored in the specified directory and organizing them into an efficient tree search structure, aiming to improve the efficiency of subsequent queries on map data, thereby meeting the business system's needs for fast access to map data.

[0006] However, although this processing flow meets the basic needs of the business system for map data to a certain extent, there are at least the following technical problems in the actual application process:

[0007] 1) Inflexible data loading: No matter how large a range of map data the business system actually needs, the full amount of map data will be loaded, which not only leads to a waste of resources, but also increases the processing pressure of the business system;

[0008] 2) Large disk space usage: As long as the business system relies on map data, it will need to occupy corresponding disk space locally to store this data, resulting in a waste of resources on the business system side.

[0009] 3) Slow startup speed: Since the business system needs to load and parse the full amount of map data from the disk at startup, this process is often time-consuming, which not only affects the startup speed of the system, but may also slow down the deployment and launch progress of the entire project. Summary of the invention

[0010] The embodiments of the present application provide a map data management method, device, electronic device, and computer program product to improve the convenience and flexibility of map data users in managing and using map data.

[0011] The present application embodiment adopts the following technical solutions:

[0012] In a first aspect, an embodiment of the present application provides a map data management method, wherein the map data management method is executed by a map data management client, and the map data management method includes:

[0013] When the map data management client is started, a map data pull request is sent to the map data management server, wherein the map data pull request is a request for pulling map data of a specified range or full map data;

[0014] receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure;

[0015] When the map data management client queries the map data, the map data is loaded from the local cache and queried.

[0016] Optionally, when the map data management client is started, sending a map data pull request to the map data management server includes:

[0017] When the map data management client is started, determine whether the map data can be loaded from the local cache;

[0018] If not, a map data pull request is sent directly to the map data management server;

[0019] If so, it is determined whether the locally cached map data needs to be updated based on the locally cached map data, and if the locally cached map data needs to be updated, a map data pull request is sent to the map data management server.

[0020] Optionally, determining whether the locally cached map data needs to be updated according to the locally cached map data includes:

[0021] Parsing the locally cached map data to obtain a parsing result of the locally cached map data, wherein the parsing result of the map data includes version information of the map data;

[0022] Obtaining the latest version of the map data from the map data management server;

[0023] It is determined whether the locally cached map data needs to be updated according to the version information of the locally cached map data and the latest version information of the map data.

[0024] Optionally, when the map data management client is started, sending a map data pull request to the map data management server includes:

[0025] Configure the map data range in the configuration file;

[0026] The map data fetching request is sent to the map data management server according to the map data range.

[0027] Optionally, the map data management method further includes:

[0028] When the map data management client is started, the message subscription configuration information is pulled from the map data management server;

[0029] Establishing a subscription connection for a target message queue with the map data management server based on the message subscription configuration information, wherein the target message queue is used to cache map data update messages issued by the map data management server;

[0030] In the case of subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message;

[0031] The map data in the local cache is updated using the updated map data.

[0032] Optionally, in the case of subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message comprises:

[0033] In the case of subscribing to the map data update message cached in the target message queue, parsing the map data update message to obtain a parsing result of the map data update message, wherein the parsing result of the map data update message includes a map data update range;

[0034] Get the map data range in the configuration file;

[0035] Determining whether it is necessary to update the locally cached map data according to the map data range in the configuration file and the map data update range;

[0036] When the locally cached map data needs to be updated, the updated map data is pulled from the map data management server.

[0037] Optionally, the map data management method further includes:

[0038] Configure the offline usage strategy of map data in the configuration file;

[0039] In the case where the map data management client queries the map data, loading the map data from the local cache and querying the map data includes:

[0040] In the case that the map data management client and the map data management server cannot communicate, based on the offline use policy of the map data, the map data is loaded from the local cache and queried.

[0041] In a second aspect, an embodiment of the present application further provides a map data management device, wherein the map data management device is applied to a map data management client, and the map data management device includes:

[0042] A data pulling unit, used for sending a map data pulling request to a map data management server when the map data management client is started, wherein the map data pulling request is a request for pulling map data of a specified range or full map data;

[0043] A local cache unit, used for receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure;

[0044] The query unit is used to load the map data from the local cache and perform the query when the map data management client queries the map data.

[0045] In a third aspect, an embodiment of the present application further provides a map data management system, wherein the map data management system comprises at least one map data management client and a map data management server, wherein the map data management client is used to execute any of the aforementioned map data management methods, and the map data management server is used to execute:

[0046] When the map data management server is started, a map file is obtained and initialized to obtain initialized map data, wherein the initialized map data is map data including a map query structure;

[0047] Receiving a map data fetching request sent by the map data management client;

[0048] Map data is pulled according to the map data pulling request and returned to the map data management client.

[0049] In a fourth aspect, an embodiment of the present application further provides an electronic device, including:

[0050] A processor; and a memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor executes any of the aforementioned map data management methods.

[0051] In a fifth aspect, an embodiment of the present application further provides a computer program product, including a computer program or instructions, which implement any of the aforementioned map data management methods when executed by a processor.

[0052] At least one of the above technical solutions adopted in the embodiment of the present application can achieve the following beneficial effects: the map data management method of the embodiment of the present application is executed by the map data management client. When the map data management client is started, a map data pull request is sent to the map data management server, and the map data pull request refers to a request for pulling map data of a specified range or full map data; then the map data returned by the map data management server is received and cached locally, and the map data is map data containing a map query structure; finally, when the map data management client queries the map data, the map data is loaded from the local cache and queried. The map data management method of the embodiment of the present application supports the map data management client, i.e., the map data user, to flexibly pull map data from the server according to its own business needs, without having to pull full data every time, thereby meeting the map data usage needs of different business parties; on the other hand, the map data is cached locally in each map data user, without having to load it from the disk every time, thereby improving the efficiency of loading and using map data; on the other hand, the client-server model is adopted to separate and decouple functional services unrelated to the business party from specific businesses, thereby reducing the map data management cost of the business party. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0054] Figure 1 A flowchart of a map data management method in an embodiment of the present application;

[0055] Figure 2 This is a structural diagram of a map data management device in an embodiment of the present application;

[0056] Figure 3 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0058] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0059] The present application embodiment provides a map data management method, such as Figure 1 As shown, a flowchart of a map data management method in an embodiment of the present application is provided. The map data management method is executed by a map data management client, and the map data management method at least includes the following steps S110 to S130:

[0060] Step S110, when the map data management client is started, a map data pull request is sent to the map data management server, wherein the map data pull request is a request for pulling map data of a specified range or full map data.

[0061] The map data management method of the embodiment of the present application is executed by a map data management client, which can be deployed in the form of an SDK in a business system that uses map data. The business system uses the SDK that implements the map data management function through Maven. In the vehicle-road-cloud collaborative scenario, the business system that uses map data may involve the vehicle side, the road side, and the cloud side. Since there are obvious differences in the map data usage requirements between the vehicle side, the cloud side, and the road side, the business system of the embodiment of the present application mainly refers to the road side and the cloud side.

[0062] In the process of managing and using map data, the business system needs to start the map data management client first, then establish a communication connection with the map data management server, and send a map data pull request to the server. The map data pull request here can be used to pull the full amount of map data from the server, and also supports pulling map data within a specified range. The specific method of pulling can be flexibly set by each map data user according to their own business needs. For example, for a cloud engine, it may be necessary to pull the full amount of map data, while for road-side equipment deployed on a specific road section, only the local map data of the covered road section area needs to be pulled.

[0063] Step S120, receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure.

[0064] After sending a map data pull request to the map data management server, the map data management server will receive the map data returned by the map data management server. The map data management server will pull the full amount of map data or map data of a specified range according to the client's request. The map data here refers to map data with a tree query structure, which is constructed and maintained by the server. The client caches the map data returned by the server locally for subsequent queries.

[0065] The embodiment of the present application does not require each business system to build and maintain the index structure of the map data. The index structure is created and maintained uniformly by the server, thereby further reducing the map data management cost of each business system and saving resources.

[0066] Step S130: when the map data management client queries the map data, the map data is loaded from the local cache and queried.

[0067] Based on the local cached map data, when the map data management client needs to query and use the map data, the map data can be quickly loaded directly from the local cache, and the required map data can be quickly queried based on the query structure of the map data.

[0068] The map data management method of the embodiment of the present application supports, on the one hand, a map data management client, i.e., a map data user, which can flexibly pull map data from the server according to its own business needs, without having to pull the full amount of data every time, thereby meeting the map data usage needs of different business parties; on the other hand, the map data is cached locally at each map data user, without having to load it from the disk every time, thereby improving the efficiency of map data loading and usage; on the other hand, the client-server model is adopted to separate and decouple functional services unrelated to the business party from specific businesses, thereby reducing the map data management costs of the business party.

[0069] In some embodiments of the present application, when the map data management client is started, sending a map data pull request to the map data management server includes: when the map data management client is started, determining whether the map data can be loaded from the local cache; if not, directly sending a map data pull request to the map data management server; if yes, determining whether the locally cached map data needs to be updated based on the locally cached map data, and sending a map data pull request to the map data management server if the locally cached map data needs to be updated.

[0070] For the business system, it is not necessary to initiate a request to pull map data from the server every time the client is started. It can determine whether it is necessary to initiate a request to pull map data based on the actual situation. Specifically, when the map data management client is started, it can first determine whether the client has cached map data locally. If there is cached map data, it is not necessary to initiate a request to pull map data from the server. If not, it will initiate a request to pull map data from the server.

[0071] Since map data is not updated frequently in actual scenarios, the above judgment strategy can, to a certain extent, avoid the waste of resources caused by requesting the remote server to pull data every time.

[0072] In some embodiments of the present application, determining whether the locally cached map data needs to be updated based on the locally cached map data includes: parsing the locally cached map data to obtain a parsing result of the locally cached map data, the parsing result of the map data including version information of the map data; obtaining the latest version information of the map data from the map data management server; and determining whether the locally cached map data needs to be updated based on the version information of the locally cached map data and the latest version information of the map data.

[0073] Considering the possibility of irregular updates of map data, in order to ensure the accuracy of map data usage, the embodiment of the present application can also further determine whether the map data in the local cache needs to be updated when the map data already exists in the local cache. Specifically, the locally cached map data can be loaded and parsed first, and the version information of the map data can be parsed out. At the same time, the latest version information of the current map data can be pulled from the server, and the version information of the locally cached map data can be compared with the latest version information. If they are consistent, it means that the map data does not need to be updated. If they are inconsistent, it means that the locally cached map data is not the latest, and the latest map data needs to be pulled from the server again to update the locally cached map data.

[0074] It should be noted that the updated map data is generated on the server side, and the client side only needs to make a conditional judgment on whether to update.

[0075] In some embodiments of the present application, when the map data management client is started, sending the map data pull request to the map data management server includes: configuring a map data range in a configuration file; and sending the map data pull request to the map data management server according to the map data range.

[0076] As mentioned above, the embodiments of the present application support the business system to flexibly configure the range of map data that needs to be pulled according to its own map data usage requirements. Specifically, each business system client will maintain a configuration file. The business system can add configuration information for the map data range based on the original configuration file. For example, it can configure the center longitude and latitude coordinates and range information. When it is necessary to pull data, the configuration information of the map data range is carried, and the need to pull map data within the specified range can be realized. Of course, if the map data range is not configured, the full amount of data will be pulled by default.

[0077] In actual application scenarios, since the area monitored by the road side and the cloud is basically fixed, the range of the map data configured above is also basically fixed. Of course, this does not constitute a restriction on the configuration of the map data range by the road side and the cloud side, that is, the configuration can be adjusted according to needs.

[0078] In some embodiments of the present application, the map data management method also includes: when the map data management client is started, pulling message subscription configuration information from the map data management server; establishing a subscription connection to a target message queue with the map data management server based on the message subscription configuration information, the target message queue being used to cache map data update messages published by the map data management server; when subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message; and updating the map data in the local cache using the updated map data.

[0079] In the existing map data management solution, when map data is updated, the new map file needs to be synchronized to all business systems that use this data. This process is not only cumbersome and complex, but also prone to errors, which brings great challenges to the maintenance and management of map data.

[0080] Based on this, the embodiment of the present application is based on the client-server (Server-Client) architecture and adopts the message queue mode to update and maintain the map data. In this mode, the server is responsible for building and maintaining the message queue, as well as maintaining the updated map data and publishing the map update messages to the message queue. The client mainly subscribes to the message queue in advance according to its own needs. Specifically, when the client starts, it can pull the configuration information of the message subscription from the server, such as the name, address, subscription key and other configuration information of the message queue, and establish a subscription connection with the server based on the configuration information. When there is a new update message in the message queue, the client can automatically pull the updated map data from the server.

[0081] In the above process, on the one hand, the server does not need to actively push updated map data to each business party, nor does it need to pay attention to which business parties have subscribed to the map update messages on the message queue. It only needs to pay attention to whether the map data maintained by the server is updated. On the other hand, the client only needs to pay attention to whether there is a subscribed map update message published. When the server is connected to a large number of business devices, the use of this message queue publish-subscribe method can improve the efficiency and convenience of map data management and use.

[0082] In some embodiments of the present application, in the case of subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message includes: in the case of subscribing to the map data update message cached in the target message queue, parsing the map data update message to obtain a parsing result of the map data update message, the parsing result of the map data update message including a map data update range; obtaining the map data range in the configuration file; determining whether it is necessary to update the locally cached map data based on the map data range in the configuration file and the map data update range; and pulling the updated map data from the map data management server if it is necessary to update the locally cached map data.

[0083] In the above-mentioned embodiment, the update message of the map data published by the server to the message queue is essentially a message that will be published as long as the map data on the server is updated. Each business system that subscribes to the message queue will pull the updated map data from the server for local update. However, considering that the scope of map data maintained and managed by different business systems may be different, not every map data updated by the server will affect the map data cached locally by the client of the business system.

[0084] Based on this, the embodiment of the present application further sets the judgment condition for data update. First, the server needs to clarify the map data range of this update and publish the updated map data range to the message queue. Then, after the client obtains the subscribed map update message, it first parses the map update message to parse out the data range of this map update, and then compares it with the map data range required for local cache maintenance or configuration. If the data range overlaps, it means that this update affects the map data cached locally on the client, and only then will the updated map data be pulled from the server. This judgment strategy can further avoid unnecessary waste of resources.

[0085] In some embodiments of the present application, the map data management method further includes: configuring an offline usage policy of the map data in a configuration file; when the map data management client queries the map data, loading the map data from the local cache and querying it includes: when the map data management client and the map data management server cannot communicate, based on the offline usage policy of the map data, loading the map data from the local cache and querying it.

[0086] Taking into account that the communication connection between the client and the server is not always stable and reliable, the embodiment of the present application can also implement an offline strategy in the client SDK. By supporting the configuration of the offline strategy in the configuration file, when the client cannot communicate with the server, it can continue to use the locally cached map data to ensure basic map data usage functions.

[0087] The present application also provides a map data management device 200, such as Figure 2 As shown, a structural schematic diagram of a map data management device in an embodiment of the present application is provided. The map data management device is applied to a map data management client. The map data management device 200 includes: a data pulling unit 210, a local cache unit 220 and a query unit 230, wherein:

[0088] The data pulling unit 210 is used to send a map data pulling request to the map data management server when the map data management client is started, wherein the map data pulling request is a request for pulling map data of a specified range or full map data;

[0089] A local cache unit 220, for receiving the map data returned by the map data management server and performing local cache, wherein the map data is map data including a map query structure;

[0090] The query unit 230 is used to load the map data from the local cache and perform the query when the map data management client queries the map data.

[0091] In some embodiments of the present application, the data pulling unit 210 is specifically used to: when the map data management client is started, determine whether the map data can be loaded from the local cache; if not, directly send a map data pulling request to the map data management server; if yes, determine whether the locally cached map data needs to be updated based on the locally cached map data, and send a map data pulling request to the map data management server if the locally cached map data needs to be updated.

[0092] In some embodiments of the present application, the data pulling unit 210 is specifically used to: parse the locally cached map data to obtain the parsing result of the locally cached map data, the parsing result of the map data including the version information of the map data; obtain the latest version information of the map data from the map data management server; determine whether the locally cached map data needs to be updated based on the version information of the locally cached map data and the latest version information of the map data.

[0093] In some embodiments of the present application, the data pulling unit 210 is specifically used to: configure a map data range in a configuration file; and send the map data pulling request to the map data management server according to the map data range.

[0094] In some embodiments of the present application, the map data management device 200 also includes: a subscription pulling unit, which is used to pull message subscription configuration information from the map data management server when the map data management client is started; a connection unit, which is used to establish a subscription connection of a target message queue with the map data management server based on the message subscription configuration information, and the target message queue is used to cache map data update messages published by the map data management server; the data pulling unit is also used to: when subscribing to the map data update message cached in the target message queue, pull updated map data from the map data management server based on the map data update message; an update unit, which is used to update the map data in the local cache using the updated map data.

[0095] In some embodiments of the present application, the data pulling unit 210 is further used to: when subscribing to the map data update message cached in the target message queue, parse the map data update message to obtain a parsing result of the map data update message, wherein the parsing result of the map data update message includes a map data update range; obtain the map data range in the configuration file; determine whether it is necessary to update the locally cached map data according to the map data range in the configuration file and the map data update range; and when it is necessary to update the locally cached map data, pull the updated map data from the map data management server.

[0096] In some embodiments of the present application, the map data management device 200 also includes: a configuration unit, used to configure an offline usage policy of the map data in a configuration file; the query unit is specifically used to: when the map data management client and the map data management server cannot communicate, based on the offline usage policy of the map data, load the map data from the local cache and query it.

[0097] It can be understood that the above-mentioned map data management device can implement each step of the map data management method provided in the above-mentioned embodiment, and the relevant explanations about the map data management method are applicable to the map data management device and will not be repeated here.

[0098] The embodiment of the present application also provides a map data management system, wherein the map data management system includes at least one map data management client and a map data management server, the map data management client is used to execute any of the aforementioned map data management methods, and the map data management server is used to execute: when the map data management server is started, obtain a map file and initialize it to obtain initialized map data, wherein the initialized map data is map data containing a map query structure; receive a map data pull request sent by the map data management client; pull map data according to the map data pull request and return it to the map data management client.

[0099] The map data management system of the embodiment of the present application is composed of a map data management client and a map data management server. The map data management server is mainly responsible for the initialization of map files, query structure construction, and map version maintenance. The server relies on map data in the form of map files, completes map file initialization at startup, and constructs the data into a tree query structure to facilitate subsequent client quick queries.

[0100] The map data management system of the embodiment of the present application adopts the Server-Client mode, which realizes the separation and decoupling of map data management and maintenance from specific business. For the map data management server, there is no need to pay attention to which specific users are connected, nor is there a need to synchronize new map files to each user when the map data is updated; for the map data management client, the query and use of map data are more convenient, and only the relevant jar package needs to be introduced and simple configuration is performed in the configuration file.

[0101] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 3 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0102] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0103] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0104] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a map data management device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0105] When the map data management client is started, a map data pull request is sent to the map data management server, wherein the map data pull request is a request for pulling map data of a specified range or full map data;

[0106] receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure;

[0107] When the map data management client queries the map data, the map data is loaded from the local cache and queried.

[0108] The above application Figure 1The method performed by the map data management device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by a hardware integrated logic circuit in the processor or a software instruction. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0109] The present application also provides a computer program product, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 1 The method executed by the map data management device in the illustrated embodiment is specifically used to execute:

[0110] When the map data management client is started, a map data pull request is sent to the map data management server, wherein the map data pull request is a request for pulling map data of a specified range or full map data;

[0111] receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure;

[0112] When the map data management client queries the map data, the map data is loaded from the local cache and queried.

[0113] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0114] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0115] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0116] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0117] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0118] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0119] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0120] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0121] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0122] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A map data management method, wherein: The map data management method is executed by a map data management client, and the map data management method includes: When the map data management client is started, a map data pull request is sent to the map data management server, wherein the map data pull request is a request for pulling map data of a specified range or full map data; receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure; When the map data management client queries the map data, the map data is loaded from the local cache and queried.

2. The map data management method according to claim 1, wherein: When the map data management client is started, sending a map data pull request to the map data management server includes: When the map data management client is started, determine whether the map data can be loaded from the local cache; If not, a map data pull request is sent directly to the map data management server; If so, it is determined whether the locally cached map data needs to be updated based on the locally cached map data, and if the locally cached map data needs to be updated, a map data pull request is sent to the map data management server.

3. The map data management method according to claim 2, wherein: The determining whether the locally cached map data needs to be updated according to the locally cached map data includes: Parsing the locally cached map data to obtain a parsing result of the locally cached map data, wherein the parsing result of the map data includes version information of the map data; Obtaining the latest version of the map data from the map data management server; It is determined whether the locally cached map data needs to be updated according to the version information of the locally cached map data and the latest version information of the map data.

4. The map data management method according to claim 1, wherein: When the map data management client is started, sending a map data pull request to the map data management server includes: Configure the map data range in the configuration file; The map data fetching request is sent to the map data management server according to the map data range.

5. The map data management method according to claim 1, wherein: The map data management method further includes: When the map data management client is started, the message subscription configuration information is pulled from the map data management server; Establishing a subscription connection for a target message queue with the map data management server based on the message subscription configuration information, wherein the target message queue is used to cache map data update messages issued by the map data management server; In the case of subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message; The map data in the local cache is updated using the updated map data.

6. The map data management method according to claim 5, wherein: In the case of subscribing to the map data update message cached in the target message queue, pulling updated map data from the map data management server based on the map data update message includes: In the case of subscribing to the map data update message cached in the target message queue, parsing the map data update message to obtain a parsing result of the map data update message, wherein the parsing result of the map data update message includes a map data update range; Get the map data range in the configuration file; Determining whether it is necessary to update the locally cached map data according to the map data range in the configuration file and the map data update range; When the locally cached map data needs to be updated, the updated map data is pulled from the map data management server.

7. The map data management method according to claim 1, wherein: The map data management method further includes: Configure the offline usage strategy of map data in the configuration file; In the case where the map data management client queries the map data, loading the map data from the local cache and querying the map data includes: In the case that the map data management client and the map data management server cannot communicate, based on the offline use policy of the map data, the map data is loaded from the local cache and queried.

8. A map data management device, wherein: The map data management device is applied to a map data management client, and the map data management device comprises: A data pulling unit, used for sending a map data pulling request to a map data management server when the map data management client is started, wherein the map data pulling request is a request for pulling map data of a specified range or full map data; A local cache unit, used for receiving the map data returned by the map data management server and caching it locally, wherein the map data is map data including a map query structure; The query unit is used to load the map data from the local cache and perform the query when the map data management client queries the map data.

9. A map data management system, wherein: The map data management system comprises at least one map data management client and a map data management server, wherein the map data management client is used to execute the map data management method according to any one of claims 1 to 7, and the map data management server is used to execute: When the map data management server is started, a map file is obtained and initialized to obtain initialized map data, wherein the initialized map data is map data including a map query structure; Receiving a map data pull request sent by the map data management client; Map data is pulled according to the map data pulling request and returned to the map data management client.

10. An electronic device, comprising: processor; and a memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor executes the map data management method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, wherein when the computer program or instructions are executed by a processor, the map data management method according to any one of claims 1 to 7 is implemented.

Images