Vehicle application login method, device and vehicle

Abstract

The present disclosure relates to a vehicle-mounted application login method, device and vehicle. The method includes: generating a login verification code in response to a login request for logging into a vehicle-mounted application; sending the login verification code to the vehicle-mounted application server corresponding to the vehicle-mounted application, so that the vehicle-mounted application server obtains a login session credential through the vehicle's account server according to the login verification code and a preset application service key; the login session credential is a credential generated by the account server after successfully verifying the login verification code and the preset application service key; receiving the login session credential sent by the vehicle-mounted application server; obtaining the vehicle's currently logged-in user account information according to the login session credential, and using the user account information to log in to the vehicle-mounted application. In this way, under the premise of ensuring the security of the account, the vehicle-mounted application can directly log in using the vehicle's currently logged-in user account information, without the user having to manually enter the account password, which can improve the user's driving experience.

Description

Technical Field

[0001] The present disclosure relates to the field of intelligent vehicles, and in particular, to a vehicle-mounted application login method, device and vehicle. Background Art

[0002] With the promotion of smart cars and the popularity of in-vehicle applications, more and more in-vehicle applications are configured on in-vehicle terminals, such as navigation map applications, entertainment applications, and vehicle control applications, which facilitate the work, entertainment, and driving assistance needs of drivers or passengers. However, various in-vehicle applications require separate accounts to log in, resulting in drivers or passengers needing to enter account information (such as user name and password, etc.) for each in-vehicle application, which is complicated and affects the driving experience. Summary of the invention

[0003] In order to solve the above problems, the present disclosure provides a method, device and vehicle for logging into an in-vehicle application.

[0004] In a first aspect, the present disclosure provides a vehicle-mounted application login method, which is applied to a vehicle-mounted terminal installed with the vehicle-mounted application, and the method includes:

[0005] In response to a login request for logging into the in-vehicle application, generating a login verification code;

[0006] Sending the login verification code to the vehicle-mounted application server corresponding to the vehicle-mounted application, so that the vehicle-mounted application server obtains the login session credential through the vehicle account server according to the login verification code and the preset application service key, wherein the login session credential is a credential generated by the account server after successfully verifying the login verification code and the preset application service key;

[0007] Receiving a login session credential sent by the vehicle-mounted application server;

[0008] The user account information currently logged in to the vehicle is obtained according to the login session credential, and the user account information is used to log in to the vehicle application.

[0009] Optionally, obtaining the user account information currently logged in to the vehicle according to the login session credential, and using the user account information to log in to the vehicle application includes:

[0010] Sending the login session credential to the account server so that the account server verifies the validity of the login session credential;

[0011] Receiving a verification result of the user login session credential sent by the account server;

[0012] When the verification result of the login session credential is valid, the user account information currently logged in to the vehicle is obtained, and the user account information is used to log in to the vehicle application.

[0013] Optionally, in response to a login request for logging into the in-vehicle application, generating a login verification code includes:

[0014] In response to a login request for logging into the in-vehicle application, a login verification code is generated according to the vehicle identification and the login request time and in accordance with a first preset encryption algorithm.

[0015] Optionally, the user account information currently logged in to the vehicle is obtained in the following manner:

[0016] When a vehicle unlocking signal is received, unlocking user account information corresponding to the vehicle unlocking signal is acquired, and the unlocking user account information is used as the user account information currently logged in to the vehicle.

[0017] Optionally, after using the user account information to log in to the in-vehicle application, the method further includes:

[0018] Sending a parameter acquisition request message to the account server according to the user account information;

[0019] Receive the vehicle-mounted application parameters sent by the account server according to the parameter acquisition request message, and set the configuration parameters of the vehicle-mounted application or the vehicle according to the vehicle-mounted application parameters.

[0020] Optionally, the vehicle-mounted terminal further includes a pre-installed account application, and the obtaining of a login verification code in response to a login request for logging into the vehicle-mounted application includes:

[0021] In response to a login request for logging into the in-vehicle application, the in-vehicle application sends an in-vehicle application login request message to the account application;

[0022] The account application obtains a login verification code according to the received in-vehicle application login request message, and sends the login verification code to the in-vehicle application;

[0023] The in-vehicle application receives the login verification code sent by the account application.

[0024] Optionally, the in-vehicle application includes an account SDK, and the account SDK is used for data transmission between the in-vehicle application and the account application.

[0025] In a second aspect, the present disclosure provides another in-vehicle application login method, which is applied to an account server, and the method includes:

[0026] Receive the login verification code and preset application service key sent by the vehicle application server;

[0027] Verifying the login verification code and the preset application service key, and generating a login session credential based on the login verification code and the preset application service key if the verification succeeds;

[0028] The login session credentials are sent to the in-vehicle application server.

[0029] Optionally, the method further comprises:

[0030] Receive the login session credentials sent by the vehicle terminal;

[0031] Verify the validity of the login session credential and send the verification result to the vehicle terminal so that the vehicle terminal can obtain the user account information currently logged in to the vehicle if the verification result of the login session credential is valid, and use the user account information to log in to the vehicle application.

