Map rendering method, electronic device, and storage medium

Abstract

This application provides a map rendering method, electronic device, and storage medium. In response to detecting entry into map calibration mode, the method acquires application operation scenario data of the foreground process, determines the corresponding layer resource consumption information, and then, for each preset scale of the map application, determines the corresponding candidate layers according to the corresponding granularity. It acquires the single-layer rendering frame rate of the candidate layers and combines candidate layers with single-layer rendering frame rates higher than a preset smoothness threshold. This determines the multi-layer rendering frame rate of the candidate layer combination under the given layer resource consumption information. If the multi-layer rendering frame rate is lower than a preset acceptable threshold, some layers in the combination are hidden to obtain the corresponding displayable layer combination. Finally, a display / hidden rule table corresponding to the layer resource consumption information is constructed so that layer rendering can be performed according to this rule table during subsequent map application operation, ensuring that the map display layers meet actual resource consumption and avoiding system lag.

Description

Technical Field

[0001] This application relates to the field of map display technology, specifically to a map rendering method, electronic device, and storage medium. Background Technology

[0002] Currently, map applications suffer from significant bottlenecks in terms of interface responsiveness, specifically manifested as follows:

[0003] 1. Insufficient rendering performance: The frame rate of the self-developed map at a scale of 200m or 500m is only 23 / 17 frames, far below the smooth benchmark of 60 frames; 2. Redundant resource loading: The existing OCM layers (OpenCycleMap layers) are configured to load too much unnecessary data (such as non-highway roads and secondary POIs), resulting in a POI (Point of Interest) cluster density of more than 300 per screen at a scale of 500m or above; 3. Lack of dynamic adjustment: There is a lack of a mechanism to dynamically adjust the rendering mode, resulting in high-density road lines still being drawn at medium and long distances, such as more than 200 road lines at a scale of 100m. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, this application aims to provide a map rendering method, electronic device and storage medium to solve the problems of low rendering performance, redundant resource loading and lack of dynamic adjustment in the related art, and improve the running performance and user experience of map applications.

[0005] This application provides a map rendering method, the method comprising:

[0006] In response to detecting that a vehicle has entered map calibration mode, the application operation scenario data of the foreground process is obtained, and the corresponding layer resource consumption information is determined based on the application operation scenario data.

[0007] Obtain each preset scale of the map application in the vehicle, and for each preset scale, determine each candidate layer corresponding to the preset scale according to the granularity of the preset scale.

[0008] Obtain the single-layer rendering frame rate of the candidate layers, and combine the candidate layers whose single-layer rendering frame rate is higher than a preset smoothness threshold to obtain a candidate layer combination;

[0009] Determine the multi-layer rendering frame rate of the candidate layer combination under the layer resource consumption information. If the multi-layer rendering frame rate is less than a preset acceptable threshold, hide some layers in the candidate layer combination to obtain a displayable layer combination corresponding to the preset scale.

[0010] Based on the combination of displayable layers corresponding to each preset scale, a display rule table corresponding to the layer resource consumption information is constructed, wherein the display rule table is used for layer rendering during the map application runtime of the vehicle.

[0011] Optionally, the corresponding layer resource consumption information is determined based on the application operation scenario data, including:

[0012] Based on the application operation scenario data, determine the operation application, the corresponding operation type, operation duration, and operation resource consumption.

[0013] The CPU utilization, memory usage, and display frame rate are determined based on the operation type, operation duration, and operation resource consumption.

[0014] Based on the CPU utilization, memory usage, and display frame rate, the layer resource consumption information corresponding to the application operation scenario data is determined.

[0015] Optionally, after constructing the display / hidden rule table corresponding to the layer resource consumption information, the method further includes:

[0016] In response to detecting a change in the scale during the startup or operation of a map application, the system acquires current operation scenario data and determines current resource consumption information based on the current operation scenario data.

[0017] Obtain the display / hidden rule table corresponding to the current resource consumption information, and determine the current scale;

[0018] Based on the current scale, the currently displayable layer combination is queried in the obtained display rule table, and the current layer priority sequence is determined according to the current scale;

[0019] Render the currently displayable layer combination and obtain the actual frame rate after rendering the currently displayable layer combination;

[0020] If the actual frame rate is less than the preset smoothness threshold, then some layers in the currently displayable layer combination are hidden according to the current layer priority sequence until the actual frame rate is greater than the preset smoothness threshold.

[0021] Optionally, the priority sequence of the current layer is determined based on the current scale, including:

[0022] The priority coefficient list corresponding to the current scale is retrieved from the preset priority table. The priority coefficient list includes the priority coefficients of each layer corresponding to the current scale, and each layer corresponding to the current scale is a layer that satisfies the granularity corresponding to the current scale.

[0023] Sort the layers corresponding to the current scale in descending order of priority coefficients in the priority coefficient list to obtain the current layer priority sequence corresponding to the current scale.

[0024] Optionally, the preset priority table is used to describe the correspondence between each preset scale and each priority coefficient list. The construction of the preset priority table includes:

[0025] Obtain a preset scale and determine each layer corresponding to the preset scale based on the granularity corresponding to the preset scale.

[0026] For each layer corresponding to the preset scale, determine the predicted rendering time and user demand frequency of the layer, and determine the priority coefficient of the layer based on the predicted rendering time and user demand frequency.

[0027] Based on the priority coefficients of each layer corresponding to the preset scale, construct a priority coefficient list corresponding to the preset scale.

[0028] Construct a preset priority table based on the priority coefficient list corresponding to each preset scale.

[0029] Optionally, determining the frequency of user demand for the layer includes:

[0030] Obtain the map element click records and navigation records of the map application, and determine the user demand frequency for each layer based on the map element click records and navigation records;

[0031] Alternatively, display element query information on the vehicle's infotainment system interface, obtain the elements of interest that the user responds to inquiries about, and determine the frequency of user demand for each layer based on the elements of interest.

