Vehicle-mounted computer account login method, system and equipment based on NFC (Near Field Communication)

Abstract

The invention discloses a vehicle-mounted computer account login method based on NFC (Near Field Communication), which comprises the following steps: step 1, a mobile terminal is connected with a vehicle-mounted computer through NFC, and an NFC communication channel is established; 2, after the mobile terminal is authorized, the login token is transmitted to the vehicle-mounted computer through the NFC communication channel; and step 3, the vehicle-mounted computer verifies the login token, and the vehicle-mounted computer logs in the user account after the verification is passed. Compared with an existing mainstream method, the user operation is simpler, and the use process is faster. Compared with a short message verification code mode, the scheme has the advantages that a user does not need to manually input a mobile phone number in a vehicle-mounted computer, and does not need to wait for the verification code to be received to perform backfilling, so that the operation is simpler; compared with a code scanning login mode, the scheme adopts NFC interaction, a user does not need to click a code scanning function on a vehicle APP, and the process is faster; a symmetric encryption algorithm is adopted for token generation, it is ensured that key information cannot be tampered and falsely used, and the safety is further improved.

Description

Technical Field

[0001] This application belongs to the field of vehicle information security, and particularly relates to a vehicle-mounted computer account login method, system and device based on NFC. Background Art

[0002] With the rapid popularization and promotion of intelligent vehicles, vehicle enterprises generally deeply apply the vehicle networking system, integrate or develop more and more intelligent functions on the vehicle-mounted computer to provide a better user experience. Currently, the vehicle-mounted computer has become the main ability carrier and user access portal of intelligent vehicles.

[0003] In this context, the use experience of the vehicle-mounted computer is becoming more and more important. However, compared with other intelligent terminals, the operation method of the vehicle-mounted computer is still relatively traditional. Especially, the current login process of the vehicle-mounted computer account is more cumbersome and complex. To establish an application linkage between the vehicle-mounted computer and the user's mobile phone, the main method is to require the user to perform operation verification on the mobile terminal, mainly including two login methods: SMS verification code login and mobile phone QR code login. The current mainstream login methods have many operation steps and complex processes. Users must have the application and log in to the account on the mobile phone, and repeatedly operate on both ends to log in. Moreover, it still requires a good signal reception on the mobile terminal, and it is difficult to complete the login in places with poor signals such as basements. There are also security risks such as account leakage. There is a need for a vehicle-mounted account login method that takes into account both security and convenience and can solve the above problems. Summary of the Invention

[0004] To solve the deficiencies of the above-mentioned prior art, this application provides a vehicle-mounted computer account login method, system and device based on NFC, which uses the NFC near-field communication method to transmit the login token associated with the account, and the transmission method is safe and convenient.

[0005] The technical effects to be achieved by this application are realized through the following solutions: According to the first aspect of this application, a vehicle-mounted computer account login method based on NFC is provided, including the following steps: Step 1: The mobile terminal is connected to the vehicle-mounted computer through NFC to establish an NFC communication channel; Step 2: After the mobile terminal authorizes, the login token is transmitted to the vehicle-mounted computer through the NFC communication channel; Step 3: The vehicle-mounted computer verifies the login token, and after the verification passes, the vehicle-mounted computer logs in to the user account.

[0006] Preferably, the login token includes encrypted user account information and associated vehicle information. The user account information includes the user's mobile phone number, the IMEI number of the mobile device, the Internet Protocol (IP) address, and the Media Access Control (MAC) address. The vehicle information includes the vehicle VIN code. The in-vehicle computer sends the login token to the vehicle server for decryption and verification. The vehicle server performs a comparison verification by comparing the pre-stored user account information with the vehicle information.

[0007] Preferably, a vehicle APP is installed in the mobile terminal. When used for the first time, after the account login authorization, the vehicle APP obtains the user account information and the vehicle information, and sends the user account information and the vehicle information to the vehicle server for pre-storage.

