CN116611042A

CN116611042A - Vehicle account protection method, electronic equipment and storage medium

Info

Publication number: CN116611042A
Application number: CN202310456383.2A
Authority: CN
Inventors: 汪浩
Original assignee: Pateo Connect Nanjing Co Ltd
Current assignee: Pateo Connect Nanjing Co Ltd
Priority date: 2023-04-25
Filing date: 2023-04-25
Publication date: 2023-08-18

Abstract

The embodiment of the application provides a vehicle account protection method, electronic equipment and a storage medium. The vehicle account protection method comprises the following steps: the method comprises the steps that a vehicle terminal responds to the success of automatic login of a current account number, and the first face feature of a current user at a main driving position in a vehicle is obtained; comparing the first face features with the second face features bound with the current account; determining the user type of the current user in response to inconsistent comparison of the first face feature and the second face feature; and responding to the current user to operate a current function item, and determining the operation authority of the current user on the current function item based on the user type. In the embodiment of the application, under the condition that the current user at the main driving position is not the logged-in current account number owner, the current account number can be effectively protected, and the loss to the current account number owner is avoided.

Description

Vehicle account protection method, electronic equipment and storage medium

Technical Field

The present application relates to the field of internet of vehicles, and in particular, to a vehicle account protection method, an electronic device, and a storage medium.

Background

With the rapid development of internet of vehicles, vehicles are often equipped with an on-board intelligent vehicle terminal, which can provide various functional items for users to use, such as navigation, multimedia, and the like.

In order to meet the personalized demands of users, the vehicle-mounted terminal usually supports account login, the user can register own account, after logging in the vehicle-mounted terminal, related function items can be operated under own account, the system records personalized settings of the users, and after the subsequent account is automatically logged in, the personalized settings of the users are loaded, so that personalized user services are realized.

However, when other users use the vehicle, after the vehicle terminal automatically logs in a certain account, the current user can also use the automatically logged-in account, so that the account cannot be protected, and the account owner is lost.

Disclosure of Invention

In view of the above problems, an embodiment of the application provides a vehicle account protection method, electronic equipment and storage medium, which are used for solving the technical problem that a vehicle account cannot be protected.

According to an aspect of an embodiment of the present application, there is provided a vehicle account protection method applied to a vehicle terminal, the method including:

Responding to the success of automatic login of the current account number, and acquiring the first face feature of the current user at the main driving position in the vehicle;

comparing the first face features with the second face features bound with the current account;

determining the user type of the current user in response to inconsistent comparison of the first face feature and the second face feature;

and responding to the current user to operate a current function item, and determining the operation authority of the current user on the current function item based on the user type.

Optionally, before determining the user type of the current user, the method further includes: responding to inconsistent comparison between the first face features and the second face features, and sending prompt information for prompting the current user to switch accounts; the determining the user type of the current user comprises the following steps: and determining the user type of the current user in response to the current user not switching the account.

Optionally, after comparing the first face feature with the second face feature bound to the current account, the method further includes: and generating account alarming information in response to inconsistent comparison between the first face features and the second face features, and transmitting the account alarming information to the mobile terminal bound with the current account.

Optionally, before generating the account alarm information, the method further includes: acquiring a third face feature of a user at other positions except the main driving position in the vehicle, and comparing the third face feature with the second face feature; the generating account alarm information comprises the following steps: generating account alarm information in response to inconsistent comparison between the third face features and the second face features; or, before generating the account alarm information, the method further comprises the following steps: acquiring a fourth face feature of a user outside the vehicle, and comparing the fourth face feature with the second face feature; the generating account alarm information comprises the following steps: and generating account alarm information in response to inconsistent comparison between the fourth face feature and the second face feature.

Optionally, after transmitting the account alert information to the mobile terminal bound to the current account, the method further includes: responding to the received account exit request, and exiting the current account; the account exit request is sent by the mobile terminal.

Optionally, after exiting the current account, the method further includes: and clearing the used times of the first face feature under the current account number, wherein the used times are used for determining the user type of the current user.

