Login verification method and device, equipment and storage medium

Abstract

The invention provides a login verification method and device, equipment and a storage medium, and relates to the technical field of intelligent vehicles. The method comprises the following steps: receiving a login request sent by vehicle-mounted equipment; the login request comprises identification information of the vehicle-mounted equipment and identification information of a vehicle corresponding to the vehicle-mounted equipment; according to the identification information of the vehicle and the identification information of the vehicle-mounted equipment, verifying whether the vehicle and the vehicle-mounted equipment have a binding relationship or not; and in response to the binding relationship between the vehicle and the vehicle-mounted equipment, determining that the login request passes verification. By verifying the binding relationship between the vehicle and the vehicle-mounted equipment, it is ensured that only the vehicle-mounted equipment bound with the vehicle can log in successfully, so that the problem of account login conflict is effectively avoided, and it is ensured that the service data can be broadcasted to the vehicle-mounted equipment.

Description

Technical Field

[0001] The present disclosure relates to the field of intelligent vehicle technology, and in particular to a login verification method, device, equipment, and storage medium. Background Art

[0002] Smart car service applications are rich in applications, relying on third-party service platforms to provide data services to ensure the normal operation of vehicle-side functions. This has led to the emergence of accounts related to service rights, such as map rights accounts for map navigation services. To distinguish rights between different vehicles, these services use the vehicle's unique identity as the account ID to manage permissions.

[0003] During vehicle R&D testing, mass production delivery, or user use, multiple in-vehicle devices may log in simultaneously using the same account ID. However, the current account ID login verification mechanism only verifies the account ID itself. When faced with such scenarios where multiple devices log in simultaneously, account login conflicts will occur, causing service data broadcast anomalies. Summary of the Invention

[0004] The present disclosure provides a login verification method, apparatus, device and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a login verification method is provided, comprising: receiving a login request sent by a vehicle-mounted device; the login request comprising identification information of the vehicle-mounted device and identification information of a vehicle corresponding to the vehicle-mounted device; verifying whether a binding relationship exists between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the identification information of the vehicle-mounted device; and determining that the login request verification is successful in response to the existence of a binding relationship between the vehicle and the vehicle-mounted device.

[0006] In some embodiments of the present disclosure, verifying whether there is a binding relationship between the vehicle and the onboard device based on the identification information of the vehicle and the identification information of the onboard device includes: obtaining the identification code of the vehicle based on the identification information of the vehicle, and obtaining the identification code of the onboard device based on the identification information of the onboard device; querying the onboard device identification code bound to the vehicle identification code in a database; the database is used to store the binding relationship between the vehicle identification code and the onboard device identification code, and the binding relationship in the database is generated and reported by the vehicle diagnostic device; in response to the queried onboard device identification code including the identification code of the onboard device, determining that there is a binding relationship between the vehicle and the onboard device.

[0007] In some embodiments of the present disclosure, obtaining the identification code of the vehicle based on the identification information of the vehicle and obtaining the identification code of the on-board device based on the identification information of the on-board device include: decrypting the identification information of the vehicle to obtain the identification code of the vehicle; decrypting the identification information of the on-board device to obtain the identification code of the on-board device.

[0008] In some embodiments of the present disclosure, after determining that the login request verification is successful, the method further includes: obtaining operating status information of the vehicle-mounted device; and generating an operating status report of the vehicle-mounted device based on the operating status information of the vehicle-mounted device.

[0009] In some embodiments of the present disclosure, the method further includes: in response to the absence of a binding relationship between the vehicle and the on-board device, determining that the login request verification fails; and recording information on the vehicle verification failure and the on-board device verification failure.

[0010] In some embodiments of the present disclosure, the method further includes: based on the information of the vehicle failure verification, counting the first number of times the vehicle fails verification within a first preset time; in response to the first number exceeding the first preset number, determining to verify the binding relationship corresponding to the vehicle.

[0011] In some embodiments of the present disclosure, the method further includes: based on the information of the failure of verification of the vehicle-mounted device, counting the second number of times the vehicle-mounted device fails verification within a second preset time; in response to the second number exceeding the second preset number, starting a disabling mechanism for the vehicle-mounted device.

[0012] According to a second aspect of an embodiment of the present disclosure, a login verification method is provided, comprising: sending a login request; the login request comprising identification information of a vehicle-mounted device and identification information of a vehicle corresponding to the vehicle-mounted device; receiving a verification result of the login request; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the identification information of the vehicle-mounted device.

[0013] In some embodiments of the present disclosure, before sending the login request, the method also includes: obtaining the identification code of the vehicle and the identification code of the on-board device; encrypting the identification code of the vehicle to obtain the identification information of the vehicle; encrypting the identification code of the on-board device to obtain the identification information of the on-board device; and generating the login request based on the identification information of the vehicle and the identification information of the on-board device.

[0014] According to the third aspect of an embodiment of the present disclosure, a login verification device is provided, including: a request receiving module, configured to receive a login request sent by a vehicle-mounted device; the login request includes identification information of a vehicle corresponding to the vehicle-mounted device and identification information of the vehicle-mounted device; a verification module, configured to verify whether there is a binding relationship between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the identification information of the vehicle-mounted device; a determination module, configured to determine that the login request verification is successful in response to the existence of a binding relationship between the vehicle and the vehicle-mounted device.

[0015] According to the fourth aspect of an embodiment of the present disclosure, a login verification device is provided, including: a request sending module, configured to send a login request; the login request includes identification information of the vehicle-mounted device and identification information of the vehicle corresponding to the vehicle-mounted device; a result receiving module, configured to receive a verification result of the login request; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the identification information of the vehicle-mounted device.

[0016] According to a fifth aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to: implement the above-mentioned login verification method.

