Method, system, electronic device and vehicle for entering engineering mode verification

Abstract

The application relates to a verification method and system for entering an engineering mode, an electronic device and a vehicle. The method comprises the following steps: acquiring a system version of a vehicle machine and a communication state between the vehicle machine and a cloud platform; determining a verification mode according to the system version of the vehicle machine and the communication state between the vehicle machine and the cloud platform; verifying a password input by a user according to the verification mode; and entering the engineering mode when the password verification is passed. According to the application, the corresponding verification mode is determined according to the system version of the vehicle machine and the communication state between the vehicle machine and the cloud platform, and verification is performed, so that the engineering mode can be entered relatively safely and conveniently.

Description

Technical Field

[0001] This application relates to the field of automotive technology, and more specifically to a verification method, system, electronic device, and vehicle for entering engineering mode. Background Technology

[0002] Engineering mode is used for centralized debugging of various parameters of equipment application systems. Therefore, access to the equipment's engineering mode needs to be verified to prevent users from easily debugging the system, creating security risks, and causing after-sales disputes. Currently, the verification method for accessing engineering mode is generally that the manufacturer sets a fixed and complex password, which both R&D personnel and market users can use to open the equipment's engineering mode. This method cannot guarantee the security of accessing engineering mode and is prone to mass leakage of the password. Once market users know the password, they can freely open the engineering mode of other devices, while during the R&D phase, R&D personnel must also enter the complex password every time, causing great inconvenience.

[0003] Therefore, how to safely and conveniently enter the engineering mode remains an urgent problem to be solved. Summary of the Invention

[0004] One objective of this application is to provide a verification method for entering engineering mode, so as to solve or partially solve the problem in the prior art that it is not possible to enter engineering mode safely and conveniently; another objective is to provide a verification system for entering engineering mode; a third objective is to provide an electronic device; and a fourth objective is to provide a vehicle.

[0005] To achieve the above objectives, the technical solution adopted in this application is as follows:

[0006] A verification method for entering engineering mode, applied to an in-vehicle infotainment system, the method comprising: obtaining the system version of the in-vehicle infotainment system and obtaining the communication status between the in-vehicle infotainment system and a cloud platform; determining a verification method based on the system version of the in-vehicle infotainment system and the communication status between the in-vehicle infotainment system and the cloud platform; verifying a password entered by the user according to the verification method; and entering engineering mode if the password verification is successful.

[0007] Optionally, the password includes an identifier and a verification code; before obtaining the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform; the above method further includes: determining whether the identifier included in the password is consistent with a preset identifier, the preset identifier being used to characterize the intention to enter the vehicle infotainment system's engineering mode; if the identifier included in the password is consistent with the preset identifier, obtaining the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform.

[0008] Optionally, the verification code is a cloud verification code generated or updated by the cloud platform according to the project to which the vehicle-mounted system belongs, or a local verification code generated by encrypting the vehicle identification code of the vehicle-mounted system according to a preset encryption algorithm; the verification method is either cloud verification or local verification; according to the verification method, the password entered by the user is verified, including: if the verification method is determined to be cloud verification, the cloud platform determines whether the verification code included in the password is consistent with the cloud verification code; if the verification code included in the password is consistent with the cloud verification code, the password verification is successful; if the verification method is determined to be local verification, the verification code included in the password is determined whether it is consistent with the local verification code; if the verification code included in the password is consistent with the local verification code, the password verification is successful.

[0009] Optionally, determining the verification method based on the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform includes: determining the verification method as cloud verification when the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is normal; and determining the verification method as local verification when the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is abnormal.

[0010] Optionally, if the identifier included in the password is consistent with the preset identifier, and the system version of the vehicle system is in the research and development stage, the system enters the engineering mode.

[0011] Optionally, if the system version of the vehicle infotainment system cannot be obtained, the stage to which the system version of the vehicle infotainment system belongs shall be regarded as the after-sales stage.

[0012] Optionally, the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform are obtained, including: obtaining the system version of the vehicle infotainment system; if the system version of the vehicle infotainment system is in the after-sales stage, sending verification information to the cloud platform; and determining the communication status between the vehicle infotainment system and the cloud platform based on whether the verification message was successfully sent.

[0013] Optionally, the communication status between the vehicle-mounted system and the cloud platform is determined based on whether the verification message is successfully sent, including: if the verification message is successfully sent, the communication status between the vehicle-mounted system and the cloud platform is determined to be normal; if the verification message fails to be sent, the communication status between the vehicle-mounted system and the cloud platform is determined to be abnormal.