[0032] Optionally, hiding some layers in the currently displayable layer group according to the current layer priority sequence includes:

[0033] If the actual frame rate is less than the preset smoothness threshold and the actual frame rate is greater than the preset acceptable threshold, a high-priority layer is determined according to the current layer priority sequence.

[0034] Retain the high-priority layer in the currently displayable layer combination, and hide all other layers except the high-priority layer;

[0035] Wherein, the preset smoothness threshold is greater than the preset acceptable threshold.

[0036] Optionally, hiding some layers in the currently displayable layer group according to the current layer priority sequence further includes:

[0037] If the actual frame rate is less than the preset acceptable threshold, the layer with the lowest priority coefficient in the current layer priority sequence will be determined as the current layer to be hidden.

[0038] Hide the currently hidden layer and reacquire the actual frame rate;

[0039] If the actual frame rate is less than the preset acceptable threshold, then the layer preceding the current layer to be hidden in the current layer priority sequence is determined as the new current layer to be hidden, and the process of hiding the current layer to be hidden is returned until the actual frame rate is greater than the preset acceptable threshold, or all low-priority layers in the current layer priority sequence are hidden.

[0040] This application embodiment also provides an electronic device, the electronic device comprising:

[0041] Processor and memory;

[0042] The processor executes the steps of the map rendering method provided in any embodiment of this application by calling the program or instructions stored in the memory.

[0043] This application also provides a computer-readable storage medium that stores a program or instructions that cause a computer to perform the steps of the map rendering method provided in any embodiment of this application.

[0044] In summary, this application proposes a map rendering method. This method, in response to detecting a vehicle entering map calibration mode, acquires application operation scenario data of the foreground process and determines the corresponding layer resource consumption information based on the application operation scenario data. Then, it acquires each preset scale of the map application. For each preset scale, it determines corresponding candidate layers based on the granularity of the preset scale, acquires the single-layer rendering frame rate of the candidate layers, and combines candidate layers with single-layer rendering frame rates higher than a preset smoothness threshold to obtain a candidate layer combination. Then, it determines the multi-layer rendering frame rate of the candidate layer combination under the layer resource consumption information. If the multi-layer rendering frame rate is lower than a preset acceptable threshold, it hides some layers in the candidate layer combination to obtain a displayable layer combination corresponding to the preset scale. Finally, it calculates the displayable layer combination corresponding to each preset scale. A display / hiding rule table corresponding to layer resource consumption information is constructed so that layer rendering can be performed according to this rule table during subsequent map application operation. This method realizes the construction of display / hiding rule table based on the foreground operation scenario, so that the constructed display / hiding rule table can meet the actual resource consumption and avoid system lag caused by too many map layers being displayed. Furthermore, this method determines the multi-layer rendering frame rate of candidate layer combinations under different preset scales based on resource consumption. When the frame rate is low, some layers are hidden to construct the display / hiding rule table, which can dynamically adjust the displayed layers and achieve the purpose of precise allocation of rendering resources, thereby improving rendering performance. Compared with empirical adjustment based on pre-tested rules, this method can solve the performance instability problem caused by empirical adjustment, and can also ensure rendering performance while taking into account user experience, so that the finally loaded layers are more in line with the requirements. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0046] Figure 1 This is a flowchart of a map rendering method provided in an embodiment of this application;

[0047] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0048] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0049] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0050] As mentioned in the background section, in response to the problems in the prior art, this application proposes a map rendering method that can be applied to vehicle infotainment systems or other systems containing map applications. For example, it can construct a display / hidden rule table for map applications in a vehicle infotainment system so that subsequent map applications can perform layer rendering based on the display / hidden rule table during operation. Figure 1 This is a flowchart of a map rendering method provided in an embodiment of this application. This method can be executed by the background testing process of the vehicle system.

[0051] See Figure 1 The map rendering method specifically includes:

[0052] S110. In response to detecting that a vehicle has entered the map calibration mode, obtain the application operation scenario data of the foreground process, and determine the corresponding layer resource consumption information based on the application operation scenario data.

[0053] The map calibration mode can be used to calibrate the display and hiding rule tables corresponding to different resource consumption conditions. For example, users can actively enter the map calibration mode by triggering a control on the vehicle's infotainment system interface; alternatively, during the operation of the map application, the frame rate after the map application renders the layers can be collected in real time. When the collected real-time frame rate is lower than a set threshold, a prompt message to enter the map calibration mode is generated to ask the user whether to confirm entering the map calibration mode, and the map calibration mode is entered after the user's confirmation operation is detected.

[0054] After entering map calibration mode, application operation scenario data of the foreground process can be collected. This data describes the user's actions on the foreground application, such as playing videos, playing music, browsing the gallery, browsing web pages, and adjusting cockpit settings. Furthermore, this application scenario operation data can be mapped equivalently to the map application, converting it into corresponding layer resource consumption information.

[0055] In one specific implementation, determining the corresponding layer resource consumption information based on application operation scenario data includes:

[0056] Based on application operation scenario data, determine the operation application, the corresponding operation type, operation duration, and operation resource consumption.

[0057] Based on the operation type, operation duration, and operation resource consumption, determine the CPU utilization, memory usage, and display frame rate; based on the CPU utilization, memory usage, and display frame rate, determine the layer resource consumption information corresponding to the application operation scenario data.

[0058] Specifically, it can identify the application performing the operation in the application operation scenario data, as well as the corresponding operation type, operation duration, and operation resource consumption. The operation type refers to the type of application operation performed by the user, such as changing music or searching for videos; the operation duration refers to the duration of the user's operation on the application, such as the time spent browsing a page; and the operation resource consumption refers to the memory resources consumed by the user's operation on the application.

[0059] After determining the application, operation type, operation duration, and resource consumption, the CPU (Central Processing Unit) utilization, memory usage, and display frame rate of the vehicle system can be determined based on the operation type, operation duration, and resource consumption.

