A method and device for remotely logging out of a vehicle machine application account

Abstract

The application relates to the field of new energy vehicles and provides a method and device for remotely logging out of an application account of a vehicle machine. The method comprises the following steps: when it is determined that the identity information of a current driver is inconsistent with that of a registered driver, or an operation of initiating sharing of vehicle rights by a vehicle owner end is monitored, or an account logout request is received, obtaining a plurality of application accounts of the vehicle machine system which are currently in a login state; selecting at least one target application account which has a binding relationship with the registered driver from the plurality of application accounts of the vehicle machine system, and pushing logout inquiry information to the vehicle owner end; when an account logout application is received, issuing an account logout instruction to the vehicle machine system via a login server, so that the vehicle machine system executes the account logout instruction and modifies the login state of each target application account in the vehicle machine system to a logout state. The application can remotely log out of an application program which has been used on the vehicle machine system, reduces the risk of user information leakage, and improves the security of user information.

Description

Technical Field

[0001] This application relates to the field of new energy vehicles, and in particular to a method and apparatus for remotely logging out of a vehicle-mounted application account. Background Technology

[0002] For ease of use and a better driving experience, car owners usually log in to and use some applications on the car's infotainment system, such as navigation apps, music apps, and video apps.

[0003] In existing technologies, vehicle owners can only log out of certain applications logged into and used on the vehicle's infotainment system locally via the vehicle's infotainment system. If a vehicle owner forgets to log out of the applications they logged into and used on the vehicle's infotainment system before sharing (or renting) the vehicle to someone else, there is no way to log out of those applications after the vehicle has been driven away. This makes it easy for the recipient to obtain the vehicle owner's personal information (such as ID number) through the applications logged into and used on the vehicle's infotainment system, thus posing a significant information security risk and privacy breach. Summary of the Invention

[0004] In view of this, this application provides a method and apparatus for remotely logging out of a vehicle infotainment application account to solve the problem that when a vehicle owner forgets to log out of some applications logged in and used on the vehicle infotainment system before sharing the vehicle with others and the vehicle has already been driven away, the owner is unable to log out of the applications logged in on the vehicle infotainment system, which poses a significant risk of information security and privacy leakage.

[0005] A first aspect of this application provides a method for remotely logging out of a vehicle infotainment application account, including:

[0006] When it is determined that the identity information of the current driver is inconsistent with that of the registered driver, or when the operation of sharing vehicle permissions initiated by the vehicle owner is detected, or when an account logout request is received, the system obtains multiple vehicle application accounts that are currently logged in to the vehicle system.

[0007] Select at least one target application account that is bound to the registered driver from multiple vehicle application accounts, and push a logout inquiry message to the vehicle owner, which includes the target application account;

[0008] Upon receiving an account logout request in response to a logout inquiry, the login server sends an account logout command to the vehicle infotainment system. The account logout command includes at least one target application account, so that the vehicle infotainment system executes the account logout command and changes the login status of each target application account in the vehicle infotainment system to the logout status.

[0009] A second aspect of this application provides an apparatus for remotely logging out of a vehicle infotainment application account, comprising:

[0010] The acquisition module is configured to acquire multiple vehicle system application accounts that are currently logged in when the identity information of the current driver is inconsistent with that of the registered driver, or when the vehicle owner initiates a vehicle permission sharing operation, or when an account logout request is received.

[0011] The filtering module is configured to filter out at least one target application account that is bound to the registered driver from multiple vehicle application accounts, and push a logout inquiry message to the vehicle owner's terminal, the logout inquiry message including the target application account;

[0012] The logout module is configured to send an account logout command to the vehicle system via the login server when it receives an account logout request for a logout query. The account logout command includes at least one target application account, so that the vehicle system executes the account logout command and changes the login status of each target application account in the vehicle system to the logout status.

[0013] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0014] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method.

[0015] Compared with the prior art, the beneficial effects of this application embodiment include at least the following: When a car owner forgets to log out of some applications logged in and used on the vehicle's infotainment system before sharing the vehicle with others, and the vehicle has already been driven away, the system can first obtain multiple currently logged-in vehicle infotainment application accounts when it is determined that the current driver's identity information is inconsistent with the registered driver, or when the owner initiates a vehicle permission sharing operation, or when an account logout request is received. Then, it filters out at least one target application account that is bound to the registered driver from the multiple vehicle infotainment application accounts and pushes a logout query message to the owner, which includes the target application account. Afterwards, when an account logout request is received in response to the logout query message, the system sends an account logout command to the vehicle infotainment system via the login server. The account logout command includes at least one target application account, causing the vehicle infotainment system to execute the account logout command and change the login status of each target application account in the vehicle infotainment system to a logged-out status. This allows the car owner to remotely log out of some applications logged in and used on the vehicle infotainment system, reducing the risk of leakage of user privacy / sensitive information and improving the security of user information. Attached Figure Description

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

[0017] Figure 1 This is a schematic diagram illustrating one application scenario of this application.

[0018] Figure 2 This is a flowchart illustrating a method for remotely logging out of a vehicle infotainment application account, as provided in an embodiment of this application.

[0019] Figure 3 This is a schematic diagram of the structure of a system for remotely logging out of a vehicle-mounted application account, provided in an embodiment of this application.

[0020] Figure 4 This is a schematic diagram of the structure of another system for remotely logging out of a vehicle-mounted application account provided in an embodiment of this application;

[0021] Figure 5 This is a flowchart of another method for remotely logging out of a vehicle infotainment application account provided in this application embodiment;

[0022] Figure 6 This is a schematic diagram of the structure of a device for remotely logging out of a vehicle-mounted application account provided in an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0025] The following will describe in detail, with reference to the accompanying drawings, a method and apparatus for remotely logging out of a vehicle-mounted application account according to an embodiment of this application.

[0026] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application. The application scenario may include a logout server 101, a vehicle owner terminal 102, a login server 103, a vehicle infotainment system 104, and a network 105.

[0027] Logout server 101 and login server 103 can both be servers that provide various services. For example, they can be a single server, a server cluster consisting of several servers, or a cloud computing service center. This application embodiment does not limit them in this way.