[0014] Optionally, the vehicle infotainment system includes a Bluetooth phone, and the above method further includes: receiving the password entered by the user through the Bluetooth phone dialing interface.

[0015] A verification method for entering engineering mode, applied to a cloud platform, the method comprising: receiving verification information sent by a vehicle-mounted system, the verification information including a password entered by a user, the password including a verification code; determining whether the verification code included in the password is consistent with a cloud verification code; if the verification code included in the password is consistent with the cloud verification code, sending confirmation information to the vehicle-mounted system; so that the vehicle-mounted system enters engineering mode based on the confirmation information.

[0016] Optionally, the above method further includes: obtaining the vehicle identification code of the vehicle system; encrypting the vehicle identification code of the vehicle system according to a preset encryption algorithm to generate a local verification code corresponding to the vehicle system; the local verification code is used for local verification by the vehicle system, and the preset encryption algorithm is an encryption algorithm shared by the vehicle system and the cloud platform.

[0017] A verification system for entering engineering mode, applied to an in-vehicle infotainment system, the system comprising: an acquisition module for acquiring the system version of the in-vehicle infotainment system and the communication status between the in-vehicle infotainment system and a cloud platform; a determination module for determining a verification method based on the system version of the in-vehicle infotainment system and the communication status between the in-vehicle infotainment system and the cloud platform; a verification module for verifying a password entered by a user according to the verification method; and an entry module for entering engineering mode if the password verification is successful.

[0018] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described verification method for entering engineering mode.

[0019] A vehicle equipped with the aforementioned verification system for entering engineering mode.

[0020] The beneficial effects of this application are:

[0021] This application obtains the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform; determines the verification method based on the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform; verifies the password entered by the user according to the verification method; and enters the engineering mode if the password verification is successful. This enables the targeted selection of the verification method for entering the engineering mode in different application scenarios, and achieves convenient and secure entry into the engineering mode. Attached Figure Description

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

[0023] Figure 1 This is a flowchart of a verification method for entering engineering mode according to one embodiment of this application;

[0024] Figure 2 This is a logical diagram illustrating the entry into engineering mode as described in one embodiment of this application;

[0025] Figure 3 This is a schematic diagram of the framework of the verification system for entering engineering mode as described in one embodiment of this application. Detailed Implementation

[0026] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0027] Reference Figure 1 , Figure 1 This is a flowchart of a verification method for entering engineering mode in one embodiment of this application. In this embodiment, the verification method for entering engineering mode is applied to an in-vehicle infotainment system, which includes the vehicle's central control system and may be equipped with in-vehicle infotainment products. Optionally, the in-vehicle infotainment system can be replaced with a smart device with an engineering mode, such as a mobile terminal.

[0028] In this embodiment, the verification method for entering engineering mode may include the following steps:

[0029] Step S101: Obtain the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform.

[0030] Specifically, the system version of the software system installed in the vehicle can be obtained through the vehicle's control center, and the communication status between the vehicle and the cloud platform can be determined by whether the information is successfully sent.

[0031] Step S102: Determine the verification method based on the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform.

[0032] In related technologies, verification for entering engineering mode typically involves setting a fixed password, and the device locally verifies whether the password entered by the user matches this fixed password. In this embodiment, different verification methods are determined based on the vehicle's system version and the communication status between the vehicle and the cloud platform. This allows for flexible verification of entering engineering mode in multiple scenarios, which helps ensure both the security and convenience of entering engineering mode.

[0033] Step S103: Verify the password entered by the user according to the verification method.

[0034] Specifically, after determining the verification method for different situations, the password entered by the user can be verified according to that method. The verification process involves comparing the password entered by the user with the password corresponding to the determined verification method to confirm whether the password entered by the user has been successfully verified.

[0035] Step S104: If the password verification is successful, enter engineering mode.

[0036] Specifically, once the user's password verification is successful, the vehicle's infotainment system enters engineering mode, allowing the user to configure relevant parameters within the engineering mode.

[0037] In this embodiment, by obtaining the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform, the method for verifying the user's input password is determined based on the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform, and the verification is performed. If the password verification is successful, the system enters the engineering mode. Different verification methods can be flexibly determined for different application scenarios, realizing safe and convenient entry into the engineering mode in multiple scenarios.

[0038] In one feasible implementation, specifically, the password entered by the user includes an identifier and a verification code. Before step S101, the above method further includes the following steps:

[0039] Determine whether the identifier included in the password is consistent with a preset identifier, the preset identifier being used to characterize the intent to enter the vehicle system engineering mode; if the identifier included in the password is consistent with the preset identifier, obtain the system version of the vehicle system and obtain the communication status between the vehicle system and the cloud platform.

[0040] In this embodiment, when designing the password to enter engineering mode, the password includes a verification code and a preset identifier. Specifically, the verification code can be an 8-digit number located in the middle of the password, while the preset identifier is located before and after the verification code. After receiving the password entered by the user, the password is parsed to determine whether the identifier included in the password matches the preset identifier.

[0041] If the password does not contain an identifier or the identifier it contains is inconsistent with the preset identifier, then it is determined that this is not an operation that requires entering engineering mode, there is no intention to enter engineering mode, and no further steps need to be executed. If the identifier contained in the password is consistent with the preset identifier, it indicates that there is an intention to enter engineering mode, it is determined that engineering mode needs to be entered, and then step S101 is executed.

[0042] In this embodiment, a preset identifier can be used to determine whether it is necessary to enter the engineering mode, thereby determining whether to execute subsequent processes. This filters out some unnecessary verification processes, reduces the workload of verification, and alleviates the load on the vehicle's infotainment system.

[0043] In one feasible implementation, the verification code is a cloud verification code generated or updated by the cloud platform according to the project to which the vehicle-mounted system belongs, or a local verification code generated by encrypting the vehicle identification number of the vehicle-mounted system according to a preset encryption algorithm; the verification method is either cloud verification or local verification; specifically, step S103 verifies the password entered by the user according to the verification method, and may further include the following steps:

[0044] If the verification method is determined to be cloud verification, the verification code included in the password is checked through the cloud platform to see if it matches the cloud verification code; if the verification code included in the password matches the cloud verification code, the password verification is successful. If the verification method is determined to be local verification, the verification code included in the password is checked to see if it matches the local verification code; if the verification code included in the password matches the local verification code, the password verification is successful.

[0045] In this embodiment, when setting a password to enter the vehicle infotainment system's engineering mode, the verification code included in the password can be generated in several ways. Specifically, a cloud verification code can be generated by the cloud platform based on the project to which the vehicle infotainment system belongs. Alternatively, the cloud platform or the vehicle infotainment system can encrypt the vehicle identification number (VIN) of the vehicle infotainment system using a shared preset encryption algorithm to generate a local verification code corresponding to that vehicle infotainment system. Correspondingly, the verification methods also include cloud verification or local verification.

[0046] Specifically, if the verification method is determined to be cloud verification based on the vehicle's system version and the communication status between the vehicle and the cloud platform, then the user's entered password is verified through the cloud platform to determine if the verification code included in the password matches the corresponding cloud verification code on the vehicle. If the verification code in the password matches the corresponding cloud verification code on the vehicle, the password verification is successful, and the vehicle can enter the vehicle's engineering mode. If the verification method is determined to be local verification based on the vehicle's system version and the communication status between the vehicle and the cloud platform, then the vehicle performs local verification on the user's entered password, determining if the verification code included in the password matches the corresponding local verification code on the vehicle. If the verification code included in the password matches the corresponding local verification code on the vehicle, the password verification is successful, and the vehicle can enter the vehicle's engineering mode.

[0047] In this embodiment, the verification code in the password for entering engineering mode is designed with different verification methods, enabling both cloud and local verification of the password. This adapts to the verification needs of entering engineering mode in multiple scenarios, improving the security and convenience of verification, and avoiding the problem of mass leakage of passwords for entering vehicle-mounted engineering mode.

[0048] In one feasible implementation, step S102 involves determining the verification method based on the vehicle's system version and the communication status between the vehicle and the cloud platform. Specifically, this can be performed as follows:

[0049] If the vehicle infotainment system version is in the after-sales stage and the communication between the vehicle infotainment system and the cloud platform is normal, the verification method is determined to be cloud verification; if the vehicle infotainment system version is in the after-sales stage and the communication between the vehicle infotainment system and the cloud platform is abnormal, the verification method is determined to be local verification.

[0050] In this implementation, the system version of the in-vehicle infotainment system is classified into both the R&D and after-sales stages. Specifically, the verification method is determined based on the system version and the communication status between the in-vehicle infotainment system and the cloud platform. First, we can analyze how to determine the verification method when the system version is in the after-sales stage. If the system version is in the after-sales stage and the communication status between the in-vehicle infotainment system and the cloud platform is normal, then cloud verification of the password is performed. If the system version is in the after-sales stage and the communication status between the in-vehicle infotainment system and the cloud platform is abnormal, then local verification of the password is performed.

