Image loading method and system, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an image loading method and system, electronic equipment and a storage medium. In some embodiments, the image loading method comprises the steps that in response to image information in interest point data indicating that the access type of an image needing to be displayed is a first specified type, an image analysis request is sent to a host background according to access address information of the image in the image information, and the image analysis request comprises the access address information of the image; and receiving and displaying the image data of the image fed back by the host background.

Description

Technical Field

[0001] The embodiments of this application relate to the field of data processing, and more specifically, to an image loading method, system, electronic device, and storage medium. Background Technology

[0002] With the rapid development of technology, map search and navigation functions are becoming increasingly sophisticated and widely used. When using these functions, it may be necessary to obtain detailed information about points of interest (or map points). This information may include images of the point of interest, such as food images or environmental images for food-related points of interest. To enhance security, many point-of-interest images employ encryption or authentication mechanisms, which increases the difficulty for the terminal to load and display such images. Summary of the Invention

[0003] The embodiments of this application provide an image loading method, system, electronic device, and storage medium that can at least partially solve the above-mentioned or other problems existing in the prior art.

[0004] One embodiment of this application provides an image loading method, including: responding to image information in point-of-interest data indicating that the access type of the image to be displayed is a first specified type, sending an image parsing request to a host backend according to the image access address information in the image information, wherein the image parsing request includes the image access address information; and receiving and displaying image data of the image fed back by the host backend.

[0005] Another embodiment of this application provides an image loading system, including a host, a host backend, and a map service provider backend. The host can be configured to, in response to image information in point-of-interest data indicating that the access type of the image to be displayed is a first specified type, send an image parsing request based on the image access address information in the image information. The image parsing request includes the image access address information. The host backend can be configured to, in response to receiving the image parsing request, initiate an image data acquisition request based on the image access address information in the image parsing request, and send the image data of the image returned by the map service provider backend to the host. The map service provider backend can be configured to, in response to receiving the image data acquisition request, send the image data of the image to the host backend; wherein the host receives and displays the image data of the image returned by the host backend.

[0006] Another embodiment of this application provides an electronic device including at least one processor and a memory. The memory is communicatively connected to the at least one processor and stores instructions executable by the at least one processor. These instructions, when executed by the at least one processor, enable the at least one processor to perform the image loading method mentioned in the above embodiments.

[0007] Another embodiment of this application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the image loading method mentioned in the above embodiments.

[0008] According to some embodiments of this application, after determining that the image information in the point of interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. This image parsing request may include the image access address information, so that the host backend can verify with the image provider's backend based on the image access address information and obtain the image data. This eliminates the need for the executing entity to store too many certificates for image information of various formats and data sources (e.g., image domain names), allowing it to focus solely on the business itself and reducing the likelihood of image display failures due to parsing failures.

[0009] In some embodiments of this application, the image information also includes the domain name information of the host backend. Sending an image parsing request to the host backend based on the image access address information in the image information includes: generating an image parsing request based on the image access address information; and sending an image parsing request to the host backend based on the domain name information of the host backend.

[0010] In some embodiments of this application, the access address information of the image and the domain name information of the host backend are combined in a preset format to form the combined access address information of the image, and the combined access address information of the image is written into the image information of the point of interest data.

[0011] In some embodiments of this application, sending an image parsing request to the host backend based on the image access address information in the image information includes: generating an image parsing request based on the image access address information; and sending the image parsing request to the host backend based on the pre-set domain name information of the host backend.

[0012] In some embodiments of this application, the method is applied to a host, the host's configuration file stores a domain name whitelist, and in response to the image information of the point of interest data indicating that the access type of the image to be displayed is a first specified type, an image resolution request is sent to the host backend according to the image access address information in the image information, including: in response to the image information indicating that the access type of the image to be displayed is a first specified type, and the domain name carried in the access address information is within the whitelist, an image resolution request is sent to the host backend according to the image access address information in the point of interest data.

[0013] In some embodiments of this application, the method further includes: responding to an image information indicating that the access type of the image to be displayed is a second specified type, requesting image data of the image from the map provider's backend according to the image access address information in the image information; receiving and displaying the image data of the image fed back by the map provider's backend; wherein the first specified type is Hypertext Transfer Protocol Security (HTTPS) type and the second specified type is Hypertext Transfer Protocol HTTP type.

[0014] In some embodiments of this application, the method further includes: in response to detecting a point of interest search instruction, sending a point of interest data acquisition request to a host backend; receiving point of interest data fed back by the host backend, the point of interest data including location information and image information of the point of interest. Attached Figure Description

[0015] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings. Wherein:

[0016] Figure 1 A schematic block diagram of an exemplary system architecture to which the image loading method of this disclosure can be applied is shown;

[0017] Figure 2 This is a flowchart illustrating the image loading method according to the first embodiment of this application;