[0028] The vehicle owner terminal 102 can be either hardware or software. When the vehicle owner terminal 102 is hardware, it can be various electronic devices with a display screen that support communication with the logout server 101 and / or login server 103, including but not limited to smartphones, tablets, laptops, and desktop computers. When the vehicle owner terminal 102 is software, it can be installed on the aforementioned electronic devices. The vehicle owner terminal 102 can be implemented as multiple software programs or software modules, or as a single software program or software module; this application embodiment does not impose any limitations on this. Furthermore, various applications can be installed on the vehicle owner terminal 102, such as data processing applications, instant messaging tools, social platform software, search applications, etc.

[0029] The vehicle infotainment system 104 typically refers to an in-vehicle operating system with communication capabilities, which can integrate various functional modules such as maps, music, social networking, and vehicle control.

[0030] Network 105 can be a wired network using coaxial cable, twisted pair, and fiber optic connection, or it can be a wireless network that enables interconnection of various communication devices without wiring, such as Bluetooth, Near Field Communication (NFC), and Infrared. This application embodiment does not limit this.

[0031] In some embodiments, when the logout server 101 determines that the identity information of the current driver is inconsistent with that of the registered driver, or detects that the vehicle owner terminal 102 has initiated a vehicle permission sharing operation, or receives an account logout request, it obtains multiple vehicle system application accounts currently logged in to the vehicle system 104. Then, it filters out at least one target application account that is bound to the registered driver from the multiple vehicle system application accounts and pushes a logout query message to the vehicle owner terminal 102, the logout query message including the target application account. Subsequently, upon receiving an account logout request initiated in response to the logout query message, the login server 103 issues an account logout command to the vehicle system 102, the account logout command including at least one target application account, so that the vehicle system 102 executes the account logout command and changes the login status of each target application account in the vehicle system to a logged-out status. This method allows vehicle owners to remotely log out of applications they have logged into and used on the vehicle system, thereby preventing the leakage of sensitive information when sharing the vehicle with others, reducing the risk of privacy information leakage, and improving the security of user information.

[0032] It should be noted that the specific types, quantities, and combinations of the logout server 101, vehicle owner terminal 102, login server 103, vehicle system 104, and network 105 can be adjusted according to the actual needs of the application scenario, and this application embodiment does not impose any restrictions on this.

[0033] Figure 2 This is a flowchart illustrating a method for remotely logging out of a vehicle-mounted application account, as provided in an embodiment of this application. Figure 2 The method for remotely logging out of the vehicle's infotainment system account can be provided by Figure 1 Logout server 101 is executed.

[0034] like Figure 2 As shown, the method for remotely logging out of the vehicle infotainment application account includes:

[0035] Step S201: When it is determined that the identity information of the current driver is inconsistent with that of the registered driver, or when the operation of sharing vehicle permissions initiated by the vehicle owner is detected, or when an account logout request is received, obtain the multiple vehicle application accounts that are currently logged in to the vehicle system.

[0036] The current driver can be either a person who has entered the vehicle's cockpit and is using the vehicle, or an intelligent robot.