[0051] By determining different verification methods based on the vehicle's system version and the communication status between the vehicle and the cloud platform, verification can be performed even if the vehicle's network conditions are poor. This flexibly adapts to the verification needs of different scenarios, ensuring the security and convenience of entering engineering mode.

[0052] In one feasible implementation, if the identifier included in the password is consistent with the preset identifier and the system version of the vehicle system is in the research and development stage, the system enters the engineering mode.

[0053] In this embodiment, if the vehicle infotainment system version is in the development stage, the user who needs to open the vehicle infotainment system's engineering mode is an R&D personnel within the automaker. In this application scenario, the risk of password leakage is relatively low when R&D personnel open the vehicle infotainment system's engineering mode to debug various parameters. Performing complex verifications on the R&D personnel's input would waste unnecessary time. Therefore, when the vehicle infotainment system version is in the development stage, referring to the above embodiment, if the entered password includes a preset identifier, it can directly enter the engineering mode. Further verification of whether the password contains a verification code or whether the verification code is correct is not required. This provides convenience for entering the engineering mode during the development stage.

[0054] Optionally, the preset identifier set in the password for entering the vehicle's engineering mode can be fixed, or it can be updated as needed.

[0055] In one optional implementation, step S101 involves obtaining the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform. Specifically, this can be performed as follows:

[0056] Obtain the system version of the vehicle infotainment system; if the system version of the vehicle infotainment system is in the after-sales stage, send verification information to the cloud platform; determine the communication status between the vehicle infotainment system and the cloud platform based on whether the verification message was sent successfully.

[0057] Furthermore, based on whether the verification message was successfully sent, the communication status between the vehicle-mounted system and the cloud platform is determined, including:

[0058] If the verification message is sent successfully, the communication status between the vehicle system and the cloud platform is determined to be normal; if the verification message fails to be sent, the communication status between the vehicle system and the cloud platform is determined to be abnormal.

[0059] In this embodiment, the system version of the vehicle's infotainment system is first obtained. Specifically, the system version identifier is used to determine the stage to which the system version belongs. If the system version belongs to the after-sales stage, verification information is sent to the cloud platform. The communication status between the vehicle's infotainment system and the cloud platform is determined based on whether the verification message is successfully sent, thus further obtaining the communication status between the vehicle's infotainment system and the cloud platform.

[0060] It is understandable that if the verification message is sent successfully, it is determined that the communication status between the vehicle system and the cloud platform is normal; if the verification message fails to be sent, it is determined that the communication status between the vehicle system and the cloud platform is abnormal. In this way, the communication status between the vehicle system and the cloud platform can be obtained.

[0061] In this embodiment, the communication status between the vehicle system and the cloud platform is determined based on whether the verification message is successfully sent. If the message is successfully sent, the password entered by the user can be directly verified through the cloud platform. There is no need to test the communication status between the cloud platform and the vehicle system through other means before applying for verification from the cloud platform, which simplifies the steps of the verification method for entering engineering mode.

[0062] In one feasible implementation, the vehicle infotainment system includes a Bluetooth phone that receives a password entered by the user through the vehicle infotainment system's Bluetooth phone dialing interface.

[0063] In this embodiment, the vehicle system includes a Bluetooth phone. Users can enter a password through the vehicle system's Bluetooth phone dialing interface. After confirmation, the vehicle system receives the password entered by the user and then recognizes the password.

[0064] In this embodiment, there is no need to configure a new entry page for the vehicle's engineering mode to require the user to enter a password, thus reducing the optimization cost of the verification method for entering the engineering mode.

[0065] Optionally, a new function can be added to the vehicle's Bluetooth phone function, enabling the Bluetooth phone to recognize the password entered by the user. For example, the vehicle's Bluetooth phone can be used to recognize the password entered by the user and determine whether it contains a preset identifier that indicates entry into engineering mode. If the password includes the preset identifier, the system version of the vehicle can be obtained. In addition, a local verification code generated by encrypting the vehicle identifier of the device according to a preset encryption algorithm can be stored. The password entered by the user can be verified based on the local verification code. Specifically, the Bluetooth phone function module of the vehicle can execute the verification method for entering engineering mode described in the above embodiment.

[0066] This application also covers scenarios where the system version of the vehicle infotainment system does not have a version identifier, or it is impossible to determine the stage to which the system version of the vehicle infotainment system belongs.

[0067] In one feasible implementation, the above method further includes: if the system version of the vehicle system cannot be obtained, the stage to which the system version of the vehicle system belongs is regarded as the after-sales stage.