[0017] According to a sixth aspect of an embodiment of the present disclosure, a non-transitory computer-readable storage medium is provided, which enables the mobile terminal to execute the above-mentioned login verification method when instructions in the storage medium are executed by a processor of the mobile terminal.

[0018] The technical solutions provided by the embodiments of the present disclosure may have the following beneficial effects:

[0019] The login request sent by the on-board device contains the identification information of the on-board device and the identification information of the vehicle associated with the on-board device. After receiving the login request, the on-board device can verify whether there is a binding relationship between the vehicle and the on-board device based on the identification information of the vehicle and the on-board device. If a binding relationship exists, the login request is verified and the on-board device is allowed to log in. By verifying the binding relationship between the vehicle and the on-board device, it is ensured that only the on-board device bound to the vehicle can successfully log in, effectively avoiding account login conflicts and ensuring that service data can be broadcast to the on-board device.

[0020] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0022] Figure 1 This is a flowchart of a login verification method according to some embodiments of the present disclosure.

[0023] Figure 2 This is a flowchart of another login verification method according to some embodiments of the present disclosure.

[0024] Figure 3 This is a flowchart of another login verification method according to some embodiments of the present disclosure.

[0025] Figure 4 The diagram is a schematic diagram of the architecture of a login verification system according to some embodiments of the present disclosure.

[0026] Figure 5 This is a block diagram of a login verification device according to some embodiments of the present disclosure.

[0027] Figure 6 It is a block diagram of another login verification device according to some embodiments of the present disclosure.

[0028] Figure 7 is a block diagram of an electronic device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0029] Some exemplary embodiments of the present disclosure will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. Various changes, modifications and equivalents of the methods, devices and / or systems described herein will become apparent after understanding the present disclosure. For example, the order of operations described herein is merely an example and is not limited to those orders set forth herein, but may be changed as becomes apparent after understanding the present disclosure, except for operations that must be performed in a specific order. In addition, for the sake of clarity and brevity, descriptions of features known in the art may be omitted.

[0030] The following exemplary embodiments of the present disclosure do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0031] It should be noted that the acquisition, storage, use, and processing of data in the technical solution disclosed herein are in compliance with the relevant provisions of national laws and regulations. Various types of data such as personal identity data, operation data, behavioral data, etc. related to individuals, customers, and groups obtained in the embodiments of the present disclosure have been authorized.

[0032] Figure 1 This is a flowchart of a login verification method according to some embodiments of the present disclosure. The execution subject of the login verification method can be a service broadcasting platform, which can also be called a third-party service platform. Figure 1 , the login verification method may include the following steps.

[0033] In step S110 , a login request sent by the vehicle-mounted device is received; the login request includes identification information of the vehicle-mounted device and identification information of the vehicle corresponding to the vehicle-mounted device.

[0034] In the disclosed embodiments, the in-vehicle devices may include, but are not limited to, a vehicle computer (in-vehicle infotainment system), a T-Box (telematics control system), a smart rearview mirror, an in-vehicle gateway, an intelligent cockpit controller, an on-board diagnostic device, and a user's mobile device. The in-vehicle devices interact with the service delivery platform and log in using a service rights account to obtain data services, thereby realizing the functions of the smart car.

[0035] In the embodiment of the present disclosure, the vehicle corresponding to the vehicle-mounted device can be understood as a vehicle that has an associated relationship with the vehicle-mounted device, for example, the vehicle-mounted device is installed on the vehicle, or the function of the vehicle is tested by the vehicle-mounted device.

[0036] In the embodiment of the present disclosure, the identification information of the vehicle-mounted device is used to uniquely identify the vehicle-mounted device, and the identification information of the vehicle is used to uniquely identify the vehicle.

[0037] In step S120 , it is verified whether there is a binding relationship between the vehicle and the in-vehicle device based on the identification information of the vehicle and the identification information of the in-vehicle device.

[0038] The login request sent by the vehicle-mounted device includes the identification information of the vehicle-mounted device and the identification information of the vehicle corresponding to the vehicle-mounted device. Therefore, after receiving the login request, the identification information of the vehicle-mounted device and the identification information of the vehicle device can be obtained, and then the two identification information can be used to verify whether there is a binding relationship between the vehicle-mounted device and the vehicle.

[0039] In step S130 , in response to the existence of a binding relationship between the vehicle and the in-vehicle device, it is determined that the login request verification is successful.

[0040] If it is verified that there is a binding relationship between the vehicle and the on-board device, the login request is determined to be successful, that is, the on-board device is allowed to log in and can use the corresponding services. For example, the vehicle computer can obtain real-time navigation data and the T-Box can receive remote control commands.

[0041] As can be seen from the above steps, in the login verification method provided by the disclosed embodiments, the login request sent by the vehicle-mounted device includes the identification information of the vehicle-mounted device and the identification information of the vehicle associated with the vehicle-mounted device. After receiving the login request, the vehicle-mounted device can verify whether there is a binding relationship between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the vehicle-mounted device. If a binding relationship exists, the login request is verified and the vehicle-mounted device is allowed to log in. By verifying the binding relationship between the vehicle and the vehicle-mounted device, it is ensured that only the vehicle-mounted device bound to the vehicle can successfully log in, thereby effectively avoiding account login conflicts and ensuring that service data can be broadcast to the vehicle-mounted device.

[0042] Figure 2 FIG. 1 is a flow chart of another login verification method according to some embodiments of the present disclosure. Figure 2 Steps S210 and S250 in the login verification method are respectively Figure 1 Steps S110 and S130 in the login verification method shown correspond to each other and are not repeated here.

[0043] In the embodiment of the present disclosure, Figure 1 Based on the login verification method shown, Figure 2 The login verification method shown may further include the following steps.