Optionally, the determining the user type of the current user includes: acquiring the used times of the first face feature under the current account; determining that the user type of the current user is an intimate user in a non-owner of the current account in response to the number of times of use exceeding a preset threshold; and determining that the user type of the current user is a common user in a non-owner of the current account number in response to the used times not exceeding the preset threshold.

Optionally, the user type includes an intimate user in a non-owner of the current account and a common user in the non-owner of the current account; the determining the operation authority of the current user to the current function item based on the user type comprises the following steps: responding to the user type as an intimate user in a non-owner of the current account, judging that the current function item belongs to a preset first safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user; responding to the user type as a common user in a non-owner of the current account, judging that the current function item belongs to a preset second safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user; wherein the first security function item includes the second security function item and a third security function item, the third security function item being of higher importance than the second security function item.

According to another aspect of an embodiment of the present application, there is provided an electronic apparatus including: one or more processors; and one or more computer-readable storage media having instructions stored thereon; the instructions, when executed by the one or more processors, cause the processor to perform the vehicle account protection method of any one of the above.

According to another aspect of an embodiment of the present application, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the vehicle account number protection method as any one of the above.

In the embodiment of the application, a vehicle terminal responds to the success of automatic login of a current account number and acquires the first face feature of a current user at the main driving position in a vehicle; comparing the first face features with the second face features bound with the current account; determining the user type of the current user in response to inconsistent comparison of the first face feature and the second face feature; and responding to the current user to operate a current function item, and determining the operation authority of the current user on the current function item based on the user type. Therefore, in the embodiment of the application, under the condition that the current user at the main driving position is not the logged-in current account owner, the vehicle terminal can determine the operation authority of the current user under the current account according to the user type of the current user, so that different operation authorities are given to different user types, effective protection of the current account is realized, for example, the current user is forbidden to use the functional items with higher security requirements, such as money, and the loss to the current account owner is avoided.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some drawings of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a system architecture diagram of an embodiment of the present application.

Fig. 2 is a flowchart illustrating steps of a method for protecting a vehicle account according to an embodiment of the present application.

Fig. 3 is a flowchart illustrating steps of another method for protecting a vehicle account according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a first process according to an embodiment of the present application.

Fig. 5 is a schematic diagram of a second process according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a third process according to an embodiment of the present application.

Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The vehicle account protection method in the embodiment of the application can be applied to the system architecture as shown in fig. 1. As shown in fig. 1, the system architecture includes a vehicle terminal and a mobile terminal. The vehicle terminal can be in bidirectional communication with the mobile terminal.

The vehicle terminal is a vehicle-mounted intelligent terminal, is a vehicle-mounted information entertainment product arranged in a vehicle, and can provide various functions such as navigation, multimedia, communication and the like.

The mobile terminal may include, but is not limited to: smart phones, notebook computers, tablet computers, desktop computers, and the like.

In some possible scenarios, the system architecture may further include a cloud server. The vehicle terminal can be in bidirectional communication with the cloud server, the cloud server can be in bidirectional communication with the mobile terminal, and interaction between the vehicle terminal and the mobile terminal can be performed through the cloud server. The cloud server may be an independent server or a server cluster composed of a plurality of servers.

Referring to fig. 2, a flowchart of steps of a method for protecting a vehicle account according to an embodiment of the present application is shown.

As shown in fig. 2, the vehicle account protection method may include the steps of:

In step 201, the vehicle terminal responds to the success of automatic login of the current account number, and obtains the first face feature of the current user at the main driving position in the vehicle.

In the embodiment of the application, if the vehicle terminal logs in an account before the last shutdown, the vehicle terminal automatically logs in the account logged in before the last shutdown after the startup of the current startup. The vehicle terminal responds to the current account number (namely the account number logged in before the last shutdown) to automatically log in successfully, and can acquire the first face feature of the current user at the main driving position in the vehicle.