[0018] Figure 3 This is a schematic flowchart of an image loading method according to the second embodiment of this application;

[0019] Figure 4 This is an interactive diagram of a host, a host backend search service, a host backend image service, and a map provider backend according to some embodiments of this application;

[0020] Figure 5 This is a schematic flowchart of an image loading method according to the third embodiment of this application;

[0021] Figure 6 This is a schematic block diagram of an image loading system according to some embodiments of this application;

[0022] Figure 7 These are schematic block diagrams of electronic devices according to some embodiments of this application. Detailed Implementation

[0023] To better understand this application, various aspects of this application will be described in more detail with reference to the accompanying drawings. It should be understood that these detailed descriptions are merely illustrative of exemplary embodiments of this application and are not intended to limit the scope of this application in any way. Throughout the specification, the same reference numerals refer to the same elements. The expression "and / or" includes any and all combinations of one or more of the associated listed items.

[0024] It should also be understood that expressions such as "comprising," "including," "having," "containing," and / or "comprising" are open-ended rather than closed-ended expressions in this specification, indicating the presence of the stated features, elements, and / or components, but not excluding the presence of one or more other features, elements, components, and / or combinations thereof. Furthermore, when describing embodiments of this application, the word "may" is used to mean "one or more embodiments of this application." And the term "exemplary" is intended to refer to examples or illustrations.

[0025] Unless otherwise specified, all terms used herein (including engineering and technical terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that, unless expressly stated herein, terms defined in common dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as having an idealized or overly formalized meaning.

[0026] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. Furthermore, unless explicitly limited or contradicted by the context, the specific steps included in the methods described in this application are not limited to the order in which they are described, but can be performed in any order or in parallel. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0027] Figure 1 A schematic block diagram of an exemplary system architecture to which the image loading method of this disclosure can be applied is shown.

[0028] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0029] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as video applications, live streaming applications, instant messaging tools, email clients, social media platform software, etc.

[0030] The terminal devices 101, 102, and 103 here can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with displays, such as in-vehicle infotainment systems. When terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. They can be implemented as multiple software programs or software modules (e.g., multiple software programs or software modules used to provide distributed services) or as a single software program or software module. No specific limitations are made here.

[0031] As an example, the terminal device could also be a vehicle-mounted host, for instance; there are no limitations on this.

[0032] Server 105 can be a server that provides various services, such as a backend server that supports terminal devices 101, 102, and 103. The backend server can process received image parsing requests and feed back the processing results (such as the image data corresponding to the image parsing request) to the terminal devices.

[0033] It should be noted that the image loading method provided in this embodiment can be executed by server 105 or terminal devices 101, 102, 103. Accordingly, the image loading device can be set in server 105 or terminal devices 101, 102, 103.

[0034] It should be understood that, Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0035] Figure 2 This is a schematic flowchart of an image loading method according to a first embodiment of this application. The executing entity of this image loading method 200 can be various types of terminals, such as vehicle-mounted terminals; this application does not impose any limitations on this. Figure 2 As shown, the image loading method 200 may include the following steps:

[0036] Step 201: In response to the image information in the point of interest data indicating that the access type of the image to be displayed is the first specified type, an image parsing request is sent to the host backend according to the image access address information in the image information.

[0037] In this embodiment, Point of Interest (POI) data may include location information, depth information, and so on. Taking a charging station as an example, the depth information of the charging station may include the power of the charging gun, its occupancy status, parking fee information, parking lot images, and parking discount information (such as points redemption). Just as the depth information of a charging station includes parking lot images, the depth information in other types of POI data may also include images. For example, the depth information in attraction-type POI data may include attraction images and attraction ratings, while the depth information in restaurant-type POI data may include food images, shop images, unit prices, ratings, etc.

[0038] In this embodiment, the image information may include, for example, the access address information of the image. This access address information can be transmitted in the form of a Uniform Resource Locator (URL) or in other forms; no limitation is imposed here. The executing entity can generate an image parsing request based on the image's access address information to request the host backend to return the image data. The executing entity can generate the image parsing request by using the access address information as an input parameter in a pre-set image parsing request format to obtain a valid image parsing request, or it can use other methods; no limitation is imposed here.

[0039] In this embodiment, the host backend can be, for example, a backend service platform that provides the host with search services, vehicle networking services, and other related services. This host backend can be deployed on a cloud server or other devices; there are no restrictions here.

[0040] In some embodiments of this application, the executing entity may also, in response to detecting a point-of-interest (POI) search command, send a POI data acquisition request to the host backend; and receive POI data fed back by the host backend, which may include the location information and image information of the POI. For example, a user may perform a POI search operation on the executing entity. For instance, a user triggers a POI search command through the executing entity's interactive system (such as a touchscreen-based or voice-based interactive system). After detecting that the user has triggered the POI search command, the executing entity may initiate a POI data acquisition request to the host backend. The host backend performs a POI retrieval based on the POI data acquisition request and determines POI data that meets the requirements of the POI data acquisition request. The executing entity then performs subsequent operations based on whether the POI data contains image information.