[0037] A registered driver usually refers to the vehicle owner, i.e., the person who owns the vehicle, or another person (such as the owner's relatives or friends) who is authorized by the vehicle owner to complete the relevant registration.

[0038] Identity information can be at least one of the following: fingerprint information, iris information, facial image, ID card number, telephone number, etc.

[0039] In-vehicle application accounts typically refer to the application accounts of some applications (referred to as "APPs") installed in the in-vehicle system, including but not limited to music APP accounts, navigation APP accounts, shopping APP accounts, video APP accounts, etc.

[0040] In one embodiment, the logout server 101 can monitor the interior of the vehicle in real time. For example, it can acquire image data collected by cameras inside the vehicle in real time and analyze the image data to confirm whether someone has entered the vehicle cabin. When it is confirmed that someone has entered the vehicle cabin, the server can extract a first facial image of the person entering the vehicle cabin from the image data and retrieve a second facial image uploaded by the registered driver during registration. Then, the similarity between the first and second facial images is compared to obtain a comparison result. Based on the comparison result, the server can determine whether the current driver (i.e., the person currently entering the vehicle cabin) is the same person as the registered driver, i.e., confirm whether their identity information is consistent. If they are inconsistent (e.g., the similarity between the first and second facial images is lower than a preset threshold), the server determines that the current driver and the registered driver's identity information are inconsistent. At this time, the logout server 101 can send a request to the vehicle system 104 to obtain multiple vehicle system application accounts that are currently logged in to the vehicle system, and receive the multiple vehicle system application accounts that are currently logged in to the vehicle system 104 in response to the request. Of course, the logout server 101 can also send a request to the login server 103 to obtain multiple vehicle system application accounts that are currently logged in to the vehicle system. The login server 103 then forwards the request to the vehicle system 104, and the login server 103 then forwards the multiple vehicle system application accounts returned by the vehicle system 104 to the logout server 101.

[0041] In another implementation, the logout server 101 can monitor in real time whether the vehicle owner's terminal 102 initiates a vehicle permission sharing operation. This vehicle permission sharing operation could be the vehicle owner authorizing the user's overall vehicle control permissions (or partial vehicle function permissions, such as the right to turn on / off the vehicle's air conditioning) to user A on a specific date. If the vehicle owner's terminal 102 initiates a vehicle permission sharing operation, it can either directly send a request to the vehicle infotainment system 104 to obtain the user's currently logged-in vehicle infotainment application accounts, or forward the request via the login server 103, to obtain the multiple vehicle infotainment application accounts currently logged into the vehicle infotainment system.

[0042] In another embodiment, when the logout server 101 receives an account logout request sent by the vehicle owner terminal 102, or an account logout request initiated by the vehicle owner terminal 102 and forwarded by the login server 103, it can obtain multiple vehicle application accounts that are currently logged in by directly sending a request to the vehicle system 104 to obtain the multiple vehicle application accounts that are currently logged in, or by forwarding the request by the login server 103.

[0043] Step S202: Select at least one target application account that is bound to the registered driver from multiple vehicle application accounts, and push a logout inquiry message to the vehicle owner's terminal. The logout inquiry message includes the target application account.

[0044] A binding relationship typically refers to the process where, during the registration of a vehicle infotainment application account, the account is linked to the registered driver's identity information, thus establishing a binding relationship between the two. For example, when registering for a music app, a driver binds their mobile phone number to that music app account, thus creating a binding relationship between the driver's mobile phone number and the music app account.

[0045] In one embodiment, after the logout server 101 selects at least one target application account that is bound to the registered driver from multiple vehicle application accounts, it can directly push a logout query message to the vehicle owner terminal 102.

[0046] Figure 3 This illustration shows a structural diagram of a system for remotely logging out of a vehicle-mounted application account, as provided in an embodiment of this application. Figure 3 As shown, the system includes a logout server 101, a vehicle owner terminal 102, a login server 103, a vehicle infotainment system 104, a network 105, and a push server 106.

[0047] The push server 106 is mainly used to push the logout query information sent by the logout server 101 to the vehicle owner terminal 102, and to forward the account logout request returned by the vehicle owner terminal 102 to the logout server 101.

[0048] In another embodiment, the logout server 101 may select at least one target application account that is bound to the registered driver from multiple vehicle application accounts and then send the logout query information to the push server 106, which will then forward the logout query information to the vehicle owner terminal 102.

[0049] When a logout request is pushed to the vehicle owner's terminal 102, the pre-set "Remote Logout of Vehicle Application Account" function button can be simultaneously triggered on the display interface of the vehicle owner's terminal 102.

[0050] As an example, suppose there are 5 in-vehicle application accounts currently logged in to the vehicle system, namely accounts A, B, C, D, and E. Among them, accounts A, B, and C are bound to the registered driver's mobile phone number, while accounts D and E are not bound to the registered driver's mobile phone number or other identity information. Therefore, it can be determined that accounts A, B, and C are the target application accounts.

[0051] Step S203: Upon receiving an account logout request initiated in response to a logout inquiry, an account logout instruction is sent to the vehicle system via the login server. The account logout instruction includes at least one target application account, so that the vehicle system executes the account logout instruction and changes the login status of each target application account in the vehicle system to the logout status.

[0052] Logout status, which is the state of logging out.

[0053] In one embodiment, when the logout server 101 receives an account logout request from the vehicle owner's terminal 102 in response to a logout inquiry, or when the login server 103 forwards an account logout request from the vehicle owner's terminal 102 in response to a logout inquiry, it can send an account logout command to the login server 103. The login server 103 then forwards the account logout command to the vehicle infotainment system 104. Upon receiving the account logout command, the vehicle infotainment system 104 executes the account logout command, changing the login status of each target application account in the vehicle infotainment system to the logout status. For example, the number 1 can be set to represent the login status, and the number 0 can represent the logout status. Before logging into and using the vehicle infotainment application account in the vehicle infotainment system, the default value of the login status of the vehicle infotainment application account is set to 0; after the vehicle infotainment application account is logged into and used in the vehicle infotainment system, the vehicle infotainment system can change the default value from "0" to "1"; subsequently, when the vehicle infotainment system executes the account logout command, it changes "1" back to "0".

[0054] The technical solution provided in this application addresses the situation where a vehicle owner forgets to log out of some applications they have logged into and used on the vehicle's infotainment system before sharing the vehicle with others, and the vehicle has already been driven away. This solution works by first obtaining multiple currently logged-in vehicle infotainment application accounts when the current driver's identity information is inconsistent with the registered driver, or when the vehicle owner initiates a vehicle permission sharing operation, or when an account logout request is received. Then, it filters out at least one target application account that is bound to the registered driver and pushes a logout query message to the vehicle owner, which includes the target application account. Subsequently, upon receiving an account logout request based on the logout query message, the login server sends an account logout command to the vehicle infotainment system, which includes at least one target application account. This causes the vehicle infotainment system to execute the account logout command, changing the login status of each target application account in the vehicle infotainment system to a logged-out status. This allows the vehicle owner to remotely log out of applications they have logged into and used on the vehicle infotainment system, reducing the risk of privacy information leakage and improving user information security.

[0055] In some embodiments, the account logout request includes the requesting device identification information of the requesting party.

[0056] In step S201 above, multiple vehicle system application accounts that are currently logged in to the vehicle system are obtained, including:

[0057] Retrieve the registration device identification information and registered facial image corresponding to the registered driver;

[0058] If the requested device identification information does not match the registered device identification information, an identity authentication request will be sent to the requesting party.

[0059] The receiving end returns video data based on the identity authentication request. The video data includes the facial image to be verified.

[0060] If the facial image to be verified matches the registered facial image, then retrieve the multiple vehicle system application accounts that are currently logged in.

[0061] As an example, in a scenario where the car owner loses their phone F, the owner can send an account logout request to the logout server 101 via login server 103 using another phone G, or directly send the account logout request to logout server 101 via phone G. In this scenario, the requesting end is phone G, and the requesting device identification information can be phone G's phone ID or phone number, or other information that can uniquely identify phone G. Registered device identification information refers to the phone ID or phone number, or other information that can uniquely identify phone F, which is bound to the registered driver's (car owner's) phone F when registering their vehicle application account. Registered facial image refers to the facial image uploaded by the registered driver when registering their vehicle application account.

[0062] If the logout server 101 confirms after comparison that the mobile phone ID of mobile phone G does not match the mobile phone ID of mobile phone F, it sends an authentication request to the requesting end (i.e., mobile phone G). For example, it could send a request to the requesting end stating, "Please record video data containing your face on site." After receiving the authentication request, the vehicle owner can use mobile phone G to record video data containing their face and upload it to the logout server 101. The facial image to be verified is the image frame containing the vehicle owner's face in the video data.

[0063] Next, the logout server 101 can extract the facial image to be verified from the video data and compare it with the registered facial image to confirm whether the facial image to be verified and the registered facial image are consistent. For example, the cosine similarity between the facial image to be verified and the registered facial image can be calculated, and then it can be determined whether the cosine similarity meets a preset similarity range (e.g., ≥90%). If the cosine similarity is 95%, meeting the preset similarity range (e.g., ≥90%), then the facial image to be verified and the registered facial image can be considered consistent. Afterwards, multiple vehicle system application accounts currently logged in can be further retrieved from the vehicle system.

[0064] The technical solution provided by this invention verifies the legitimacy of the requesting device identifier information of the requesting end that initiates the account logout request to be consistent with the registered device identifier information of the registered driver. If the requesting end is not legitimate, it further verifies whether the person who initiated the account logout request using the requesting end is the registered driver (i.e., the vehicle owner). If it is determined that the person is the vehicle owner, the subsequent logout process is executed; if it is determined that the person is not the vehicle owner, the subsequent logout process is not executed. This effectively prevents other people (non-vehicle owners) from manipulating and logging out of the vehicle application account logged into the vehicle system, thus affecting the vehicle owner's driving experience. At the same time, it can also effectively prevent other people from obtaining the vehicle owner's privacy / sensitive information during this process, which helps reduce the risk of information leakage and improves information security. In addition, it can also effectively prevent other people from tampering with the information of the vehicle system during this process, thus affecting the driving safety of the vehicle.

[0065] In some embodiments, if the facial image to be verified matches the registered facial image, after obtaining multiple vehicle system application accounts currently logged in to the vehicle system, the method further includes:

[0066] Remove the binding relationship between the registered device identification information and the registered driver;

[0067] Establish a binding relationship between the requested device identification information and the registered driver.

[0068] In one implementation, if the registered device identification information was previously bound to the registered driver's identity information, then the requested device identification information can be overwritten with the registered device identification information to unbind the registered device identification information from the registered driver while simultaneously establishing a binding relationship between the requested device identification information and the registered driver.

[0069] The technical solution provided in this application embodiment, when a vehicle owner loses their original registration device and uses a new requesting device to remotely log out of the vehicle's application account, verifies through the above steps that the person initiating the account logout request using the requesting device is indeed the vehicle owner, then removes the binding relationship between the registration device identification information and the registered driver, and establishes a binding relationship between the requesting device identification information and the registered driver. This prevents others from remotely logging out of the vehicle's application account after finding the vehicle owner's lost phone, which helps reduce the risk of user information leakage and improves the security of user information.

[0070] In some embodiments, in step S202 above, selecting at least one target application account that is bound to the registered driver from multiple vehicle-mounted application accounts includes:

[0071] Obtain biometric data and driving habit data of registered drivers and current drivers;

[0072] Based on biometric data and driving habit data, multiple vehicle-mounted application accounts are categorized to obtain at least one target application account that is linked to a registered driver.

[0073] Biometric data includes facial data, fingerprint data, and weight data; driving habit data includes preferred seat position, preferred steering wheel position, and preferred rearview mirror position.

[0074] The facial data of the registered driver can be an image / picture / photo / video containing the facial features of the registered driver (vehicle owner).

[0075] The fingerprint data of a registered driver can be the fingerprint that the registered driver enters in the fingerprint enrollment area of ​​the vehicle (where a fingerprint recognition device is installed).

[0076] A registered driver’s preferred seat position refers to a position that a registered driver typically prefers to adjust the seat to, in a way that makes driving easier or more comfortable.

[0077] The preferred steering wheel position of a registered driver refers to the position in which a registered driver typically adjusts the steering wheel when using the vehicle, making it easier or more comfortable to drive.

[0078] The preferred rearview mirror position of a registered driver refers to the position that a registered driver usually prefers to adjust the rearview mirror to when driving the vehicle, a position that they find convenient or comfortable.

[0079] Figure 4 This illustration shows a schematic diagram of another system for remotely logging out of a vehicle infotainment application account, as provided in an embodiment of this application. Figure 3 Compared to the system shown, Figure 4 The system shown also includes a vehicle owner information server 401 and an on-board component status server 402.

[0080] The vehicle owner information server 401 is mainly used to provide the vehicle owner's biometric data and driving habit data to the logout server 101. The vehicle component status server 402 is mainly used to provide the current driver's biometric data and driving habit data who has entered the vehicle to the logout server 101.

[0081] The vehicle component status server 402 can communicate with seat sensors, vehicle fingerprint recognition devices, vehicle cameras, etc., to receive / send information. Among them, the seat sensors can detect the current driver / passenger's weight and feed it back to the vehicle component status server 402; the vehicle fingerprint recognition device can recognize the fingerprint registered by the current driver in the fingerprint enrollment area and feed it back to the vehicle component status server 402; the vehicle camera can collect facial data of people entering the vehicle and feed it back to the vehicle component status server 402.

[0082] In one embodiment, multiple vehicle-mounted application accounts are categorized based on biometric data and driving habit data to obtain at least one target application account that is linked to a registered driver, including:

[0083] Extract the account identifier information for each vehicle infotainment application account;

[0084] If the account identification information does not match at least one of the current driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, or preferred rearview mirror position, then the vehicle application account corresponding to the account identification information will be identified as the target application account.

[0085] Account identification information can include account name, account ID (IDentity), etc.

[0086] As an example, a mapping table can be pre-set between the car owner's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, preferred rearview mirror position, and the account identification information of the car owner's in-vehicle application account used to log in to the in-vehicle system.

[0087] Assuming there are five in-vehicle application accounts currently logged in to the vehicle infotainment system, with account IDs A, B, C, D, and E, the aforementioned correspondence table can be consulted to confirm whether the registered driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position for each account ID correspond one-to-one with the current driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position. This confirms whether the account identification information completely matches the current driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position.

[0088] If the facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position of the driver corresponding to the vehicle application account with account IDs A, B, and C do not match any one or more of the current driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position (for example, the registered driver's facial data is inconsistent with the current driver's facial data), then the vehicle application account with account IDs A, B, and C will be identified as the target application account.

[0089] The technical solution provided in this application obtains the biometric data and driving habit data of the registered driver and the current driver, and uses the correspondence between the account identifier information of the vehicle application account and the biometric data and driving habit data of the registered driver to verify whether the biometric data and driving habit data of the current driver match the account identifier information of the currently logged-in vehicle application account. This allows the target application account that is bound to the registered driver to be filtered out. This enables the vehicle owner to remotely control the vehicle application account they use to log out of the vehicle system without affecting the normal use of the vehicle application account logged in by non-vehicle owners on the vehicle system. This can improve the information security of the vehicle owner and also take into account the driving experience of the current driver.

[0090] The technical solution provided in this application embodiment can realize remote intelligent logout of vehicle application accounts that are logged in in the vehicle system through the interconnection between the vehicle terminal and the cloud service group (including logout server, login server, push server, vehicle owner information server, and vehicle component status server), which helps to avoid the leakage of user privacy data and improves user information security.

[0091] In some embodiments, in step S203 above, the vehicle system executes an account logout command, changing the login status of each target application account in the vehicle system to a logout status, specifically including:

[0092] If the target application account is a driver assistance application account and the driver assistance application account is currently in use, then the account logout command will be temporarily suspended.

[0093] When it is detected that the account of the assisted driving application has been changed to the end of use status, the account logout command is triggered to change the login status of the target application account in the vehicle system to the logout status.

[0094] Accounts for driver assistance applications, including accounts for navigation apps, panoramic imaging apps, reversing camera apps, and other applications related to enabling driver assistance functions.

[0095] In practical applications, all vehicle application accounts installed on the vehicle system can be categorized in advance to distinguish between driver assistance application accounts and non-driver assistance application accounts, so as to differentiate whether the target application account is a driver assistance application account or a non-driver assistance application account later.

[0096] As an example, suppose the target application accounts are A, B, and C, where account A is a music app account, account B is a video app account, and account C is a navigation app account. If account C is a driver assistance application account and is currently in use, the logout operation for account C will be temporarily suspended. When account C has been changed to a deactivated state, the logout operation for account C will be triggered, and the login status of account C in the vehicle's infotainment system will be changed to logged-out status.

[0097] If accounts A and B are not accounts for driver assistance applications, then continue to perform the logout operation for accounts A and B, and change the login status of accounts A and B in the vehicle system to the logout status.

[0098] If accounts A and B are not for driver assistance applications, determine whether accounts A and B are currently in use. If they are not currently in use, logout operations can be performed directly on accounts A and B, setting their login status on the vehicle system to logged-out. If they are currently in use, a logout prompt message can be sent to the vehicle owner's terminal 102. This logout prompt message may include a logout time option, allowing the vehicle owner to select a suitable logout time or decide whether to continue with the logout operation.

[0099] The technical solution provided by this invention further determines whether the target application account is a driver assistance application account or a non-driver assistance application account. For target application accounts that are driver assistance application accounts and are currently in use, the logout operation is temporarily suspended until the current driver finishes using the target application account (at the latest until the vehicle is turned off and then powered on again), and then the logout operation is performed. For target application accounts that are non-driver assistance application accounts, the logout operation is performed, thereby better protecting the driver's driving safety and reducing the risk of leakage of the vehicle owner's information.

[0100] In some embodiments, the above method further includes:

[0101] Obtain the current device location of the registered device corresponding to the registered driver;

[0102] If the vehicle's current location does not match the device's current location, an authentication request will be sent to both the vehicle system and the registration device.

[0103] If the vehicle system receives the first identity information in response to the identity verification request, and the first identity information is verified successfully, and the registered device does not receive the second identity information in response to the identity verification request or the second identity information is not verified successfully, then a request to obtain the historical vehicle system account information is sent to the vehicle system.

[0104] The system will forward the historical vehicle infotainment account information received from the vehicle infotainment system to the login server, so that the login server will issue a forced logout command to the registered device. The forced logout command includes all vehicle infotainment application accounts corresponding to the historical vehicle infotainment account information, controls the registered device to log out of all vehicle infotainment application accounts, and cancels the association between the registered device and all vehicle infotainment application accounts.

[0105] Current device location refers to the current location of the registered device that the registered driver linked to when registering their vehicle application account. For example, if the registered device is mobile phone A, then the current device location is the real-time location of mobile phone A.

[0106] The first and second identity information can be any of the following: ID card number, mobile phone number, facial image, etc. Furthermore, to facilitate subsequent comparison, the first and second identity information should be of the same type; for example, both could be ID card numbers, mobile phone numbers, or facial images.

[0107] Historical vehicle infotainment system account information, including at least the account name.

[0108] Typically, registered devices (such as mobile phones) are carried by people at all times. Therefore, when a registered driver uses a vehicle with their registered device, the current location of the registered device and the current location of the vehicle can be considered to be the same.

[0109] Often, for convenience, users (such as car owners) set applications on their registered devices (such as mobile phones) to be login-free, allowing them to directly access the application interface and use functions such as browsing or setting personal information upon opening the phone. However, if users forget their account and / or password for these applications already logged into their phones, they will find it difficult to log out of these applications in time if the phone is stolen or lost, potentially leading to the leakage of user information.

[0110] As an example, if the current driver is the vehicle owner (i.e., the registered driver), the logout server 101 can first communicate with the registration device to collect the current location of the registration device via its positioning device (such as a mobile phone GPS); it can also communicate with the vehicle's onboard positioning device to collect the vehicle's current location. Then, by calculating the distance between the current device location and the vehicle's current location, if the distance is greater than a preset distance range (e.g., >0.1 meters, >0.2 meters, etc.), it is determined that the vehicle's current location and the current device location are inconsistent. At this time, authentication requests are sent to both the vehicle system and the registration device. If the logout server 101 receives the first identity information (such as a facial image) returned by the vehicle system and verifies that the facial image matches the facial image uploaded by the vehicle owner when registering the vehicle application account; at the same time, if it does not receive the second identity information (such as a facial image) returned by the registration device, or if the second identity information fails verification, it sends a request to the vehicle system to obtain historical vehicle account information. When the logout server 101 receives the historical vehicle infotainment system account information returned by the vehicle infotainment system, it forwards the historical vehicle infotainment system account information to the login server 103. After receiving the historical vehicle infotainment system account information, the login server 103 issues a forced logout command to the registered device to control the registered device to log out of all vehicle infotainment application accounts corresponding to the historical vehicle infotainment system account information, and to cancel the association between the registered device and all vehicle infotainment application accounts.

[0111] As an example, assuming the historical vehicle infotainment system account information includes accounts A, B, C, D, and E, then all vehicle infotainment system application accounts corresponding to this historical vehicle infotainment system account information are accounts A, B, C, D, and E. The login server 103 sends a forced logout command to the registered device to control the registered device to log out of accounts A, B, C, D, and E, and to cancel the association between the registered device and accounts A, B, C, D, and E.

[0112] The technical solution provided by this invention addresses the situation where a vehicle owner's registration device is stolen or lost, preventing them from promptly logging out of the application accounts logged in on that device. The solution involves first verifying whether the current location of the registration device matches the current location of the vehicle; then verifying whether identity information returned by both the registration device and the vehicle system can be received simultaneously, and whether that identity information is legitimate; next, obtaining the vehicle system's historical vehicle system account information used by the owner; and then, using this historical vehicle system account information, issuing a forced logout command to the registration device via the login server. This controls the registration device to log out of all vehicle system application accounts corresponding to the historical vehicle system account information, thereby ensuring timely logout of applications logged in on the stolen or lost registration device and reducing the risk of user information leakage.

[0113] Figure 5 This is a flowchart illustrating another method for remotely logging out of a vehicle infotainment application account provided in this application embodiment. For example... Figure 5 As shown, the method includes:

[0114] Step S501: The user (such as the car owner) logs in to the car owner's mobile APP using their account and password;

[0115] Step S502: Determine whether the current account is logged into the vehicle system;

[0116] Step S503: If the current account is logged in to the vehicle system, the interface of the car owner's APP mobile phone will display that the current account is logged in to the vehicle system.

[0117] Step S504: If the current account is not logged in to the vehicle system, the interface of the car owner's APP mobile phone will display that the current account is not logged in to the vehicle system, and the process will end.

[0118] Step S505: Determine whether the user chooses to remotely log out of the current account logged in on the vehicle system;

[0119] Step S506: When the user chooses to exit, they can click the "Remotely exit vehicle account" function button displayed on the interface of the car owner's mobile APP.

[0120] Step S507: Determine if the vehicle infotainment system is online;

[0121] Step S508: If the vehicle system is online, the vehicle system will receive an account logout command in real time and exit the target application account.

[0122] In step S509, if the vehicle system is offline, the system will request the login status of the current account from the login server after the vehicle system comes online, and log out of the target application account upon receiving the account logout command.

[0123] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0124] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0125] Figure 6 This is a schematic diagram of a device for remotely logging out of a vehicle-mounted application account, as provided in an embodiment of this application. Figure 6 As shown, the device for remotely logging out of the vehicle infotainment application account includes:

[0126] The acquisition module 601 is configured to acquire multiple vehicle system application accounts that are currently logged in when it is determined that the identity information of the current driver is inconsistent with that of the registered driver, or when the vehicle owner initiates a vehicle permission sharing operation, or when an account logout request is received.

[0127] The filtering module 602 is configured to filter out at least one target application account that is bound to the registered driver from multiple vehicle application accounts, and push a logout inquiry message to the vehicle owner's terminal, the logout inquiry message including the target application account;

[0128] The logout module 603 is configured to send an account logout instruction to the vehicle system via the login server when it receives an account logout request for a logout query. The account logout instruction includes at least one target application account, so that the vehicle system executes the account logout instruction and changes the login status of each target application account in the vehicle system to the logout status.

[0129] The technical solution provided in this application embodiment addresses the situation where a vehicle owner forgets to log out of some applications they have logged into and used on the vehicle's infotainment system before sharing the vehicle with others, and the vehicle has already been driven away. The acquisition module 601, upon determining that the current driver's identity information is inconsistent with the registered driver, detecting a vehicle permission sharing operation initiated by the vehicle owner, or receiving an account logout request, first acquires multiple currently logged-in vehicle infotainment system application accounts. Then, the filtering module 602 filters out at least one target application account that is bound to the registered driver from these accounts and pushes a logout query message to the vehicle owner, which includes the target application account. Subsequently, upon receiving an account logout request based on the logout query message, the logout module 603 sends an account logout command to the vehicle infotainment system via the login server. This account logout command includes at least one target application account, causing the vehicle infotainment system to execute the logout command and change the login status of each target application account to a logged-out status. This allows the vehicle owner to remotely log out of applications they have logged into and used on the vehicle infotainment system, reducing the risk of privacy information leakage and improving user information security.

[0130] In some embodiments, the account logout request includes the requesting device identification information of the requesting party.

[0131] The aforementioned acquisition module 601 includes:

[0132] The retrieval unit is configured to retrieve the registration device identification information and registered facial image corresponding to the registered driver;

[0133] The sending unit is configured to send an authentication request to the requesting end if the requesting device identification information does not match the registered device identification information.

[0134] The receiving unit is configured to receive video data returned by the requesting end based on the identity authentication application. The video data includes the facial image to be verified.

[0135] The acquisition unit is configured to acquire multiple vehicle system application accounts that are currently logged in if the facial image to be verified matches the registered facial image.

[0136] The technical solution provided by this invention verifies the legitimacy of the requesting device identifier information of the requesting end that initiates the account logout request to be consistent with the registered device identifier information of the registered driver. If the requesting end is not legitimate, it further verifies whether the person who initiated the account logout request using the requesting end is the registered driver (i.e., the vehicle owner). If it is determined that the person is the vehicle owner, the subsequent logout process is executed; if it is determined that the person is not the vehicle owner, the subsequent logout process is not executed. This effectively prevents other people (non-vehicle owners) from manipulating and logging out of the vehicle application account logged into the vehicle system, thus affecting the vehicle owner's driving experience. At the same time, it can also effectively prevent other people from obtaining the vehicle owner's privacy / sensitive information during this process, which helps reduce the risk of information leakage and improves information security. In addition, it can also effectively prevent other people from tampering with the information of the vehicle system during this process, thus affecting the driving safety of the vehicle.

[0137] In some embodiments, the above-described apparatus further includes:

[0138] The unbinding module is configured to remove the binding relationship between the registered device identification information and the registered driver;

[0139] The module is configured to establish a binding relationship between the requesting device identification information and the registered driver.

[0140] The technical solution provided in this application embodiment, when a vehicle owner loses their original registration device and uses a new requesting device to remotely log out of the vehicle's application account, verifies through the above steps that the person initiating the account logout request using the requesting device is indeed the vehicle owner, then removes the binding relationship between the registration device identification information and the registered driver, and establishes a binding relationship between the requesting device identification information and the registered driver. This prevents others from remotely logging out of the vehicle's application account after finding the vehicle owner's lost phone, which helps reduce the risk of user information leakage and improves the security of user information.

[0141] In some embodiments, the filtering module 602 includes:

[0142] The data acquisition unit is configured to acquire biometric data and driving habit data of registered drivers and current drivers;

[0143] The classification unit is configured to classify multiple vehicle-mounted application accounts based on biometric data and driving habit data in order to obtain at least one target application account that is bound to the registered driver.

[0144] In some embodiments, biometric data includes facial data, fingerprint data, and weight data; driving habit data includes preferred seat position, preferred steering wheel position, and preferred rearview mirror position.

[0145] The above classification units include:

[0146] Extract components and extract the account identifier information for each vehicle infotainment application account;

[0147] The component is configured to identify the vehicle application account corresponding to the account identification information as the target application account if the account identification information does not match at least one of the current driver's facial data, fingerprint data, weight data, seat preference position, steering wheel preference position, and rearview mirror preference position.

[0148] The technical solution provided in this application embodiment acquires the biometric data and driving habit data of the registered driver and the current driver through a data acquisition unit. It then uses the correspondence between the account identifier information of the vehicle application account and the biometric data and driving habit data of the registered driver to verify whether the biometric data and driving habit data of the current driver match the account identifier information of the currently logged-in vehicle application account. This allows the selection of target application accounts that are bound to the registered driver, enabling the vehicle owner to remotely control the vehicle application account they use to log out of the vehicle system without affecting the normal use of vehicle application accounts logged in by non-vehicle owners. This improves the information security of the vehicle owner while also taking into account the driving experience of the current driver.

[0149] In some embodiments, the vehicle infotainment system includes:

[0150] The deferred execution module is configured to deferred the execution of the account logout command if the target application account is an assisted driving application account and the assisted driving application account is in use.

[0151] The module is modified to trigger an account logout command when it detects that the assisted driving application account has been changed to a deactivated state, thereby changing the login status of the target application account in the vehicle system to a logged-out state.

[0152] The technical solution provided by this invention further determines whether the target application account is a driver assistance application account or a non-driver assistance application account. For target application accounts that are driver assistance application accounts and are currently in use, the logout operation is temporarily suspended until the current driver finishes using the target application account (at the latest until the vehicle is turned off and then powered on again), and then the logout operation is performed. For target application accounts that are non-driver assistance application accounts, the logout operation is performed, thereby better protecting the driver's driving safety and reducing the risk of leakage of the vehicle owner's information.

[0153] In some embodiments, the above-described apparatus further includes:

[0154] The location acquisition module is configured to acquire the current device location of the registered device corresponding to the registered driver.

[0155] The request sending module is configured to send an authentication request to both the vehicle system and the registration device if the vehicle's current location does not match the current device location.

[0156] The information acquisition module is configured to send a request to the vehicle system to obtain historical vehicle system account information if it receives the first identity information sent by the vehicle system in response to the identity verification request and the first identity information is verified successfully, and if it does not receive the second identity information sent by the registered device in response to the identity verification request or the second identity information is not verified successfully.

[0157] The forced logout module is configured to forward the historical vehicle infotainment system account information received from the vehicle infotainment system to the login server, so that the login server issues a forced logout command to the registered device. The forced logout command includes all vehicle infotainment application accounts corresponding to the historical vehicle infotainment system account information, controls the registered device to log out of all vehicle infotainment application accounts, and cancels the association between the registered device and all vehicle infotainment application accounts.

[0158] The technical solution provided by this invention addresses the situation where a vehicle owner's registration device is stolen or lost, preventing them from promptly logging out of the application accounts logged in on that device. The solution involves first verifying whether the current location of the registration device matches the current location of the vehicle; then verifying whether identity information returned by both the registration device and the vehicle system can be received simultaneously, and whether that identity information is legitimate; next, obtaining the vehicle system's historical vehicle system account information used by the owner; and then, using this historical vehicle system account information, issuing a forced logout command to the registration device via the login server. This controls the registration device to log out of all vehicle system application accounts corresponding to the historical vehicle system account information, thereby ensuring timely logout of applications logged in on the stolen or lost registration device and reducing the risk of user information leakage.

[0159] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0160] Figure 7 This is a schematic diagram of the electronic device 7 provided in an embodiment of this application. Figure 7 As shown, the electronic device 7 of this embodiment includes a processor 701, a memory 702, and a computer program 703 stored in the memory 702 and executable on the processor 701. When the processor 701 executes the computer program 703, it implements the steps in the various method embodiments described above. Alternatively, when the processor 701 executes the computer program 703, it implements the functions of each module / unit in the various device embodiments described above.