An image acquisition device (the image acquisition device may be a camera or the like) may be disposed in the vehicle, an image of a current user at a main driving position in the vehicle (may be a face image of the current user in particular) may be acquired by the image acquisition device, face recognition is performed on the acquired image by the image acquisition device, a first face feature of the current user at the main driving position is obtained, and the image acquisition device may transmit the first face feature of the current user at the main driving position to a vehicle terminal.

An image acquisition device may be disposed in a vehicle, through which an image of a current user (specifically, a face image of the current user) of a main driving position in the vehicle may be acquired, and the image acquisition device may transmit the acquired image to a vehicle terminal, and face recognition may be performed on the image through the vehicle terminal, so as to obtain a first face feature of the current user of the main driving position.

For example, the image capturing apparatus may be provided at any suitable position inside the vehicle as long as the face of the current user at the main driving position can be captured. It can be understood that, based on the difference of the setting positions of the image acquisition device, the acquired image may include the current user of the main driving position, or may include the current user of the main driving position and the user of other positions (such as the auxiliary driving position and the rear seat position), if the image includes the current user of the main driving position and the user of other positions, the current user of the main driving position in the image can be detected first, and then the face recognition is performed on the current user of the main driving position in the image, so as to obtain the first face feature of the current user of the main driving position.

Illustratively, the process of acquiring the first face feature of the current user of the main driving position in the vehicle described above may be implemented using a DMS (Driver Monitoring System ), OMS (Occupancy Monitoring System, in-vehicle human monitoring system), or the like.

And 202, the vehicle-mounted terminal compares the first face characteristics with the second face characteristics bound with the current account.

In the embodiment of the application, the vehicle terminal can acquire the second face feature bound by the current account number, and compare the first face feature of the current user at the main driving position with the second face feature bound by the current account number.

The second face feature bound by the current account number can be stored locally in the vehicle-mounted terminal, and the vehicle-mounted terminal obtains the second face feature bound by the current account number locally.

The second face feature bound by the current account number can be stored in the cloud server, and the vehicle terminal obtains the second face feature bound by the current account number from the cloud server. Specifically, the vehicle terminal may send a feature acquisition request to the cloud server, where the feature acquisition request may include the current account number, and the cloud server returns, in response to the feature acquisition request, the second face feature bound by the current account number to the vehicle terminal.

And 203, the vehicle-mounted terminal determines the user type of the current user in response to inconsistent comparison between the first face feature and the second face feature.

The vehicle-mounted terminal responds to the inconsistent comparison between the first face feature and the second face feature, and the user type of the current user can be further determined; and responding to the consistency of the comparison of the first face characteristic and the second face characteristic, the processing can be omitted.

Illustratively, the user types may include, but are not limited to: an intimate user in a non-owner of the current account, a normal user in a non-owner of the current account, and so forth. Of course, the user types may also be classified according to intimacy level or the like.

The specific procedure for determining the user type of the current user will be described in detail in the following embodiments.

And 204, the vehicle terminal responds to the current user to operate the current function item, and determines the operation authority of the current user on the current function item based on the user type.

In the embodiment of the application, users with different user types can be set to have different operation rights to the function items of the vehicle terminal. For example, the number of function items that the close user allows to operate is greater than the number of function items that the normal user allows to operate, the importance of function items that the close user allows to operate is higher than the importance of function items that the normal user allows to operate, and so on.

Therefore, the vehicle terminal responds to the current user to operate the current function item, and determines the operation authority of the current user on the current function item based on the user type. And will be described in detail in the following examples.

In the embodiment of the application, under the condition that the current user at the main driving position is not the logged-in current account owner, the vehicle terminal can determine the operation authority of the current user under the current account according to the user type of the current user, so that different operation authorities are given to different user types, effective protection of the current account is realized, for example, the current user is forbidden to use functional items with higher security requirements such as money, and loss to the current account owner is avoided.

Referring to fig. 3, a flowchart of steps of another vehicle account protection method of an embodiment of the present application is shown.

As shown in fig. 3, the vehicle account protection method may include the steps of:

step 301, the vehicle terminal responds to the success of automatic login of the current account number, and obtains the first face feature of the current user at the main driving position in the vehicle.

And 302, the vehicle-mounted terminal compares the first face feature with the second face feature bound with the current account.

And 303, the vehicle-mounted terminal responds to the inconsistent comparison between the first face features and the second face features and sends out prompt information for prompting the current user to switch accounts.

If the comparison in step 302 shows that the comparison between the first face feature and the second face feature is inconsistent, the vehicle-mounted terminal responds to the fact that the comparison between the first face feature and the second face feature is inconsistent, and can send out prompt information for prompting the current user to switch accounts. And the vehicle terminal responds to the fact that the first face features are consistent with the second face features in comparison, and the vehicle terminal system can be continuously used without processing.

The vehicle terminal may send a prompt message for prompting the current user to switch the account in a text display manner in the display interface, or may send a prompt message for prompting the current user to switch the account in a voice broadcast manner, and so on.

For example, the vehicle terminal may display an option control in the display interface for the current user to select whether to switch the account. If the current user selects to switch the account, the vehicle terminal can jump to an account login page so that the current user can log in the own account; if the current user selects not to switch the account, the vehicle terminal can exit the option control for the current user to select whether to switch the account or not, and the vehicle terminal system is continuously used.

And 304, the vehicle terminal determines the user type of the current user in response to the current user not switching the account.

And if the current user selects to not switch the account, the vehicle-mounted terminal responds to the current user, which does not switch the account, and determines the user type of the current user.

For example, for a user who uses an account that is not the account owner, the number of times the face feature of the user has been used under the account may be set, and each time the user uses the account, if the face feature of the user obtained through face recognition is inconsistent with the face feature bound to the account, the number of times the face feature of the user has been used under the account may be increased by 1.

Therefore, after the face feature comparison in step 302, the vehicle-mounted terminal may further add 1 to the number of times the first face feature is used under the current account and store the number of times the first face feature is used under the current account in response to the fact that the first face feature is inconsistent with the second face feature comparison.

For example, the number of times the first face feature has been used under the current account can indicate the affinity of the first face feature with the owner of the current account, the greater the number of times the first face feature has been used, the higher the affinity.

Thus, the process of determining the user type of the current user may comprise: acquiring the used times of the first face feature under the current account; determining that the user type of the current user is an intimate user in a non-owner of the current account in response to the number of times of use exceeding a preset threshold; and determining that the user type of the current user is a common user in a non-owner of the current account number in response to the used times not exceeding the preset threshold. The specific value of the preset threshold may be set according to practical experience, for example, the preset threshold may be set to 5, 10, 15, etc., which is not limited in this embodiment.

And step 305, the vehicle terminal responds to the current user to operate the current function item, and determines the operation authority of the current user on the current function item based on the user type.

When a current user operates a certain function item on a vehicle, the vehicle-mounted terminal responds to the current user to operate the current function item, and the operation authority of the current user on the current function item can be determined based on the user type.

In an alternative embodiment, different security functions may be provided for different user types, the security functions being functions that allow operation of that user type. For example, the account owner can use all the function items, record the operation results of the function items, store the operation results in a local database, and reset the corresponding function items by taking out the function item storage values from the local database after logging in the account again (the account function record storage and setting is defined as thousands of people); the close user can use all or most of the function items and can prohibit recording the operation result of the function items; the common user uses basic function items such as multimedia, navigation and the like, and prohibits recording of the operation results of the function items.

The first and second security function items described above may be stored, for example, by a security function item list. The set safety function item list can be determined according to actual products, and mainly relates to functions of vehicle related functions, screen brightness, volume, navigation and the like. The set list of security function items may store the function item names and whether boolean values are available via an XML (eXtensible Markup Language ) file that the system will read by default. The list of security function items may have editable functions in the account application, editing which function items may not be limiting, and storing the edited content in a local database. When clicking the function, the list of the security function items in the local database is read preferentially, and if the list does not exist, the XML file is analyzed.