[0060] Furthermore, based on the pre-established correspondence between CPU utilization, memory usage, display frame rate and layer resource consumption, the map layers consumed corresponding to the current CPU utilization, memory usage and display frame rate can be predicted, so as to equivalently map the application operation scenario data to the fixed layer or layers of different granularities of the map application and obtain the layer resource consumption information.

[0061] For example, if a foreground process runs a video software and the operation type is playing video, the corresponding layer resource consumption information can be 50 road lines. That is, the playback operation of the video software can be equivalently mapped to rendering 50 road lines.

[0062] Through the above implementation method, the user's regular operations in the foreground process can be mapped to the map application, which facilitates the subsequent construction of the corresponding display and hidden rule table, ensures the accuracy of the construction of display and hidden rules under different preset scales, and makes the display and hidden rules better meet the performance requirements.

[0063] S120. Obtain the preset scales of the map application in the vehicle. For each preset scale, determine the candidate layers corresponding to the preset scale based on the granularity of the preset scale.

[0064] The map scale describes the proportional relationship between the map and actual distances. For example, a scale of 1:500 means that one unit displayed in the map application corresponds to 500 actual units. Preset scales can be pre-built, usable scales for map applications.

[0065] It should be noted that, in order to achieve accurate rendering at different scales and effectively improve the smoothness of map applications, all layers in the map application can be divided into three types: fixed layers, disabled layers, and optimizable layers. The candidate layers corresponding to the preset scale are for optimizable layers; that is, some layers from the optimizable layers are selected as candidate layers.

[0066] The fixed layer is the layer that requires constant rendering and mainly contains basic geographic elements such as terrain and rivers. These elements are the core components of geographic information and play a crucial role in enabling users to fully understand the geographic environment. These basic geographic elements can be forcibly rendered regardless of the scale. In other words, whether users are viewing detailed local geographic information at a large scale or browsing the macroscopic geographic panorama at a small scale, basic geographic elements such as terrain and rivers can be displayed, providing users with a stable and comprehensive foundation of geographic information.

[0067] Disabled layers can be layers that are prohibited from rendering, primarily including non-core elements such as motorcycle lanes and bicycle lanes. During map application operation, considering that these elements are not critical information for most users' core needs, the system can globally disable these non-core elements through preset strategies to optimize resource utilization and reduce unnecessary rendering overhead. This allows the system to allocate more resources to more important geographic information display and processing tasks.

[0068] The optimizable layers are layers that can be selected for rendering, primarily including dynamically adjustable objects such as POIs (Points of Interest), road lines, and Labels. These objects are characterized by their display requirements changing based on user interaction and different scales. To better manage and render these dynamically adjustable objects, the system can construct independent rendering pipelines for them. Through these independent rendering pipelines, the system can process and adjust these optimizable layers individually, thereby achieving fine-grained control and efficient rendering.

[0069] For example, all optimizable layers can be divided into three granularity levels based on the granularity of geographic elements: small-granularity layers, medium-granularity layers, and large-granularity layers. For instance, small points of interest, sidewalks, and paths belong to small-granularity layers; main roads, viaducts, and large points of interest belong to medium-granularity layers; and highways, national roads, and provincial borders belong to large-granularity layers.

[0070] In this embodiment of the application, in order to ensure the smoothness of map rendering under various preset scales, a corresponding granularity can be set for each preset scale so as to display the corresponding granularity layer under each preset scale, avoid loading too much irrelevant data, and achieve the purpose of improving smoothness.

[0071] Specifically, for each preset scale, the corresponding granularity can be determined based on the granularity set for the preset scale, thereby obtaining each candidate layer corresponding to the preset scale.

[0072] For example, a preset scale of 5m corresponds to a small granularity (the corresponding layer may include sidewalks, paths, regions of interest, etc.), a preset scale of 100m corresponds to small and medium granularity (the corresponding layer may include main roads, viaducts, etc.), and a preset scale of 2000m corresponds to a large granularity (the corresponding layer may include highways, provincial boundaries, etc.). To further improve smoothness at the 100m preset scale, the small granularity layer can be further subdivided to focus on small points of interest and avoid rendering elements such as sidewalks and paths.

[0073] S130. Obtain the single-layer rendering frame rate of the candidate layers, and combine the candidate layers whose single-layer rendering frame rate is higher than the preset smoothness threshold to obtain the candidate layer combination.

[0074] Specifically, for each candidate layer corresponding to the preset scale, single-layer rendering can be enabled through the target hardware platform (such as Snapdragon 8155) to obtain the frame rate of each candidate layer after rendering, and then determine it as the single-layer rendering frame rate.

[0075] Furthermore, candidate layers with a single-layer rendering frame rate higher than a preset smoothness threshold can be selected, while candidate layers with a single-layer rendering frame rate lower than the preset smoothness threshold can be filtered out, thereby limiting the display of candidate layers with excessively low single-layer rendering frame rates. The preset smoothness threshold is a pre-set frame rate threshold that indicates smooth map operation.

[0076] Furthermore, candidate layers with a single-layer rendering frame rate higher than a preset smoothness threshold can be combined to obtain a candidate layer combination.

[0077] S140. Determine the multi-layer rendering frame rate of the candidate layer combination under the layer resource consumption information. If the multi-layer rendering frame rate is less than the preset acceptable threshold, hide some layers in the candidate layer combination to obtain the displayable layer combination corresponding to the preset scale.

[0078] Specifically, after obtaining the candidate layer combination, multi-layer combination rendering can be enabled through the target hardware platform to simulate the frame rate after rendering the candidate layer combination under the layer resource consumption information, and then determine it as the multi-layer rendering frame rate.

[0079] After obtaining the multi-layer rendering frame rate, it can be determined whether the multi-layer rendering frame rate is less than the preset acceptable threshold. The preset acceptable threshold can be a pre-set frame rate threshold that represents the acceptable standard of map smoothness. The preset acceptable threshold is less than the preset smoothness threshold.