[0044] In step S220, the vehicle identification code is acquired according to the vehicle identification information, and the vehicle-mounted device identification code is acquired according to the vehicle-mounted device identification information.

[0045] In the disclosed embodiments, the vehicle identification information may be the vehicle identification code or an encrypted form thereof. Exemplarily, the vehicle identification code refers to the vehicle's unique identifier, such as the vehicle's frame VIN number. The vehicle-mounted device identification information may be the vehicle-mounted device's identification code or an encrypted form thereof. Exemplarily, the vehicle-mounted device identification information refers to the vehicle-mounted device's unique identifier, such as the device's serial number (SN).

[0046] In some embodiments of the present disclosure, obtaining a vehicle identification code based on the vehicle identification information, and obtaining an onboard device identification code based on the onboard device identification information include: decrypting the vehicle identification information to obtain the vehicle identification code; decrypting the onboard device identification information to obtain the onboard device identification code.

[0047] If the vehicle identification information is encrypted, a decryption algorithm can be used to parse and decrypt the vehicle identification information to restore the vehicle identification code. For example, the vehicle identification information is the encrypted string "ABC123XYZ", and after decryption, the VIN number "1234567890ABCDEF" is obtained.

[0048] If the vehicle-mounted device's identification information is encrypted, a decryption algorithm can be used to parse and decrypt the vehicle-mounted device's identification information to restore the vehicle-mounted device's identification code. For example, the vehicle-mounted device's identification information is the encrypted string "DEV987654," which can be decrypted to obtain the device serial number SN "DEVICE001."

[0049] In the disclosed embodiments, the decryption algorithm is a computational method for restoring encrypted vehicle identification information and vehicle-mounted device identification information to the original identification code. The decryption algorithm can be used in conjunction with the encryption algorithm. Symmetric encryption algorithms, such as the AES algorithm, can be used, where the same key is used for encryption and decryption. Asymmetric encryption algorithms, such as the RSA algorithm, can also be used, where different keys are used for encryption and decryption. Of course, other algorithms, such as the MD5 algorithm, can also be used, and this is not limited in the disclosed embodiments.

[0050] In step S230, the vehicle-mounted device identification code bound to the vehicle identification code is searched in the database; the database is used to store the binding relationship between the vehicle identification code and the vehicle-mounted device identification code, and the binding relationship in the database is generated and reported by the vehicle diagnostic device.

[0051] In the disclosed embodiments, the database may be referred to as a legal binding relationship database, which is used to store the binding relationships between vehicle identification codes and vehicle-mounted device identification codes. This database is maintained and generated by a legal binding relationship maintenance platform. After generating the database, the legal binding relationship maintenance platform pushes it to the service broadcast platform, which then queries the database to determine whether the vehicle and the vehicle-mounted device are bound.

[0052] In an exemplary embodiment of the present disclosure, the database may be generated according to the following process:

[0053] (1) During the vehicle production line, the vehicle diagnostic equipment will read the vehicle identification code (such as VIN). This identification code serves as the vehicle's unique identity and can accurately distinguish each vehicle. At the same time, the vehicle diagnostic equipment will also read the identification code (such as the SN) of the on-board equipment that carries related service functions. The identification code of each on-board equipment is also unique and is used to determine the identity information of the on-board equipment.

[0054] (2) The vehicle diagnostic device obtains the vehicle identification code and the identification code of the on-board device and then associates and binds them. This binding relationship can be based on the actual assembly relationship between the vehicle and the corresponding on-board device, ensuring that each vehicle and its installed on-board device form a corresponding relationship;

[0055] (3) After the binding operation is completed, the vehicle diagnostic device uploads the data to the legal binding relationship database; when receiving the data, the database will structure the binding relationship information between the vehicle identification code and the vehicle-mounted device identification code according to the established data format and storage rules, for example, recording the binding relationship in a table form, with each row of data representing an independent binding relationship, including the corresponding vehicle identification code, vehicle-mounted device identification code, and auxiliary information such as data upload time and upload device identification, so as to facilitate subsequent data management and query operations;

[0056] (4) As more vehicle and on-board equipment data are uploaded to the production line, the database will continue to be updated and expanded, gradually building an information collection that records the legal binding relationship between vehicles and on-board equipment, providing reliable data support for the broadcast service platform to verify the legitimacy of the equity account.

[0057] In an exemplary embodiment of the present disclosure, when the on-board device corresponding to the vehicle is replaced, the binding relationship in the database can be updated as follows: after the on-board device is replaced, the vehicle diagnostic device reads the identification information of the replaced on-board device and the identification information of the vehicle, generates a new binding relationship, and generates an update request; the vehicle diagnostic device reports the new binding relationship to the legal binding relationship database and sends an update request to the database; after receiving the update request, the database verifies the legality of the new binding relationship. If the new binding relationship passes the legality check, the database will replace the original binding relationship with the new binding relationship, and record auxiliary information such as the update time and the operating device identification; after the database completes the binding relationship update, it will synchronously feed back the update results to the service broadcasting platform to ensure the accuracy of subsequent service rights verification.

[0058] In the disclosed embodiment, after the service playback platform obtains the vehicle identification code, it searches the database for all vehicle-mounted device identification codes that are bound to the vehicle identification code. For example, if the vehicle's VIN number is "1234567890ABCDEF," the vehicle-mounted device identification codes that are bound to the VIN number found in the database are "DEVICE001" and "TBOX002."

[0059] In step S240 , in response to the queried in-vehicle device identification code including the in-vehicle device identification code, it is determined that there is a binding relationship between the vehicle and the in-vehicle device.