[0041] In some technologies, image information is written into depth information. The executing entity can determine whether to request the image data corresponding to the image information based on whether the depth information contains image information. For example, if the parameter used to indicate whether the point of interest (POI) contains depth information (e.g., hasdeep) has a first specified value (e.g., the value "1"), the executing entity needs to request the depth information interface (deepinfo) again after receiving the POI data to obtain the depth information, and then summarize the depth information returned by the interface and the previously returned POI data before providing feedback. If the parameter used to indicate whether the POI contains depth information (e.g., hasdeep) has a second specified value (e.g., the value "0"), the executing entity can directly provide the POI data. In other words, a single POI search may request the host backend interface twice depending on business needs. One request requests the basic information of the POI, i.e., the POI data, which can indicate whether the POI contains detailed information (e.g., images, reviews, etc.), and the other request requests the detailed information of the POI.

[0042] Typically, the images in Points of Interest (POI) data are provided by map providers, and the implementing entity can retrieve relevant images of POIs from the map provider's backend based on the image information. Different map providers may define different fields for the images, but they are generally similar. For example, the data format of POI data is JSON (an open standard file and data exchange format). In some technologies, the image access type is Hypertext Transfer Protocol (HTTP). In this case, JSON-formatted POI data might look like this:

[0043] {

[0044] "adCode":"", / / "Interest Point Code":"";

[0045] "address":"", / / "address":"";

[0046] "addressHighlights":[], / / "addressHighlights":[];

[0047] "areacode":"021", / / "region code":"021";

[0048] "category":null, / / "category": empty;

[0049] "cityCode":"xxx", / / "city code":"xxx";

[0050] "cityName":"xxx", / / "city name":"xxx";

[0051] "distance":null, / / "distance": empty;

[0052] "districtCode":"xxx", / / "Administrative District Code":"xxx";

[0053] "districtName":"xxx", / / "Administrative District Name":"xxx";

[0054] "hasDeep":"1", / / "Contains depth information":"1";

[0055] "id":"xxx", / / "identifier":"xxx";

[0056] "latitude":"xxx", / / "latitude":"xxx";

[0057] "latitudeEntrance":"xxx", / / "latitude entrance":"xxx";

[0058] "longitude":"xxx", / / "longitude entrance":"xxx";

[0059] "longitudeEntrance":"xxx", / / "longitude entrance":"xxx";

[0060] "name":"demo", / / "name":"demo";

[0061] "pid":"xxx", / / "Personal ID":"xxx";

[0062] "deepinfo":{ / / Entry point for deep information;

[0063] "picture_info":[ / / Image entry point;]

[0064] "http%3A%2F%2F……", / / URL of image 1;

[0065] "http%3A%2F%2F……", / / URL of image 2; ]

[0067] }

[0068] }

[0069] Regarding the aforementioned point-of-interest data, since images are of HTTP type and do not require two-way authentication, in most cases, the executing entity can obtain the image data from the depth information based on the image information (such as the image URL).

[0070] However, with the widespread adoption of cloud computing, a large number of images have been converted from HTTP to HTTPS (Hypertext Transfer Protocol Secure). Taking the JSON above as an example, most image information requested from image providers' backends is currently in HTTPS format, and its corresponding JSON format is as follows:

[0071] "deepinfo":{ / / Entry point for deep information;

[0072] "picture_info":[ / / Image entry point;]

[0073] "https%3A%2F%2F……", / / URL of image 1;

[0074] "https%3A%2F%2F……" / / URL of image 2; ]

[0076] }

[0077] Compared to HTTP, HTTPS (Hypertext Transfer Protocol Secure) is an HTTP channel with security as its primary goal. Building upon HTTP, it ensures security during transmission through encryption and authentication. The principles of HTTPS content encryption, authentication, and data integrity protection mainly rely on the SSL / TLS (Secure Sockets Layer / Transport Layer Security) protocol. Taking a client and server as an example, the HTTPS verification process includes: the client receiving the server's digital certificate and verifying its legitimacy; the digital certificate is issued by an authoritative Certificate Authority (CA) and contains the server's public key, server identity information, and the CA's signature; when the client establishes an HTTPS connection with the server, the server sends its digital certificate to the client; the client checks whether the certificate was issued by a trusted CA; the client checks whether the certificate has expired and whether the server identity information in the certificate matches the server being connected to; the client uses the CA's public key to verify the signature on the certificate, ensuring that the certificate has not been tampered with during transmission; if the certificate verification passes, the client can confirm that the server's identity is trustworthy. Because HTTPS requires encryption and decryption, its performance may be slightly lower than HTTP. However, with technological advancements, this performance gap has become negligible. Therefore, image information provided by image providers has been converted from HTTP to HTTPS.