[0032] In a third aspect, the present disclosure provides another in-vehicle application login method, which is applied to an in-vehicle application server, and the method includes:

[0033] Receive the login verification code sent by the vehicle terminal;

[0034] Sending the login verification code and the vehicle application service key to the vehicle account server;

[0035] Receiving a login session credential generated by the account server after successfully verifying the login verification code and the preset application service key;

[0036] The login session credential is sent to the vehicle-mounted terminal so that the vehicle-mounted terminal obtains the user account information currently logged in to the vehicle according to the session credential, and uses the user account information to log in to the vehicle-mounted application.

[0037] In a fourth aspect, the present disclosure provides a vehicle-mounted application login device, which is applied to a vehicle-mounted terminal installed with a vehicle-mounted application, and the device includes:

[0038] a memory having a computer program stored thereon;

[0039] A processor is used to execute the computer program in the memory to implement the steps of the method described in the first aspect of the present disclosure.

[0040] In a fifth aspect, the present disclosure provides another in-vehicle application login device, which is applied to an account server, and the device includes:

[0041] a memory having a computer program stored thereon;

[0042] A processor is used to execute the computer program in the memory to implement the steps of the method described in the second aspect of the present disclosure.

[0043] In a sixth aspect, the present disclosure provides another vehicle-mounted application login device, which is applied to a vehicle-mounted application server, and the device includes:

[0044] a memory having a computer program stored thereon;

[0045] A processor is used to execute the computer program in the memory to implement the steps of the method described in the third aspect of the present disclosure.

[0046] In a seventh aspect, the present disclosure provides a vehicle, comprising the in-vehicle application login device described in the fourth aspect of the present disclosure.

[0047] With the above technical solution, the vehicle terminal generates a login verification code in response to a login request for logging into the vehicle application; sends the login verification code to the vehicle application server corresponding to the vehicle application, so that the vehicle application server obtains the login session credential through the vehicle's account server based on the login verification code and the preset application service key; the login session credential is a credential generated by the account server after the login verification code and the preset application service key are successfully verified; receives the login session credential sent by the vehicle application server; obtains the vehicle's currently logged-in user account information based on the login session credential, and uses the user account information to log in to the vehicle application. In this way, the vehicle application can directly log in using the vehicle's currently logged-in user account information, without the user having to manually enter the account password, which is simple to operate and can improve the user's driving experience. At the same time, since the login verification is performed through the vehicle application server and the account server, the security of the account is also guaranteed.

[0048] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0050] Figure 1 is a structural diagram of a vehicle-mounted application login system provided by an embodiment of the present disclosure;

[0051] Figure 2 is a flow chart of a vehicle application login method provided by an embodiment of the present disclosure;

[0052] Figure 3 is a flow chart of a second vehicle-mounted application login method provided by an embodiment of the present disclosure;

[0053] Figure 4 is a flowchart of a third in-vehicle application login method provided by an embodiment of the present disclosure;

[0054] Figure 5 is a flowchart of a fourth in-vehicle application login method provided by an embodiment of the present disclosure;

[0055] Figure 6 is a structural diagram of another vehicle-mounted application login system provided by an embodiment of the present disclosure;

[0056] Figure 7 is a block diagram of a vehicle-mounted application login device provided by an embodiment of the present disclosure;

[0057] Figure 8 is a block diagram of another vehicle-mounted application login device provided by an embodiment of the present disclosure;

[0058] Fig. 9 It is a block diagram of a vehicle provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0059] The specific implementation of the present disclosure is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described herein is only used to illustrate and explain the present disclosure, and is not used to limit the present disclosure.

[0060] It should be noted that, in the present disclosure, words such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order; terms such as "S101", "S102", "S201", "S202", etc. are used to distinguish steps, and do not have to be understood as performing method steps in a specific order or sequential order; when the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements.

[0061] First, the application scenario of the present disclosure is described. The present disclosure can be applied to the vehicle application control scenario. There are more and more vehicle applications configured on the vehicle terminal, including various vehicle cooperative ecological applications (such as navigation map applications, entertainment applications, etc.), and vehicle self-developed ecological applications (such as vehicle control applications). Since different vehicle applications are developed by different manufacturers, users need to enter separate account information (such as user name and password, etc.) to log in when using each vehicle application. The operation is complicated and affects the driving experience. In the related art, the vehicle application can record the account information logged in by the user, so that the user can log in with the recorded account information without manual input the next time he logs in. However, this method will have the problem of wrong login account when multiple users use the same vehicle. For example: the same vehicle can be driven by different users, such as different family members. In this way, when user A uses the vehicle and logs in to the vehicle application, the vehicle application can record the account information of user A; then, when user B uses the vehicle, the vehicle application will automatically use the account information of user A to log in. On the one hand, there will be privacy leakage problems, and on the other hand, different accounts have different settings or permissions, which will also affect the user's driving experience.