[0060] In the disclosed embodiment, the identification code of the vehicle-mounted device obtained in step S220 is compared with the identification code of the bound vehicle-mounted device queried in step S230. If the identification code of the bound vehicle-mounted device queried includes the identification code of the vehicle-mounted device, it indicates that a binding relationship exists between the vehicle and the vehicle-mounted device. If the identification code of the bound vehicle-mounted device queried does not include the identification code of the vehicle-mounted device, it indicates that no binding relationship exists between the vehicle and the vehicle-mounted device.

[0061] For example, the identification code of the vehicle-mounted device is "DEVICE001", and the queried bound vehicle-mounted device identification codes include "DEVICE001" and "TBOX002". Since "DEVICE001" is among the queried identification codes, it is determined that there is a binding relationship between the vehicle and the vehicle-mounted device.

[0062] Through the above steps, the identification information of the vehicle and the onboard device is decrypted to obtain the vehicle identification code and the onboard device identification code. Then, the onboard device identification code bound to the vehicle identification code is searched in the database. Then, by comparing the onboard device identification code with the query result, it is determined whether the vehicle and the onboard device are bound. In this way, the binding relationship between the onboard device and the vehicle can be accurately verified, and the decision on whether to allow login is made. This ensures the legitimacy of service rights and data security, while avoiding account conflicts and service data anomalies.

[0063] In some embodiments of the present disclosure, before determining that the login request verification is successful, the login verification method also includes: generating a dynamic verification code and sending the dynamic verification code to a terminal device associated with the vehicle; obtaining a verification code input through the vehicle-mounted device; and determining that the login request verification is successful in response to the input verification code matching the dynamic verification code.

[0064] In the disclosed embodiment, in addition to verifying the binding relationship, dynamic verification code verification may also be included. Exemplarily, after verifying that there is a binding relationship between the vehicle and the on-board device, the service broadcasting platform generates a dynamic verification code, and the verification code is time-sensitive, and the generated dynamic verification code is sent to the terminal device associated with the vehicle, such as the user's mobile phone, car computer or other bound devices, wherein the sending method may include SMS, push notification, email, etc. The user can enter the received dynamic verification code on the on-board device, and the on-board device uploads the verification code entered by the user to the service broadcasting platform. The service broadcasting platform then compares the verification code entered by the user with the generated dynamic verification code. If the entered verification code matches the dynamic verification code, and the verification code is within the validity period, the verification code verification passes, and it is determined that the login request verification passes. If there is no match, the verification code verification fails, and it is determined that the login request verification fails.

[0065] In some embodiments of the present disclosure, before determining whether the login request verification is successful, the login verification method also includes: obtaining user feature information collected by the vehicle-mounted device; verifying whether the user feature information matches the pre-registered feature information; and determining that the login request verification is successful in response to the user feature information matching the pre-registered feature information.

[0066] In the disclosed embodiment, in addition to verifying the binding relationship, user feature information verification may also be included. Exemplarily, after verifying that there is a binding relationship between the vehicle and the on-board device, the on-board device collects user feature information, such as fingerprints, facial features, voiceprints, etc., through built-in sensors or external devices, and uploads the collected user feature information to the service broadcasting platform. The service broadcasting platform then compares the uploaded user feature information with the feature information pre-registered by the user. The comparison process may use feature extraction and matching algorithms, for example, for fingerprint verification, a fingerprint recognition algorithm is used, for facial recognition, a face recognition algorithm is used, and for voiceprint verification, a voiceprint recognition algorithm is used. If the uploaded user feature information matches the feature information pre-registered by the user, the user feature information verification passes, and it is determined that the login request verification passes. If there is no match, the user feature information verification fails, and it is determined that the login request verification fails.

[0067] Through the above steps, the login verification method of the disclosed embodiment can include dynamic verification code verification and user profile verification, further enhancing the security of login verification. Dynamic verification code verification ensures the legitimacy of the login request by generating and comparing a one-time password; user profile verification ensures the legitimacy of the user's identity by comparing biometric or behavioral characteristics. These two verification mechanisms, combined with binding relationship verification, achieve multi-layered, multi-factor security authentication, providing reliable security for smart car service applications.

[0068] In some embodiments of the present disclosure, after determining that the login request verification is successful, the login verification method further includes: obtaining operating status information of the vehicle-mounted device; and generating an operating status report of the vehicle-mounted device based on the operating status information of the vehicle-mounted device.

[0069] In the disclosed embodiment, the operating status information of the vehicle-mounted equipment may include hardware status, such as CPU usage, memory occupancy, storage space, network connection status, etc., may include software status, such as operating system version, application running status, error log, etc., and may also include service status, such as service connection status, data transmission status, etc.

[0070] In the disclosed embodiments, the operating status report of the vehicle-mounted device may include device health status, detailed hardware and software status data, and records of abnormal or error information. This operating status report can be used for: troubleshooting, helping technicians quickly locate device problems; performance optimization, optimizing service delivery strategies based on device status; and preventive maintenance, identifying potential problems in advance and avoiding service interruptions.

[0071] Through the above steps, after the login request is verified, its operating status information can be obtained from the vehicle-mounted device, and then an operating status report of the vehicle-mounted device can be generated based on the obtained operating status information, so as to obtain the operating status of the vehicle-mounted device, ensure the stability and reliability of the service, and provide data support to help optimize device performance and service distribution strategies.

[0072] In some embodiments of the present disclosure, the login verification method further includes: in response to the absence of a binding relationship between the vehicle and the on-board device, determining that the login request verification fails; and recording information on the vehicle verification failure and the on-board device verification failure.