[0078] After image information adopts HTTPS, the executing entity, upon receiving the HTTPS format image returned by the host backend, may be unable to resolve the image because it cannot verify the image's domain name certificate. Taking the executing entity as an in-vehicle host as an example, the cause of this problem may include issues with the in-vehicle host's integration process. For instance, the underlying system of the in-vehicle system (e.g., Linux) integrates various applications, such as common multimedia applications (music, radio, multimedia, karaoke, etc.), navigation services (various maps, POI search, charging map POI), account login, real-name authentication, third-party application markets, and application stores. Each module is handled by a different vendor. Therefore, an in-vehicle system version needs to integrate all applications before being packaged into a single final version. A final version of an in-vehicle system may take two weeks; for example, one week to collect sub-module versions from various content providers (CPs), and another week for testing before release. During the development of the in-vehicle system version project, if a new HTTPS image address is available, authentication can be added. However, once the project is completed and the system is packaged, supporting authentication for that new HTTPS image address becomes quite complicated, as vehicles using this in-vehicle system version may have already been sold. Considering cost-effectiveness, it's not worthwhile to upgrade images requiring detailed display within the Point of Interest (POI) data using Over-the-Air (OTA) technology. In short, images may be stored in the cloud, and map providers obtain images from diverse sources, potentially from multiple network providers, making control difficult. This leads to frequent changes in cloud image addresses, requiring the vehicle's head unit (HMU) certificate to be hardcoded in advance. This makes it difficult for the HMU to verify certificates for various URLs, preventing verification of cloud images outside the configured certificate range. Consequently, images not within the HTTPS verification range cannot be displayed on the HMU. After the project ends (version closed), it's difficult for project personnel to provide technical support. Suppliers may need to be evaluated, and even if they are willing to support, it incurs costs, and the scope of integration is uncertain. Implementing this functionality via OTA is less cost-effective.

[0079] To address the above issues, in some embodiments of this application, after determining that the image information in the point-of-interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. This image parsing request may include the image access address information. Based on this access address information, the host backend can verify with the image provider's backend and obtain the image data. Since the executing entity typically verifies the interface domain's certificate when initiating a request to the host backend (e.g., a point-of-interest search command), and this certificate is pre-embedded in the executing entity, the executing entity does not need to store too many certificate URLs for image information (e.g., image domains) of various formats and data sources; it only needs to focus on the business itself. The host backend can store certificates for various data sources so that it can subsequently obtain HTTPS format image data based on these certificates and feed the obtained image data back to the host backend. Through this method, the executing entity can obtain image data without configuring the image source's certificate, reducing the possibility of image display failure due to parsing failure.

[0080] Optionally, when adding image sources (e.g., adding image providers), certificates for the new image sources can be added in the host backend to obtain image data from those new sources. This process does not require an OTA upgrade of the executing entity to enable it to parse and obtain image data from the new image source, making the operation more convenient.

[0081] Optionally, the executing entity can also, in response to the image information indicating that the access type of the image to be displayed is a second specified type, request image data from the map provider's backend based on the image access address information in the image information; and receive and display the image data returned by the map provider's backend. Here, the first specified type is Hypertext Transfer Protocol Security (HTTPS), and the second specified type is Hypertext Transfer Protocol (HTTP). In other words, if the image information in the point of interest data indicates that the access type of the image to be displayed is HTTP (which does not require authentication), the executing entity can request image data from the map provider's backend based on the image access address information, without needing to obtain image data through the host backend, thus reducing the burden on the host backend.

[0082] It should be understood that, without departing from the teachings of this application, the first designated type may also be other access types that require authentication, and the second designated type may also be other access types that do not require authentication, and this application does not impose any restrictions on this.

[0083] In some embodiments of this application, the executing entity may be a host (such as an in-vehicle host). The host's configuration file stores a domain name whitelist. After determining that the image information in the point-of-interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image resolution request to the host backend based on the image access address information in the image information. This step may include: in response to the image information indicating that the access type of the image to be displayed is the first specified type, and the domain name carried in the access address information being within the domain name whitelist, sending an image resolution request to the host backend based on the image access address information in the point-of-interest data. The domain name whitelist may be determined based on domain names with authentication certificates held by the host backend. In other words, after determining that the image to be displayed according to the point of interest data is the first specified type requiring authentication, the executing entity checks whether the domain name carried by the access address information of the image is in the domain whitelist. If it is determined that the domain name carried by the access address information of the image is in the domain whitelist, it means that the host backend has the ability to obtain the image data of the image, and requests the image data of the image from the host backend. If it is determined that the domain name carried by the access address information of the image is not in the domain whitelist, it means that the host backend does not have the ability to obtain the image data of the image, and does not request the image data of the image from the host backend, so as to reduce the burden on the host backend caused by unprocessable requests.

