Map management methods, devices, equipment and storage media
By sending a remote control request to the mobile terminal and verifying the request information of the map provider's cloud server when a remote control request is received from the target vehicle, the security issue of transferring surveying and mapping maps between platforms is solved, and the secure and compliant transfer of maps between multiple platforms is realized.
Patent Information
- Application Number
- CN202311670397.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-07
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-12-07
AI Technical Summary
How to securely transfer and use surveying maps between platforms, especially in beyond-line-of-sight vehicle control mode, while ensuring map security and compliance.
Upon receiving a remote control request from the target vehicle, a remote control request is sent to the mobile terminal, and the target key is sent after receiving a remote control agreement response from the mobile terminal. Then, the request verification information sent by the map provider cloud server is verified according to the account binding relationship. If the verification passes, the map download interface of the mobile terminal is opened.
It enables secure and compliant transfer of surveying maps across multiple platforms. The method is highly adaptable and has a short workflow, allowing for quick and easy deployment on various platforms.
Smart Images

Figure CN117668143B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of map management technology, and in particular to a map management method, apparatus, device, and storage medium. Background Technology
[0002] The current memory parking function in intelligent driving assistance systems learns driving paths and converts them into a mapping-like memory map, which is then saved locally. Later, when using the memory parking function, the memory map can be repeatedly loaded, and the intelligent driving controller and vehicle control system can jointly display the map and the vehicle's driving status on the vehicle's large screen during memory parking. However, if the application of memory parking is expanded to beyond-line-of-sight vehicle control, that is, by connecting the vehicle, mobile devices, cloud servers, and other units via Ethernet to establish a link, it would allow users to use their mobile devices for beyond-line-of-sight vehicle control, enabling valet parking and summoning parking. The learned memory map has mapping attributes, and unlicensed service providers are prohibited from uploading, illegally displaying, downloading, and using mapping maps. Generally, it only supports local use and cannot achieve the same map rendering effect on the mobile device as on the vehicle's local mode. Therefore, how to securely transfer and use mapping-like maps between platforms is a pressing issue that needs to be addressed.
[0003] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention
[0004] The main objective of this invention is to provide a map management method, apparatus, device, and storage medium, aiming to solve the technical problem of how to securely transfer and use maps with surveying and mapping characteristics between platforms.
[0005] To achieve the above objectives, the present invention provides a map management method, the method comprising the following steps: Upon receiving a remote control request from the target vehicle, the remote control request is sent to the mobile terminal; Upon receiving the remote control consent response from the mobile terminal, the target key is sent to the mobile terminal; Upon receiving a request verification information from the map service provider cloud server, the request verification information is verified according to the account binding relationship to obtain a verification result. The request verification information is generated by the map service provider cloud server based on the target key sent by the mobile terminal. When the verification result is successful, a verification success message is sent to the map provider's cloud server, so that the map provider's cloud server can open the map download interface to the mobile terminal based on the verification success message.
[0006] Optionally, before verifying the requested transaction information based on the account binding relationship, the method further includes: Obtain the vehicle identification code of the target vehicle and the terminal identification information of the mobile terminal; The ownership relationship key is determined based on the terminal identification information and the key generation rules; A key binding relationship is constructed based on the property rights key and the terminal identification information; An identifier binding relationship is constructed based on the vehicle identification code and the terminal identification information; The account binding relationship is obtained based on the identifier binding relationship and the key binding relationship.
[0007] Optionally, before sending the target key to the mobile terminal, the method further includes: The target terminal identifier of the mobile terminal is determined based on the remote control consent response of the mobile terminal; Determine the key binding relationship based on the account binding relationship; The target key corresponding to the target terminal identifier is determined based on the key binding relationship.
[0008] Optionally, the step of verifying the request verification information based on the account binding relationship to obtain the verification result includes: The requesting terminal identifier and target key are determined based on the request verification information; Determine the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship; The request verification information is verified based on the key body, the request vehicle identifier, and the target key to obtain the verification result.
[0009] Optionally, the step of verifying the request verification information based on the key body, the requesting vehicle identifier, and the target key to obtain a verification result includes: The target vehicle identifier of the target vehicle is determined based on the remote control request; The target vehicle identifier is compared with the requested vehicle identifier to obtain a first comparison result; The target key is compared with the key body to obtain a second comparison result; The verification result is determined based on the first comparison result and the second comparison result.
[0010] Optionally, after sending verification pass information to the map provider's cloud server when the verification result is successful, so that the map provider's cloud server opens the map download interface to the mobile terminal based on the verification pass information, the method further includes: Obtain the target route requested by the target vehicle; The target requested route is sent to the mobile terminal so that the mobile terminal can download the route map corresponding to the target requested route according to the map download interface. The route map is obtained by the target vehicle by converting the format of the survey map, and the survey map is generated by the target vehicle based on the collected image information.
[0011] Optionally, after verifying the request verification information based on the account binding relationship and obtaining the verification result, the method further includes: When the verification result is that the verification fails, the verification exception parameters are determined based on the verification result; Generate a verification error message based on the verification error parameters; A verification error message is sent to the map provider's cloud server, so that the map provider's cloud server can close the map download interface of the mobile terminal based on the verification failure message.
[0012] Furthermore, to achieve the above objectives, the present invention also proposes a map management device, the map management device comprising: The sending module is used to send the remote control request to the mobile terminal when it receives the remote control request sent by the target vehicle; The sending module is further configured to send the target key to the mobile terminal when it receives the remote control consent response from the mobile terminal; The verification module is used to verify the request verification information according to the account binding relationship when it receives the request verification information sent by the map merchant cloud server, and obtain the verification result. The request verification information is generated by the map merchant cloud server based on the target key sent by the mobile terminal. The sending module is further configured to send verification pass information to the map provider cloud server when the verification result is verification pass, so that the map provider cloud server can open the map download interface to the mobile terminal according to the verification pass information.
[0013] In addition, to achieve the above objectives, the present invention also proposes a map management device, the map management device comprising: a memory, a processor, and a map management program stored in the memory and executable on the processor, the map management program being configured to implement the steps of the map management method as described above.
[0014] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing a map management program, which, when executed by a processor, implements the steps of the map management method described above.
[0015] This invention achieves security and compliance in the transfer of mapping maps across multiple platforms by sending a remote control request to a mobile terminal upon receiving a remote control consent response from the target vehicle; sending a target key to the mobile terminal upon receiving a remote control consent response from the mobile terminal; verifying the request verification information based on the account binding relationship upon receiving a request verification information from the map service provider's cloud server, whereby the request verification information is generated by the map service provider's cloud server based on the target key sent by the mobile terminal; and sending verification pass information to the map service provider's cloud server when the verification result is successful, thereby enabling the map service provider's cloud server to open the map download interface to the mobile terminal based on the verification pass information. Through this method, when the mobile terminal agrees to the remote control request issued by the target vehicle, the target key is sent to the mobile terminal, and the request verification information sent by the map service provider's cloud server is verified. Upon successful verification, the map service provider's cloud server opens the map download interface to the mobile terminal. This closed-loop verification of the key on the link ensures the security and compliance of mapping maps transferred between multiple platforms. Furthermore, the method has high adaptability and a short link, allowing for quick and convenient deployment on various platforms. Attached Figure Description
[0016] Figure 1 This is a schematic diagram of the structure of a map management device in the hardware operating environment involved in the embodiments of the present invention; Figure 2 This is a flowchart illustrating the first embodiment of the map management method of the present invention; Figure 3 This is a remote control request flow diagram according to an embodiment of the map management method of the present invention; Figure 4 This is a wake-up request flow diagram according to an embodiment of the map management method of the present invention; Figure 5 This is a flowchart illustrating the key sending process of an embodiment of the map management method of the present invention. Figure 6 This is a schematic diagram illustrating information entry in an embodiment of the map management method of the present invention; Figure 7 This is a schematic diagram of the verification process of an embodiment of the map management method of the present invention; Figure 8 This is a schematic diagram of the map writing process according to an embodiment of the map management method of the present invention; Figure 9 This is a flowchart illustrating the second embodiment of the map management method of the present invention; Figure 10 This is a structural block diagram of the first embodiment of the map management device of the present invention.
[0017] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0018] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.
[0019] Reference Figure 1 , Figure 1 This is a schematic diagram of the map management device structure in the hardware operating environment involved in the embodiments of the present invention.
[0020] like Figure 1 As shown, the map management device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.
[0021] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the map management device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0022] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a map management program.
[0023] exist Figure 1 In the map management device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the map management device of the present invention can be set in the map management device, and the map management device calls the map management program stored in the memory 1005 through the processor 1001 and executes the map management method provided in the embodiment of the present invention.
[0024] This invention provides a map management method, referring to... Figure 2 , Figure 2 This is a flowchart illustrating a first embodiment of a map management method according to the present invention.
[0025] In this embodiment, the map management method includes the following steps: Step S10: Upon receiving a remote control request from the target vehicle, send the remote control request to the mobile terminal.
[0026] It should be noted that the execution entity in this embodiment is the vehicle dealer cloud server in the map management system. The map management system includes the target vehicle, the mobile terminal, the map dealer cloud server, and the vehicle dealer cloud server. The target vehicle includes, but is not limited to, a map acquisition module, a terminal controller, a terminal router, and a gigabit vehicle Ethernet harness. The map acquisition module consists of a front-facing wide-angle camera and a surround-view camera module. The vehicle dealer cloud server includes, but is not limited to, a vehicle entry data module, a vehicle owner data module, and a property rights database module. The map dealer cloud server includes, but is not limited to, a map database, a map uplink entry management group, and a download authentication module. The mobile terminal includes, but is not limited to, a vehicle owner authentication module and a map dealer cloud SDK module.
[0027] Understandably, after the target vehicle generates a mapping map, it is uploaded to the map provider's cloud server. The map provider's cloud server stores the mapping map. When the mobile terminal requests the map from the map provider's cloud server, the map provider's cloud server verifies the request information on the vehicle provider's cloud server. If the verification is successful, the map provider's cloud server opens the map download interface to the mobile terminal.
[0028] In practice, when the target vehicle is in actual use, if it needs to request the user to remotely control it via a mobile terminal, such as requesting remote parking via the mobile terminal, it will send a remote control request to the car dealer cloud server. The car dealer cloud server will provide a relay channel for message forwarding. After receiving the remote control request sent by the target vehicle, the car dealer cloud server needs to keep the request in place until the mobile terminal receives the remote control request and responds.
[0029] It should be noted that remote control requests can be initiated by the target vehicle itself, and the information transmission path is as follows: Figure 3 As shown, a remote control request can also be initiated by the mobile terminal while the target vehicle is in sleep mode. The car dealer's cloud server sends a wake-up request to the target vehicle. Upon receiving the request, the target vehicle interacts with the system, agreeing to the remote control request and determining the target request route based on its current location. At this point, after receiving the target request route from the target vehicle, the car dealer's cloud server sends the corresponding target key to the mobile terminal and performs subsequent verification procedures. The information transmission path is as follows: Figure 4 As shown.
[0030] Step S20: Upon receiving the remote control consent response from the mobile terminal, send the target key to the mobile terminal.
[0031] It should be noted that after the mobile terminal receives the remote control request forwarded by the car dealer cloud server, it interacts with the client. If the mobile terminal agrees to the remote control request, it generates a remote control agreement response based on the agreement and the key request, and sends it to the car dealer cloud server. The mobile terminal calls the car dealer cloud server's key application interface. After receiving the remote control agreement response, the car dealer cloud server obtains the key corresponding to the mobile terminal using HTTP and returns a key object or key body to the mobile terminal. The key object or key body returned to the mobile terminal is the target key. In this embodiment, the car dealer cloud server provides a user key application interface for sending and receiving key applications and key feedback from mobile terminals. The information transmission path is as follows: Figure 5 As shown.
[0032] In a specific implementation, in order to send the correct key to the mobile terminal, before sending the target key to the mobile terminal, the method further includes: determining the target terminal identifier of the mobile terminal based on the remote control consent response of the mobile terminal; determining the key binding relationship based on the account binding relationship; and determining the target key corresponding to the target terminal identifier based on the key binding relationship.
[0033] In the specific implementation, the remote control consent response of the mobile terminal will include the vehicle owner registration ID of the mobile terminal. The vehicle owner registration ID of the mobile terminal is the target terminal identifier of the mobile terminal. The account binding relationship includes key binding relationship and identifier binding relationship. In the key binding relationship, a key body and a vehicle owner registration ID are associated. In the identifier binding relationship, a vehicle owner registration ID is associated with a vehicle VIN.
[0034] It should be noted that the key binding relationship list is determined based on the account binding relationship, the key body corresponding to the target terminal identifier is found based on the key binding relationship list, and the key body corresponding to the target terminal identifier is returned to the mobile terminal.
[0035] Step S30: Upon receiving the request verification information sent by the map service provider cloud server, the request verification information is verified according to the account binding relationship to obtain the verification result. The request verification information is generated by the map service provider cloud server based on the target key sent by the mobile terminal.
[0036] It should be noted that after obtaining the target key, the mobile terminal makes an Ethernet request using the POST method. Then, the mobile terminal generates a pre-prepared URL access request and attaches the target key to access the map service provider's cloud server. Upon receiving the target key from the mobile terminal, the map service provider's cloud server generates verification information based on the target key and sends this verification information to the vehicle service provider's cloud server for verification. The vehicle service provider's cloud server verifies the target key attached to the verification information based on the account binding relationship, thus obtaining a verification result. The verification result includes two types: verification successful and verification failed. The specific verification process is as follows: Figure 7 As shown.
[0037] Understandably, the car dealer cloud server needs to provide the map merchant cloud server with a verification interface to perform cloud-to-cloud request security authentication, while the map merchant cloud server provides a key authentication service interface.
[0038] In a specific implementation, to ensure accurate account binding relationships, before verifying the requested transaction information based on the account binding relationship, the method further includes: obtaining the vehicle identification code of the target vehicle and the terminal identification information of the mobile terminal; determining the ownership relationship key based on the terminal identification information and key generation rules; constructing a key binding relationship based on the ownership relationship key and the terminal identification information; constructing an identifier binding relationship based on the vehicle identification code and the terminal identification information; and obtaining the account binding relationship based on the identifier binding relationship and the key binding relationship.
[0039] It should be noted that the dealer cloud server provides a user information access interface, while the mobile terminal provides a user information input interface. Whenever a vehicle rolls off the production line, it passes through the production line's electrical inspection equipment, and the production line automatically inputs the Vehicle Identification Number (VIN) into the dealer cloud server. When the vehicle is sold to the owner, the owner's information is entered on the mobile terminal, and the mobile terminal uploads the information to the dealer cloud server. When the vehicle is delivered to the user, the owner's information is entered on the mobile terminal, and the mobile terminal stores the information in the dealer cloud server. The dealer cloud server binds the VIN to the owner's registration ID entered on the mobile terminal. The owner's registration ID is the terminal's identification information. This establishes the identification binding relationship between the owner's registration ID and the VIN. The specific input process is as follows: Figure 6 As shown.
[0040] Understandably, after receiving the car owner registration ID entered by the mobile terminal, the car dealer cloud server will generate a property rights key corresponding to the car owner registration ID based on the key generation rules, and bind the car owner registration ID with the property rights key to obtain the key binding relationship. Based on the key binding relationship and the identifier binding relationship, an account binding relationship database will be built.
[0041] Step S40: When the verification result is successful, send the verification success information to the map provider cloud server so that the map provider cloud server can open the map download interface to the mobile terminal based on the verification success information.
[0042] It should be noted that when the verification result is successful, the car dealer cloud server will send a verification success message to the map provider cloud server. The verification success message contains the target vehicle's VIN. Based on the verification success message, the map provider cloud server opens the map download interface to the mobile terminal, allowing the mobile terminal to download the memory map uploaded by the target vehicle through the map download interface.
[0043] It should be understood that the route information in the map provider's cloud server is calculated based on the vehicle's VIN. When performing remote control, such as memory parking, the use of the vehicle's VIN and the map provider's cloud server must be consistent, so that maps between different vehicle models are not reusable and the databases are independent.
[0044] Understandably, to ensure the accuracy of map downloads by mobile terminals, the process further includes, after sending verification pass information to the map provider's cloud server when the verification result is successful, so that the map provider's cloud server can open the map download interface to the mobile terminal based on the verification pass information, obtaining the target request route sent by the target vehicle; sending the target request route to the mobile terminal, so that the mobile terminal can download the route map corresponding to the target request route according to the map download interface, wherein the route map is obtained by the target vehicle through format conversion of the survey map, and the survey map is generated by the target vehicle based on the collected image information.
[0045] In practice, when a target vehicle sends a remote control request, it simultaneously sends the route requested for remote control. This requested route is the target route, which the target vehicle can determine based on its current location. The car dealer cloud server then sends the target route to the mobile terminal, which downloads the corresponding route map using a map download interface.
[0046] Understandably, the target vehicle's map acquisition module uses a front-view camera and a surround-view camera module, transmitting image information to the terminal controller via the GMSL protocol. The controller then generates a corresponding mapping map based on the acquired image information and creates a YAML or JSON file. The controller is internally configured with the URL of the map provider's cloud server, which is automatically accessed during map generation. This URL is accessed by the vehicle's wireless router. For each generated map mapping file, the local map file is uploaded to the map provider's cloud server. In this embodiment, the third-party map provider's cloud server provides the map database writing interface, the vehicle's interrupt router provides the Ethernet access path service, and the vehicle terminal provides its own Ethernet terminal IP. The specific map writing process is as follows: Figure 8 As shown.
[0047] This embodiment achieves security and compliance in the transfer of mapping maps between multiple platforms by sending the remote control request to the mobile terminal upon receiving a remote control consent response from the target vehicle; sending the target key to the mobile terminal upon receiving a remote control consent response from the mobile terminal; verifying the request verification information based on the account binding relationship upon receiving a request verification information from the map provider's cloud server, whereby the request verification information is generated by the map provider's cloud server based on the target key sent by the mobile terminal; and sending verification pass information to the map provider's cloud server when the verification result is successful, so that the map provider's cloud server can open the map download interface to the mobile terminal based on the verification pass information. Through this method, when the mobile terminal agrees to the remote control request issued by the target vehicle, the target key is sent to the mobile terminal, and the request verification information sent by the map provider's cloud server is verified. When the verification is successful, the map provider's cloud server opens the map download interface to the mobile terminal. This closed-loop verification of the key on the link ensures the security and compliance of mapping maps transferred between multiple platforms. Furthermore, the method has high adaptability and a short link, enabling rapid and convenient deployment on various platforms.
[0048] refer to Figure 9 , Figure 9 This is a flowchart illustrating a second embodiment of a map management method according to the present invention.
[0049] Based on the first embodiment described above, the map management method of this embodiment includes the following in step S30: Step S31: Determine the requesting terminal identifier and target key based on the request verification information.
[0050] It should be noted that the car dealer cloud server determines the car owner registration ID and target key that need to be verified based on the request verification information. The car owner registration ID that needs to be verified is the identifier of the requesting terminal.
[0051] Step S32: Determine the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship.
[0052] It should be noted that the car dealer cloud server determines the vehicle identification code corresponding to the requesting terminal identifier based on the identifier binding relationship in the account binding relationship, and determines the key body corresponding to the requesting terminal identifier based on the key binding relationship in the account binding relationship. The vehicle identification code corresponding to the requesting terminal identifier is the requesting vehicle identifier.
[0053] Step S33: Verify the request verification information based on the key body, the request vehicle identifier, and the target key to obtain the verification result.
[0054] It should be noted that the car dealer cloud server verifies the request verification information based on the key body, the vehicle request identifier, and the target key. To ensure the accuracy of the verification process, the verification of the request verification information based on the key body, the request vehicle identifier, and the target key to obtain the verification result includes: determining the target vehicle identifier of the target vehicle based on the remote control request; comparing the target vehicle identifier with the request vehicle identifier to obtain a first comparison result; comparing the target key with the key body to obtain a second comparison result; and determining the verification result based on the first comparison result and the second comparison result.
[0055] Understandably, the car dealer cloud server determines the vehicle identification code corresponding to the target vehicle based on the remote control request sent by the target vehicle. The vehicle identification code corresponding to the target vehicle is the target vehicle identifier. The target vehicle identifier is compared with the requesting vehicle identifier to obtain the first comparison result. If they match, it means that there is a binding between the vehicle owner registration ID of the mobile terminal that initiated the access request to the map dealer cloud server and the vehicle VIN of the target vehicle. If they do not match, it means that there is no binding between the vehicle owner registration ID of the mobile terminal that initiated the access request to the map dealer cloud server and the vehicle VIN of the target vehicle.
[0056] In the specific implementation, the target key is compared with the key body corresponding to the requesting terminal identifier to obtain a second comparison result. If the two match, it means that the target key of the mobile terminal that initiated the access request to the map provider cloud server is legitimate.
[0057] It should be noted that if both the first and second comparison results are consistent, the verification result is considered successful; otherwise, the verification result is considered unsuccessful.
[0058] Understandably, to ensure the security of map downloads, the process of verifying the request verification information based on the account binding relationship and obtaining the verification result further includes: when the verification result is a verification failure, determining verification exception parameters based on the verification result; generating verification exception prompt information based on the verification exception parameters; and sending the verification exception prompt information to the map provider's cloud server, so that the map provider's cloud server can close the map download interface for the mobile terminal based on the verification failure information.
[0059] In the specific implementation, when the verification result is that the verification fails, it is determined that there is inconsistent information based on the verification result. The inconsistent information is the verification exception parameter. Based on the verification exception parameter, a verification exception prompt message is generated and sent to the map provider cloud server. According to the verification exception prompt message, the map provider cloud server temporarily does not open the map download interface to mobile terminals.
[0060] This embodiment determines the requesting terminal identifier and target key based on the request verification information; determines the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship; and verifies the request verification information based on the key body, the requesting vehicle identifier, and the target key to obtain the verification result. Through this method, verification is performed based on the key body, the requesting vehicle identifier, and the target key, ensuring the security of the verification through dual verification.
[0061] Furthermore, this embodiment of the invention also proposes a storage medium storing a map management program, which, when executed by a processor, implements the steps of the map management method described above.
[0062] Reference Figure 10 , Figure 10 This is a structural block diagram of the first embodiment of the map management device of the present invention.
[0063] like Figure 10 As shown, the map management device proposed in this embodiment of the invention includes: The sending module 10 is used to send the remote control request to the mobile terminal when it receives the remote control request sent by the target vehicle.
[0064] The sending module 10 is further configured to send the target key to the mobile terminal when it receives the remote control consent response from the mobile terminal.
[0065] The verification module 20 is used to verify the request verification information according to the account binding relationship when it receives the request verification information sent by the map service provider cloud server, and obtain the verification result. The request verification information is generated by the map service provider cloud server based on the target key sent by the mobile terminal.
[0066] The sending module 10 is further configured to send verification pass information to the map provider cloud server when the verification result is verification pass, so that the map provider cloud server opens the map download interface to the mobile terminal according to the verification pass information.
[0067] This embodiment achieves security and compliance in the transfer of mapping maps between multiple platforms by sending the remote control request to the mobile terminal upon receiving a remote control consent response from the target vehicle; sending the target key to the mobile terminal upon receiving a remote control consent response from the mobile terminal; verifying the request verification information based on the account binding relationship upon receiving a request verification information from the map provider's cloud server, whereby the request verification information is generated by the map provider's cloud server based on the target key sent by the mobile terminal; and sending verification pass information to the map provider's cloud server when the verification result is successful, so that the map provider's cloud server can open the map download interface to the mobile terminal based on the verification pass information. Through this method, when the mobile terminal agrees to the remote control request issued by the target vehicle, the target key is sent to the mobile terminal, and the request verification information sent by the map provider's cloud server is verified. When the verification is successful, the map provider's cloud server opens the map download interface to the mobile terminal. This closed-loop verification of the key on the link ensures the security and compliance of mapping maps transferred between multiple platforms. Furthermore, the method has high adaptability and a short link, enabling rapid and convenient deployment on various platforms.
[0068] In one embodiment, the verification module 20 is further configured to obtain the vehicle identification code of the target vehicle and the terminal identification information of the mobile terminal; The ownership relationship key is determined based on the terminal identification information and the key generation rules; A key binding relationship is constructed based on the property rights key and the terminal identification information; An identifier binding relationship is constructed based on the vehicle identification code and the terminal identification information; The account binding relationship is obtained based on the identifier binding relationship and the key binding relationship.
[0069] In one embodiment, the sending module 10 is further configured to determine the target terminal identifier of the mobile terminal based on the remote control consent response of the mobile terminal; Determine the key binding relationship based on the account binding relationship; The target key corresponding to the target terminal identifier is determined based on the key binding relationship.
[0070] In one embodiment, the verification module 20 is further configured to determine the requesting terminal identifier and the target key based on the request verification information; Determine the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship; The request verification information is verified based on the key body, the request vehicle identifier, and the target key to obtain the verification result.
[0071] In one embodiment, the verification module 20 is further configured to determine the target vehicle identifier of the target vehicle based on the remote control request; The target vehicle identifier is compared with the requested vehicle identifier to obtain a first comparison result; The target key is compared with the key body to obtain a second comparison result; The verification result is determined based on the first comparison result and the second comparison result.
[0072] In one embodiment, the verification module 20 is further configured to obtain the target request route sent by the target vehicle; The target requested route is sent to the mobile terminal so that the mobile terminal can download the route map corresponding to the target requested route according to the map download interface. The route map is obtained by the target vehicle by converting the format of the survey map, and the survey map is generated by the target vehicle based on the collected image information.
[0073] In one embodiment, the verification module 20 is further configured to determine a verification anomaly parameter based on the verification result when the verification result is a verification failure. Generate a verification error message based on the verification error parameters; A verification error message is sent to the map provider's cloud server, so that the map provider's cloud server can close the map download interface of the mobile terminal based on the verification failure message.
[0074] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.
[0075] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.
[0076] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.
[0077] Furthermore, it should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system 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, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0078] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0079] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.
[0080] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.
Claims
1. A map management method characterized by comprising: The map management method is applied to a car dealer cloud server, and the method includes: Upon receiving a remote control request from the target vehicle, the remote control request is sent to the mobile terminal, wherein the remote control request includes a remote parking request; Upon receiving the remote control consent response from the mobile terminal, a target key is sent to the mobile terminal, causing the mobile terminal to generate an access request with the target key and send the access request to the map service cloud server. Upon receiving the request verification information sent by the map merchant cloud server, the request verification information is verified according to the account binding relationship to obtain the verification result. The request verification information is generated by the map merchant cloud server based on the target key sent by the mobile terminal. When the verification result is successful, a verification success message is sent to the map provider cloud server, so that the map provider cloud server can open the map download interface to the mobile terminal based on the verification success message. Before verifying the request verification information based on the account binding relationship, the method further includes: Obtain the vehicle identification code of the target vehicle and the terminal identification information of the mobile terminal; The ownership relationship key is determined based on the terminal identification information and the key generation rules; A key binding relationship is constructed based on the property rights key and the terminal identification information; An identifier binding relationship is constructed based on the vehicle identification code and the terminal identification information; The account binding relationship is obtained based on the identifier binding relationship and the key binding relationship; The step of verifying the request verification information based on the account binding relationship to obtain the verification result includes: The requesting terminal identifier and target key are determined based on the request verification information; Determine the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship; The request verification information is verified based on the key body, the request vehicle identifier, and the target key to obtain the verification result.
2. The map management method according to claim 1, wherein Before sending the target key to the mobile terminal, the method further includes: The target terminal identifier of the mobile terminal is determined based on the remote control consent response of the mobile terminal; Determine the key binding relationship based on the account binding relationship; The target key corresponding to the target terminal identifier is determined based on the key binding relationship.
3. The map management method as described in claim 1, characterized in that, The step of verifying the request verification information based on the key body, the requesting vehicle identifier, and the target key to obtain the verification result includes: The target vehicle identifier of the target vehicle is determined based on the remote control request; The target vehicle identifier is compared with the requested vehicle identifier to obtain a first comparison result; The target key is compared with the key body to obtain a second comparison result; The verification result is determined based on the first comparison result and the second comparison result.
4. The map management method as described in any one of claims 1 to 3, characterized in that, When the verification result is successful, sending verification success information to the map provider's cloud server, so that the map provider's cloud server opens the map download interface to the mobile terminal based on the verification success information, further includes: Obtain the target route requested by the target vehicle; The target requested route is sent to the mobile terminal so that the mobile terminal can download the route map corresponding to the target requested route according to the map download interface. The route map is obtained by the target vehicle by converting the format of the survey map, and the survey map is generated by the target vehicle based on the collected image information.
5. The map management method as described in any one of claims 1 to 3, characterized in that, After verifying the request verification information based on the account binding relationship and obtaining the verification result, the process further includes: When the verification result is that the verification fails, the verification exception parameters are determined based on the verification result; Generate a verification error message based on the verification error parameters; A verification failure message is sent to the map provider's cloud server, so that the map provider's cloud server can close the map download interface of the mobile terminal based on the verification failure message.
6. A map management device, characterized in that, The map management device includes: The sending module is used to send the remote control request to the mobile terminal when it receives the remote control request sent by the target vehicle, wherein the remote control request includes a remote parking request; The sending module is further configured to send a target key to the mobile terminal when it receives a remote control consent response from the mobile terminal, so that the mobile terminal generates an access request with the target key and sends the access request to the map service cloud server. The verification module is used to verify the request verification information according to the account binding relationship when it receives the request verification information sent by the map merchant cloud server, and obtain the verification result. The request verification information is generated by the map merchant cloud server based on the target key sent by the mobile terminal. The sending module is also used to send verification pass information to the map provider cloud server when the verification result is verification pass, so that the map provider cloud server opens the map download interface to the mobile terminal according to the verification pass information; The binding module is used to obtain the vehicle identification code of the target vehicle and the terminal identification information of the mobile terminal; determine the ownership relationship key according to the terminal identification information and the key generation rule; construct a key binding relationship according to the ownership relationship key and the terminal identification information; construct an identifier binding relationship according to the vehicle identification code and the terminal identification information; and obtain an account binding relationship according to the identifier binding relationship and the key binding relationship. The verification module is further configured to determine the requesting terminal identifier and the target key based on the request verification information; determine the key body corresponding to the requesting terminal identifier and the requesting vehicle identifier corresponding to the requesting terminal based on the account binding relationship; and verify the request verification information based on the key body, the requesting vehicle identifier, and the target key to obtain a verification result.
7. A map management device, characterized in that, The device includes: a memory, a processor, and a map management program stored in the memory and executable on the processor, the map management program being configured to implement the map management method as described in any one of claims 1 to 5.
8. A storage medium, characterized in that, The storage medium stores a map management program, which, when executed by a processor, implements the map management method as described in any one of claims 1 to 5.
Citation Information
Patent Citations
Augmented reality map updating method, device and system, storage and equipment
CN111177167A
KR20220006379A