[0073] In the embodiment of the present disclosure, if there is no binding relationship between the vehicle and the on-board device, it can be determined that the login request verification failed, and the information that the vehicle verification failed and the information that the on-board device verification failed are recorded. The recorded information may include: the identification code of the vehicle, the identification code of the on-board device, the timestamp of the verification failure, and the reason for the verification failure, such as the binding relationship does not exist. For example, the vehicle VIN number is "1234567890ABCDEF", the on-board device SN number is "DEVICE002", and the verification fails, then the record is: {VIN:"1234567890ABCDEF",SN:"DEVICE002",Time:"2023-10-01 12:00:00",Reason:"Binding relationship does not exist"}.

[0074] In some embodiments of the present disclosure, the login verification method further includes: counting the first number of times the vehicle fails verification within a first preset time based on the information of failed vehicle verification; and in response to the first number exceeding the first preset number, determining to check the binding relationship corresponding to the vehicle.

[0075] In the disclosed embodiment, based on the recorded vehicle verification failure information, a first number of verification failures for the vehicle within a first preset time period (e.g., 24 hours) may be determined. If the first number exceeds the first preset number (e.g., 3 times), it may be determined that the binding relationship corresponding to the vehicle is to be checked.

[0076] In the disclosed embodiment, the binding relationship between the vehicle identification code and the vehicle-mounted device identification code is stored in a database, which is maintained and generated by a legal binding relationship maintenance platform and then pushed to a service broadcasting platform. Therefore, after determining to verify the binding relationship corresponding to the vehicle, it is pushed to the service broadcasting platform to send a verification request to the legal binding relationship maintenance platform to verify the binding relationship corresponding to the vehicle. The verification content may include but is not limited to: checking whether the binding relationship is correct, checking whether the vehicle identification information has been tampered with, and checking whether the vehicle-mounted device has been replaced or damaged. If the legal binding relationship maintenance platform verifies that the binding relationship is abnormal, the binding relationship can be updated. For example, if the vehicle VIN number "1234567890ABCDEF" fails to pass verification 4 times within 24 hours, it may trigger the legal binding relationship maintenance platform to verify the binding relationship of the vehicle, find that the binding relationship of the vehicle is abnormal, update the binding relationship and notify the user.

[0077] In some embodiments of the present disclosure, the login verification method further includes: counting a second number of times the vehicle-mounted device fails verification within a second preset time based on information about failed verification of the vehicle-mounted device; and in response to the second number exceeding the second preset number, starting a disabling mechanism for the vehicle-mounted device.

[0078] In the embodiment of the present disclosure, the second number of times the vehicle-mounted device fails to pass verification within a second preset time (such as 24 hours) can be counted based on the recorded information on the vehicle-mounted device's failed verification. If the second number exceeds the second preset number (such as 4 times), a disabling mechanism can be activated for the vehicle-mounted device. Exemplarily, the disabling mechanism may include but is not limited to: prohibiting the vehicle-mounted device from logging into the service broadcasting platform, blacklisting the vehicle-mounted device, and notifying the administrator or user to handle it. For example, if the vehicle-mounted device SN number is "DEVICE002" and fails to pass verification 6 times within 24 days, the vehicle-mounted device is prohibited from logging in, and the user is notified to contact technical support.

[0079] Through the above steps, after the login request verification fails, the verification failure information is recorded, and then the number of vehicle verification failures can be counted based on the verification failure information, and binding relationship anomalies can be discovered in time to ensure the accuracy of the binding relationship. The number of vehicle-mounted device verification failures can also be counted based on the verification failure information, abnormal vehicle-mounted devices can be identified, malicious logins or abuse of vehicle-mounted devices can be prevented, and the legitimate rights and interests of the service platform can be protected.

[0080] Figure 3 FIG1 is a flow chart of another login verification method according to some embodiments of the present disclosure. The execution subject of the login verification method may be an in-vehicle device. Figure 3 , the login verification method may include the following steps.

[0081] In step S310, a login request is sent; the login request includes identification information of the vehicle-mounted device and identification information of the vehicle corresponding to the vehicle-mounted device.

[0082] In the disclosed embodiments, the in-vehicle devices may include, but are not limited to, a vehicle computer (in-vehicle infotainment system), a T-Box (telematics control system), a smart rearview mirror, an in-vehicle gateway, an intelligent cockpit controller, an on-board diagnostic device, and a user's mobile device. The in-vehicle devices interact with the service delivery platform and log in using a service rights account to obtain data services, thereby realizing the functions of the smart car.

[0083] In the embodiment of the present disclosure, the vehicle corresponding to the vehicle-mounted device can be understood as a vehicle that has an associated relationship with the vehicle-mounted device, for example, the vehicle-mounted device is installed on the vehicle, or the function of the vehicle is tested by the vehicle-mounted device.

[0084] In the embodiment of the present disclosure, the identification information of the vehicle-mounted device is used to uniquely identify the vehicle-mounted device, and the identification information of the vehicle is used to uniquely identify the vehicle.

[0085] In step S320, a verification result of the login request is received; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the onboard device based on the identification information of the vehicle and the identification information of the onboard device.

[0086] In the disclosed embodiment, the vehicle-mounted device sends a login request to the service broadcast platform. The login request includes the identification information of the vehicle-mounted device and the identification information of the vehicle corresponding to the vehicle-mounted device. Therefore, after receiving the login request, the service broadcast platform can obtain the identification information of the vehicle-mounted device and the identification information of the vehicle device, and then use these two identification information to verify whether there is a binding relationship between the vehicle-mounted device and the vehicle, determine the verification result, and then send the verification result to the vehicle-mounted device.

[0087] For example, if the in-vehicle device and the vehicle's identification information verify that the in-vehicle device is bound to the vehicle, the verification result is determined to be a successful login request. If the in-vehicle device and the vehicle are not bound to each other, the verification result is determined to be a failed login request. Verification of the binding relationship has been described in the above embodiment and will not be repeated here.