[0084] Optionally, the domain whitelist in the host can be updated. For example, when some domain certificates are added or removed in the host backend, the domain whitelist can be updated according to the updated certificates. The domain whitelist can be made into a configuration file and then distributed to the execution entity. Because the domain whitelist is made into a configuration file, the microservice code does not need to be modified. The execution entity and the host backend only need to restart the service after making the configuration changes for the new domain whitelist to take effect, making the operation simpler and the process more controllable.

[0085] It should be understood that, without departing from the teachings of this application, the implementing entity may obtain information about the domain names that the host backend can resolve through other means, and this application does not restrict this.

[0086] Step 202: Receive and display the image data fed back by the host backend.

[0087] In some embodiments of this application, after the host backend obtains the image data, it can send the image data back to the execution entity. After receiving the image data, the execution entity can display the image data.

[0088] Optionally, the image data can be an image stream. For example, the host backend requests image data from the image provider's backend based on the image's access address information. The image provider's backend can then obtain the image stream based on this access address information and send it back to the host backend. The host backend then sends the received image stream back to the executing entity. The executing entity renders the image based on the image stream and displays detailed information about the points of interest.

[0089] Optionally, after receiving image data, the executing entity can aggregate the image data with previously received point-of-interest (POI) data before displaying it. The aggregation method for image data and POI data can be preset and is not restricted here. In other words, after receiving POI data, the executing entity may not display the POI data immediately, but wait until the image data is acquired before displaying them together.

[0090] It should be understood that, without departing from the teachings of this application, the implementing entity may first display the point of interest data, and then display the image data at a designated location on the interface after receiving the image data; there are no restrictions on this.

[0091] According to some embodiments of this application, after determining that the image information in the point of interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. This image parsing request may include the image access address information. Based on this access address information, the host backend can verify with the image provider's backend and obtain the image data. Since the executing entity typically verifies the interface domain's certificate when initiating a request to the host backend (e.g., a point of interest search command), and this certificate is pre-embedded in the executing entity, the executing entity does not need to store too many certificate URLs for image information (e.g., image domains) of various formats and data sources; it only needs to focus on the business itself. The host backend can store certificates for various data sources so that it can subsequently obtain HTTPS format image data based on these certificates and feed the obtained image data back to the host backend. Through this method, the executing entity can obtain image data without configuring the image source's certificate, reducing the possibility of image display failure due to parsing failure.

[0092] Figure 3 This is a flowchart illustrating an image loading method according to a second embodiment of this application. This embodiment is largely the same as the first embodiment, with the main difference being that it executorably describes the process by which the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. Figure 3 As shown, the image loading method 300 may include the following steps:

[0093] Step 301: In response to the image information in the point of interest data indicating that the access type of the image to be displayed is the first specified type, generate an image parsing request based on the image access address information.

[0094] In this embodiment, the image information also includes the domain name information of the host backend. That is, the image information contains both the image access address information and the domain name information of the host backend that can be authenticated, so that the executing entity can obtain the image data through the host backend. The executing entity can generate an image parsing request based on the image access address information to request the host backend to return the image data.

[0095] In this embodiment, the domain name information of the host backend can be the domain name of the interface request used by the host backend to obtain image data, or the domain name of the interface used by the host backend to perform POI search. Through this domain name, other devices can call the function of obtaining image data from the host backend.

[0096] Step 302: Based on the domain name information of the host backend, send an image parsing request to the host backend.

[0097] In this embodiment, after obtaining the image information, the executing entity accesses the interface of the host backend for obtaining image data based on the domain name information of the host backend in the image information, and sends an image parsing request to request the host backend to provide the image data of the image to be displayed.

[0098] In some embodiments of this application, the image access address information and the host backend domain name information are combined according to a preset format to form the image combined access address information, which is then written into the image information of the point of interest data. In other words, the image access address information and the host backend domain name information are combined into a single piece of information and written into the image information, without needing to add a new field to the host backend domain name information.

[0099] As an example, if the JSON format of the image access address information is as follows:

[0100]

[0101] The JSON format of the combined access address information corresponding to this image is as follows:

[0102]

[0103]

[0104] The image information of each image in the image provider's backend can be modified as shown in the example above, that is, by appending the domain name of the host backend to the original address of the image provider's backend. After obtaining the image information with the host backend domain name, the executing entity uses the actual address of the image provider's backend in the image information (i.e., the image access address information) as input parameter to request the image forwarding interface (the interface used to obtain image data) from the host backend. After receiving this request (image parsing request), the host backend can request image data from the image provider's backend based on the input parameter.

[0105] It should be understood that, without departing from the teachings of this application, the access address information of the image and the domain name information of the host backend may also be combined in other formats, and this application does not restrict this.