[0080] If the multi-layer rendering frame rate is less than the preset acceptable threshold, it means that the smoothness of the rendering after combination is low. At this time, some layers in the candidate layer combination can be hidden. For example, some low-priority layers can be hidden. Then, the combination after hiding some layers is determined as the displayable layer combination corresponding to the preset scale under the layer resource consumption information.

[0081] For example, at a preset scale of 10m, if the layer resource consumption information is empty, 100 road lines can be displayed; if the layer resource consumption information is equivalently mapped to 50 road lines, then 50 road lines can be displayed at a scale of 10m.

[0082] S150. Based on the combination of displayable layers corresponding to each preset scale, construct a display rule table corresponding to the layer resource consumption information. The display rule table is used for layer rendering during the vehicle's map application runtime.

[0083] Specifically, a preset display / hidden rule table corresponding to the displayable layer combination for each preset scale can be constructed. To ensure the accuracy of the preset display / hidden rule table, it can be generated by repeated testing with multiple sets (e.g., at least 3 sets). As shown in Table 1, Table 1 uses a combination of three layers as an example to illustrate a preset display / hidden rule table.

[0084] Table 1. A Preset Show / Hide Rule Table

[0085]

[0086] Taking a preset acceptable threshold of 45 frames per second and a preset smoothness threshold of 60 frames per second as an example, assuming the base frame rate corresponding to the layer resource consumption information when there is no layer rendering is 65. Referring to Table 2, at a preset scale of 50m, the multi-layer rendering frame rate of the combination of layers 1 to 3 is 58 frames per second, which is higher than the preset acceptable threshold. Therefore, layers 1 to 3 can be regarded as the displayable layer combination corresponding to the preset scale of 50m under the layer resource consumption information.

[0087] At a preset scale of 100m, the multi-layer rendering frame rate of the combination of layers 1 to 3 is 45 (frames per second), which is close to the preset acceptable threshold. Layer 3 can be hidden according to priority, and layers 1 and 2 can be used as the displayable layer combination corresponding to the preset scale of 100m under the layer resource consumption information.

[0088] At a preset scale of 500m, the multi-layer rendering frame rate of the combination of layers 1 to 3 is 30 (frames per second), which is lower than the preset acceptable threshold. Layers 1 and 3 can be hidden according to the priority coefficient, and layer 2 can be used as the displayable layer combination corresponding to the preset scale of 500m under the layer resource consumption information.

[0089] At a preset scale of 1000m, the multi-layer rendering frame rate of the combination of layers 1 to 3 is 20 (frames per second), which is far below the preset acceptable threshold. Therefore, layers 1 to 3 can be hidden. In the layer resource consumption information, the displayable layer combination corresponding to the preset scale of 1000m is empty.

[0090] In this embodiment, for each preset scale, layers with higher single-layer rendering frame rates are selected for combination based on the single-layer rendering frame rate of each layer, so as to avoid the final determined displayable layer combination containing layers with extremely low smoothness; then, according to the multi-layer rendering frame rate under the layer resource consumption information, some layers in the combination are hidden, which can ensure the rendering smoothness of the displayable layer combination corresponding to the preset scale.

[0091] Specifically, based on the displayable layer combinations corresponding to each preset scale, a display rule table corresponding to the layer resource consumption information can be constructed. This display rule table includes the displayable layer combinations corresponding to each preset scale under the corresponding layer resource consumption information.

[0092] The map rendering method provided in this application embodiment, in response to detecting a vehicle entering map calibration mode, acquires application operation scenario data of the foreground process, determines the corresponding layer resource consumption information based on the application operation scenario data, and then acquires each preset scale of the map application. For each preset scale, it can determine each candidate layer according to the granularity corresponding to the preset scale, acquire the single-layer rendering frame rate of the candidate layer, and combine the candidate layers with a single-layer rendering frame rate higher than a preset smoothness threshold to obtain a candidate layer combination. Then, it determines the multi-layer rendering frame rate of the candidate layer combination under the layer resource consumption information. If the multi-layer rendering frame rate is less than a preset acceptable threshold, it hides some layers in the candidate layer combination to obtain a displayable layer combination corresponding to the preset scale. Finally, it constructs a map based on the displayable layer combination corresponding to each preset scale. This method constructs a display / hidden rule table corresponding to layer resource consumption information. This table is used for subsequent map application rendering, enabling the construction of a display / hidden rule table based on the foreground operation scenario. This ensures the constructed rule table meets actual resource consumption requirements, preventing system lag caused by displaying too many map layers. Furthermore, this method determines the multi-layer rendering frame rate of candidate layer combinations at different preset scales based on resource consumption. When the frame rate is low, some layers are hidden in the constructed display / hidden rule table. This allows for dynamic adjustment of displayed layers, achieving precise allocation of rendering resources and improving rendering performance. Compared to empirical adjustment based on pre-tested rules, this method solves the performance instability problem caused by empirical adjustment and ensures both rendering performance and user experience, resulting in ultimately loaded layers that better meet requirements.

[0093] In some implementations, after constructing the visibility rule table corresponding to the layer resource consumption information, the method further includes the following steps:

[0094] Step 21: In response to the detection of a change in the map scale during map application startup or operation;

[0095] Step 22: Obtain the display / hidden rule table corresponding to the current resource consumption information and determine the current scale;

[0096] Step 23: Based on the current scale, query the currently displayable layer combination in the obtained display rule table, and determine the current layer priority sequence according to the current scale;

[0097] Step 24: Render the currently displayable layer combination and obtain the actual frame rate after rendering the currently displayable layer combination;

[0098] Step 25: If the actual frame rate is less than the preset smoothness threshold, hide some layers in the currently displayable layer combination according to the current layer priority sequence until the actual frame rate is greater than the preset smoothness threshold.

[0099] In step 21, a map scale parameter monitoring module can be pre-deployed. The current map scale is collected in real time during the operation of the map application. If the current map scale is inconsistent with the map scale collected at the previous moment, it is determined that a change in map scale has been detected.