[0088] In some embodiments of the present disclosure, before sending a login request, it also includes: obtaining the vehicle's identification code and the vehicle-mounted device's identification code; encrypting the vehicle's identification code to obtain the vehicle's identification information; encrypting the vehicle's identification code to obtain the vehicle's identification information; and generating a login request based on the vehicle's identification information and the vehicle-mounted device's identification information.

[0089] In the disclosed embodiments, an encryption algorithm can be used to encrypt a vehicle's identification code to obtain vehicle identification information. For example, the vehicle's VIN number "1234567890ABCDEF" can be encrypted to obtain the identification information "ABC123XYZ." Furthermore, an encryption algorithm can be used to encrypt an onboard device's identification code to obtain the device's identification information. For example, the onboard device's serial number SN "DEVICE001" can be encrypted to obtain the identification information "DEV987654."

[0090] In the disclosed embodiments, an encryption algorithm is a computational method for encrypting the identification code of the vehicle-mounted device and the identification code of the vehicle to obtain identification information. The encryption algorithm can be used in conjunction with a decryption algorithm. Symmetric encryption algorithms, such as the AES algorithm, can be used, where the same key is used for encryption and decryption. Asymmetric encryption algorithms, such as the RSA algorithm, can also be used, where different keys are used for encryption and decryption. Of course, other algorithms, such as the MD5 algorithm, can also be used, and this is not limited in the disclosed embodiments.

[0091] Figure 4 FIG. 1 is a schematic diagram of the architecture of a login verification system according to some embodiments of the present disclosure. Figure 4 As shown, the system includes a legal relationship maintenance platform, a service broadcasting platform, a vehicle, and an onboard device. The vehicle uses a VIN number as a unique identification code, and the onboard device uses a device serial number SN as a unique identification code.

[0092] like Figure 4 As shown, the legal relationship maintenance platform can generate a legal binding relationship database and push the legal binding relationship database to the service broadcasting platform, so that the service broadcasting platform can verify the rights and interests of the service broadcasting platform based on the database. The database can be generated according to the following process:

[0093] (1) During the vehicle production line, the vehicle diagnostic equipment will read the vehicle identification code (such as VIN). This identification code serves as the vehicle's unique identity and can accurately distinguish each vehicle. At the same time, the vehicle diagnostic equipment will also read the identification code (such as the SN) of the on-board equipment that carries related service functions. The identification code of each on-board equipment is also unique and is used to determine the identity information of the on-board equipment.

[0094] (2) The vehicle diagnostic device obtains the vehicle identification code and the identification code of the on-board device and then associates and binds them. This binding relationship can be based on the actual assembly relationship between the vehicle and the corresponding on-board device, ensuring that each vehicle and its installed on-board device form a corresponding relationship;

[0095] (3) After the binding operation is completed, the vehicle diagnostic device uploads the data to the legal binding relationship database; when receiving the data, the database will structure the binding relationship information between the vehicle identification code and the vehicle-mounted device identification code according to the established data format and storage rules, for example, recording the binding relationship in a table form, with each row of data representing an independent binding relationship, including the corresponding vehicle identification code, vehicle-mounted device identification code, and auxiliary information such as data upload time and upload device identification, so as to facilitate subsequent data management and query operations;

[0096] (4) As more vehicle and on-board equipment data are uploaded to the production line, the database will continue to be updated and expanded, gradually building an information collection that records the legal binding relationship between vehicles and on-board equipment, providing reliable data support for the broadcast service platform to verify the legitimacy of the equity account.

[0097] In an exemplary embodiment of the present disclosure, when the on-board device corresponding to the vehicle is replaced, the binding relationship in the database can be updated as follows: after the on-board device is replaced, the vehicle diagnostic device reads the identification information of the replaced on-board device and the identification information of the vehicle, generates a new binding relationship, and generates an update request; the vehicle diagnostic device reports the new binding relationship to the legal binding relationship database and sends an update request to the database; after receiving the update request, the database verifies the legality of the new binding relationship. If the new binding relationship passes the legality check, the database will replace the original binding relationship with the new binding relationship, and record auxiliary information such as the update time and the operating device identification; after the database completes the binding relationship update, it will synchronously feed back the update results to the service broadcasting platform to ensure the accuracy of subsequent service rights verification.

[0098] like Figure 4 As shown, the vehicle-mounted device has the service platform login function and sends a login request to the service broadcast platform. The login request includes the vehicle VIN number and the vehicle-mounted device SN number. For information security reasons, the vehicle VIN number can be encrypted to obtain f(vin), and the vehicle-mounted device SN number can be encrypted to obtain the legal binding relationship f(sn). After receiving the login request from the vehicle-mounted device, the service broadcast platform performs a binding legality verification on the vehicle-mounted device f(sn) and the vehicle f(vin) in the login request based on the legal binding relationship database to determine whether the binding relationship is legal, thereby verifying the rights and interests of the service broadcast platform account.

[0099] In the login verification method provided by the disclosed embodiments, a login request sent by an on-board device includes the identification information of the on-board device and the identification information of the vehicle associated with the on-board device. Upon receiving the login request, the service broadcast platform can verify whether there is a binding relationship between the vehicle and the on-board device based on the identification information of the vehicle and the on-board device. If so, the login request is verified and the on-board device is allowed to log in. By verifying the binding relationship between the vehicle and the on-board device, only the on-board device bound to the vehicle can successfully log in, thereby effectively avoiding account login conflicts and ensuring that service data can be broadcast to the on-board device.

[0100] It should be noted that the above figures are merely illustrative of the processes included in the methods according to some embodiments of the present disclosure and are not intended to be limiting. It is readily understood that the processes illustrated in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0101] The following are embodiments of the apparatus disclosed herein, which can be used to implement the method embodiments disclosed herein. For details not disclosed in the apparatus embodiments disclosed herein, please refer to the method embodiments disclosed herein.