[0106] It should be understood that, without departing from the teachings of this application, the map provider's backend may add new fields to the point of interest data for inputting the domain name information of the host backend, or may add the domain name information of the host backend in other ways. This application does not restrict the way the domain name information of the host backend is added.

[0107] Step 303: Receive and display the image data fed back by the host backend.

[0108] In this embodiment, step 303 and Figure 2 Step 202 is roughly the same, and will not be repeated here.

[0109] To facilitate understanding, the following example uses the executing entity as the host, with a retrieval service for POI searches and an image service for requesting image data set up in the host's backend, to illustrate the interaction process between the various ends. For example, Figure 4 This is an interactive diagram of a host, a host background search service, a host background image service, and a map provider background according to some embodiments of this application.

[0110] like Figure 4 As shown, the interaction process includes:

[0111] Step 401: Host 410 sends a point of interest search command to the retrieval service 420 in the host background.

[0112] For example, a point of interest (POI) search instruction can include information about the POIs to be searched, used to request POI data. In this example, the information about the POIs to be retrieved contains detailed information (e.g., images, ratings, etc.).

[0113] Step 402: The retrieval service 420 of the host backend initiates a retrieval request to the map provider backend 440 based on the point of interest search command.

[0114] For example, the retrieval service 420 in the host backend may store the request address of the map provider backend 440. After receiving a point of interest search instruction, the retrieval service 420 in the host backend initiates a retrieval request to the map provider backend 440 based on the request address.

[0115] In step 403, the map provider's backend 440 feeds back the point of interest data to the host backend's retrieval service 420.

[0116] For example, point-of-interest data includes image information of an image, which can be a combination of image access address information, i.e., the image information of an image includes the image access address information and the domain name information of the image service 430 on the host backend.

[0117] In step 404, the retrieval service 420 in the host background feeds back the point of interest data to the host 410.

[0118] For example, the retrieval service 420 in the host background can determine the address of the host 410 based on the source address in the point of interest search instruction, and then feed back the point of interest data to the host 410.

[0119] Step 405: Host 410 sends an image parsing request to the image service 430 in the host backend based on the access address information of the image in the point of interest data.

[0120] For example, since the information of the point of interest to be retrieved in this example contains detailed information, namely an image, after receiving the point of interest data, if the host 410 determines that the image information in the point of interest data indicates that the access type of the image to be displayed is the first specified type, it can send an image parsing request to the image service 430 in the host background according to the access address information of the image in the image information and the domain name information of the image service 430 in the host background.

[0121] Step 406: The image service 430 in the host backend requests image data from the image provider backend 440.

[0122] For example, the image service 430 in the host backend may store authentication certificates for multiple image source domains, so as to authenticate with the image backend 440 based on the authentication certificates and thereby obtain the image data of the image.

[0123] Step 407: The image provider's backend 440 sends the image data to the host backend image service 430.

[0124] For example, the image data of an image can be streaming image data so that the host can display the image faster.

[0125] Step 408: The image service 430 in the host background sends the image data back to the host 410.

[0126] For example, the image service 430 in the host background can determine the address of the host 410 based on the source address in the image parsing request, and then send the image data back to the host 410.

[0127] According to some embodiments of this application, after determining that the image information in the point of interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. This image parsing request may include the image access address information, so that the host backend can verify with the image provider's backend based on the image access address information and obtain the image data. This eliminates the need for the executing entity to store too many certificates for image information of various formats and data sources (e.g., image domain names), allowing it to focus solely on the business itself and reducing the likelihood of image display failures due to parsing failures.

[0128] Figure 5 This is a flowchart illustrating an image loading method according to a third embodiment of this application. This embodiment is largely the same as the first embodiment, with the main difference being that it executorably describes the process by which the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. Figure 5 As shown, the image loading method 500 may include the following steps:

[0129] Step 501: In response to the image information in the point of interest data indicating that the access type of the image to be displayed is the first specified type, generate an image parsing request based on the image access address information.

[0130] In this embodiment, step 501 and Figure 2 The process of generating the image parsing request in step 201 is roughly the same, and will not be repeated here.

[0131] Step 502: Based on the pre-set domain name information of the host backend, send an image parsing request to the host backend.

[0132] In this embodiment, the domain name information of the host backend can be pre-embedded in the execution entity. After determining that the access type of the image to be displayed is the first specified type, the execution entity can generate an image parsing request with the host backend as the target based on the pre-embedded domain name information of the host backend, and then send the image parsing request to the host backend.

[0133] It should be understood that, without departing from the teachings of this application, the domain name information of the host backend can be set in the host backend in a manner that may vary depending on the software version of the executing entity, and no restrictions are imposed here.

[0134] Step 503: Receive and display the image data fed back by the host backend.

[0135] In this embodiment, step 503 and Figure 2 Step 202 is roughly the same, and will not be repeated here.