[0008] Preferably, the account login authorization includes verification code verification, password verification, and biometric verification. The biometric verification includes fingerprint verification and / or face recognition verification of the mobile terminal.

[0009] Preferably, after the account login authorization of the vehicle APP, the vehicle server packs and encrypts the user account information and the vehicle information to form the login token, and stores it in the secure storage area of the mobile terminal.

[0010] Preferably, in step 2, the mobile terminal authorization includes one or more of clicking the confirmation button, fingerprint verification, or face recognition verification.

[0011] Preferably, the login token includes an owner token and an affiliated token. After the account login authorization of the vehicle APP, the owner token is generated. The affiliated token is generated by the vehicle server according to the owner token and the authorized mobile phone number, and is sent to the corresponding mobile terminal for storage according to the authorized mobile phone number.

[0012] Preferably, the vehicle server packs and encrypts the string of the owner token, the authorized mobile phone number, and the validity period to form the affiliated token. When verifying the affiliated token in step 3, it includes verifying the validity period.

[0013] According to the second aspect of the present application, there is provided an in-vehicle computer account login system using the above NFC-based in-vehicle computer account login method, including: A mobile terminal, configured to connect to the in-vehicle computer through NFC to establish an NFC communication channel; and transmit the login token to the in-vehicle computer through the NFC communication channel; An in-vehicle terminal, configured to establish an NFC communication channel with the mobile terminal and communicate with the vehicle server; A vehicle server, configured to obtain the user's mobile phone number and perform verification of the login token.

[0014] According to a third aspect of the present application, a server is provided, including: a memory and at least one processor; The memory stores a computer program, and the at least one processor executes the computer program stored in the memory to implement the above-mentioned NFC-based in-vehicle computer account login method.

[0015] According to an embodiment of the present application, the beneficial effects of adopting the NFC-based in-vehicle computer account login method are as follows: compared with the existing mainstream methods, the user operation is simpler and the usage process is faster. Compared with the SMS verification code method, in this solution, the user does not need to manually enter the mobile phone number on the in-vehicle computer, nor does he need to wait to receive the verification code and then operate to fill it back, so the operation is simpler; compared with the scan code login method, this solution uses NFC interaction, and the user does not need to click on the scan code function in the vehicle APP, so the process is faster; the token generation adopts a symmetric encryption algorithm to ensure that key information cannot be tampered with or misused, further improving security. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or the existing technical solutions, the following will briefly introduce the drawings required for the description of the embodiments or the existing technical solutions. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0017] Figure 1 It is a flowchart of an NFC-based in-vehicle computer account login method in an embodiment of the present application; Figure 2 It is a signal flow diagram of an NFC-based in-vehicle computer account login system in an embodiment of the present application; Figure 3 It is a signal flow diagram for generating a vehicle owner token and an affiliated token in an embodiment of the present application; Figure 4 It is a flowchart for setting up logins for different tokens in an embodiment of the present application; Figure 5 It is a structural block diagram of a server in an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0018] In order to make the objectives, technical solutions, and advantages of the present application clearer, the following will clearly and completely describe the technical solutions of the present application in conjunction with specific embodiments and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0019] As Figure 1 shown, a method for logging in to an in-vehicle computer account based on NFC in this application includes the following steps: Step 1: The mobile terminal and the in-vehicle computer are connected through NFC to establish an NFC communication channel; In this step, it is necessary to install a vehicle APP on the mobile terminal. When using it for the first time, in an environment with good signal, it is not necessary to be inside or beside the vehicle. Just operate in the vehicle APP on the mobile terminal to complete user account registration and login, and complete the binding of the account and the vehicle on the vehicle APP. This step only needs to be operated once without changing the mobile phone number and reinstalling the APP. There is no need to log in again during subsequent use.

[0020] During the binding process, based on user authorization, the mobile terminal accesses the vehicle server and sends a token generation request to the server. After receiving the request, the server obtains information such as the user's mobile phone number, mobile device IMEI number, Internet Protocol IP address, Media Access Control MAC address, vehicle VIN code, etc. from the token request, and generates a login token that can uniquely identify the mobile terminal according to the above information. The login token is used as the identity credential for the mobile terminal to access the vehicle server.