[0062] In order to solve the above problems, the present disclosure provides a method, device and vehicle for logging into an in-vehicle application. The in-vehicle terminal can respond to a login request for logging into the in-vehicle application, perform login verification through the in-vehicle application server and the account server, and use the vehicle's currently logged-in user account information to log in to the in-vehicle application if the verification passes. In this way, the in-vehicle application can be logged in using the vehicle's currently logged-in user account information without the user having to manually enter an account password, which is simple to operate and improves the user's driving experience. At the same time, since the login verification is performed through the in-vehicle application server and the account server, the security of the account is also guaranteed.

[0063] The specific embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0064] Figure 1 is a structural diagram of a vehicle application login system provided by an embodiment of the present disclosure, such as Figure 1 As shown, the vehicle application login system includes: a vehicle terminal 101, a vehicle application server 102 and an account server 103, wherein one or more vehicle applications can be installed on the vehicle terminal 101, and different vehicle applications can correspond to different vehicle application servers.

[0065] Further, Figure 2 is a structural diagram of another vehicle application login system provided by the present disclosure, such as Figure 2As shown, the vehicle terminal 101 of the vehicle application login system includes a pre-installed account application 1012, and one or more vehicle applications 1011. Different vehicle applications 1011 may correspond to different vehicle application servers 102. Among them, the account application 1012 may be a built-in application pre-installed in the vehicle terminal. After the vehicle terminal is powered on, the account application starts automatically and continues to run in the background to provide account services. Through this account application, a unified account system can be used to connect multiple vehicle applications (including vehicle-mounted cooperative ecological applications and vehicle-mounted self-developed ecological applications) in series, so as to automatically log in to the vehicle application when the user gets on the car. It should be noted that the account application may not provide a human-computer interaction interface; while the vehicle application needs to provide a human-computer interaction interface to display information and parameters related to the vehicle application to the user, and the vehicle application parameters can be configured by the user.

[0066] Figure 3 is a flow chart of a vehicle application login method provided by an embodiment of the present disclosure, such as Figure 3 As shown, the execution subject of the method may be the vehicle-mounted terminal installed with the vehicle-mounted application, and the method includes:

[0067] S301. In response to a login request for logging into an in-vehicle application, generate a login verification code.

[0068] Among them, the login request for logging into the in-vehicle application can be a user operation in which the user opens the in-vehicle application and clicks to log in, such as clicking a virtual button for logging in; it can also be a login request message automatically triggered when the in-vehicle application is started.

[0069] In this step, the current time can be used as the login request time, so that the login verification code can be generated according to the vehicle identification and / or the login request time, and the vehicle identification can be the vehicle frame number. For example: the vehicle identification or the login request time can be used as the login verification code; the vehicle identification and the login request time can also be simply combined to generate the login verification code; the login verification code can also be generated according to the vehicle identification and the login request time according to the first preset encryption algorithm.

[0070] The first preset encryption algorithm may be AES (Advanced Encryption Standard), specifically, a 128-bit AES128 encryption algorithm or a 256-bit AES356 encryption algorithm. As a new encryption algorithm, AES can quickly encrypt and decrypt in software and hardware, is relatively easy to implement, and requires only a small amount of memory, so it is convenient to deploy on the vehicle terminal.

[0071] S302: Send the login verification code to the vehicle-mounted application server corresponding to the vehicle-mounted application, so that the vehicle-mounted application server obtains the login session credential through the vehicle's account server according to the login verification code and the preset application service key.

[0072] The login session credential is a credential generated after the account server successfully verifies the login verification code and the preset application service key.

[0073] It should be noted that both the vehicle-mounted application server and the account server can be cloud servers, and login verification is implemented through the vehicle-mounted application server and the account server. The above-mentioned preset application service key can be a key pre-set in the vehicle-mounted application server, and the preset application service key corresponding to different vehicle-mounted applications can be different, so as to improve the security of application login.

[0074] S303: Receive the login session credential sent by the vehicle-mounted application server.

[0075] S304: Obtain the user account information currently logged in to the vehicle according to the login session credential, and use the user account information to log in to the vehicle-mounted application.

[0076] In this step, when the login session credential is received, it can be determined that the login verification code of the vehicle-mounted application has been verified, and the user account information of the vehicle currently logged in saved in the vehicle-mounted terminal can be directly obtained, and the user account information can be used to log in to the vehicle-mounted application.

[0077] Furthermore, when the login session credential is received, the login session credential can also be verified according to a preset verification algorithm. If the verification passes, the user account information currently logged in to the vehicle is obtained, and the user account information is used to log in to the vehicle application.

[0078] For example, the vehicle terminal may also save the preset application service key corresponding to the vehicle application, and verify the received login session credentials based on the above-mentioned login verification code and the preset application service key. If the verification is successful, the user account information currently logged in to the vehicle is obtained, and the user account information is used to log in to the vehicle application; conversely, if the verification fails, the vehicle application may not be logged in, and the login failure information may be displayed to the user so that the user can log in manually.