[0136] According to some embodiments of this application, after determining that the image information in the point of interest data indicates that the access type of the image to be displayed is a first specified type, the executing entity sends an image parsing request to the host backend based on the image access address information in the image information. This image parsing request may include the image access address information, so that the host backend can verify with the image provider's backend based on the image access address information and obtain the image data. This eliminates the need for the executing entity to store too many certificates for image information of various formats and data sources (e.g., image domain names), allowing it to focus solely on the business itself and reducing the likelihood of image display failures due to parsing failures.

[0137] It should be noted that the acquisition, storage, and application of user personal information involved in the technical solution disclosed herein all comply with relevant laws and regulations and do not violate public order and good morals. It should also be noted that the information in this embodiment was obtained after being authorized by the user (i.e., with the user's consent).

[0138] The steps of the various methods described above are only for clarity. In implementation, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the protection scope of this disclosure. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the protection scope of this disclosure.

[0139] This application also provides an image loading system. For example... Figure 6 As shown, the image loading system 600 may include a host 610, a host backend 620, and a map provider backend 630. The host 610 can be configured to, in response to an image information in the point of interest data indicating that the access type of the image to be displayed is a first specified type, send an image parsing request based on the image access address information in the image information. The image parsing request includes the image access address information. The host backend 620 can be configured to, in response to receiving the image parsing request, initiate an image data acquisition request based on the image access address information in the image parsing request, and send the image data of the image fed back by the map provider backend to the host. The map provider backend 630 can be configured to, in response to receiving the image data acquisition request, send the image data of the image to the host backend. The host 610 receives and displays the image data of the image fed back by the host backend 620.

[0140] In some embodiments of this application, the image information also includes the domain name information of the host backend 620. The host 610 is further configured to: generate an image parsing request based on the image access address information; and send the image parsing request to the host backend 620 based on the domain name information of the host backend 620.

[0141] In some embodiments of this application, the access address information of the image and the domain name information of the host backend 620 are combined in a preset format to form the combined access address information of the image, and the combined access address information of the image is written into the image information of the point of interest data.

[0142] In some embodiments of this application, the host 610 is further configured to: generate an image parsing request based on the image access address information; and send the image parsing request to the host backend 620 based on the pre-set domain name information of the host backend 620.

[0143] In some embodiments of this application, the configuration file of the host 610 stores a domain name whitelist, and the host 610 is further configured to: in response to the image information indicating that the access type of the image to be displayed is a first specified type, and the domain name carried by the access address information is within the domain name whitelist, send an image parsing request to the host backend 620 according to the access address information of the image in the point of interest data.

[0144] In some embodiments of this application, the host 610 is further configured to: in response to an image information indicating that the access type of the image to be displayed is a second specified type, request image data from the image provider backend 630 according to the image access address information in the image information; receive and display the image data fed back by the image provider backend 630; wherein the first specified type is Hypertext Transfer Protocol Security (HTTPS) type and the second specified type is Hypertext Transfer Protocol HTTP type.

[0145] In some embodiments of this application, the host 610 is further configured to: send a point of interest data acquisition request to the host backend 620 in response to detecting a point of interest search command; and receive point of interest data fed back by the host backend 620, wherein the point of interest data includes the location information and image information of the point of interest.

[0146] It is not difficult to see that this embodiment is a system implementation method corresponding to the above method embodiments, and this embodiment can be implemented in conjunction with the above method embodiments. The relevant technical details mentioned in the above method embodiments are still valid in this embodiment, and will not be repeated here to reduce repetition. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the above method embodiments.

[0147] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by this invention; however, this does not mean that other units are absent from this embodiment.

[0148] Embodiments of this application also provide an electronic device, such as... Figure 7 As shown, the electronic device 700 may include: at least one processor and a memory, the memory being communicatively connected to the at least one processor and storing instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the image loading method mentioned in the above embodiments.

[0149] For example, the electronic device 700 may be, for instance, an in-vehicle host unit that is communicatively connected to the display screen, executes the image loading method through the processor and memory in the in-vehicle host unit, and displays the image data through the display screen.

[0150] One embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the image loading method mentioned in the above embodiments.

[0151] Figure 7 This is a schematic block diagram of an electronic device 700 according to some embodiments of this application. For example... Figure 7 As shown, the electronic device 700 includes a processor 701, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 702 or a computer program loaded from a memory 708 into a random access memory (RAM) 703. The RAM 703 may also store various programs and data required for the operation of the electronic device 700. The processor 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0152] Multiple components in electronic device 700 are connected to I / O interface 705, including: input unit 706, such as buttons or a touchscreen in a vehicle infotainment system; output unit 707, connected to various types of displays, speakers, etc., to output various forms of signals; memory 708, including any medium for storing computer-executable programs; and communication unit 709, such as a network interface card (NIC), modem, or wireless transceiver. Communication unit 709 allows electronic device 700 to exchange information / data with other devices via a local area network (LAN) or other wireless communication networks.