[0100] In addition to detecting map scale changes through the scale parameter monitoring module, map scale changes can also be detected by detecting user actions within the map application. For example, if a user triggers a zoom operation within the map application, and the zoom level is greater than a preset level, then a map scale change can be determined.

[0101] Alternatively, considering that some map applications can zoom in to display the map near the destination when approaching or arriving at the destination, changes in map scale can also be detected through the navigation path in the map application. For example, it can detect whether the vehicle has reached the destination in the navigation path, or whether the distance between the vehicle and the destination is less than a set distance threshold; if so, it is determined that a change in map scale has been detected.

[0102] In this embodiment of the application, if a change in map scale is detected, the current operation scenario data can be obtained, and the current resource consumption information can be determined based on the current operation scenario data.

[0103] Furthermore, in step 22, the display / hidden rule table corresponding to the current resource consumption information can be queried; then in step 23, the displayable layer combination corresponding to the current scale can be queried according to the obtained display / hidden rule table to obtain the current displayable layer combination; and the current layer priority sequence can be determined through the current scale.

[0104] The current layer priority sequence refers to the priority order of each layer displayed at the current scale. The layer priority sequence corresponding to each preset scale can be determined in advance based on the user demand frequency and rendering time of each preset scale.

[0105] In this application embodiment, the focus is on optimizable layers, refining the combination of displayable layers at various preset scales, and determining the layer priority sequence at various preset scales, so as to ensure the rendering effect of map layers at different scale levels while satisfying the user experience.

[0106] Regarding step 23 above, in one example, determining the priority sequence of the current layer based on the current scale includes the following steps:

[0107] Step 231: Query the priority coefficient list corresponding to the current scale from the preset priority table. The priority coefficient list includes the priority coefficient of each layer corresponding to the current scale. Each layer corresponding to the current scale is a layer that meets the granularity corresponding to the current scale.

[0108] Step 232: Sort the layers corresponding to the current scale in descending order of priority coefficients in the priority coefficient list to obtain the priority sequence of the current layer corresponding to the current scale.

[0109] The preset priority table can include a list of preset scales and their corresponding priority coefficients. In step 231, the current scale can be searched from the preset priority table to obtain the list of priority coefficients corresponding to the current scale.

[0110] In this embodiment, the priority coefficient list consists of the priority coefficients of each layer corresponding to the current scale. Each layer corresponding to the current scale refers to a layer that conforms to the granularity corresponding to the current scale. As shown in Table 2, Table 2 displays a preset priority table, which includes a priority coefficient list corresponding to different preset scales.

[0111] Table 2. A preset priority table

[0112]

[0113] After obtaining the priority coefficient list corresponding to the current scale, in step 132, the layers corresponding to the current scale can be sorted in descending order of priority coefficients in the priority coefficient list to obtain the priority sequence of the current layer corresponding to the current scale.

[0114] Taking Table 2 as an example, when the current scale is 5m, the corresponding current layer priority sequence is: POI, sidewalk, path; when the current scale is 100m, the corresponding current layer priority sequence is: main road, overpass, POI.

[0115] Steps 231-232 above involve querying the priority coefficients of each layer corresponding to the current scale from a preset priority table, and then sorting them in descending order of priority coefficients to obtain the current layer priority sequence. This accurately determines the layer priority at the current scale, facilitating precise adjustments based on the current layer priority sequence and ensuring map smoothness and user experience. Furthermore, querying the priority coefficients of each layer corresponding to the current scale using preset priorities allows for focusing on layers with high display demand at the current scale, avoiding attention to other layers with low display demand, and improving the efficiency of obtaining the current layer priority sequence.

[0116] In some implementations, before sorting the layers corresponding to the current scale according to the priority coefficients in the priority coefficient list from largest to smallest, the following steps are also included:

[0117] Obtain the current running memory of the vehicle's infotainment system; adjust the priority coefficients of some layers in the priority coefficient list based on the current running memory.

[0118] Specifically, the current running memory of the vehicle's infotainment system can be obtained. This current running memory reflects the remaining memory space of the vehicle's infotainment system. The larger the current running memory, the smaller the remaining memory, and the lower the overall response speed of the vehicle's infotainment system.

[0119] In this embodiment, a memory threshold for stable map application operation can be preset. If the current memory usage is below this threshold, the map application can run stably without adjusting the priority coefficients of some layers. If the current memory usage is above this threshold, the priority coefficients of some layers in the priority coefficient list can be adjusted.

[0120] For example, the priority coefficient of layers with high predicted rendering time in the priority coefficient list can be reduced. Specifically, a rendering time threshold can be set, and the priority coefficient of layers with rendering time higher than the threshold can be reduced.

[0121] Through the above implementation method, the priority of layers with long rendering times can be reduced when the system load is high, so that such layers can be hidden first when the actual frame rate is low in the future, thereby improving the efficiency of dynamic adjustment. In addition, system lag can be avoided, thereby avoiding affecting other services provided by the system.

[0122] In addition to obtaining the layer priority sequence corresponding to the current scale, it is also necessary to obtain the displayable layer combination corresponding to the current scale. Among them, the displayable layer combination corresponding to various scales can be determined in advance by analyzing the rendering frame rate of a single layer and the rendering frame rate of multiple layer combinations.

[0123] In this embodiment of the application, the priority coefficient of each layer corresponding to the preset scale in the preset priority table can be determined based on the rendering time of each layer and the frequency of user demand for that layer. This combines the user's actual usage needs and the rendering time as two factors to determine the priority, avoiding the limitations caused by determining the priority based on a single dimension of data, and making subsequent priority-based adjustments more in line with user needs.

[0124] In one specific implementation, a preset priority table is used to describe the correspondence between each preset scale and each priority coefficient list. The construction of the preset priority table includes the following steps:

[0125] Step 2301: Obtain the preset scale and determine the layers corresponding to the preset scale based on the granularity of the preset scale.