[0021] The login token is generated based on information such as the user's mobile phone number, mobile device IMEI number, Internet Protocol IP address, Media Access Control MAC address, vehicle VIN code, and validity period using an encryption algorithm to ensure that key information cannot be tampered with or misused, further improving security.

[0022] Among them, the user's mobile phone number can be obtained from the network service provider through one-key login and sent to the vehicle server together with the mobile device IMEI number, Internet Protocol IP address, and Media Access Control MAC address. Vehicle information including the vehicle VIN code is sent to the vehicle server for association, thereby completing the binding of the user and the vehicle.

[0023] After the user completes account registration and binds with the vehicle in the vehicle APP for the first time, the login token is generated by the vehicle server and sent to the mobile terminal, and is stored in the secure storage area of the mobile terminal. During subsequent use, after the NFC communication channel is established, the login token can be directly passed to the in-vehicle computer for verification without operating the mobile terminal again.

[0024] The above login token is generated based on the AES symmetric encryption algorithm. The specific method is as follows: 1. Compose the information required to generate the token (mobile phone number, IMEI, IP, MAC, VIN, validity period) into a dictionary, and then serialize it into a JSON string; 2. Randomly generate an initialization vector IV to ensure that the ciphertexts after encrypting the same information are different each time, improving security; 4. Encrypt the JSON data using the key and IV, and use PKCS7 padding; 5. Concatenate the IV and the ciphertext, and then perform Base64 encoding to complete the generation of the token; In this step, the user authorization methods adopted when logging in to the vehicle APP include verification code verification, password verification, and biometric verification. Biometric verification includes fingerprint verification and / or face recognition verification of the mobile terminal.

[0025] Both the mobile terminal and the in-vehicle computer in this step have NFC functions and can be connected and communicate. The mobile terminal can be directly connected to the in-vehicle computer by means such as close contact.

[0026] Step 2: After the mobile terminal is authorized, transmit the login token to the in-vehicle computer through the NFC communication channel; In this step, after the NFC communication channel between the mobile terminal and the in-vehicle computer is established, an inquiry page can be popped up to initiate authorization, such as displaying one or more of a confirmation button, fingerprint verification, or face recognition verification. After the user clicks the confirmation button, or after passing the authentication using the biometric authentication system such as the fingerprint verification module or face recognition module of the mobile terminal, then transmit the NFC communication channel to the in-vehicle computer to improve security.

[0027] In other embodiments, the login token can also be directly transmitted to the in-vehicle computer after the NFC communication channel is established to improve the login speed.

[0028] Step 3: The in-vehicle computer verifies the login token, and after passing the verification, the in-vehicle computer logs in to the user account.

[0029] In this step, the in-vehicle computer sends the login token to the vehicle server for verification. The vehicle server performs a comparison verification through information such as the pre-stored user mobile phone number, mobile device IMEI number, Internet protocol IP address, media access control MAC address, vehicle VIN code, and validity period.

[0030] After decrypting the login token according to the encryption rule, the vehicle server obtains the user mobile phone number, mobile device IMEI number, Internet protocol IP address, media access control MAC address, vehicle VIN code, and validity period, and compares this information with the pre-stored information. If the information is consistent and within the validity period, the verification passes, and the in-vehicle computer logs in to the corresponding user account; if the information is inconsistent or the token has expired, the verification fails and logging in is not allowed.

[0031] The steps for token verification are: 1. The vehicle server receives the token, performs Base64 decoding, and obtains IV and ciphertext; 2. Decrypt the data using the key and IV to get a JSON string; 3. Deserialize JSON into a dictionary; 4. Compare the information and check whether the validity period has expired; 5. Return the verification result.