[0153] Processor 701 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 701 performs the various methods and processes described above, such as the image loading method mentioned in the above embodiments. For example, in some embodiments, the image loading method mentioned in the above embodiments can be implemented as a computer software program, which is tangibly contained in a computer-readable storage medium, such as memory 708. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 700 via ROM 702 and / or communication unit 709. When the computer program is loaded into RAM 703 and executed by processor 701, one or more steps of the image loading method described above can be performed. Alternatively, in other embodiments, processor 701 can be configured to perform the image loading method mentioned in the above embodiments by any other suitable means (e.g., by means of firmware).

[0154] Various aspects of this application have been described herein with reference to flowchart illustrations and / or timing diagrams of methods, apparatus (systems), and computer program products according to exemplary embodiments of this application. It should be understood that each step of the flowchart illustrations and / or timing diagrams, as well as combinations of steps in the flowchart illustrations and / or timing diagrams, can be implemented by computer-readable program instructions.

[0155] These computer-readable program instructions can be provided to a processor, general-purpose computer, special-purpose computer, or other programmable data processing unit in an electronic device to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing device, they create means for implementing the functions / steps specified in one or more steps of a flowchart and / or timing diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing device, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / steps specified in one or more steps of a flowchart and / or timing diagram.

[0156] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / steps specified in one or more steps of a flowchart and / or timing diagram.

[0157] The flowcharts and timing diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each step in a flowchart or timing diagram may represent a module, segment, or part of an instruction that contains one or more executable instructions for implementing a specified logical function. In some alternative embodiments, the functions indicated in the steps may occur in a different order than those indicated in the drawings. For example, two consecutive steps may actually be performed substantially in parallel, and they may sometimes be performed in reverse order, depending on the functions involved. It should also be noted that each step in a timing diagram and / or flowchart, and combinations of steps in timing diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0158] The above description is merely an illustration of the embodiments of this application and the technical principles employed. Those skilled in the art should understand that the scope of protection involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the technical concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. An image loading method, comprising: In response to the image information in the point of interest data indicating that the access type of the image to be displayed is a first specified type, an image parsing request is sent to the host backend according to the access address information of the image in the image information, and the image parsing request includes the access address information of the image; Receive and display the image data of the image fed back by the host backend.

2. The method according to claim 1, wherein, The image information also includes the domain name information of the host backend. Sending an image parsing request to the host backend based on the image access address information in the image information includes: The image parsing request is generated based on the image's access address information; Based on the domain name information of the host backend, the image parsing request is sent to the host backend.

3. The method according to claim 2, wherein, The access address information of the image and the domain name information of the host backend are combined in a preset format to form the combined access address information of the image, and the combined access address information of the image is written into the image information of the point of interest data.

4. The method according to claim 1, wherein, The step of sending an image parsing request to the host backend based on the image access address information in the image information includes: The image parsing request is generated based on the image's access address information; Based on the pre-set domain name information of the host backend, the image parsing request is sent to the host backend.

5. The method according to any one of claims 1 to 4, wherein, The method is applied to a host whose configuration file stores a domain name whitelist. The image information in response to the point of interest data indicates that the access type of the image to be displayed is a first specified type. Based on the access address information of the image in the image information, an image parsing request is sent to the host backend, including: In response to the image information indicating that the access type of the image to be displayed is a first specified type, and the domain name carried by the access address information is within the domain name whitelist, the image parsing request is sent to the host backend according to the access address information of the image in the point of interest data.

6. The method according to any one of claims 1 to 4, further comprising: In response to the image information indicating that the access type of the image to be displayed is the second specified type, the image data of the image is requested from the image provider's backend according to the access address information of the image in the image information; Receive and display the image data of the image fed back by the map provider's backend; Wherein, the first specified type is the Hypertext Transfer Protocol Security (HTTPS) type, and the second specified type is the Hypertext Transfer Protocol HTTP type.

7. The method according to any one of claims 1 to 4, further comprising: In response to the detection of a point of interest search command, a request to obtain point of interest data is sent to the host backend; The system receives point-of-interest (POI) data from the host backend, which includes the location information of the POIs and the image information.

8. An image loading system, comprising: The host is configured to respond to an image information in the point of interest data indicating that the access type of the image to be displayed is a first specified type, and to send an image parsing request based on the access address information of the image in the image information, wherein the image parsing request includes the access address information of the image; The host backend is configured to, in response to receiving the image parsing request, initiate an image data acquisition request based on the image access address information in the image parsing request, and send the image data of the image fed back by the image provider backend to the host; The image provider's backend is configured to send the image data of the image to the host backend in response to receiving the image data acquisition request; The host receives and displays the image data of the image fed back by the host backend.

9. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the image loading method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the image loading method as described in any one of claims 1 to 7.

Images