[0161] Electronic device 7 can be a desktop computer, laptop, handheld computer, cloud server, or other electronic device. Electronic device 7 may include, but is not limited to, processor 701 and memory 702. Those skilled in the art will understand that... Figure 7 This is merely an example of electronic device 7 and does not constitute a limitation on electronic device 7. It may include more or fewer components than shown, or different components.

[0162] The processor 701 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0163] The memory 702 can be an internal storage unit of the electronic device 7, such as a hard disk or RAM of the electronic device 7. The memory 702 can also be an external storage device of the electronic device 7, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc., equipped on the electronic device 7. The memory 702 can also include both internal and external storage units of the electronic device 7. The memory 702 is used to store computer programs and other programs and data required by the electronic device.

[0164] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0165] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0166] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for remotely logging out of a vehicle-mounted application account, characterized in that, include: When it is determined that the identity information of the current driver is inconsistent with that of the registered driver, or when the operation of sharing vehicle permissions initiated by the vehicle owner is detected, or when an account logout request is received, the system obtains multiple vehicle application accounts that are currently logged in to the vehicle system. Filter out at least one target application account that is bound to the registered driver from the multiple vehicle application accounts, and push a logout inquiry message to the vehicle owner's terminal, the logout inquiry message including the target application account; Upon receiving an account logout request in response to the logout inquiry, the system sends an account logout instruction to the vehicle system via the login server. The account logout instruction includes at least one target application account, so that the vehicle system executes the account logout instruction and changes the login status of each target application account in the vehicle system to the logout status. The process involves pre-categorizing all in-vehicle application accounts installed on the vehicle system to distinguish between assisted driving application accounts and non-assisted driving application accounts. The assisted driving application accounts are those for applications related to assisted driving functions, including navigation apps, panoramic imaging apps, and reversing camera apps. The execution of the account logout command, which changes the login status of each target application account on the vehicle system to a logout status, includes: If the target application account is an assisted driving application account and the assisted driving application account is in use, the account logout command will be temporarily suspended; if it is detected that the assisted driving application account has been changed to a deactivated state, the account logout command will be triggered to change the login status of the target application account in the vehicle system to a logged-out state. If the target application account is not a driver assistance application account, then continue with the logout operation.