[0032] When the verification is passed, the on-board computer completes the user account login and caches the correspondence between the token and the user account locally. When the network environment is poor, or the communication between the on-board computer and the vehicle server is poor, when the mobile terminal transmits the same login token to the on-board computer via NFC, based on user authorization, the on-board computer does not need to transmit the token to the vehicle server for verification, and can directly log in to the corresponding user account. When the on-board computer and the vehicle server communicate well later, the login information will be uploaded to the vehicle server, which can effectively improve the on-board computer account login experience in weak network environments such as underground garages.

[0033] When using, the specific process is as follows Figure 2 As shown: 1. The mobile terminal launches the vehicle APP user to log in and authorize the account on the one-click login interface. The authorization method can be through fingerprint authentication on the mobile terminal; and a login request is initiated to the vehicle server; 2. After the vehicle server authentication is passed, complete the login of the mobile terminal; 3. After the user authorizes, he / she applies to bind the vehicle relationship, and encrypts the user account information and vehicle information and transmits them to the vehicle server, which will retain the data; 4. The vehicle server generates a token based on the user account information and vehicle information, and sets the validity period of the token according to the system settings; 5. After the user activates the token, the token is stored in the secure area of ​​the mobile terminal; 6. When in use, the mobile terminal and the vehicle-mounted computer establish a communication channel through NFC, and the mobile terminal transmits the login token corresponding to the user account to the vehicle-mounted computer through the NFC communication channel; 5. The onboard computer uploads the login token to the vehicle server for decryption. The vehicle server verifies the decrypted user's mobile phone number and device IMEI number with the information corresponding to the mobile terminal, and verifies the token validity period; 7. After verification, the vehicle server sends a command to allow the on-board computer to log in to the user account and complete the login.

[0034] In another embodiment of the present application, a multi-user authorization mechanism is also provided. Since the current relationship between users and vehicles is more complicated, family vehicle sharing, vehicle rental and other phenomena are more common, so there are widespread situations where multiple users use the same vehicle. And since the vehicle computer account involves user information, if the account information is also disclosed to other users when the vehicle is loaned out, there will be a problem of important information leakage. If each user is required to register a vehicle computer account separately and then log in, the process is complicated and the experience is not good, and the owner also lacks permission management for multiple user accounts, and in the case of multiple users, the efficiency of vehicle computer account login further affects the user experience. For this reason, the present application provides a multi-user authorization mechanism based on the method one, which divides the login token into a car owner token and an affiliated token. The car owner generates the car owner token after the vehicle APP performs account login authorization. The car owner logs in to the vehicle terminal through the car owner token to display the information required by the car owner.

[0035] The vehicle server generates a subsidiary token based on the vehicle owner token and the authorized mobile phone number, and sends it to the corresponding mobile terminal for storage according to the authorized mobile phone number. After authorization, the subsidiary user logs in to the vehicle terminal through the subsidiary token. The vehicle terminal only displays the corresponding content as needed, and hides the private content set by the vehicle owner. The specific process is as follows: Figure 3 As shown: 1. After the car owner completes the binding of the account and the vehicle in the vehicle APP, the server generates a unique token associated with the car owner's account and adds an identifier to the token as the car owner token.

[0036] 2. The car owner initiates a request to the vehicle server in the vehicle APP, applies for a token for other users based on their mobile phone number and adds an identification mark as an affiliated token.

[0037] 3. The generation of the subsidiary token is based on the owner token and the authorized subsidiary user's mobile phone number. The specific generation method of the subsidiary token is as follows: Step 31: The car owner token string, the affiliated user's mobile phone number, and the validity period are combined into a dictionary and then serialized into a JSON string; Step 32: Randomly generate an initialization vector IV; Step 33: Encrypt the JSON data using the key and IV and pad it using PKCS7; Step 34: Concatenate the IV and the ciphertext, and then perform Base64 encoding to complete the token generation.

[0038] 4. The vehicle server will send the generated subsidiary token to the vehicle APP of other users based on the mobile phone number. The subsidiary user activates the token on the APP and stores it in the secure storage area of ​​the corresponding mobile terminal.