Illustratively, a first security function item corresponding to an intimate user in a non-owner is set, and a second security function item corresponding to a normal user in the non-owner is set, wherein the first security function item comprises the second security function item and a third security function item, and the third security function item has higher importance than the second security function item.

Thus, the process of determining the operation authority of the current user to the current function item based on the user type may include: responding to the user type as an intimate user in a non-owner of the current account, judging that the current function item belongs to a preset first safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user; and responding to the user type as a common user in a non-owner of the current account, judging that the current function item belongs to a preset second safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user.

And 306, the vehicle-mounted terminal responds to the inconsistent comparison of the first face features and the second face features, generates account alarming information and transmits the account alarming information to the mobile terminal bound with the current account.

If the comparison in step 302 shows that the comparison between the first face feature and the second face feature is inconsistent, the vehicle terminal responds to the fact that the comparison between the first face feature and the second face feature is inconsistent, generates account alarming information, and transmits the account alarming information to the mobile terminal bound with the current account.

Illustratively, the account alert information may include, but is not limited to: face images of the current user of the main driving position, first face features of the current user of the main driving position, current account information of automatic login, vehicle information, current time and the like.

The vehicle terminal can transmit the account alarming information to the mobile terminal bound with the current account through the connection established between the vehicle terminal and the mobile terminal bound with the current account.

The vehicle terminal may also call a related interface provided by the cloud server to upload the account alarm information to the cloud server, and the cloud server may acquire the mobile terminal information bound by the current account after receiving the account alarm information sent by the vehicle terminal, and send the account alarm information to the mobile terminal bound by the current account based on the mobile terminal information bound by the current account.

After receiving the account alarm information, the mobile terminal bound with the current account can display the account alarm information in an interface so as to inform the owner of the current account that other users are using the current account.

In an optional implementation manner, the vehicle-mounted terminal may further obtain a third face feature of the user at a position other than the main driving position in the vehicle before generating the account alarm information in response to the inconsistent comparison between the first face feature and the second face feature, and compare the third face feature with the second face feature. And the vehicle-mounted terminal responds to the fact that the comparison of the third face features and the second face features is inconsistent, and generates account alarming information.

For example, an image capturing device (the image capturing device may be a camera or the like) may be disposed in the vehicle, through which an image of a user at other positions in the vehicle (specifically, a face image of the user) may be captured, and face recognition may be performed on the captured image by the image capturing device, so as to obtain a third face feature of the user at other positions in the vehicle, and the image capturing device may transmit the third face feature of the user at other positions in the vehicle to the vehicle terminal.

For example, an image acquisition device may be disposed in the vehicle, through which images of the user (specifically, face images of the user) at other positions in the vehicle may be acquired, and the image acquisition device may transmit the acquired images to a vehicle terminal, and face recognition may be performed on the images through the vehicle terminal, so as to obtain third face features of the user at other positions in the vehicle.

For example, the procedure of acquiring the third face feature of the user at other locations in the vehicle described above may be implemented using an OMS or the like.

In an optional implementation manner, the vehicle-mounted terminal may further obtain a fourth face feature of the user outside the vehicle and compare the fourth face feature with the second face feature before generating the account alarm information in response to the inconsistent comparison between the first face feature and the second face feature. And the vehicle-mounted terminal responds to the fact that the fourth face features are inconsistent with the second face features in comparison, and generates account alarming information.

For example, an image capturing device (the image capturing device may be a camera or the like) may be disposed outside the vehicle, through which an image of a user outside the vehicle (specifically, a face image of the user) may be captured, and through which the captured image is subjected to face recognition to obtain a fourth face feature of the user outside the vehicle, and the image capturing device may transmit the fourth face feature of the user outside the vehicle to the vehicle terminal.

For example, an image acquisition device may be disposed outside the vehicle, through which an image of a user outside the vehicle (specifically, a face image of the user) may be acquired, and the image acquisition device may transmit the acquired image to a vehicle terminal, and face recognition may be performed on the image through the vehicle terminal, so as to obtain a fourth face feature of the user outside the vehicle.