[0126] Step 2302: For each layer corresponding to the preset scale, determine the predicted rendering time and user demand frequency of the layer, and determine the priority coefficient of the layer based on the predicted rendering time and user demand frequency.

[0127] Step 2303: Construct a priority coefficient list corresponding to the preset scale based on the priority coefficients of each layer corresponding to the preset scale.

[0128] Step 2304: Construct a preset priority table based on the priority coefficient list corresponding to each preset scale.

[0129] In step 2301, the layers that meet the granularity of the preset scale can be determined as the layers corresponding to the preset scale.

[0130] In step 2302, for each layer corresponding to the preset scale, the predicted rendering time of the layer and the frequency of user demand can be determined. The predicted rendering time can be obtained in advance through experimental data collection, or the number of elements contained in the layer at the preset scale can be predicted, and the predicted rendering time of the layer at the preset scale can be obtained based on the predicted number of elements.

[0131] Among them, the frequency of user demand can reflect the user's demand for the layer, which can be obtained by analyzing the user's historical usage records of map applications.

[0132] Regarding step 2302 above, in one example, determining the frequency of user demand for a layer includes:

[0133] Obtain map element click records and navigation records from the map application, and determine the user demand frequency for each layer based on these records.

[0134] Alternatively, display element query information on the vehicle's infotainment system interface, obtain the elements of interest that users respond to inquiries about, and determine the frequency of user demand for each layer based on the elements of interest.

[0135] Specifically, it can retrieve map element click records and navigation records from map applications. Map element click records describe the map elements clicked by the user within the map application; these map elements include, but are not limited to, sidewalks, paths, points of interest, main roads, overpasses, and highways. Navigation records describe the user's historical destinations, which can be understood as the map elements the user has been following.

[0136] In this embodiment of the application, after obtaining the map element click records and navigation records, the map element click records and navigation records can be classified according to the scale to obtain map element click records and navigation records under different scales. Then, according to the records under different scales, the number of clicks and the number of times each map element is used as a destination are counted.

[0137] Furthermore, for each map element, the user demand frequency of that map element is determined based on the number of clicks on the map element and the number of times it is used as a destination, as well as the sum of the number of clicks on all map elements and the sum of the number of times it is used as a destination. Each map element corresponds to a layer, thus the user demand frequency of each layer at different scales can be obtained.

[0138] In addition to analyzing users' historical usage records of map applications to obtain the frequency of user demand for each layer, the frequency of user demand for each layer at each preset scale can also be determined by actively asking users and their feedback.

[0139] Specifically, the vehicle's infotainment system can display element query information, which can be used to ask users which map elements they are interested in at each preset scale. Users can enter the elements of interest at each preset scale by checking the boxes.

[0140] Furthermore, if the user's feedback on the element inquiries is detected, the frequency of user demand for each layer under each preset scale can be determined based on the feedback of the element of interest.

[0141] The above examples enable accurate analysis of the frequency of user demand for each layer, allowing subsequent dynamic adjustments to better meet user needs. This achieves the goal of preserving map elements that users are more interested in and hiding map elements that users are not interested in, thereby improving the user experience.

[0142] In step 2302 above, after obtaining the predicted rendering time and user demand frequency of each layer under each preset scale, the priority coefficient of the layer can be determined by combining the predicted rendering time and user demand frequency.

[0143] For example, the predicted rendering time can be normalized to convert it into a value in the range of 0 to 1. Then, a priority coefficient can be determined based on the normalized predicted rendering time and the frequency of user requests, as shown in the following formula: ;

[0145] In the formula, , These are the weighting coefficients corresponding to the frequency of user requests and the predicted rendering time, for example, , They are 0.6 and 0.4 respectively; The frequency of user demand for the i-th layer under the preset scale S, with a value range of 0 to 1; The normalized prediction rendering time for the i-th layer at a preset scale S, with a value ranging from 0 to 1; This is the priority coefficient for the i-th layer at the preset scale S.

[0146] After obtaining the priority coefficients of each layer at the preset scale, in step 2303, a priority coefficient list containing the priority coefficients of each layer can be constructed based on the priority coefficients of each layer.

[0147] Furthermore, in step 2304, a preset priority table can be constructed using the priority coefficient list corresponding to each preset scale.

[0148] Steps 2301-2304 above determine the priority coefficient by the rendering time of each layer and the frequency of user demand for that layer, so that the priority coefficient can accurately reflect user needs and make subsequent priority-based adjustments more in line with user needs for map usage.

[0149] It should be noted that, after obtaining the priority coefficient list corresponding to the current scale from the preset priority table, the current operating memory of the vehicle's infotainment system also affects the rendering time of some layers. For example, for layers with high predicted rendering time, their rendering consumes more memory. Given high current operating memory, the actual rendering time of these layers should be much longer than the predicted rendering time. Therefore, before obtaining the layer priority sequence by sorting according to the priority coefficient list, the priority coefficients of layers with high predicted rendering time can be adjusted based on the current operating memory of the vehicle's infotainment system. This further reduces the priority of these layers, preventing system lag caused by rendering such layers when operating memory is high, and thus avoiding impact on other services provided by the vehicle's infotainment system.

[0150] In this embodiment, after obtaining the displayable layer combination and layer priority sequence corresponding to the current scale, in step 24, the current displayable layer combination can be rendered first to load all layers in the current displayable layer combination into the map application, achieving full display of the combination. After rendering the current displayable layer combination, the actual frame rate of the rendered map application can be obtained in real time.

[0151] Specifically, in step 25, the actual frame rate can be compared with the preset smoothness threshold. If the actual frame rate is lower than the preset smoothness threshold, it means that the smoothness of the map application is insufficient. In this case, some layers in the currently displayable layer combination can be hidden according to the current layer priority sequence to achieve dynamic layer control.

[0152] Regarding step 25 above, in one specific implementation, hiding some layers in the currently displayable layer group according to the current layer priority sequence includes the following steps:

[0153] Step 251: When the actual frame rate is less than the preset smoothness threshold and the actual frame rate is greater than the preset acceptable threshold, determine the high priority layer according to the current layer priority sequence.

[0154] Step 252: Keep the high-priority layer in the currently visible layer group and hide the other layers except for the high-priority layer.

[0155] Among them, the preset smoothness threshold is greater than the preset acceptable threshold.

[0156] Specifically, in step 251, if the actual frame rate is less than a preset smoothness threshold and greater than a preset acceptable threshold, it indicates that the map application is running with low smoothness, but within an acceptable range. In this case, a high-priority layer can be determined based on the current layer priority sequence. The preset smoothness threshold is greater than the preset acceptable threshold.

[0157] Furthermore, in step 252, high-priority layers in the currently displayable layer combination can be retained, while other layers can be hidden to achieve dynamic control. For example, a priority coefficient threshold can be set, and layers in the current layer priority sequence that are higher than this priority coefficient threshold can be identified as high-priority layers.

[0158] Through steps 251-252 above, a preset smoothness threshold and a preset acceptable threshold can be set. When the actual frame rate is greater than the preset acceptable threshold but less than the preset smoothness threshold, the high-priority layer is retained for one-time dynamic adjustment. This improves the efficiency of dynamic adjustment while ensuring the smoothness of the application after adjustment.

[0159] Regarding step 25 above, in one example, hiding some layers in the currently displayable layer group according to the current layer priority sequence further includes the following steps:

[0160] Step 253: If the actual frame rate is less than the preset acceptable threshold, the layer with the lowest priority coefficient in the current layer priority sequence is determined as the current layer to be hidden.

[0161] Step 254: Hide the current layer to be hidden and reacquire the actual frame rate;

[0162] Step 255: If the actual frame rate is less than the preset acceptable threshold, then the layer preceding the current layer to be hidden in the current layer priority sequence is determined as the new current layer to be hidden, and the process of hiding the current layer to be hidden is returned until the actual frame rate is greater than the preset acceptable threshold, or all low-priority layers in the current layer priority sequence are hidden.

[0163] In step 253, if the actual frame rate is less than the preset acceptable threshold, it indicates that the map application is running poorly. In this case, the layer with the lowest priority coefficient can be selected as the current layer to be hidden based on the current layer priority sequence.

[0164] Furthermore, in step 254, the currently hidden layer can be hidden, and the actual frame rate of the map application can be re-captured.

[0165] In step 255, it is determined whether the actual frame rate is still less than the preset acceptable threshold. If so, the layer before the current layer to be hidden in the current layer priority sequence, that is, the layer with a higher priority coefficient than the current layer to be hidden, is taken as the new current layer to be hidden, and step 52 is returned to be executed. This process is repeated until the actual frame rate is greater than the preset acceptable threshold, or all low-priority layers in the current layer priority sequence are hidden.

[0166] Among them, low-priority layers in the current layer priority sequence can be determined by a pre-set priority coefficient threshold. If the priority coefficient is lower than the threshold, it can be determined as a low-priority layer.

[0167] Through steps 253-255 above, when the actual frame rate is less than the preset acceptable threshold, each layer can be gradually hidden in order of priority from low to high until the actual frame rate reaches the preset acceptable threshold or there are no low-priority layers to hide. This enables precise dynamic control and avoids hiding too many layers at once, which would affect the user experience.

[0168] In this embodiment of the application, in order to avoid the user experience being affected by too many hidden layers, the actual frame rate of the map application can be collected in real time after the dynamic adjustment is completed. If the actual frame rate is greater than the preset smoothness threshold and the user does not operate for a certain period of time (such as 5 seconds), the hidden layers can be restored in order of priority from high to low according to the current layer priority sequence to ensure the continuity of user interaction.

[0169] It should also be noted that, in this embodiment of the application, when the map scale changes and the actual frame rate after rendering is lower than the preset smoothness threshold, dynamic adjustment is initiated, which can realize the combination of user-active zooming and passive frame rate triggering mechanism, taking into account both user experience and rendering performance, making the operation of map application more robust.

[0170] In steps 21-25 above, during the operation of the map application, in response to the detection of a change in map scale or the launch of the map application, the priority sequence of the current layer corresponding to the current scale is obtained. Then, the currently displayable layer combination is rendered according to the current layer priority sequence to load the elements of interest at the current scale, avoiding loading too much unnecessary data, solving the problem of redundant resource loading, and improving the smoothness of the map application. Furthermore, after rendering the currently displayable layer combination, the actual frame rate after rendering is obtained. If the actual frame rate is less than the preset smoothness threshold, some layers in the currently displayable layer combination are hidden according to the current layer priority sequence to achieve dynamic adjustment and achieve the purpose of precise allocation of rendering resources. This can improve rendering performance and thus improve the smoothness of the map application. While ensuring rendering performance, user experience is also taken into account, making the finally loaded layers more in line with user needs.

[0171] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example... Figure 2 As shown, the electronic device 400 includes one or more processors 401 and memory 402.

[0172] The processor 401 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 400 to perform desired functions.

[0173] The memory 402 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 401 may execute the program instructions to implement the map rendering method of any embodiment of this application described above and / or other desired functions. Various contents such as initial extrinsic parameters and thresholds may also be stored in the computer-readable storage medium.

[0174] In one example, the electronic device 400 may further include an input device 403 and an output device 404, these components being interconnected via a bus system and / or other forms of connection mechanisms (not shown). The input device 403 may include, for example, a keyboard, a mouse, etc. The output device 404 may output various information to the outside, including warning messages, braking force, etc. The output device 404 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0175] Of course, for the sake of simplicity, Figure 2 Only some of the components of the electronic device 400 relevant to this application are shown in this illustration; components such as buses, input / output interfaces, etc., are omitted. In addition, the electronic device 400 may include any other suitable components depending on the specific application.