[0068] In this implementation, to ensure the security of entering the engineering mode, vehicle systems whose system versions cannot be recognized are considered to be in the after-sales stage, so that the corresponding verification method can be selected later.

[0069] Optionally, if the communication between the vehicle's infotainment system and the cloud platform is abnormal, or if the vehicle's infotainment system cannot connect to the internet, it will enter engineering mode and require local verification. If the vehicle identification number (VIN) cannot be read at this time, the default VIN will be a preset initial identification number. For example, if the vehicle's VIN cannot be recognized, the default VIN is 000000000000000000. A local verification code will be generated based on this preset initial identification number for verification.

[0070] Reference Figure 2 , Figure 2 This is a logical diagram illustrating the entry into engineering mode in one embodiment of this application. For example... Figure 2 As shown, the user is the operator, and the administrator can be the R&D project manager or the after-sales project manager.

[0071] First, the operator contacts the administrator to obtain the password to enter the engineering mode.

[0072] Specifically, administrators can use the cloud platform to query the vehicle's cloud verification code, or enter the vehicle identification number (VIN) into the cloud platform to generate a local verification code for the vehicle. When operators contact the administrator to retrieve the password, they can first inform the administrator of the vehicle's network status. The administrator can then anticipate the verification method corresponding to the current network status of the vehicle and choose which password to provide to the operator.

[0073] Assuming the operator is a maintenance worker, after the administrator verifies the operator's identity, if the operator's vehicle network is abnormal and unable to connect to the cloud platform, the administrator will provide the operator with a password including a local verification code. Conversely, if the operator's vehicle network is normal and can connect to the cloud platform, the administrator will provide the operator with a password including a cloud verification code corresponding to the vehicle model and relevant project. This allows the administrator to provide the password based on the vehicle's current network status, enabling the user to access engineering mode.

[0074] Next, the operator enters the password.

[0075] When a password is preset, it includes an identifier and a verification code. Therefore, the password entered by the operator should also include an identifier and a verification code. Specifically, the verification code can be set to eight digits and located in the middle of the password, while symmetrical identifiers are added to the beginning and end of the password. For example, *#12345678#* is the password to enter the vehicle's engineering mode, 12345678 is the verification code, and *#……#* is the identifier. In this embodiment, the preset identifier representing the intention to enter the engineering mode is also set to *#……#*.

[0076] After the operator enters the password, the vehicle's system receives the password and can first determine whether the password entered by the operator contains a preset identifier.

[0077] Specifically, if the password entered by the operator has no identifier or the identifier is not a preset identifier, it means that the operator does not intend to open the vehicle's engineering mode, and all the following steps will not be executed, and the verification process will end directly. If the password entered by the operator has an identifier, and the identifier is a preset identifier, it indicates that there is a need to open the engineering mode, and the system version of the vehicle will be further obtained for judgment.

[0078] The vehicle's infotainment system identifies the system version as user or userdebug.

[0079] Specifically, the system version of a vehicle's infotainment system is generally determined by the project to which the infotainment system model belongs. Projects have different phases, and the system version varies depending on the phase. The phase to which the system version belongs can be determined by the version identifier. The version identifier is either "user" or "userdebug." When the system version identifier is "userdebug," the project is generally in the development phase, meaning the system version belongs to the development phase. When the system version identifier is "user," the project is generally in the after-sales phase after mass production, meaning the system version belongs to the after-sales phase.

[0080] If the system version of the vehicle's infotainment system is identified as "userdebug," indicating that the system is in the development stage, you can directly enter the engineering mode.

[0081] Specifically, since this in-vehicle infotainment system is in the development stage, the users are the R&D personnel, who are the car manufacturer's internal technical staff. Therefore, at this stage, the R&D personnel can directly enter the engineering mode of the system using a preset identifier. The password entered by the R&D personnel can contain only the preset identifier, or the preset identifier and any verification code. This facilitates internal R&D personnel accessing the in-vehicle infotainment system's engineering mode during the development phase.

[0082] If the system version of the vehicle's infotainment system is identified as "user" and the system version is in the after-sales stage, an application for verification should be submitted to the cloud platform.

[0083] Specifically, the vehicle's infotainment system requests verification from the cloud platform and sends a verification message. This message may include the infotainment system's model number and the password entered by the operator. If the cloud platform successfully receives the verification information, it can find the cloud verification code corresponding to the system's model and match it with the verification code in the operator's password to determine if they match.

[0084] The vehicle's infotainment system sends a verification message to the cloud platform to request verification. The following scenarios may occur:

[0085] First, the communication between the vehicle's infotainment system and the cloud platform is abnormal; the vehicle's system cannot connect to the cloud platform, and the cloud platform has not successfully received the verification message sent by the vehicle's system. In this case, the vehicle's system will perform local verification of the password entered by the operator. If the local verification is successful, it will enter engineering mode; if the local verification fails, it will display an incorrect password message.

[0086] Secondly, the cloud platform verifies the password entered by the operator, but the password verification fails. Upon receiving a message from the cloud platform indicating that the verification failed, an error message is displayed indicating an incorrect password.

[0087] Third, the cloud platform verifies the password entered by the operator. If the password verification is successful, the system receives a verification confirmation message from the cloud platform and enters engineering mode.

[0088] If the password entered by the operator fails to verify, it may be due to a change in the vehicle network status, resulting in the failure to obtain the correct password. Therefore, the operator can choose to obtain the password again from the administrator.

[0089] In this embodiment, verification is performed by selecting an appropriate verification method based on the vehicle's system version and the communication status between the vehicle and the cloud platform. This approach addresses the verification needs of different scenarios, enabling secure and convenient access to engineering mode. The unique design of the password for entering engineering mode also prevents the risk of mass leakage of this password.

[0090] In one embodiment of this application, the verification method for entering the engineering mode is applied to a cloud platform. The cloud platform is a management platform configured on a cloud server, used to generate a cloud verification code based on the project to which the vehicle-mounted unit belongs; and to update the cloud verification code at preset intervals, or reset the cloud verification code corresponding to the project to which the vehicle-mounted unit belongs based on changes in project stage; and to encrypt the vehicle identification number (VIN) of the vehicle-mounted unit according to a preset encryption algorithm shared with the vehicle-mounted unit, generating a local verification code corresponding to that vehicle-mounted unit. The preset encryption algorithm is kept confidential from the outside world, and the administrator can query the local verification codes corresponding to each vehicle-mounted unit on the cloud platform. The cloud verification code is a dynamically updated verification code. In a project, the vehicle-mounted units corresponding to the vehicle models included in the project share a single cloud verification code, which is dynamically updated, reducing the risk of password leakage; while the local verification code is generated based on the vehicle-mounted unit's own VIN, and each vehicle-mounted unit's local verification code is unique. Local verification codes from different vehicle-mounted units cannot be shared, preventing the mass leakage of passwords for entering the vehicle-mounted unit's engineering mode.

[0091] Specifically, the verification methods for entering engineering mode include:

[0092] Receive a verification message sent by the vehicle's infotainment system. The verification message includes the password entered by the operator, and the password includes a verification code. Determine whether the verification code included in the password matches the cloud verification code. If the verification code included in the password matches the cloud verification code, send a confirmation message to the vehicle's infotainment system so that the vehicle's infotainment system can enter engineering mode based on the confirmation message.

[0093] In this embodiment, the cloud platform verifies the password entered by the user, determining whether the verification code included in the password matches the cloud verification code. Specifically, the verification message received by the cloud platform includes the password entered by the user and the model of the vehicle's infotainment system that sent the verification message. The cloud platform then locates the cloud verification code corresponding to the project of that vehicle's infotainment system model locally and matches it with the verification code included in the user's password to determine whether the cloud verification code matches the local verification code. If the verification code included in the user's password matches the cloud verification code, the password entered by the user is verified successfully. After receiving the confirmation message, the vehicle's infotainment system can enter engineering mode based on the confirmation message.

[0094] In one feasible implementation, the cloud platform can obtain the vehicle identification code of the vehicle's infotainment system, encrypt the vehicle identification code according to a preset encryption algorithm, and generate a local verification code corresponding to the vehicle's infotainment system. The local verification code is used for local verification by the vehicle's infotainment system, and the preset encryption algorithm is an encryption algorithm shared by the vehicle's infotainment system and the cloud platform.

[0095] In this embodiment, the cloud platform, following an encryption algorithm agreed upon with the vehicle's infotainment system, encrypts the vehicle identification number (VIN) after obtaining it, and then generates a local verification code for the system. Specifically, this local verification code is used for local verification within the vehicle. For example, an administrator can retrieve the local verification code from the cloud platform and, if the user's vehicle is offline, provide the user with a password including this local verification code. The user then enters the password into the vehicle's Bluetooth dialing interface, and the system verifies the password to determine whether to enter engineering mode. The cloud platform and the vehicle share a preset encryption algorithm. Even if the vehicle malfunctions and cannot connect to the cloud platform for cloud verification, the system can still verify the user's entered password to determine whether to enter engineering mode.