And step 307, the vehicle terminal responds to the received account exit request and exits the current account.

After seeing the account alarming information, the owner of the current account can choose whether to exit the current account according to the actual situation. If the owner of the current account selects to exit the current account on the mobile terminal, the mobile terminal will generate an account exit request. Illustratively, the account exit request may include, but is not limited to: the current account information, vehicle information, account exit indication information, and the like.

The mobile terminal may send an account exit request to the vehicle terminal through a connection established with the vehicle terminal. And the vehicle terminal responds to the received account exit request and exits the current account.

The mobile terminal may invoke a related interface provided by the cloud server to send an account exit request to the cloud server, and after the cloud server receives the account exit request sent by the mobile terminal, the cloud server may determine whether the current account is in a logged-in state, and after determining that the current account is in a logged-in state, exit the current account (for example, the cloud server sets the current account to be invalid), and send an account exit request to the vehicle terminal. And after receiving an account exit request sent by the cloud server, the vehicle terminal exits the current account.

The vehicle-mounted terminal may also clear the number of times the first face feature is used under the current account after exiting the current account.

In the embodiment of the application, under the condition that the current user at the main driving position is not the logged-in current account number owner, different operation authorities can be given to different user types, the current account number owner can be notified, and the current account number owner can remotely exit the current account number, so that the safety of the current account number is ensured.

Next, a vehicle account number protection method is described through the following three processing procedures.

Referring to fig. 4, a schematic diagram of a first process of an embodiment of the present application is shown.

As shown in fig. 4, the first process is as follows:

and after the terminal system of the vehicle is started, judging whether an account number is logged in before shutdown.

If the vehicle machine terminal judges that the account number is logged in before shutdown, the account number is automatically logged in (the account number is used as a current account number), the first face feature of the current user at the main driving position is identified, and the first face feature is compared with the second face feature bound with the current account number.

And the vehicle-mounted terminal judges whether the comparison of the first face features and the second face features is consistent.

And if the vehicle-mounted terminal judges that the comparison is consistent, the system is continuously used.

If the vehicle-mounted terminal judges that the comparison is inconsistent, prompting the current user to switch the account numbers, and adding 1 to the number of times that the first face features are used under the current account numbers. For example, the car terminal prompts "you are not the current account holder, whether to switch accounts", and so on.

The vehicle terminal uploads the account alarming information to a cloud server, the cloud server stores the account alarming information, and then a subsequent third processing process is executed. The uploaded account alert information may include, but is not limited to: face images of the current user, first face features of the current user, current account information, vehicle information, and so forth.

And the vehicle terminal judges whether the current user selects to switch the account.

And if the vehicle terminal judges that the current user selects the switching account, displaying a login page for the current user to login the own account.

And if the vehicle terminal judges that the current user selects the non-switched account, the system is continuously used, and then a subsequent second processing process is executed.

Referring to fig. 5, a schematic diagram of a second process of an embodiment of the present application is shown.

As shown in fig. 5, the second process is as follows:

And the vehicle terminal judges that the current user selects the non-switched account number and continues to use the system.

The vehicle terminal sets the current user as a non-owner of the current account. For example, a first identifier iscurrentAccount user of the current user is set to false, and the first identifier iscurrentAccount user defaults to true, where iscurrentAccount user indicates that the user is a non-owner, and iscurrentAccount user indicates that the user is a true.

And the vehicle terminal sets the user type of the current user. For example, if the number of times the first face feature of the current user is used under the current account exceeds a preset threshold (for example, 10 times), setting the user type of the current user as an intimate user in the non-owner of the current account, otherwise setting the user type of the current user as a common user in the non-owner of the current account. For example, when the second identifier isaquaintance of the current user is set to true, the current user is indicated as an intimate user, and when the second identifier isaquaintance of the current user is set to false, the current user is indicated as a normal user.

And when the current user operates the current function item, the vehicle terminal judges whether the current user is the owner of the current account.