[0079] The above method is adopted to generate a login verification code in response to a login request for logging into an in-vehicle application; the login verification code is sent to the in-vehicle application server corresponding to the in-vehicle application, so that the in-vehicle application server obtains the login session credential through the vehicle's account server according to the login verification code and the preset application service key; the login session credential is the credential generated by the account server after the login verification code and the preset application service key are successfully verified; the login session credential sent by the in-vehicle application server is received; the user account information currently logged in to the vehicle is obtained according to the login session credential, and the user account information is used to log in to the in-vehicle application. In this way, the in-vehicle application can directly log in using the user account information currently logged in to the vehicle, without the user having to manually enter the account password, which is simple to operate and can improve the user's driving experience. At the same time, since the login verification is performed through the in-vehicle application server and the account server, the security of the account is also guaranteed.

[0080] In another embodiment of the present disclosure, the above step S304 obtains the user account information currently logged in by the vehicle according to the login session credential, and uses the user account information to log in to the vehicle application, which may also be implemented by the following steps:

[0081] First, the login session credential is sent to the account server so that the account server can verify the validity of the login session credential.

[0082] Secondly, receive the verification result of the user's login session credential sent by the account server.

[0083] Finally, when the verification result of the login session credential is valid, the user account information currently logged in to the vehicle is obtained, and the user account information is used to log in to the vehicle application.

[0084] In this way, the login session credentials are verified twice by the account server, further improving the security of the account.

[0085] Furthermore, the user account information currently logged in to the vehicle can be obtained in the following ways:

[0086] When a vehicle unlocking signal is received, the unlocking user account information corresponding to the vehicle unlocking signal is obtained, and the unlocking user account information is used as the user account information currently logged in to the vehicle.

[0087] It should be noted that the vehicle unlocking methods may include vehicle key unlocking, wristband unlocking, and cloud service APP unlocking. The unlocking user account information corresponding to the vehicle unlocking signal may be obtained based on the vehicle unlocking signal of different unlocking methods.

[0088] For example, there are multiple vehicle keys, and the vehicle unlocking signal emitted by each vehicle key is different and corresponds to different unlocking user account information. When a vehicle unlocking signal emitted by a vehicle key is received, the unlocking user account information corresponding to the vehicle unlocking signal can be obtained.

[0089] In another example, the vehicle cloud service APP can distinguish different users through the cloud service APP login account. When receiving a vehicle unlocking signal sent by the cloud service APP, it obtains the APP login account in the vehicle unlocking signal, thereby obtaining the unlocking user account information.

[0090] In this way, after the vehicle is unlocked, the user account information can be obtained, and the user does not need to log in manually, which further improves the user's driving experience.

[0091] In another embodiment of the present disclosure, after the in-vehicle application is logged in using the user account information, the in-vehicle application may also obtain the in-vehicle application parameters corresponding to the user account information, specifically including:

[0092] First, according to the user account information, a parameter acquisition request message is sent to the account server.

[0093] Then, the in-vehicle application parameters sent by the account server according to the parameter acquisition request message are received, and the configuration parameters of the in-vehicle application or the vehicle are set according to the in-vehicle application parameters.

[0094] The vehicle application parameters may be personalized configuration parameters corresponding to the user account information, and different user account information may correspond to different vehicle application parameters. In this way, the vehicle application parameters may be personalized according to user habits. The vehicle application parameters may include vehicle software parameters and hardware parameters, such as vehicle air conditioning temperature, seat angle, theme skin used by the vehicle terminal, favorite music list, etc.

[0095] In addition, when the user modifies the parameters of the in-vehicle application, the in-vehicle terminal can upload the modified in-vehicle application parameters to the account server so that the account server can update and save the in-vehicle application parameters corresponding to the user account information, so that the in-vehicle application can use the latest in-vehicle application parameters for settings the next time it logs in using the user account information.

[0096] In this way, the parameters of vehicle-mounted application can be personalized to further improve the vehicle's driving experience.

[0097] Furthermore, the above-mentioned in-vehicle application parameters can also be jointly determined by the user account information and the vehicle identification, so that the same account can have different personalized configurations on different vehicles, and different accounts on the same vehicle can also have their own different personalized configurations.

[0098] Figure 4 is a flow chart of a second vehicle application login method provided by an embodiment of the present disclosure, such as Figure 4 As shown, the execution subject of the method may be an account server, and the method includes:

[0099] S401: Receive a login verification code and a preset application service key sent by the vehicle-mounted application server.

[0100] S402: Verify the login verification code and the preset application service key, and if the verification is successful, generate a login session credential according to the login verification code and the preset application service key.

[0101] Similarly, the above-mentioned preset application service key can be a key pre-set in the vehicle-mounted application server, and the preset application service keys corresponding to different vehicle-mounted applications can be different, so as to improve the security of application login.

[0102] Optionally, the preset application service key may be updated irregularly to avoid key leakage and increase security.

[0103] In this step, the verification is determined to be successful when the login verification code and the preset application service key meet the preset verification conditions. When the above login verification code includes the vehicle identification and the login request time, the preset verification conditions may include:

[0104] Condition 1: Obtain the vehicle identification according to the login verification code, and determine that the vehicle identification is a valid vehicle identification, which may be a sold vehicle identification stored in the account server.

[0105] It should be noted that if the above-mentioned login verification code is a verification code encrypted using the AES algorithm, it can be decrypted using the AES algorithm to obtain the vehicle identification and login request time.

[0106] Condition 2: Obtain the login request time according to the login verification code, determine that the login request time is before the current time, and the time difference between the login request time and the current time is within a first preset time range. For example, the first preset time range may be within 10 minutes or 15 minutes before the current time.

[0107] Condition three: determine that the preset application service key is consistent with the key corresponding to the in-vehicle application stored in the account server.

[0108] Furthermore, a login session credential may be generated based on the login verification code and the preset application service key using a second preset encryption algorithm, and the second preset encryption algorithm may also be an AES128 encryption algorithm or an AES256 encryption algorithm.

[0109] S403: Send the login session credential to the vehicle-mounted application server so that the vehicle-mounted application server sends the login session credential to the vehicle-mounted terminal, and the vehicle-mounted terminal logs in to the vehicle-mounted application based on the login session credential using the user account information currently logged in to the vehicle.

[0110] Using the above method, the account server can verify the login verification code and the preset application service key, and send the login session credentials to the on-board application server and the on-board application after the verification is successful. In this way, the on-board application can use the user account information currently logged in to the vehicle to log in directly, without the user having to manually enter the account password. The operation is simple and can improve the user's driving experience. At the same time, since the login verification is performed through the on-board application server and the account server, the security of the account is also guaranteed.

[0111] Furthermore, the method may also include: receiving the login session credentials sent by the vehicle-mounted terminal, verifying the validity of the login session credentials, and sending the verification result to the vehicle-mounted terminal, so that the vehicle-mounted terminal can obtain the user account information currently logged in to the vehicle if the verification result of the login session credentials is valid, and use the user account information to log in to the vehicle-mounted application.

[0112] The validity of the login session credential can be verified in any of the following ways:

[0113] Method 1: The account server saves the historical login session credentials generated within the second preset time range, and determines whether the received login session credential exists in the above historical login session credentials. If so, the verification result of the login session credential is determined to be valid; if not, the verification result of the login session credential is determined to be invalid.

[0114] Method 2: When the login session credential is generated using a second preset encryption algorithm based on the login verification code and the preset application service key, the second preset encryption algorithm can be used to verify the validity of the login session credential. For example, the second preset encryption algorithm can be used to decrypt the login session credential to obtain the login verification code and the preset application service key, and the login verification code and the preset application service key can be verified using the above preset verification conditions. If the verification passes, the verification result of the login session credential is determined to be valid; otherwise, if the verification fails, the verification result of the login session credential is determined to be invalid.

[0115] In this way, the login session credentials are verified twice by the account server, further improving the security of the account.

[0116] Figure 5is a flow chart of a third vehicle-mounted application login method provided by an embodiment of the present disclosure, such as Figure 5 As shown, the execution subject of the method may be a vehicle-mounted application server, and the method includes:

[0117] S501. Receive a login verification code sent by the vehicle-mounted terminal.

[0118] S502: Send the login verification code and the vehicle-mounted application service key to the vehicle's account server.

[0119] S503: Receive the login session credential generated by the account server after successfully verifying the login verification code and the preset application service key.

[0120] S504: Send the login session credential to the vehicle-mounted terminal so that the vehicle-mounted terminal obtains the user account information currently logged in to the vehicle according to the session credential, and uses the user account information to log in to the vehicle-mounted application.

[0121] By adopting the above method, the login session credentials are obtained through information interaction between the vehicle-mounted application server and the account server, and the login session credentials are sent to the vehicle-mounted application. In this way, the vehicle-mounted application can directly log in using the user account information currently logged in to the vehicle, without the user having to manually enter the account password. The operation is simple and can improve the user's driving experience. At the same time, since the login verification is performed through the vehicle-mounted application server and the account server, the security of the account is also guaranteed.

[0122] Figure 6 is a flowchart of a fourth in-vehicle application login method provided by an embodiment of the present disclosure. Figure 6 As shown, the vehicle-mounted terminal also includes a pre-installed account application, and the method includes:

[0123] S601. In response to a login request for logging into an in-vehicle application, the in-vehicle application sends an in-vehicle application login request message to the account application.

[0124] S602: The account application obtains a login verification code according to the received login request message, and sends the login verification code to the in-vehicle application.

[0125] Optionally, before this step, the account application can first determine the vehicle user login status based on the received vehicle application login request message, and proceed to S602 and subsequent steps if the vehicle user login status is normal; if the vehicle user has not logged in or the login fails, the vehicle user can be prompted to log in, for example, the page can be jumped to the vehicle user scan code login page to facilitate the user to scan the code to log in.

[0126] S603: The in-vehicle application receives the login verification code sent by the account application, and sends the login verification code to the in-vehicle application server corresponding to the in-vehicle application.