[0096] Reference Figure 3 , Figure 3 This is a schematic diagram of the framework of a verification system for entering engineering mode according to an embodiment of this application. In this embodiment, a verification system for entering engineering mode is proposed, applied to an in-vehicle infotainment system. The system includes:

[0097] The acquisition module is used to acquire the system version of the vehicle system and the communication status between the vehicle system and the cloud platform;

[0098] The determination module is used to determine the verification method based on the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform;

[0099] The verification module is used to verify the password entered by the user according to the verification method.

[0100] The entry module is used to enter engineering mode if the password verification is successful.

[0101] In this embodiment, the method for verifying the password entered by the user is determined based on the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform. Different verification methods can be flexibly determined for different application scenarios, enabling secure and convenient access to engineering mode in multiple scenarios.

[0102] In one feasible implementation, the password includes an identifier and a verification code, and the system further includes:

[0103] The first determining submodule is used to determine whether the identifier included in the password is consistent with a preset identifier, the preset identifier being used to characterize the intention to enter the vehicle system engineering mode; if the identifier included in the password is consistent with the preset identifier, the system version of the vehicle system is obtained, and the communication status between the vehicle system and the cloud platform is obtained.

[0104] In one feasible implementation, the verification code is a cloud verification code generated or updated by the cloud platform according to the project to which the vehicle-mounted system belongs, or a local verification code generated by encrypting the vehicle identification number of the vehicle-mounted system according to a preset encryption algorithm; the verification method is cloud verification or local verification; the above verification module is further used for:

[0105] If the verification method is determined to be cloud verification, the cloud platform determines whether the verification code included in the password matches the cloud verification code; if the verification code included in the password matches the cloud verification code, the password verification is successful.

[0106] If the verification method is determined to be local verification, it is determined whether the verification code included in the password is consistent with the local verification code; if the verification code included in the password is consistent with the local verification code, the password verification is successful.

[0107] In one feasible implementation, the aforementioned determining module is further configured to determine the verification method as cloud verification when the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is normal; and to determine the verification method as local verification when the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is abnormal.

[0108] In one feasible implementation, the system further includes:

[0109] The first entry submodule is used to enter engineering mode when the identifier included in the password is consistent with the preset identifier and the system version of the vehicle system is in the research and development stage.

[0110] In one feasible implementation, the acquisition module includes:

[0111] The first acquisition submodule is used to acquire the system version of the vehicle system;

[0112] The second acquisition submodule is used to send verification information to the cloud platform when the system version of the vehicle system is in the after-sales stage; and to obtain the communication status between the vehicle system and the cloud platform based on whether the verification message was sent successfully.

[0113] In one feasible implementation, the second acquisition submodule is further configured to determine that the communication status between the vehicle-mounted system and the cloud platform is normal if the verification message is successfully sent; and to determine that the communication status between the vehicle-mounted system and the cloud platform is abnormal if the verification message fails to be sent.

[0114] In one feasible implementation, the vehicle infotainment system includes a Bluetooth phone, and the system further includes:

[0115] A receiving module is used to receive the password entered by the user through the Bluetooth phone dialing interface.

[0116] In one embodiment of this application, based on the same inventive concept, an electronic device is proposed, including a memory processor and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described verification method for entering engineering mode.

[0117] In one embodiment of this application, a vehicle is also proposed, which is equipped with the verification system for entering engineering mode described in the above embodiments.

[0118] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0119] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0120] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0121] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0122] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0123] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device 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 terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0124] The above provides a detailed description of the verification method, system, electronic device, and vehicle for entering engineering mode. Specific examples have been used to illustrate the principles and embodiments of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in specific embodiments and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0125] The above embodiments are merely preferred embodiments provided to fully illustrate this application, and the scope of protection of this application is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on this application are all within the scope of protection of this application.

Claims

1. A verification method for entering engineering mode, characterized in that, Applied to in-vehicle infotainment systems, the method includes: Obtain the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform; The verification method is determined based on the system version of the vehicle infotainment system and the communication status between the vehicle infotainment system and the cloud platform; The password entered by the user is verified according to the verification method described above; If the password verification is successful, enter engineering mode.

2. The verification method for entering engineering mode according to claim 1, characterized in that, The password includes an identifier and a verification code; before obtaining the system version of the vehicle-mounted system and the communication status between the vehicle-mounted system and the cloud platform, the method further includes: Determine whether the identifier included in the password is consistent with a preset identifier, the preset identifier being used to characterize the intention to enter the vehicle system engineering mode; If the identifier included in the password matches the preset identifier, the system version of the vehicle system is obtained, and the communication status between the vehicle system and the cloud platform is obtained.