[0039] 5. The mobile terminal of the affiliated user returns the activation result to the vehicle server, and the vehicle server feeds back the activation result of the affiliated token to the mobile terminal of the vehicle owner and starts the record validity period.

[0040] 6. The affiliated user uses the mobile terminal to transmit the affiliated login token to the in-vehicle computer through the NFC communication channel via NFC. The in-vehicle computer transmits the login token to the vehicle server for verification. If the information verification is inconsistent or the token has expired, the verification fails and the login is not allowed.

[0041] Based on the above embodiments, according to the multi-user authorization mechanism proposed in this application, the account permissions can be automatically configured for users logging in with different tokens, and a database for different accounts can be established to retain the account historical data, providing a better user experience after the user logs in. The specific process is as Figure 4 shown: 1. The mobile terminal of the user establishes a communication channel with the in-vehicle computer through NFC and transmits its own token to the in-vehicle computer through NFC for verification; 2. The in-vehicle computer transmits the token to the vehicle server for verification. After the verification passes, the login is allowed; 3. The in-vehicle computer enables the corresponding permissions according to the token attributes, including: Requesting the vehicle server to obtain the historical data corresponding to the account; the vehicle server returns the corresponding historical data to the in-vehicle computer, and the in-vehicle computer obtains the corresponding service policy according to the historical data, such as the in-vehicle computer screensaver setting, the APP display under the current permissions, the APP corresponding account login, etc.

[0042] As Figure 2 shown, the in-vehicle computer account login system adopting the above NFC-based in-vehicle computer account login method includes: The mobile terminal refers to devices such as the user's smart phone, watch or pad, which are equipped with the vehicle APP and already have user accounts, and the devices have the NFC function. It is used to connect with the in-vehicle computer through NFC to establish an NFC communication channel; and transmit the login token to the in-vehicle computer through the NFC communication channel; NFC refers to Near Field Communication, a near-field communication technology that can establish a near-field communication channel with other terminals with NFC encryption chips to achieve data transmission.

[0043] The in-vehicle computer, that is, the in-vehicle terminal, is used to establish an NFC communication channel with the mobile terminal and communicate with the vehicle server, and can log in to the bound user account to provide richer in-vehicle control services; the NFC module of the in-vehicle terminal is, for example, set at the mobile phone wireless charging place, and when the mobile phone is placed there, it can be automatically connected and the in-vehicle terminal can log in; it can also be set at the door handle, and when the vehicle owner approaches, it can be automatically connected.

[0044] A vehicle server refers to the back-end service platform of the vehicle APP and in-vehicle computer, which is used to implement user account authentication, establish the association relationship between the user account and the vehicle, and perform token information verification, generate and distribute keys, etc.

[0045] According to the third aspect of the present application, a server is provided, including: a memory 501 and at least one processor 502; The memory 501 stores a computer program, and the at least one processor 502 executes the computer program stored in the memory 501 to implement the above-mentioned NFC-based in-vehicle computer account login method.

[0046] According to an embodiment of the present application, the beneficial effects of adopting the NFC-based in-vehicle computer account login method are as follows: compared with the existing mainstream methods, the user operation is simpler and the usage process is faster. First, compared with the SMS verification code method, this solution does not require the user to manually enter the mobile phone number on the in-vehicle computer, nor does it require waiting to receive the verification code and then operating to fill it back, so the operation is simpler; second, compared with the QR code scanning login method, this solution uses NFC interaction, and does not require the user to click on the QR code scanning function on the vehicle APP, so the process is faster; the token generation adopts a symmetric encryption algorithm to ensure that key information cannot be tampered with or misused, further improving security.

[0047] It should be noted that the above detailed description is exemplary and is intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present application belongs.

[0048] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should also be understood that when the terms "comprise" and / or "include" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0049] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0050] In addition, the terms "comprising", "having", and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to such process, method, product, or apparatus.