[0102] Figure 5 1 is a block diagram of a login verification device according to some embodiments of the present disclosure. Figure 5 The login verification device 500 includes: a request receiving module 510, a verification module 520 and a determination module 530.

[0103] The request receiving module 510 is configured to receive a login request from the vehicle-mounted device; the login request includes the vehicle identification information corresponding to the vehicle-mounted device and the identification information of the vehicle-mounted device. The verification module 520 is configured to verify whether a binding relationship exists between the vehicle and the vehicle-mounted device based on the vehicle identification information and the identification information of the vehicle-mounted device. The determination module 530 is configured to determine whether the login request has been verified in response to a binding relationship between the vehicle and the vehicle-mounted device.

[0104] In some embodiments of the present disclosure, the verification module 520 is further configured to: obtain the vehicle identification code based on the vehicle identification information, and obtain the identification code of the on-board device based on the identification information of the on-board device; query the on-board device identification code bound to the vehicle identification code in the database; the database is used to store the binding relationship between the vehicle identification code and the on-board device identification code, and the binding relationship in the database is generated and reported by the vehicle diagnostic device; in response to the queried on-board device identification code including the identification code of the on-board device, it is determined that there is a binding relationship between the vehicle and the on-board device.

[0105] In some embodiments of the present disclosure, the verification module 520 is further configured to: decrypt the identification information of the vehicle to obtain the identification code of the vehicle; decrypt the identification information of the vehicle-mounted device to obtain the identification code of the vehicle-mounted device.

[0106] In some embodiments of the present disclosure, Figure 5 As shown, the device 500 further includes an information acquisition module 540 configured to: acquire the operating status information of the vehicle-mounted device; and generate an operating status report of the vehicle-mounted device according to the operating status information of the vehicle-mounted device.

[0107] In some embodiments of the present disclosure, the determination module 530 is further configured to: determine that the login request verification fails in response to the absence of a binding relationship between the vehicle and the on-board device; and record information on the vehicle verification failure and the on-board device verification failure.

[0108] In some embodiments of the present disclosure, the determination module 530 is further configured to: count the first number of times the vehicle fails verification within a first preset time based on the information that the vehicle fails verification; and determine to check the binding relationship corresponding to the vehicle in response to the first number exceeding the first preset number.

[0109] In some embodiments of the present disclosure, the determination module 530 is further configured to: count the second number of times the vehicle-mounted device fails verification within a second preset time based on the information of the vehicle-mounted device failing verification; and activate a disabling mechanism for the vehicle-mounted device in response to the second number exceeding the second preset number.

[0110] Figure 6 FIG. 1 is a block diagram of another login verification device according to some embodiments of the present disclosure. Figure 6 The login verification device 600 includes: a request sending module 610 and a result receiving module 620.

[0111] The request sending module 610 is configured to send a login request, which includes the identification information of the vehicle-mounted device and the identification information of the vehicle corresponding to the vehicle-mounted device. The result receiving module 620 is configured to receive a verification result of the login request, which is obtained by verifying whether a binding relationship exists between the vehicle and the vehicle-mounted device based on the identification information of the vehicle and the vehicle-mounted device.

[0112] In some embodiments of the present disclosure, the request sending module 610 is also configured to: obtain the vehicle's identification code and the vehicle-mounted device's identification code; encrypt the vehicle's identification code to obtain the vehicle's identification information; encrypt the vehicle's identification code to obtain the vehicle's identification information; and generate a login request based on the vehicle's identification information and the vehicle-mounted device's identification information.

[0113] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0114] Figure 7 This is a block diagram of an electronic device according to some embodiments of the present disclosure. The electronic device 700 can be various types of electronic devices, such as a server or cloud of a service broadcasting platform, an in-vehicle device, a vehicle electronic control unit, a mobile device, a communication network device, an identity verification device, etc.

[0115] Reference Figure 7 , apparatus 700 may include one or more of the following components: a processing component 702 , a memory 704 , a power component 706 , a multimedia component 708 , an audio component 710 , an input / output (I / O) interface 712 , a sensor component 714 , and a communication component 716 .

[0116] The processing component 702 generally controls the overall operation of the device 700, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 702 may include one or more processors 720 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 702 may include one or more modules to facilitate interaction between the processing component 702 and other components. For example, the processing component 702 may include a multimedia module to facilitate interaction between the multimedia component 708 and the processing component 702.

[0117] The memory 704 is configured to store various types of data to support operations on the device 700. Examples of such data include instructions for any application or method operating on the device 700, contact data, phone book data, messages, pictures, videos, etc. The memory 704 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, magnetic disk, or optical disk.

[0118] The power supply component 706 provides power to the various components of the device 700. The power supply component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 700.

[0119] The multimedia component 708 includes a screen that provides an output interface between the device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 708 includes a front camera and / or a rear camera. When the device 700 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0120] The audio component 710 is configured to output and / or input audio signals. For example, the audio component 710 includes a microphone (MIC), which is configured to receive external audio signals when the device 700 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 704 or transmitted via the communication component 716. In some embodiments, the audio component 710 also includes a speaker for outputting audio signals.

[0121] I / O interface 712 provides an interface between processing component 702 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include but are not limited to: a home button, volume buttons, a start button, and a lock button.

[0122] The sensor assembly 714 includes one or more sensors for providing various aspects of the status assessment of the device 700. For example, the sensor assembly 714 can detect the open / closed state of the device 700, the relative positioning of components, such as the display and keypad of the device 700. The sensor assembly 714 can also detect changes in the position of the device 700 or a component of the device 700, the presence or absence of user contact with the device 700, the orientation or acceleration / deceleration of the device 700, and temperature changes of the device 700. The sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 714 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 714 may also include a magnetic sensor, a pressure sensor, or a temperature sensor.