And if the vehicle-mounted terminal judges that the current user is the owner of the current account, the vehicle-mounted terminal allows the current function item to be operated, and records the operation result.

And if the vehicle-mounted terminal judges that the current user is a non-owner of the current account, acquiring the user type of the current user, and determining the operation authority of the current function item according to the user type of the current user.

Referring to fig. 6, a schematic diagram of a third process according to an embodiment of the present application is shown.

As shown in fig. 6, the third process is as follows:

and the vehicle terminal is connected with the cloud server through MQTT (Message Queuing Telemetry Transport, message queue telemetry transmission).

And the cloud server is connected with the vehicle terminal through an MQTT.

The mobile terminal (particularly an application related to the vehicle terminal) is connected with the cloud server through an MQTT.

And the cloud server is connected with the mobile terminal through the MQTT.

The process is a process of performing initial communication connection among the vehicle terminal, the cloud server and the mobile terminal.

The vehicle terminal prompts the current user to switch the account, and uploads account alarming information to the cloud server through the MQTT connection with the cloud server, and the cloud server stores the account alarming information.

And the cloud server sends account alarm information to the mobile terminal through the MQTT connection.

The mobile terminal receives the account alarming information through the MQTT connection with the cloud server, and prompts the account alarming information.

The mobile terminal enters an account alarming information detail page. For example, the mobile terminal can display account alarm information in a notification bar, and an owner of the current account can enter a detail page of the application for displaying the account alarm information by clicking a notification; the mobile terminal can also store the account alarming information in a database of a related application, an owner of the current account can inquire a database parallel list display through a message center of the application, and click a message corresponding to the account alarming information to enter a detail page.

The mobile terminal judges whether the owner of the current account exits the current account. The owner of the current account can click the account to exit on the detail page of the mobile terminal application.

If the mobile terminal judges that the owner of the current account exits the current account, an account exit request is sent to the cloud server through the MQTT connection with the cloud server. The account exit request may contain current account information, vehicle information, etc.

The cloud server receives the account exit request and judges whether the current account is logged in a corresponding vehicle (a vehicle corresponding to the vehicle information contained in the account exit request).

And if the cloud server judges that the current account is not logged in, returning an account exit response to the mobile terminal.

And if the cloud server judges that the current account is logged in, setting the current account as invalid, sending an account exit request to the vehicle terminal, and returning an account exit response to the mobile terminal.

And the vehicle terminal receives the account exit request and switches to the visitor user interface.

The vehicle terminal receives the account exit request, acquires the first face feature of the current user of the main driving position, and clears the used times of the first face feature under the current account.

The mobile terminal receives an account exit response sent by the cloud server and prompts (test) an account exit result.

In the embodiment of the application, when other people do not want to use the account, the account can be withdrawn remotely, so that other people can be prevented from changing the use information of the account in a mess; when the vehicle is stolen, effective evidence can be provided; the same account number is used by multiple people, rights are different, and safety coefficient is improved.

In an embodiment of the application, an electronic device is also provided. The electronic device may include one or more processors and one or more computer-readable storage media having instructions stored thereon, such as an application program. The instructions, when executed by the one or more processors, cause the processor to perform the vehicle account protection method of any of the embodiments described above.