[0127] S604: The vehicle-mounted application server receives the login verification code sent by the vehicle-mounted terminal, and sends the login verification code and the vehicle-mounted application service key to the vehicle's account server.

[0128] S605. The account server verifies the login verification code and the preset application service key, and if the verification is successful, generates a login session credential based on the login verification code and the preset application service key, and sends the login session credential to the vehicle-mounted application server.

[0129] S606: The in-vehicle application server sends the login session credential to the in-vehicle application.

[0130] S607: The in-vehicle application receives and sends the login session credential to the account application.

[0131] S608: The account application sends the login session credential to the account server.

[0132] S609: The account server receives the login session credential sent by the vehicle-mounted terminal, verifies the validity of the login session credential, and sends the verification result to the vehicle-mounted terminal.

[0133] S610: The account application receives the verification result, obtains the user account information currently logged in to the vehicle if the verification result of the login session credential is valid, and sends the user account information to the in-vehicle application.

[0134] S611. The in-vehicle application uses the user account information to log in to the in-vehicle application.

[0135] In this step, if the user account information has been registered in the in-vehicle application, the user account information can be used to log in directly. If the user account information has not been registered in the in-vehicle application, the user account information can be used to register first and then log in. During the registration process, the registration information can be displayed to the user, and the user can choose whether to register; or the registration can be automatically performed, and a prompt message of successful registration can be displayed to the user after the registration is successful.

[0136] By adopting the above method, the in-vehicle application is logged in twice, namely in the cloud and on the vehicle side, through the account application, account server and in-vehicle application server. Thus, automatic login of the in-vehicle application is realized while ensuring the security of the user account. There is no need for the user to manually enter the account password, which is simple to operate and improves the driving experience of the vehicle.

[0137] Furthermore, the above-mentioned in-vehicle application may include an account SDK (Software Development Kit), which can be used for data transmission between the in-vehicle application and the account application. For example, the account SDK can provide a data transmission interface between the in-vehicle application and the account application, and the data transmission between the in-vehicle application and the account application is realized through the data transmission interface. The data transmitted by the account SDK may include one or more of the following: the vehicle's currently logged-in user account information, vehicle user login status change information, in-vehicle application parameters and version information sent by the account application to the in-vehicle application, and the account login verification code, account login request message, version query message and parameter download request message sent by the in-vehicle application to the account application. Among them, the vehicle user login status change information may include account login (carrying login account information), account logout and account information refresh (carrying complete and latest account information), etc.

[0138] Optionally, when the account application receives the account management message sent by the vehicle application, it can also open the account login page, account switching page and account management page according to the account management message, wherein the account login page can support code scanning login, user name and password login, SMS login, etc. For example, when the vehicle application is not logged in, it can open the code scanning login page; when it is logged in, it can open the account management page or the account switching page.

[0139] The in-vehicle application can actively query the version information of the account application. For example, the in-vehicle application can send a version query message to the account application through the account SDK, and receive the version information of the account application sent by the account application according to the version query message. The version information may include the current version and the latest version of the account application; the in-vehicle application can determine whether there is an upgradeable version of the account application by comparing the current version and the latest version. In the case of determining that there is an upgradeable version of the account application, the in-vehicle application can automatically download the latest version of the account application and upgrade the account application, or display the account application upgrade prompt information so that the user can manually upgrade the account application according to the prompt information. For example, a small red dot can be displayed in the user avatar part of the UI page of the in-vehicle application as the account application upgrade prompt information. In addition, if there is an upgradeable version, the account application can actively send version information to the in-vehicle application through the account SDK. The version message can also carry the current version and the latest version, and the in-vehicle application upgrades the account application according to the version information. Furthermore, after the account application is upgraded, the version information can be sent to the in-vehicle application again through the account SDK to notify the in-vehicle application that the version upgrade of the account application is complete.

[0140] The in-vehicle application can also upload the in-vehicle application parameters corresponding to the user account information to the account application and the account server through the account SDK. Specifically, the in-vehicle application sends the in-vehicle application parameters to the account application through the account SDK, and the account application saves the in-vehicle application parameters to the in-vehicle terminal and forwards them to the account server. The account server saves the received in-vehicle application parameters to the account server side. For example, the in-vehicle application can upload its own personalized in-vehicle application parameters, and can choose whether to distinguish the vehicle identification for storage. If it is distinguished, the personalized in-vehicle application parameters can be distinguished from the vehicle identification and the user account and saved to the account server and the in-vehicle terminal respectively, so that the same account has corresponding personalized configurations on different vehicles, which changes with the vehicle; if it is not distinguished, it is considered to be universal data unrelated to the vehicle, and the personalized in-vehicle application parameters are distinguished from the user account and saved to the account server and the in-vehicle terminal respectively.