[0123] The communication component 716 is configured to facilitate wired or wireless communication between the device 700 and other devices. The device 700 can access a wireless network based on a communication standard, such as WiFi, 3G, 4G, 5G, other communication standards, or a combination thereof. In some embodiments of the present disclosure, the communication component 716 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of the present disclosure, the communication component 716 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0124] In some embodiments of the present disclosure, the apparatus 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described methods.

[0125] In some embodiments of the present disclosure, a non-transitory computer-readable storage medium including instructions is further provided, such as a memory 704 including instructions, and the instructions can be executed by the processor 720 of the apparatus 700 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0126] The embodiment of the present disclosure provides a non-temporary computer-readable storage medium, which enables the mobile terminal to execute a login verification method when the instructions in the storage medium are executed by the processor of the mobile terminal. The method includes: receiving a login request sent by an on-board device; the login request includes the identification information of the on-board device and the identification information of the vehicle corresponding to the on-board device; verifying whether there is a binding relationship between the vehicle and the on-board device based on the identification information of the vehicle and the identification information of the on-board device; in response to the existence of a binding relationship between the vehicle and the on-board device, determining that the login request verification is successful. Alternatively, the method includes: sending a login request; the login request includes the identification information of the on-board device and the identification information of the vehicle corresponding to the on-board device; receiving a verification result of the login request; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the on-board device based on the identification information of the vehicle and the identification information of the on-board device.

[0127] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0128] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A login verification method, characterized in that: The method comprises: Receiving a login request sent by an on-board device; the login request includes identification information of the on-board device and identification information of a vehicle corresponding to the on-board device; Verifying whether a binding relationship exists between the vehicle and the in-vehicle device according to the identification information of the vehicle and the identification information of the in-vehicle device; In response to a binding relationship between the vehicle and the in-vehicle device, it is determined that the login request is successfully verified.

2. The method according to claim 1, characterized in that The verifying, based on the identification information of the vehicle and the identification information of the in-vehicle device, whether a binding relationship exists between the vehicle and the in-vehicle device includes: Acquire an identification code of the vehicle according to the identification information of the vehicle, and acquire an identification code of the onboard device according to the identification information of the onboard device; Querying a database for an on-board device identification code that is bound to the vehicle identification code; the database is used to store a binding relationship between the vehicle identification code and the on-board device identification code, wherein the binding relationship in the database is generated and reported by the vehicle diagnostic device; In response to the queried in-vehicle device identification code including the identification code of the in-vehicle device, it is determined that a binding relationship exists between the vehicle and the in-vehicle device.

3. The method according to claim 2, characterized in that The acquiring the identification code of the vehicle according to the identification information of the vehicle, and acquiring the identification code of the onboard device according to the identification information of the onboard device, includes: Decrypting the identification information of the vehicle to obtain an identification code of the vehicle; The identification information of the vehicle-mounted device is decrypted to obtain an identification code of the vehicle-mounted device.

4. The method according to claim 1, wherein After determining that the login request is verified, the method further includes: Obtaining operating status information of the vehicle-mounted device; Generate an operating status report of the vehicle-mounted device according to the operating status information of the vehicle-mounted device.

5. The method according to claim 1, wherein The method further comprises: In response to the absence of a binding relationship between the vehicle and the in-vehicle device, determining that the login request verification fails; Record the information that the vehicle verification fails and the information that the vehicle-mounted device verification fails.

6. The method according to claim 5, characterized in that The method further comprises: According to the information of the vehicle failing verification, counting a first number of times the vehicle fails verification within a first preset time; In response to the first number exceeding a first preset number, it is determined to check the binding relationship corresponding to the vehicle.

7. The method according to claim 5, characterized in that The method further comprises: According to the information that the on-board device fails to be verified, counting a second number of times that the on-board device fails to be verified within a second preset time; In response to the second number exceeding a second preset number, a disabling mechanism is initiated for the in-vehicle device.

8. A login verification method, characterized in that: The method comprises: Sending a login request; the login request includes identification information of the vehicle-mounted device and identification information of the vehicle corresponding to the vehicle-mounted device; Receive a verification result of the login request; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the onboard device based on the identification information of the vehicle and the identification information of the onboard device.

9. The method according to claim 8, characterized in that Before sending the login request, the method further includes: Obtaining an identification code of the vehicle and an identification code of the vehicle-mounted device; Encrypting the identification code of the vehicle to obtain identification information of the vehicle; encrypting the identification code of the vehicle-mounted device to obtain identification information of the vehicle-mounted device; The login request is generated according to the identification information of the vehicle and the identification information of the vehicle-mounted device.

10. A login verification device, characterized in that: The device comprises: A request receiving module is configured to receive a login request sent by an on-board device; the login request includes identification information of a vehicle corresponding to the on-board device and identification information of the on-board device; a verification module configured to verify whether a binding relationship exists between the vehicle and the onboard device based on the identification information of the vehicle and the identification information of the onboard device; The determination module is configured to determine whether the login request is verified in response to a binding relationship between the vehicle and the vehicle-mounted device.

11. A login verification device, characterized in that: The device comprises: A request sending module is configured to send a login request; the login request includes identification information of the vehicle-mounted device and identification information of the vehicle corresponding to the vehicle-mounted device; The result receiving module is configured to receive the verification result of the login request; the verification result is obtained by verifying whether there is a binding relationship between the vehicle and the onboard device based on the identification information of the vehicle and the identification information of the onboard device.

12. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the login verification method according to any one of claims 1 to 7, or the login verification method according to claim 8 or 9.

13. A non-temporary computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to execute the login verification method described in any one of claims 1 to 7, or the login verification method described in claim 8 or 9.

Images