Fig. 7 shows a schematic structural diagram of an electronic device 700 according to an embodiment of the present application. As shown in fig. 7, the electronic device 700 includes a central processing unit (Central Processing Unit, CPU) 701 that can perform various appropriate actions and processes according to computer program instructions stored in a Read Only Memory (ROM) 702 or computer program instructions loaded from a storage unit 708 into a random access Memory (Random Access Memory, RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 may also be stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. An Input/Output (I/O) interface 705 is also connected to bus 704.

Various components in the electronic device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, mouse, microphone, etc.; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, an optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the electronic device 700 to exchange information/data with other devices through a computer network, such as the internet, and/or various telecommunication networks.

The various procedures and processes described above may be performed by the processing unit 701. For example, the vehicle account number protection method of any of the above embodiments may be implemented as a computer software program tangibly embodied on a computer-readable medium, such as the storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 700 via the ROM 702 and/or the communication unit 709. When the computer program is loaded into RAM 703 and executed by CPU701, one or more actions of the vehicle account number protection method described above may be performed.

In an embodiment of the present application, there is also provided a computer-readable storage medium having stored thereon a computer program executable by a processor of an electronic device, the computer program, when executed by the processor, causing the processor to perform the vehicle account protection method as described in any of the embodiments above.

The processors mentioned above may include, but are not limited to: a CPU, network processor (Network Processor, NP), digital signal processor (Digital Signal Processing, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field-programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and so forth.

The computer readable storage medium mentioned above may include, but is not limited to: ROM, RAM, compact disc read-only memory (Compact Disc Read Only Memory, CD-ROM for short), electrically erasable programmable read-only memory (Electronic Erasable Programmable Read Only Memory, EEPROM for short), hard disk, floppy disk, flash memory, and so forth.

In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk) and including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. In view of the foregoing, this description should not be construed as limiting the application.

Claims

1. A vehicle account protection method, which is applied to a vehicle terminal, the method comprising:

2. The method according to claim 1,

before determining the user type of the current user, the method further comprises: responding to inconsistent comparison between the first face features and the second face features, and sending prompt information for prompting the current user to switch accounts;

The determining the user type of the current user comprises the following steps: and determining the user type of the current user in response to the current user not switching the account.

3. The method of claim 1, further comprising, after comparing the first face feature with a second face feature bound to the current account number:

and generating account alarming information in response to inconsistent comparison between the first face features and the second face features, and transmitting the account alarming information to the mobile terminal bound with the current account.

4. A method according to claim 3,

before generating the account alarm information, the method further comprises the following steps: acquiring a third face feature of a user at other positions except the main driving position in the vehicle, and comparing the third face feature with the second face feature;

the generating account alarm information comprises the following steps: generating account alarm information in response to inconsistent comparison between the third face features and the second face features;

or alternatively, the first and second heat exchangers may be,

before generating the account alarm information, the method further comprises the following steps: acquiring a fourth face feature of a user outside the vehicle, and comparing the fourth face feature with the second face feature;

The generating account alarm information comprises the following steps: and generating account alarm information in response to inconsistent comparison between the fourth face feature and the second face feature.

5. The method of claim 3, further comprising, after transmitting the account alert information to the mobile terminal to which the current account is bound:

responding to the received account exit request, and exiting the current account; the account exit request is sent by the mobile terminal.

6. The method of claim 5, further comprising, after exiting the current account number:

and clearing the used times of the first face feature under the current account number, wherein the used times are used for determining the user type of the current user.

7. The method of claim 1, the determining the user type of the current user comprising:

acquiring the used times of the first face feature under the current account;

determining that the user type of the current user is an intimate user in a non-owner of the current account in response to the number of times of use exceeding a preset threshold;

and determining that the user type of the current user is a common user in a non-owner of the current account number in response to the used times not exceeding the preset threshold.

8. The method of claim 1, the user type comprising an intimate user in a non-owner of the current account and a common user in a non-owner of the current account; the determining the operation authority of the current user to the current function item based on the user type comprises the following steps:

responding to the user type as an intimate user in a non-owner of the current account, judging that the current function item belongs to a preset first safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user;

responding to the user type as a common user in a non-owner of the current account, judging that the current function item belongs to a preset second safety function item, allowing the current user to operate the current function item, and prohibiting recording of an operation result of the current user;

wherein the first security function item includes the second security function item and a third security function item, the third security function item being of higher importance than the second security function item.

9. An electronic device, comprising:

One or more processors; and

one or more computer-readable storage media having instructions stored thereon;

the instructions, when executed by the one or more processors, cause the processor to perform the vehicle account protection method of any one of claims 1 to 8.

10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to perform the vehicle account number protection method of any one of claims 1 to 8.