2. The method according to claim 1, characterized in that, The account logout request includes the requesting device identification information of the requesting end; Retrieve multiple in-vehicle application accounts that are currently logged in to the in-vehicle infotainment system, including: Retrieve the registration device identification information and registered facial image corresponding to the registered driver; If the requested device identification information does not match the registered device identification information, an identity authentication request is sent to the requesting end. Receive video data returned by the requesting end based on the identity authentication application, the video data including the facial image to be verified; If the facial image to be verified matches the registered facial image, then obtain multiple vehicle system application accounts that are currently logged in in the vehicle system.

3. The method according to claim 2, characterized in that, If the facial image to be verified matches the registered facial image, then after obtaining multiple vehicle system application accounts currently logged in, the system further includes: The binding relationship between the registered device identification information and the registered driver is terminated; Establish a binding relationship between the requested device identification information and the registered driver.

4. The method according to claim 1, characterized in that, From the plurality of vehicle infotainment application accounts, at least one target application account that is bound to the registered driver is selected, including: Obtain the biometric data and driving habit data of the registered driver and the current driver; Based on the biometric data and driving habit data, the multiple vehicle-mounted application accounts are classified to obtain at least one target application account that is bound to the registered driver.

5. The method according to claim 4, characterized in that, The biometric data includes facial data, fingerprint data, and weight data; the driving habit data includes preferred seat position, preferred steering wheel position, and preferred rearview mirror position. Based on the biometric data and driving habit data, multiple vehicle-mounted application accounts are categorized to obtain at least one target application account that is linked to a registered driver, including: Extract the account identifier information for each of the vehicle infotainment application accounts; If the account identification information does not match at least one of the current driver's facial data, fingerprint data, weight data, preferred seat position, preferred steering wheel position, and preferred rearview mirror position, then the vehicle application account corresponding to the account identification information will be identified as the target application account.