[0141] The in-vehicle application can also download the in-vehicle application parameters corresponding to the user account information through the account SDK. Specifically, the in-vehicle application sends an application parameter download request message to the account application through the account SDK. The account application obtains the in-vehicle application parameters stored in the in-vehicle terminal according to the parameter download request message, and sends the in-vehicle application parameters to the in-vehicle application, so that the in-vehicle application can use the in-vehicle application parameters to set the configuration parameters of the in-vehicle application or the vehicle. In addition, the account application can also forward the application parameter download request message to the account server. The account server obtains the in-vehicle application parameters stored in the in-vehicle terminal according to the parameter download request message, and sends the in-vehicle application parameters to the account application. The account application forwards the received in-vehicle application parameters to the in-vehicle application. Similarly, the in-vehicle application parameters can be downloaded based on the vehicle identification and user account information, or they can be downloaded based only on the user account information.

[0142] If the account server detects that the vehicle application parameters corresponding to the user account information have changed, it can send a parameter update notification message to the account application, and the account application forwards the parameter update notification message to the vehicle application, and the vehicle application downloads the vehicle application parameters corresponding to the user account information according to the parameter update notification message. In this way, the vehicle application can monitor whether the vehicle application parameters saved by the account server have changed, and if the vehicle application parameters have changed, it can download and update the vehicle application parameters.

[0143] In addition, the account SDK can also be expanded according to customer needs, such as expanding the query interface between the account application and the in-vehicle application, with high scalability.

[0144] In this way, through the account SDK, the in-vehicle application can realize data transmission with the account application without additional software development, and implement the in-vehicle application login method provided by any of the above embodiments through the account application.

[0145] Figure 7 FIG. 1 is a block diagram of a vehicle-mounted application login device according to an exemplary embodiment. Figure 7 As shown, the vehicle-mounted application login device 700 may include: a processor 701 and a memory 702. The vehicle-mounted application login device 700 may also include one or more of a multimedia component 703, an input / output (I / O) interface 704, and a communication component 705.

[0146] The processor 701 is used to control the overall operation of the vehicle-mounted application login device 700 to complete all or part of the steps in the above-mentioned vehicle-mounted application login method. The memory 702 is used to store various types of data to support the operation of the vehicle-mounted application login device 700, and these data may include, for example, instructions for any application or method operated on the vehicle-mounted application login device 700, and application-related data, such as contact data, sent and received messages, pictures, audio, video, etc. The memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, disk or optical disk. The multimedia component 703 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 702 or sent via the communication component 705. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 704 provides an interface between the processor 701 and other interface modules, and the above-mentioned other interface modules may be a keyboard, a mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 705 is used for wired or wireless communication between the vehicle-mounted application login device 700 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, 5G, NB-IOT, eMTC, or other 6G, etc., or a combination of one or more of them, is not limited here. Therefore, the corresponding communication component 705 may include: a Wi-Fi module, a Bluetooth module, an NFC module, etc.