[0051] For ease of description, spatial relative terms such as "above", "over", "on the upper surface", "upper", etc. may be used herein to describe the spatial positional relationship of one device or feature to other devices or features as shown in the figures. It should be understood that the spatial relative terms are intended to encompass different orientations in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is inverted, a device described as "above" or "over" other devices or structures will then be positioned "below" or "under" other devices or structures. Thus, the exemplary term "above" can include both orientations of "above" and "below". The device may also be positioned in other different ways, such as rotated 90 degrees or in other orientations, and the corresponding explanations for the spatial relative descriptions used herein will be made.

[0052] In the detailed description above, reference has been made to the accompanying drawings, which form a part hereof. In the drawings, like symbols typically identify like components, unless the context indicates otherwise. The illustrated embodiments described in the detailed description, the drawings, and the claims are not meant to be limiting. Other embodiments may be used and other changes may be made without departing from the spirit or scope of the subject matter presented herein.

[0053] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. The NFC-based vehicle computer account login method is characterized by: The steps include: Step 1: The mobile terminal and the vehicle computer are connected via NFC to establish an NFC communication channel; Step 2: After the mobile terminal authorizes, the login token is transmitted to the vehicle computer through the NFC communication channel; Step 3: The onboard computer verifies the login token, and after the verification is passed, the onboard computer logs in to the user account.

2. The NFC-based vehicle-mounted computer account login method according to claim 1, characterized in that: The login token includes encrypted user account information and associated vehicle information, the user account information includes the user's mobile phone number, mobile device IMEI number, Internet Protocol IP address and Media Access Control MAC address, and the vehicle information includes the vehicle VIN code; the on-board computer sends the login token to the vehicle server for decryption and verification, and the vehicle server compares and verifies the pre-stored user account information with the vehicle information.

3. The NFC-based vehicle-mounted computer account login method according to claim 2, characterized in that: A vehicle APP is installed in the mobile terminal. When used for the first time, the vehicle APP obtains user account information and vehicle information after account login authorization, and sends the user account information and vehicle information to the vehicle server for pre-storage.

4. The NFC-based vehicle-mounted computer account login method according to claim 3, characterized in that: Account login authorization includes verification code verification, password verification and biometric verification, and the biometric verification includes fingerprint verification and / or face recognition verification of the mobile terminal.

5. The NFC-based vehicle-mounted computer account login method according to claim 3, characterized in that: After the vehicle APP's account login is authorized, the vehicle server packages and encrypts the user account information and vehicle information to form the login token, and stores it in the secure storage area of ​​the mobile terminal.

6. The NFC-based vehicle-mounted computer account login method according to claim 1, characterized in that: In step 2, the mobile terminal authorization includes one or more of clicking a confirmation button, fingerprint verification, or face recognition verification.

7. The NFC-based vehicle-mounted computer account login method according to claim 5, characterized in that: The login token includes a vehicle owner token and an accessory token. The vehicle owner token is generated after the vehicle APP account login is authorized. The accessory token is generated by the vehicle server based on the vehicle owner token and the authorized mobile phone number, and is sent to the corresponding mobile terminal for storage based on the authorized mobile phone number.

8. The NFC-based vehicle-mounted computer account login method according to claim 7, characterized in that: The vehicle server packages and encrypts the character string of the vehicle owner token, the authorized mobile phone number and the validity period to form the subsidiary token. When verifying the subsidiary token in step 3, the verification of the validity period is included.

9. A vehicle-mounted computer account login system using the NFC-based vehicle-mounted computer account login method according to any one of claims 1 to 8, characterized in that: include: The mobile terminal is used to connect with the vehicle-mounted computer through NFC to establish an NFC communication channel; and transmit the login token to the vehicle-mounted computer through the NFC communication channel; The vehicle terminal is used to establish an NFC communication channel with the mobile terminal and communicate with the vehicle server; The vehicle server is used to obtain the user's mobile phone number and verify the login token.

10. A server, characterized in that: include: memory and at least one processor; The memory stores a computer program, and the at least one processor executes the computer program stored in the memory to implement the NFC-based in-vehicle computer account login method as described in any one of claims 1 to 8.

Images