6. The method according to claim 1, characterized in that, The method further includes: Obtain the current device location of the registration device corresponding to the registered driver; If the vehicle's current location is different from the current device's location, then an authentication request is sent to both the vehicle system and the registration device. If the vehicle system receives the first identity information in response to the identity verification request, and the first identity information is verified successfully, and the registration device does not receive the second identity information in response to the identity verification request or the second identity information is not verified successfully, then a request to obtain historical vehicle system account information is sent to the vehicle system. The historical vehicle infotainment system account information received from the vehicle infotainment system is forwarded to the login server, so that the login server issues a forced logout command to the registered device. The forced logout command includes all vehicle infotainment application accounts corresponding to the historical vehicle infotainment system account information, controls the registered device to log out of all vehicle infotainment application accounts, and cancels the association between the registered device and all vehicle infotainment application accounts.

7. A device for remotely logging out of a vehicle-mounted application account, characterized in that, include: The acquisition module is configured to acquire multiple vehicle system application accounts that are currently logged in when the identity information of the current driver is inconsistent with that of the registered driver, or when the vehicle owner initiates a vehicle permission sharing operation, or when an account logout request is received. The filtering module is configured to filter out at least one target application account that is bound to the registered driver from the plurality of vehicle application accounts, and push a logout inquiry message to the vehicle owner's terminal, the logout inquiry message including the target application account; The logout module is configured to, upon receiving an account logout request initiated in response to the logout query information, send an account logout instruction to the vehicle system via the login server. The account logout instruction includes at least one target application account, so that the vehicle system executes the account logout instruction and changes the login status of each target application account in the vehicle system to the logout status. Specifically, all in-vehicle application accounts installed on the in-vehicle infotainment system are pre-categorized to distinguish between assisted driving application accounts and non-assisted driving application accounts; the in-vehicle infotainment system includes: The deferred execution module is configured to deferred the execution of the account logout command if the target application account is an assisted driving application account and the assisted driving application account is in use. The modification module is configured to trigger an account logout command when it detects that the assisted driving application account has been changed to a deactivated state, thereby changing the login status of the target application account in the vehicle system to a logout state. The modification module is also configured to: if the target application account is not a driver assistance application account, then continue to perform the logout operation.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes a computer program, it implements the steps of any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, characterized in that, When a computer program is executed by a processor, it implements the steps of any one of claims 1 to 6.

Images