[0176] In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps of the map rendering method provided in any embodiment of this application.

[0177] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0178] Furthermore, embodiments of this application may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps of the map rendering method provided in any embodiment of this application.

[0179] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0180] It should be noted that the terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates otherwise, words such as "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, or apparatus. Without further limitations, an element defined by the phrase "comprising an..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element.

[0181] It should also be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," "linked," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this application can be understood according to the specific circumstances.

[0182] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. The above descriptions are only preferred embodiments of this application. It should be noted that due to the limitations of written expression, while there are objectively infinite specific structures, those skilled in the art can make several improvements, modifications, or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner. These improvements, modifications, changes, or combinations, or the direct application of the inventive concept and technical solution to other situations without modification, should all be considered within the scope of protection of this application.

Claims

1. A map rendering method, characterized in that, include: In response to detecting that a vehicle has entered map calibration mode, the application operation scenario data of the foreground process is obtained, and the corresponding layer resource consumption information is determined based on the application operation scenario data. Obtain each preset scale of the map application in the vehicle, and for each preset scale, determine each candidate layer corresponding to the preset scale according to the granularity of the preset scale. Obtain the single-layer rendering frame rate of the candidate layers, and combine the candidate layers whose single-layer rendering frame rate is higher than a preset smoothness threshold to obtain a candidate layer combination; Determine the multi-layer rendering frame rate of the candidate layer combination under the layer resource consumption information. If the multi-layer rendering frame rate is less than a preset acceptable threshold, hide some layers in the candidate layer combination to obtain a displayable layer combination corresponding to the preset scale. Based on the combination of displayable layers corresponding to each preset scale, a display rule table corresponding to the layer resource consumption information is constructed, wherein the display rule table is used for layer rendering during the map application runtime of the vehicle.

2. The method according to claim 1, characterized in that, Based on the application operation scenario data, the corresponding layer resource consumption information is determined, including: Based on the application operation scenario data, determine the operation application, the corresponding operation type, operation duration, and operation resource consumption. The CPU utilization, memory usage, and display frame rate are determined based on the operation type, operation duration, and operation resource consumption. Based on the CPU utilization, memory usage, and display frame rate, the layer resource consumption information corresponding to the application operation scenario data is determined.

3. The method according to claim 1, characterized in that, After constructing the display / hiding rule table corresponding to the layer resource consumption information, the method further includes: In response to detecting a change in the scale during the startup or operation of a map application, the system acquires current operation scenario data and determines current resource consumption information based on the current operation scenario data. Obtain the display / hidden rule table corresponding to the current resource consumption information, and determine the current scale; Based on the current scale, the currently displayable layer combination is queried in the obtained display rule table, and the current layer priority sequence is determined according to the current scale; Render the currently displayable layer combination and obtain the actual frame rate after rendering the currently displayable layer combination; If the actual frame rate is less than the preset smoothness threshold, then some layers in the currently displayable layer combination are hidden according to the current layer priority sequence until the actual frame rate is greater than the preset smoothness threshold.

4. The method according to claim 3, characterized in that, Determine the priority sequence of the current layer based on the current scale, including: The priority coefficient list corresponding to the current scale is retrieved from the preset priority table. The priority coefficient list includes the priority coefficients of each layer corresponding to the current scale, and each layer corresponding to the current scale is a layer that satisfies the granularity corresponding to the current scale. Sort the layers corresponding to the current scale in descending order of priority coefficients in the priority coefficient list to obtain the priority sequence of the current layer corresponding to the current scale.

5. The method according to claim 4, characterized in that, The preset priority table is used to describe the correspondence between each preset scale and each priority coefficient list. The construction of the preset priority table includes: Obtain a preset scale and determine each layer corresponding to the preset scale based on the granularity corresponding to the preset scale. For each layer corresponding to the preset scale, determine the predicted rendering time and user demand frequency of the layer, and determine the priority coefficient of the layer based on the predicted rendering time and user demand frequency. Based on the priority coefficients of each layer corresponding to the preset scale, construct a priority coefficient list corresponding to the preset scale. Construct a preset priority table based on the priority coefficient list corresponding to each preset scale.

6. The method according to claim 5, characterized in that, Determining the frequency of user demand for the layer includes: Obtain the map element click records and navigation records of the map application, and determine the user demand frequency for each layer based on the map element click records and navigation records; Alternatively, display element query information on the vehicle's infotainment system interface, obtain the elements of interest that the user responds to inquiries about, and determine the frequency of user demand for each layer based on the elements of interest.

7. The method according to claim 3, characterized in that, Hides some layers in the currently displayable layer group according to the current layer priority sequence, including: If the actual frame rate is less than the preset smoothness threshold and the actual frame rate is greater than the preset acceptable threshold, a high-priority layer is determined according to the current layer priority sequence. Retain the high-priority layer in the currently displayable layer combination, and hide all other layers except the high-priority layer; Wherein, the preset smoothness threshold is greater than the preset acceptable threshold.

8. The method according to claim 7, characterized in that, Hides some layers in the currently displayable layer group according to the current layer priority sequence, including: If the actual frame rate is less than the preset acceptable threshold, the layer with the lowest priority coefficient in the current layer priority sequence will be determined as the current layer to be hidden. Hide the currently hidden layer and reacquire the actual frame rate; If the actual frame rate is less than the preset acceptable threshold, then the layer preceding the current layer to be hidden in the current layer priority sequence is determined as the new current layer to be hidden, and the process of hiding the current layer to be hidden is returned until the actual frame rate is greater than the preset acceptable threshold, or all low-priority layers in the current layer priority sequence are hidden.

9. An electronic device, characterized in that, The electronic device includes: Processor and memory; The processor executes the steps of the map rendering method as described in any one of claims 1 to 8 by calling the program or instructions stored in the memory.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that cause a computer to perform the steps of the map rendering method as described in any one of claims 1 to 8.

Images