3. The verification method for entering engineering mode according to claim 2, characterized in that, The verification code is either a cloud verification code generated or updated by the cloud platform according to the project to which the vehicle-mounted system belongs, or a local verification code generated by encrypting the vehicle identification code of the vehicle-mounted system according to a preset encryption algorithm; the verification method is either cloud verification or local verification. The password entered by the user is verified according to the aforementioned verification method, including: If the verification method is determined to be cloud verification, the cloud platform is used to determine whether the verification code included in the password is consistent with the cloud verification code. If the verification code included in the password matches the cloud verification code, the password verification is successful. If the verification method is determined to be local verification, it is determined whether the verification code included in the password is consistent with the local verification code; if the verification code included in the password is consistent with the local verification code, the password verification is successful.

4. The verification method for entering engineering mode according to claim 1, characterized in that, The step of determining the verification method based on the system version of the vehicle-mounted system and the communication status between the vehicle-mounted system and the cloud platform includes: If the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is normal, the verification method is determined to be cloud verification. If the system version of the vehicle infotainment system is in the after-sales stage and the communication status between the vehicle infotainment system and the cloud platform is abnormal, the verification method is determined to be local verification.

5. The verification method for entering engineering mode according to claim 2, characterized in that, The method further includes: If the identifier included in the password is consistent with the preset identifier, and the system version of the vehicle system is in the research and development stage, then enter the engineering mode.

6. The verification method for entering engineering mode according to claim 4, characterized in that, The method further includes: If the system version of the vehicle infotainment system cannot be obtained, the stage to which the system version of the vehicle infotainment system belongs shall be regarded as the after-sales stage.

7. The verification method for entering engineering mode according to claim 1, characterized in that, Obtain the system version of the vehicle's infotainment system and the communication status between the vehicle's infotainment system and the cloud platform, including: Obtain the system version of the vehicle's infotainment system; If the system version of the vehicle infotainment system is in the after-sales stage, a verification message is sent to the cloud platform. The communication status between the vehicle-mounted system and the cloud platform is determined based on whether the verification information was successfully sent.

8. The verification method for entering engineering mode according to claim 7, characterized in that, Based on whether the verification information was successfully sent, the communication status between the vehicle-mounted system and the cloud platform is determined, including: If the verification information is successfully sent, it is determined that the communication status between the vehicle-mounted system and the cloud platform is normal. If the verification information fails to be sent, it is determined that the communication status between the vehicle-mounted system and the cloud platform is abnormal.

9. The verification method for entering engineering mode according to claim 1, characterized in that, The vehicle infotainment system includes Bluetooth phone connectivity, and the method further includes: Receive the password entered by the user through the Bluetooth phone dialing interface.

10. A verification method for entering engineering mode, characterized in that, Applied to a cloud platform, the cloud platform is used to establish a communication connection with the vehicle's infotainment system, the vehicle's infotainment system executing the verification method for entering engineering mode as described in any one of claims 1-9, the method comprising: The system receives verification information sent by the vehicle's infotainment system, the verification information including a password entered by the user, the password including a verification code; Determine whether the verification code included in the password matches the cloud verification code; If the verification code included in the password matches the cloud verification code, a confirmation message is sent to the vehicle system so that the vehicle system can enter engineering mode based on the confirmation message.

11. The verification method for entering engineering mode according to claim 10, characterized in that, The method further includes: obtaining the vehicle identification code of the vehicle system; encrypting the vehicle identification code of the vehicle system according to a preset encryption algorithm to generate a local verification code corresponding to the vehicle system; the local verification code is used for local verification by the vehicle system, and the preset encryption algorithm is an encryption algorithm shared by the vehicle system and the cloud platform.

12. A verification system for entering engineering mode, characterized in that, The system, applied to in-vehicle infotainment systems, includes: an acquisition module for acquiring the system version of the in-vehicle infotainment system and the communication status between the in-vehicle infotainment system and the cloud platform; a determination module for determining a verification method based on the system version of the in-vehicle infotainment system and the communication status between the in-vehicle infotainment system and the cloud platform; a verification module for verifying the password entered by the user according to the verification method; and an entry module for entering engineering mode if the password verification is successful.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the verification method for entering engineering mode as described in any one of claims 1-11.

14. A vehicle, characterized in that, The vehicle is equipped with a verification system for entering engineering mode as described in claim 12.

Images