[0147] In an exemplary embodiment, the in-vehicle application login device 700 can be implemented by one or more application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), digital signal processors (Digital Signal Processor, DSP), digital signal processing devices (Digital Signal Processing Device, DSPD), programmable logic devices (Programmable Logic Device, PLD), field programmable gate arrays (Field Programmable Gate Array, FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the above-mentioned in-vehicle application login method.

[0148] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, and when the program instructions are executed by a processor, the steps of the above-mentioned vehicle-mounted application login method are implemented. For example, the computer-readable storage medium may be the above-mentioned memory 702 including program instructions, and the above-mentioned program instructions may be executed by the processor 701 of the vehicle-mounted application login device 700 to complete the above-mentioned vehicle-mounted application login method.

[0149] Figure 8 8 is a block diagram of a vehicle-mounted application login device 800 according to an exemplary embodiment. For example, the vehicle-mounted application login device 800 may be provided as a server. Figure 8 The vehicle application login device 800 includes a processor 822, which may be one or more, and a memory 832 for storing a computer program executable by the processor 822. The computer program stored in the memory 832 may include one or more modules, each corresponding to a set of instructions. In addition, the processor 822 may be configured to execute the computer program to perform the above-mentioned vehicle application login method.

[0150] In addition, the vehicle-mounted application login device 800 may further include a power supply component 826 and a communication component 850, wherein the power supply component 826 may be configured to perform power management of the vehicle-mounted application login device 800, and the communication component 850 may be configured to implement communication of the vehicle-mounted application login device 800, for example, wired or wireless communication. In addition, the vehicle-mounted application login device 800 may further include an input / output (I / O) interface 858. The vehicle-mounted application login device 800 may operate based on an operating system stored in the memory 832, such as Windows Server, Mac OS, Unix, Linux, etc.

[0151] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, and when the program instructions are executed by a processor, the steps of the above-mentioned vehicle-mounted application login method are implemented. For example, the computer-readable storage medium may be the above-mentioned memory 832 including program instructions, and the above-mentioned program instructions may be executed by the processor 822 of the vehicle-mounted application login device 800 to complete the above-mentioned vehicle-mounted application login method.

[0152] In another exemplary embodiment, a computer program product is further provided. The computer program product includes a computer program that can be executed by a programmable device. The computer program has a code portion for executing the above-mentioned in-vehicle application registration method when executed by the programmable device.

[0153] Fig. 9 is a block diagram of a vehicle provided by an embodiment of the present disclosure, such as Fig. 9 As shown, the vehicle includes: the above-mentioned vehicle-mounted application login device.

[0154] The preferred embodiments of the present disclosure are described in detail above in conjunction with the accompanying drawings; however, the present disclosure is not limited to the specific details in the above embodiments. Within the technical concept of the present disclosure, a variety of simple modifications can be made to the technical solution of the present disclosure, and these simple modifications all fall within the protection scope of the present disclosure.

[0155] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present disclosure will not further describe various possible combinations.

[0156] In addition, various embodiments of the present disclosure may be arbitrarily combined, and as long as they do not violate the concept of the present disclosure, they should also be regarded as the contents disclosed by the present disclosure.

Claims

1. A vehicle application login method, characterized in that: Applied to a vehicle-mounted terminal equipped with a vehicle-mounted application, the method comprises: In response to a login request for logging into the in-vehicle application, generating a login verification code; Sending the login verification code to the vehicle-mounted application server corresponding to the vehicle-mounted application, so that the vehicle-mounted application server obtains the login session credential through the vehicle account server according to the login verification code and the preset application service key, wherein the login session credential is a credential generated by the account server after successfully verifying the login verification code and the preset application service key; Receiving a login session credential sent by the vehicle-mounted application server; Sending the login session credential to the account server so that the account server verifies the validity of the login session credential; Receiving a verification result of the user login session credential sent by the account server; If the verification result of the user login session credential is valid, obtaining the user account information currently logged in to the vehicle, and using the user account information to log in to the vehicle application; The vehicle terminal further includes a pre-installed account application, and the generating a login verification code in response to a login request for logging into the vehicle application includes: In response to a login request for logging into the in-vehicle application, the in-vehicle application sends an in-vehicle application login request message to the account application; The account application obtains a login verification code according to the received in-vehicle application login request message, and sends the login verification code to the in-vehicle application; The in-vehicle application receives the login verification code sent by the account application.

2. The method according to claim 1, characterized in that The generating a login verification code in response to a login request for logging into the in-vehicle application comprises: In response to a login request for logging into the in-vehicle application, a login verification code is generated according to the vehicle identification and the login request time and in accordance with a first preset encryption algorithm.

3. The method according to claim 1, characterized in that The user account information currently logged in to the vehicle is obtained in the following way: When a vehicle unlocking signal is received, unlocking user account information corresponding to the vehicle unlocking signal is acquired, and the unlocking user account information is used as the user account information currently logged in to the vehicle.

4. The method according to claim 1, characterized in that: After logging into the in-vehicle application using the user account information, the method further includes: Sending a parameter acquisition request message to the account server according to the user account information; Receive the vehicle-mounted application parameters sent by the account server according to the parameter acquisition request message, and set the configuration parameters of the vehicle-mounted application or the vehicle according to the vehicle-mounted application parameters.

5. The method according to claim 1, characterized in that The in-vehicle application includes an account SDK, and the account SDK is used for data transmission between the in-vehicle application and the account application.

6. A vehicle application login method, characterized in that: Applied to an account server, the method comprises: Receive the login verification code and preset application service key sent by the vehicle application server; Verifying the login verification code and the preset application service key, and generating a login session credential based on the login verification code and the preset application service key if the verification succeeds; Sending the login session credentials to the in-vehicle application server; The method further comprises: Receiving a login session credential sent by a vehicle-mounted terminal; the vehicle-mounted terminal is used to execute the vehicle-mounted application login method according to any one of claims 1 to 5; Verify the validity of the login session credential and send the verification result to the vehicle terminal so that the vehicle terminal can obtain the user account information currently logged in to the vehicle if the verification result of the login session credential is valid, and use the user account information to log in to the vehicle application.

7. A vehicle-mounted application login method, characterized in that: Applied to a vehicle-mounted application server, the method comprises: Receiving a login verification code sent by a vehicle-mounted terminal; the vehicle-mounted terminal is used to execute the vehicle-mounted application login method according to any one of claims 1 to 5; Sending the login verification code and the vehicle application service key to the vehicle account server; Receiving a login session credential generated by the account server after successfully verifying the login verification code and the preset application service key; The login session credential is sent to the vehicle-mounted terminal so that the vehicle-mounted terminal obtains the user account information currently logged in to the vehicle according to the session credential, and uses the user account information to log in to the vehicle-mounted application.

8. A vehicle-mounted application login device, characterized in that: Applied to a vehicle terminal equipped with a vehicle application, the device comprises: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1 to 5.

9. A vehicle-mounted application login device, characterized in that: Applied to an account server, the device comprises: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to claim 6.

10. A vehicle-mounted application login device, characterized in that: Applied to a vehicle-mounted application server, the device comprises: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to claim 7.

11. A vehicle, characterized in that: The vehicle comprises: The in-vehicle application login device as described in claim 8.

Images