Vehicle-mounted login method, system, device and storage medium

Abstract

The present application provides a vehicle-mounted login method, system, device and storage medium, comprising the following steps: in response to detecting that a system login interface is opened, establishing a connection between a first vehicle-mounted electronic device and an electronic device; based on the connection, obtaining login data; based on the login data, generating a login request, the login request including the login data; based on the login request, obtaining a request result of the login request for presentation; and in the case where it is determined that the request result is a successful request, logging into the system based on the request result. The request result, request progress, and request failure reason are output in the vehicle-mounted electronic device or electronic device. In the event of a login failure, there is no need to find the source of the error by parsing the error log, and the login result can be fed back to the user in a more intuitive and timely manner.

Description

Technical Field

[0001] The present application relates to the automotive field, and in particular to an in-vehicle login method, system, device and storage medium. Background Art

[0002] With the development of science and technology, in-vehicle equipment is developing in the direction of intelligence and informationization. The development of smart cars allows every car user to have his own in-vehicle account, and after logging into the system with the in-vehicle account, he can set the vehicle settings by himself, such as air conditioning temperature, frequently played music, driving mode, etc. Users only need to log in to their in-vehicle account on the vehicle side, so that the in-vehicle system automatically loads the vehicle settings set by the user, and they can enjoy a personalized car experience.

[0003] At present, there are many ways to log in to the vehicle system, such as wireless network login, Bluetooth login, scanning QR code login, etc. In the case of login failure, the error cause is often found by parsing the error log and feedback is sent to the vehicle end. However, parsing the error log is very time-consuming and the login result cannot be fed back to the user in time. Summary of the invention

[0004] One purpose of the present application is to provide a vehicle-mounted login method, system, device and storage medium, which outputs the request results, request progress and request failure reasons during the vehicle-mounted login process to a vehicle-mounted electronic device or electronic device. The advantage is that in the event of a login failure, there is no need to parse the error log to find the source of the error, and the login results can be fed back to the user more intuitively and promptly.

[0005] Another object of the present application is to provide a vehicle-mounted login method, system, device and storage medium to establish a near-field communication connection between vehicle-mounted electronic devices and electronic devices, and obtain vehicle-mounted login data based on the connection. The advantage is that the information interaction based on the near-field communication connection belongs to triggered information transmission, and the information interaction can be completed in a short time; there are no cumbersome operations throughout the process, and easy, fast and automatic communication is established between the vehicle-mounted electronic devices and the electronic devices.

[0006] Another purpose of the present application is to provide a vehicle-mounted login method, system, device and storage medium, which uses public key encryption and private key decryption to encrypt data transmission during the vehicle-mounted login process. The advantage is that the data is encrypted using public key encryption and private key decryption to ensure that the communication data will not be known to a third party, effectively preventing the leakage of privacy data involved in the vehicle-mounted login, and ensuring the security of the data.

[0007] Another purpose of the present application is to provide a vehicle-mounted login method, system, device and storage medium. After the vehicle-mounted electronic device receives a successful login request for login data, it verifies again whether the login data matches the account information of the vehicle-mounted electronic device. The advantage of this application is that it improves system security and ensures the safe operation of the system by re-verifying whether the login data matches the information of the vehicle-mounted electronic device.

[0008] To achieve the above-mentioned objectives, in a first aspect, the present application provides a vehicle-mounted login method, comprising the following steps: in response to detecting that a system login interface is opened, establishing a connection between a first vehicle-mounted electronic device and an electronic device; based on the connection, obtaining login data; based on the login data, generating a login request, the login request including the login data; based on the login request, obtaining a request result of the login request for presentation; and in a case where it is determined that the request result is a successful request, logging into the system based on the request result.

[0009] The method provided in the first aspect is implemented, and after obtaining the request result of the login request, the request result is presented; the request result includes: at least one of request progress, request success, request failure, and request failure reason. As can be seen from the above, the request result is fed back to the user intuitively and promptly, and in the event of a request failure, the source of the error can be found without parsing the error log.

[0010] In combination with the first aspect, in some embodiments, the establishment of a connection between the first vehicle-mounted electronic device and the electronic device includes the following steps: determining whether a near-field communication function is in an on-state; and if it is determined that the near-field communication function is in an on-state, establishing a near-field communication connection between the first vehicle-mounted electronic device and the electronic device; if it is determined that the near-field communication function is not in an on-state, turning on the near-field communication function to establish a near-field communication connection between the first vehicle-mounted electronic device and the electronic device. It takes a short time to establish a near-field communication connection, and a communication connection between the first vehicle-mounted electronic device and the electronic device can be established quickly; and the information interaction based on the near-field communication connection belongs to a triggered information transmission, and the information interaction can be completed in a short time; there is no cumbersome operation throughout the process, and easy, rapid and automatic communication is established between the first vehicle-mounted electronic device and the electronic device.

[0011] In combination with the first aspect, in some embodiments, before obtaining the login data, the method further includes the following steps: generating a public key and a private key; the public key is used to encrypt the communication data to obtain the private data, and the private key is used to decrypt the private data to obtain the communication data. The communication data is encrypted using the public key encryption and private key decryption method. The sender encrypts the communication data with the private key, and only the person holding the private key can decrypt it, ensuring that the communication data will not be known to a third party, effectively preventing the leakage of private data during the vehicle login process, and ensuring the security of the data.

[0012] In combination with the first aspect, in some embodiments, the acquisition of login data includes the following steps: acquiring the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device, the device information of the first vehicle-mounted electronic device is obtained by using the public key to perform encryption and then using the private key to perform decryption, and the communication identification of the electronic device is obtained via the electronic device; or acquiring the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device, the communication identification of the electronic device is obtained by using the public key to perform encryption and then using the private key to perform decryption, and the device information of the first vehicle-mounted electronic device is obtained via the first vehicle-mounted electronic device; and combining the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device to obtain the login data. As can be seen from the above, the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device are encrypted by using the public key encryption and private key decryption method, and the sender encrypts the login data by the private key. Only the person holding the private key can decrypt and obtain the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device, ensuring that the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device will not be known by a third party, effectively preventing the leakage of data during the vehicle login process, and ensuring the security of the data.

[0013] In combination with the first aspect, in some embodiments, obtaining the request result of the login request includes the following steps: encrypting the request result using the public key to obtain second encrypted data; and decrypting the second encrypted data using the private key to obtain the request result. After receiving the request result of the login request returned by the server, the electronic device uses the first public key to encrypt the request result data to obtain second encrypted data, and sends the second encrypted data to the first vehicle-mounted electronic device; after receiving the second encrypted data, the first vehicle-mounted electronic device uses the first private key to decrypt the second encrypted data to obtain the request result data. As can be seen from the above, the request result data is encrypted by using the public key encryption and private key decryption method. The sender encrypts the request result data using the private key. Only the person holding the private key can decrypt and obtain the request result data, ensuring that the vehicle-mounted account information contained in the request result will not be known by a third party, effectively preventing the leakage of the vehicle-mounted account data during the vehicle-mounted login process, and ensuring the security of the vehicle-mounted account data.

[0014] In combination with the first aspect, in some embodiments, the login data includes device information of the first vehicle-mounted electronic device so as to identify the first vehicle-mounted electronic device; the obtaining of the request result of the login request so as to facilitate presentation includes the following steps: obtaining the request result of the login request, the request result including the device information of the first vehicle-mounted electronic device, the device information of the first vehicle-mounted electronic device being obtained based on the login data; obtaining the device information of the second vehicle-mounted electronic device; determining whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device; and in the case where it is determined that the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device, determining that the request result is a successful request; When it is determined that the device information of the second vehicle-mounted electronic device is inconsistent with the device information of the first vehicle-mounted electronic device, the request result is determined to be a request failure, and a prompt message is presented at the second vehicle-mounted electronic device or the electronic device, and the prompt message is used to indicate the request result. As can be seen from the above, a method of re-verifying whether the device information data of the first vehicle-mounted electronic device matches the current vehicle-mounted electronic device information is adopted. When the device information of the first vehicle-mounted electronic device does not match the device information of the second vehicle-mounted electronic device, the request result is determined to be a request failure, thereby improving system security and ensuring safe operation of the system, and presenting a prompt message of the request result at the second vehicle-mounted electronic device or the electronic device, and providing intuitive and timely feedback of the request result to the user.

[0015] In combination with the first aspect, in some embodiments, the login data includes the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device, and the obtaining of the request result of the login request for presentation includes the following steps: obtaining the request result of the login request; and in a case where it is determined that the request result is that there is no device information of the vehicle-mounted electronic device corresponding to the device information of the first vehicle-mounted electronic device, determining that the request result is a request failure, and outputting a prompt message, wherein the prompt message is used to indicate at least one of the request result, request progress, and the reason for the request failure; in a case where it is determined that the request result is that the communication identifier of the electronic device is in an invalid state, determining that the request result is a request failure, and outputting a prompt message, wherein the prompt message is used to indicate at least one of the request result, request progress, and the reason for the request failure. For example, when it is determined that the request result is that there is no device information of the vehicle-mounted electronic device corresponding to the unique identifier of the first vehicle-mounted electronic device, a prompt message is output indicating that the request failed and the reason for the request failure is that the vehicle-mounted electronic device information has not been stored in the database; from the above, it can be seen that the request result, request progress and reason for the request failure are intuitively output to the electronic device or the first vehicle-mounted electronic device; in the event of a login failure, there is no need to find the source of the error by parsing the error log, and the login result can be fed back to the user in a more intuitive and timely manner.

[0016] In combination with the first aspect, in some embodiments, the establishment of a connection between the first vehicle-mounted electronic device and the electronic device further includes the following steps: based on the connection status between the first vehicle-mounted electronic device and the electronic device, outputting prompt information to indicate the progress and result of establishing the connection between the first vehicle-mounted electronic device and the electronic device. For example, after the connection between the first vehicle-mounted electronic device and the electronic device is successfully established, outputting prompt information of the progress of successfully establishing the connection between the first vehicle-mounted electronic device and the electronic device; as can be seen from the above, the connection progress between the first vehicle-mounted electronic device and the electronic device in the login process is intuitively and promptly fed back to the user; the login process is displayed so as to feedback the login progress to the user and locate the error source in a timely manner when an error occurs.

[0017] In combination with the first aspect, in some embodiments, the acquisition of login data further includes the following steps: based on the acquisition status of the login data, outputting prompt information to indicate the progress and result of acquiring the login data. For example, after successfully acquiring the login data, outputting prompt information indicating the progress of successfully acquiring the login data; as can be seen from the above, displaying the acquisition progress of the login data is convenient for providing feedback to the user on the login progress and timely locating the source of the error when an error occurs.

[0018] In combination with the first aspect, in some embodiments, if it is determined that the near field communication function is turned on, establishing a near field communication connection between the first vehicle-mounted electronic device and the electronic device further includes the following steps: outputting a prompt message that the near field communication function is turned on. The near field communication connection status between the first vehicle-mounted electronic device and the electronic device is displayed to facilitate feedback to the user on the login progress and timely locate the error source when an error occurs.

[0019] In combination with the first aspect, in some embodiments, if it is determined that the near field communication function is not turned on, turning on the near field communication function to establish a near field communication connection between the first vehicle-mounted electronic device and the electronic device also includes the following steps: based on the turning-on state of the near field communication function, outputting prompt information to indicate the turning-on progress and result of the near field communication function. Displaying the connection progress of the near field communication connection between the first vehicle-mounted electronic device and the electronic device to facilitate feedback to the user on the login progress and timely locating the error source when an error occurs.

[0020] In combination with the first aspect, in some embodiments, the progress prompt information includes graphic information and voice broadcast, the graphic information includes text prompt information, static image information, dynamic image information, and the text prompt information includes time information and progress prompt. For example, in the process of acquiring login data, a dynamic image of a packaged package transmitting data is displayed, the words "acquiring login data" are output, and the voice broadcast "acquiring login data" is voiced; it can be seen from the above that the login progress prompt information is output during the vehicle login process, so as to intuitively and promptly feedback the login progress to the user and locate the error source in time when an error occurs.

[0021] In a second aspect, the present application provides a vehicle-mounted login device, comprising:

[0022] Connecting unit;

[0023] an acquisition unit, wherein the connection unit and the acquisition unit are communicably connected to each other, wherein the connection unit establishes a connection between the first vehicle-mounted electronic device and the electronic device in response to detecting that the system login interface is opened, and the acquisition unit acquires the login data based on the connection between the first vehicle-mounted electronic device and the electronic device established by the connection unit;

[0024] A request generating unit, wherein the request generating unit and the acquiring unit are communicably connected to each other, wherein the request generating unit generates a login request based on the login data acquired by the acquiring unit, the login request including the login data; and the acquiring unit acquires a request result of the login request based on the login request generated by the request generating unit;

[0025] a display unit, wherein the display unit and the acquisition unit are communicatively connected to each other so that the display unit presents the request result acquired by the acquisition unit; and

[0026] A login unit, wherein the login unit and the acquisition unit are communicably connected to each other, wherein the login unit logs into the system based on the request result when determining that the request result acquired by the acquisition unit is a successful request.

[0027] In a third aspect, the present application provides a vehicle-mounted login system, comprising:

[0028] Connect modules;

[0029] an acquisition module, wherein the connection module and the acquisition module are communicatively connected to each other, wherein the connection module establishes a connection between the first vehicle-mounted electronic device and the electronic device in response to detecting that the system login interface is opened, and the acquisition module acquires the login data based on the connection between the first vehicle-mounted electronic device and the electronic device established by the connection module;

[0030] A request generation module, wherein the request generation module and the acquisition module are communicatively connected to each other, wherein the request generation module generates a login request based on the login data acquired by the acquisition module, the login request including the login data; and the acquisition module acquires a request result of the login request based on the login request generated by the request generation module;

[0031] a display module, wherein the display module and the acquisition module are communicatively connected to each other so that the display module presents the request result acquired by the acquisition module; and

[0032] A login module, wherein the login module and the acquisition module are communicatively connected to each other, wherein the login module logs into the system based on the request result when determining that the request result acquired by the acquisition module is a successful request.

[0033] In a fourth aspect, the present application provides a computer device, comprising: a memory, a processor, wherein the memory and the processor are communicatively connected to each other; wherein the memory stores program instructions; when the program instructions are executed by the processor, the processor executes the method described in the first aspect and any possible implementation method of the first aspect.

[0034] In a fifth aspect, the present application provides a computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium; when the computer program runs on one or more processors, the method described in the first aspect and any possible implementation of the first aspect is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below.

[0036] Figure 1 A schematic diagram of the system environment application provided in the embodiment of the present application;

[0037] Figure 2 A flow chart of a vehicle login method provided in an embodiment of the present application;

[0038] Figure 3 A flowchart of another vehicle login method provided in an embodiment of the present application;

[0039] Figure 4 A flow chart of a method for interaction between a first vehicle-mounted electronic device and an electronic device provided in an embodiment of the present application;

[0040] Figure 5A A schematic diagram of a process for obtaining login data provided in an embodiment of the present application;

[0041] Figure 5B A flow chart of an interaction method between a first vehicle-mounted electronic device, an electronic device and a server provided in an embodiment of the present application;

[0042] Figure 6 A flowchart of a specific method for obtaining a request result of the login request provided in an embodiment of the present application;

[0043] Figure 7 A flowchart of another specific method for obtaining a request result of the login request provided in an embodiment of the present application;

[0044] Figure 8 A schematic diagram of a vehicle-mounted login device provided in an embodiment of the present application;

[0045] Fig. 9 A schematic diagram of a vehicle login system provided in an embodiment of the present application;

[0046] Fig.10 A flow chart of a vehicle login method provided in an embodiment of the present application;

[0047] Fig.11A A flow chart of a vehicle login method provided in an embodiment of the present application;

[0048] Fig. 11B A flow chart of a vehicle login method provided in an embodiment of the present application;

[0049] Fig.12 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The present invention is further described in detail below in conjunction with the accompanying drawings.

[0051] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and appended claims of the present application, the singular expressions "a", "a", "said", "the" and "this" are intended to also include plural expressions, unless there is a clear indication to the contrary in the context.

[0052] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0053] The embodiments of the present application provide a vehicle-mounted login method, system, device and storage medium. In order to more clearly describe the solution of the present application, some knowledge related to the vehicle-mounted login of this solution is first introduced below.

[0054] Near Field Communication: A short-range wireless communication technology. Devices using the near-field communication technology can exchange data when they are close to each other. The communication distance is generally 0 to 10 cm. The use of the near-field communication function between devices enables contactless point-to-point data transmission. For example, multiple digital cameras and mobile phones with NFC functions can use NFC technology to wirelessly interconnect to achieve data exchange such as virtual business cards or digital photos. To achieve point-to-point data exchange between two devices through the near-field communication function, the key is to establish a near-field communication connection between two devices that both have near-field communication functions. The connection method is also very simple. The connection can be completed by approaching each other at a close distance. There is no extra operation in the connection process. The establishment time is only about 0.1 seconds. After the connection is established, communication interaction can be achieved.

[0055] Key pair: In asymmetric encryption technology, there are two types of keys, private key and public key. The private key is held by the key pair owner and cannot be published. The public key is published by the key pair holder to others. The public key and private key are a pair, and both can be used for encryption or decryption. There are two ways of public key and private key encryption and decryption. One is public key encryption and private key decryption, which is used in encryption scenarios. Information decrypted using the public key is released to the public key owner. This information may be tampered with by others, but it cannot be obtained by others except the private key holder. Only the private key can be used to decrypt the data encrypted with the public key to obtain the decrypted data, ensuring data security. The other is private key encryption and public key decryption, which is used in signature scenarios to allow all public key owners to verify the identity of the private key owner and to prevent the content published by the private key owner from being tampered with, ensuring the uniqueness of the data source.

[0056] Combine the following Figure 1 A detailed introduction to the system environment application:

[0057] like Figure 1 As shown, the system environment application includes an electronic device 101, an in-vehicle electronic device 102, and a server 103;

[0058] In some embodiments, the electronic device 101 may be an electronic device with wireless transceiver capability and capable of accessing the Internet, such as but not limited to a mobile phone, a smart phone, a laptop computer, a tablet computer, a personal digital assistant (PDA), a wearable device, etc.

[0059] In some embodiments, the electronic device 101 may include at least a communication module, a memory, and a processor. The memory is used to store one or more computer programs. The processor is coupled to the memory and executes one or more programs so that the electronic device 101 can perform one or more functions. The communication module is used to communicate with at least one of the in-vehicle electronic device 102 and the server 103. In some embodiments, the communication module may include a direct communication module, which is used to directly communicate with the in-vehicle electronic device 102. For example, in response to detecting that the system login interface is opened, the direct communication module may establish a connection with the in-vehicle electronic device 102 through any direct communication technology such as Bluetooth, wifi, zigbee, near field communication (NFC) and USB, and based on the connection, obtain login data from the in-vehicle electronic device 102.

[0060] Alternatively or additionally, the communication module may include a cellular communication module for communicating with at least one of the in-vehicle electronic device 102 and the server 103 via a cellular network. For example, the cellular communication module may communicate with at least one of the in-vehicle electronic device 102 and the server 103 via any cellular communication technology such as 5G, LTE, EVDO, CDMA, GPRS, and EDGE. The electronic device 101 may, for example, generate a login request based on the login data, and send the login request to the server 103 via the cellular communication module; and obtain a request result of the login request from the server 103.

[0061] In some embodiments, the electronic device 101 may also include a display module to present relevant information, such as the request result of the login request. It can be seen from the above that the electronic device 101 acts as a communication bridge between the vehicle-mounted electronic device 102 and the server 103. After successfully establishing a connection with the vehicle-mounted electronic device 102 and obtaining the login data, the electronic device 101 initiates a login request to the server 103, receives the request result of the login request, and feeds the request result back to the vehicle-mounted electronic device 102, acting as a medium for data transmission between the vehicle-mounted electronic device 102 and the server 103.

[0062] The in-vehicle electronic device 102 is, for example, but not limited to, an in-vehicle computer, an in-vehicle controller, etc. The in-vehicle electronic device 102 includes at least a processor and a memory. The memory is used to store one or more computer programs. The processor is coupled to the memory and executes one or more programs so that the in-vehicle electronic device 102 can perform one or more functions. In some embodiments, the in-vehicle electronic device 102 can log in to the system based on the request result of the login request generated based on the login data received from the electronic device 101.

[0063] In some embodiments, the vehicle-mounted electronic device 102 may further include a communication module, such as a T-BOX, which may be used to communicate with at least one of the electronic device 101 and the server 103. The communication module here is similar to the communication module of the electronic device 101, and will not be described here. In some embodiments, the vehicle-mounted electronic device 102 detects that the system login interface is opened, and then establishes a connection with the electronic device 101 through the communication module. In other embodiments, the vehicle-mounted electronic device 102 may send login data to the electronic device 101, or may receive a request result of a login request generated based on the login data from the electronic device 101. In some embodiments, the vehicle-mounted electronic device 101 may further include a vehicle-mounted display or be coupled to a vehicle-mounted display to present relevant information, such as the request result. As can be seen from the above, the vehicle-mounted electronic device 102, as the initiator of the login request, obtains the login data after successfully establishing a connection with the electronic device 101, generates a login request, initiates a login request to the server 103, and receives the request result of the login request. When the request result is a successful request, the login system establishes a communication interconnection with the server 103.

[0064] The server 103 can communicate with at least one of the electronic device 101 and the vehicle-mounted electronic device 102. The server 103 includes, but is not limited to, a personal computer, a server computer, a multiprocessor system, a mainframe computer, and a distributed computing environment including any one of the above systems or devices. In some embodiments, the server 103 may have one or more processing units, including dedicated processing units such as GPUs, FPGAs, and ASICs, and general processing units such as CPUs. In addition, one or more virtual machines may also be running on the server 103.

[0065] In some embodiments, the server 103 can receive a login request from the electronic device 101, obtain a request result of the login request based on the login request, and send it to the electronic device 101 or send it to the vehicle-mounted electronic device 102 via the electronic device 101, so as to be presented at the vehicle-mounted electronic device or electronic device. As can be seen from the above, the server 103, as the processing end of the login request, obtains the login data, generates the login request, verifies the login request, and obtains the request result of the login request; when the request result is a successful request, the login system establishes a direct communication connection with the vehicle-mounted electronic device 102.

[0066] The following is a further introduction to some drawings involved in this application.

[0067] See also Figure 2 , Figure 2 This is a flow chart of a vehicle login method provided in an embodiment of the present application. Figure 2 As stated,

[0068] Step 201: in response to detecting that a system login interface is opened, establishing a connection between a first vehicle-mounted electronic device and an electronic device.

[0069] In some embodiments, the first vehicle-mounted electronic device may detect whether the system login interface at the first vehicle-mounted electronic device is opened, or the electronic device may detect whether the system login interface at the electronic device is opened. In the case where it is determined that the system login interface at the first vehicle-mounted electronic device and the electronic device is opened, a connection between the first vehicle-mounted electronic device and the electronic device is established. In some embodiments, after both the electronic device and the first vehicle-mounted electronic device open the system login interface, the electronic device is brought close to the first vehicle-mounted electronic device to establish a connection between the first vehicle-mounted electronic device and the electronic device. Specifically, after detecting that the login system page is opened, a page activity class is created. When the first vehicle-mounted electronic device is successfully connected to the electronic device, due to a change in the connection state, the page activity receives a new data packet (Intent), triggering the program to call the onNewIntent method, obtain and parse the data packet, and when the content of the data packet indicates that the connection is successful (for example, the parameter value indicating the connection result contained in the data packet is 1), it indicates that the first vehicle-mounted electronic device is successfully connected to the electronic device. It should be understood that when the first vehicle-mounted electronic device does not open the system login interface, the first vehicle-mounted electronic device will not obtain the connection status between the first vehicle-mounted electronic device; when the electronic device does not open the system login interface, the electronic device will not obtain the connection status between the first vehicle-mounted electronic device.

[0070] Step 202: Acquire login data based on the connection.

[0071] The login data is the data required for logging into the system, including at least one of the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device (such as a token, etc.). The device information of the first vehicle-mounted electronic device includes at least one of the unique identification of the first vehicle-mounted electronic device (such as a PDSN) and the unique identification of the vehicle associated with the first vehicle-mounted electronic device (such as a VIN) (hereinafter, the content contained in the device information of the first vehicle-mounted electronic device is the same as here and will not be repeated). The unique identification of the first vehicle-mounted electronic device is the unique identification of the vehicle central control host; the unique identification of the vehicle is the vehicle identification number (VIN), which is a set of seventeen letters or numbers, a unique number used on the car, which can identify the manufacturer, engine, chassis serial number and other performance information of the car (hereinafter, the definition of the unique identification of the first vehicle-mounted electronic device and the unique identification of the vehicle is the same as here and will not be repeated). The communication identification of the electronic device is required for the electronic device to communicate with the server, that is, when the electronic device needs to interact with the server for data (such as an electronic device account login request, a first vehicle-mounted electronic device account login request), the electronic device needs to carry the communication identification to initiate a request to the server. In some embodiments, the first in-vehicle electronic device may acquire the login data based on a connection established between the first in-vehicle electronic device and the electronic device.Specifically, the first vehicle-mounted electronic device obtains the login data according to the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device; preferably, the login data is obtained by combining the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device, for example, the login data includes the unique identification (PDSN) of the first vehicle-mounted electronic device and the communication identification (token) of the electronic device, the login data includes the unique identification (VIN) of the vehicle associated with the first vehicle-mounted electronic device and the communication identification (token) of the electronic device, or the login data includes the unique identification (PDSN) of the first vehicle-mounted electronic device, the unique identification (VIN) of the vehicle associated with the first vehicle-mounted electronic device and the communication identification (token) of the electronic device. The communication identification (token) of the electronic device is obtained by the first vehicle-mounted electronic device in the following specific method: when the page activity receives a new data packet sent by the electronic device, the array of the data packet is obtained by calling the getParcelableArrayExtra method of the data packet class (Intent), and the array length of the NdefMessage object array is created by calculating the length of the array, and the loop algorithm is set to use the NdefMessage object array to receive the array of the data packet, and the data format of the array is converted to the NFC data exchange format (Data Exchange Format, NDEF), that is, forced to convert to the NdefMessage type, and the first NdefRecord object of the NdefMessage object array is obtained, and the byte array of the NdefRecord object is obtained by the getPayload method, and the string content of the byte array is obtained by the byte array construction method of Java String, and the communication identification of the electronic device is obtained. The first vehicle-mounted electronic device extracts the device information stored in the local device to obtain the device information of the first vehicle-mounted electronic device, wherein the device information includes at least one of the unique identification of the first vehicle-mounted electronic device and the unique identification of the vehicle.

[0072] In other embodiments, the electronic device may acquire the login data based on the connection between the first vehicle-mounted electronic device and the electronic device. Specifically, the electronic device obtains the login data according to the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device (for example, the login data is obtained by combining the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device); the specific method for the electronic device to obtain the device information of the first vehicle-mounted electronic device is: when the page activity receives a new data packet, the array of the data packet is obtained by calling the getParcelableArrayExtra method of the data packet class (Intent), and an NdefMessage object array with an array length equal to the array length of the data packet is created by calculating the length of the array, and a loop algorithm is set to use the NdefMessage object array to receive the array of the data packet, and the data format of the array is converted to NDEE (forced conversion to NdefMessage type), the first NdefRecord object of the NdefMessage object array is obtained, and the byte array of the NdefRecord object is obtained by the getPayload method, and the string content of the byte array is obtained by the byte array construction method of Java String, and the device information of the first vehicle-mounted electronic device is obtained, and the device information of the first vehicle-mounted electronic device includes at least one of the unique identifier of the first vehicle-mounted electronic device and the unique identifier of the vehicle associated with the first vehicle-mounted electronic device.

[0073] Step 203: Generate a login request based on the login data, wherein the login request includes the login data.

[0074] In some embodiments, the first vehicle-mounted electronic device or the electronic device may generate a login request based on the login data and send the request to the server.

[0075] Step 204: based on the login request, obtain a request result of the login request for presentation (for example, presentation at the first vehicle-mounted electronic device or the electronic device).

[0076] In some embodiments, the server may obtain a request result of the login request based on the login request. Specifically, after receiving the login request sent by the first vehicle-mounted electronic device or electronic device, the server generates a request result of the login request and sends it to the current vehicle-mounted electronic device or electronic device, so that the request result is presented at the vehicle-mounted electronic device or electronic device.

[0077] In other embodiments, the first vehicle-mounted electronic device or the electronic device may obtain the login request result from the server, and present the request result at the first vehicle-mounted electronic device or the electronic device.

[0078] Step 205: When it is determined that the request result is successful, log in to the system based on the request result.

[0079] In some embodiments, after obtaining the request result of the login request, the first vehicle-mounted electronic device or the electronic device can parse the request result by calling the error callback function to determine whether the request result is a successful request. Specifically, the program is set so that when the network request of the server for the login request is a successful request, the function called by the electronic device through the callback interface of Retrofit is onResponse, and when the network request of the login request is a request failure, the function called by the electronic device through the callback interface of Retrofit is onFailure. When the callback function is onResponse, the request status code (statusCode) of the data of the server is obtained; when the value of the request status code is 0, the request result is determined to be a successful request; when the value of the request status code is 1, the request result is determined to be a request failure; and the failure reason is obtained by obtaining the statusMessage of the login request. When the callback function is onFailure, the request result of the login request is determined to be a request failure, and the failure reason of the request result being a request failure is obtained through the getMessage method of the Throwable object. Generally, when the callback function is onFailure, it indicates that the failure reason is a network request failure.

[0080] In some embodiments, when it is determined that the request result is a successful request, the first vehicle-mounted electronic device or the electronic device logs in to the system based on the request result. For example, after the first vehicle-mounted electronic device receives the request result from a server or an electronic device, it logs in to the system based on a login identifier (e.g., a token) in the request result. The login identifier is required to log in to the system, and the system interface information and personalized information of the first vehicle-mounted electronic device (e.g., frequently played songs, driving mode, etc.) can be obtained from the system through the login identifier. For another example, after the electronic device receives the request result from the server, it sends the request result to the first vehicle-mounted electronic device so that the first vehicle-mounted electronic device logs in to the system.

[0081] Further integration Figure 3 Describes a specific method for establishing a connection between a first vehicle-mounted electronic device and an electronic device. Figure 3 , Figure 3 A flowchart of another vehicle login method provided in an embodiment of the present application. Figure 3 As shown, Figure 2 Step 201 establishes a connection between the first vehicle-mounted electronic device and the electronic device, including the following steps:

[0082] Step 301, determining whether the near field communication function is turned on.

[0083] In some embodiments, the first vehicle-mounted electronic device may determine whether the near field communication function of the first vehicle-mounted electronic device itself is in an on-state, or the electronic device may determine whether the near field communication function of the electronic device itself is in an on-state. In some embodiments, preferably, the first vehicle-mounted electronic device determines whether the near field communication function of the first vehicle-mounted electronic device is in an on-state, and the electronic device determines whether the near field communication function of the electronic device is in an on-state.

[0084] Specifically, taking the first vehicle-mounted electronic device as an example, by calling the isEnable method of the NfcAdapter class to obtain a return value, it is determined whether the near field communication function of the first vehicle-mounted electronic device is in an enabled state.

[0085] Step 302: If it is determined that the near field communication function is turned on, establish a near field communication connection between the first vehicle-mounted electronic device and the electronic device.

[0086] In some embodiments, if it is determined that the near field communication functions of the first vehicle-mounted electronic device and the electronic device are both in an on state, a near field communication connection is established between the first vehicle-mounted electronic device and the electronic device. Specifically, when the return value obtained by calling the isEnable method of the NfcAdapter class is "true", it indicates that the on state is on.

[0087] Step 303: If it is determined that the near field communication function is not enabled, enable the near field communication function to establish a near field communication connection between the first vehicle-mounted electronic device and the electronic device.

[0088] In some embodiments, if it is determined that the near field communication function of the first vehicle-mounted electronic device is not turned on, the near field communication function of the first vehicle-mounted electronic device is turned on. Specifically, when the return value obtained by calling the isEnable method of the NfcAdapter class is "false", it indicates that the turn-on state is not turned on; the near field communication function is automatically turned on by calling the enable method of the NfcAdapter class. And by creating an action instance to register the ACTION_ADAPTER_STATE_CHANGED broadcast, monitor the state change of the near field communication function, when receiving the data packet returned by the broadcast, and parsing the data packet to obtain the value of the parameter indicating the turn-on state of the near field communication function (for example, obtaining the parameter value of EXTRA_ADAPTER_STATE), when the value of the parameter is "STATE_ON", it indicates that the near field communication function is turned on; when the value of the parameter is "STATE_OFF", it indicates that the near field communication function is not turned on. In other embodiments, if it is determined that the near field communication function of the electronic device is not turned on, the near field communication function of the electronic device is turned on. Specifically, the method for enabling the near field communication function of the electronic device is consistent with the method for enabling the near field communication function of the first vehicle-mounted electronic device. The method for enabling the near field communication function of the first vehicle-mounted electronic device has been described in detail in step 301 and will not be repeated here.

[0089] The step of establishing a connection between the first vehicle-mounted electronic device and the electronic device also includes the following steps: based on the connection status between the first vehicle-mounted electronic device and the electronic device, outputting prompt information to indicate the progress and result of establishing the connection between the first vehicle-mounted electronic device and the electronic device.

[0090] In some embodiments, the prompt information can be output at the first vehicle-mounted electronic device, or at the electronic device. The prompt information includes graphic information and voice broadcast information. The graphic information includes text prompt information, static picture information, and dynamic picture information. The text prompt information includes time information and progress prompts (the form of the prompt information described below is the same as here and will not be repeated). For example, the prompt information includes two parts: a dynamic display part and a function timeline part. The dynamic display part displays the animation effect of the progress of the current task information (for example, when the near field communication function is turned on, the dynamic display part displays the animation effect of turning on the near field communication function); the timeline part includes displaying the text time and the text description information of the current task (for example, when the near field communication function is turned on, the timeline part includes the time display and the text description information that the near field communication function is being turned on).

[0091] If it is determined that the near field communication function is turned on, establishing a near field communication connection between the first vehicle-mounted electronic device and the electronic device also includes the following steps: outputting a prompt message that the near field communication function is turned on. In some embodiments, the prompt message can be output at the first vehicle-mounted electronic device, or at the electronic device. For example, after the first vehicle-mounted electronic device or the electronic device opens the interface for logging into the system, before waiting for the connection status to change so that the current page receives a new data packet, an animation effect of establishing a connection is displayed in the dynamic display part, and a text description of the task including "connecting device" is displayed in the timeline part.

[0092] See also Figure 4 , Figure 4 A flow chart of a method for interaction between a first vehicle-mounted electronic device and an electronic device provided in an embodiment of the present application. Figure 2 Before obtaining the login data based on the connection in step 203, the method further includes the following steps: generating a public key and a private key; the public key is used to encrypt the communication data to obtain the private data, and the private key is used to decrypt the private data to obtain the communication data.

[0093] Specifically, take the first vehicle-mounted electronic device generating the first public key and the first private key as an example. Figure 4 As shown, the generation of the public key and the private key includes the following steps: step 401, the first vehicle-mounted electronic device generates a first public key and a first private key; step 402, the electronic device generates a second public key and a second private key; step 403, the electronic device sends the second public key to the first vehicle-mounted electronic device; step 404, receiving and storing the second public key, that is, the first vehicle-mounted electronic device stores the second public key after receiving the second public key; step 405, the first vehicle-mounted electronic device sends the first public key to the electronic device after receiving the second public key; step 406, receiving and storing the first public key, that is, the electronic device stores the first public key after receiving the first public key; step 407, the electronic device sends a confirmation message to the first vehicle-mounted electronic device after receiving the first public key to confirm that the data can be transmitted; step 408, receiving the confirmation message, starting to interact with the electronic device, that is, after receiving the confirmation message, the first vehicle-mounted electronic device starts to use the first public key and the second public key to interact with the electronic device. It should be understood that the above method can also generate the first public key and the first private key by the electronic device, and generate the second public key and the second private key by the first vehicle-mounted electronic device.

[0094] Similarly, when necessary, the same method can be used to establish a private communication interaction between the electronic device or the first vehicle-mounted electronic device and the server, where the public key encrypts the data and the private key decrypts the data. The communication data is encrypted using the public key and private key method. The sender encrypts the communication data using the private key, and only the person holding the private key can decrypt it, ensuring that the communication data will not be known to a third party. The public key encryption and private key decryption method effectively prevents the leakage of private data and ensures the security of the data.

[0095] The specific method of obtaining the login data is further described in conjunction with FIG5. Figure 5A , Figure 5A A schematic diagram of the process of obtaining login data provided in the embodiment of the present application, such as Figure 5A As shown:

[0096] Step 501, obtaining device information of the first vehicle-mounted electronic device and a communication identifier of the electronic device, wherein the device information of the first vehicle-mounted electronic device is obtained by using the public key to perform encryption and then using the private key to perform decryption, and the communication identifier of the electronic device is obtained by the electronic device; that is, the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device are obtained by the electronic device, wherein the device information of the first vehicle-mounted electronic device is obtained by using the public key to perform encryption and then using the private key to perform decryption, and the communication identifier of the electronic device is read by the electronic device from the electronic device itself;

[0097] Alternatively, the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device are obtained, the communication identification of the electronic device is obtained by encrypting with the public key and then decrypting with the private key, and the device information of the first vehicle-mounted electronic device is obtained via the first vehicle-mounted electronic device; that is, the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device are obtained by the first vehicle-mounted electronic device, wherein the communication identification of the electronic device is obtained by encrypting with the public key and then decrypting with the private key by the first vehicle-mounted electronic device, and the device information of the first vehicle-mounted electronic device is read by the first vehicle-mounted electronic device from the first vehicle-mounted electronic device itself.

[0098] Step 502: Combine the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device to obtain the login data. Preferably, the login data includes the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device.

[0099] Specifically, taking the first case of step 501 as an example, Figure 5B As shown, the acquisition of login data includes the following steps:

[0100] Step 503, sending the device information of the first vehicle-mounted electronic device encrypted with the public key, that is, after receiving the confirmation information sent by the electronic device to confirm that the data can be transmitted, the first vehicle-mounted electronic device uses the second public key to encrypt the device information of the first vehicle-mounted electronic device (for example, the device information of the first vehicle-mounted electronic device such as psdn) to obtain the first encrypted data, and sends the first encrypted data to the electronic device. Specifically, by calling the NdefRecord.createTextRecord method, an NdefRecord object containing the data string content of the login data is created, and the NdefRecord describes an information segment of the NDEE information; and by using the NdefRecord object, an NdefMessage object is created, and the NdefMessage object is used to describe the format information of the data string content of the login data (for example, the first byte describes the data status, several bytes describe the text language encoding, and the remaining bytes describe the text data); an NdefMessage may contain one or more NdefRecords. Finally, the NDEE data containing the data string content of the login data is transmitted by calling the NfcAdapter.enableForegroundNdefPush method; and in the process of sending the first encrypted data, a prompt message of the progress of sending the login data is output.

[0101] Step 504, use the private key to perform decryption to obtain the device information of the first vehicle-mounted electronic device, and obtain the communication identifier of the electronic device, combine the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device to obtain the login data, and generate a login request based on the login data.

[0102] Specifically, after receiving the first encrypted data, the electronic device uses the second private key to decrypt the first encrypted data to obtain the device information of the first vehicle-mounted electronic device, and the electronic device obtains the communication identifier of the electronic device itself, and combines the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device to obtain the login data; based on the login data, the electronic device generates a login request containing the login data; at the same time, after obtaining the login data, the electronic device outputs a prompt message of the progress of successfully obtaining the login data.

[0103] Step 505: the electronic device sends the login request to the server, and during the request process outputs prompt information of the progress of the login request for the login data being initiated to the server.

[0104] Step 506: The server parses the login request and generates a request result based on the login request.

[0105] like Figure 2 Obtaining the request result of the login request in step 204 includes the following steps: using the public key to encrypt the request result to obtain the second encrypted data; and using the private key to decrypt the second encrypted data to obtain the request result. In some embodiments, the first vehicle-mounted electronic device may use the public key to encrypt the request result to obtain the second encrypted data, and the electronic device may use the private key to decrypt the second encrypted data to obtain the request result; or the electronic device may use the public key to encrypt the request result to obtain the second encrypted data, and the first vehicle-mounted electronic device may use the private key to decrypt the second encrypted data to obtain the request result; or the server may use the public key to encrypt the request result to obtain the second encrypted data, and the first vehicle-mounted electronic device or the electronic device may use the private key to decrypt the second encrypted data to obtain the request result.

[0106] Specifically, taking the second case above as an example, Figure 5B As shown, in some embodiments, obtaining the request result of the login request includes the following steps: Step 507, the electronic device receives the request result returned by the server; Step 508, the electronic device parses the request result to determine whether the request result is a successful request; Step 509, the electronic device sends the request result of successful request to the first vehicle-mounted electronic device; that is, after determining that the request result is a successful request, the electronic device uses the first public key to encrypt the request result to obtain second encrypted data, and sends the second encrypted data to the first vehicle-mounted electronic device; and after determining that the request result is a successful request, outputs a prompt message indicating that the request result is a successful request; Step 510, logging in to the system based on the request result; in some embodiments, the request result includes a login identifier; that is, after receiving the second encrypted data, the first vehicle-mounted electronic device uses the first private key to decrypt the second encrypted data to obtain a request result including the login identifier, and logs in to the system based on the login identifier.

[0107] Further integration Figure 6 A specific method for obtaining the request result of the login request is described. The login data includes device information of the first vehicle-mounted electronic device so as to identify the first vehicle-mounted electronic device; the method for obtaining the request result of the login request so as to facilitate presentation includes the following steps:

[0108] Step 601, obtaining a request result of the login request, the request result including device information of the first vehicle-mounted electronic device, the device information of the first vehicle-mounted electronic device is obtained based on the login data, for example, the device information of the first vehicle-mounted electronic device is obtained by the login data obtained in step 202, the device information of the first vehicle-mounted electronic device is the same as the device information of the first vehicle-mounted electronic device contained in the login data (for example, the device information of the first vehicle-mounted electronic device contained in the login data is PDSN, and the device information of the first vehicle-mounted electronic device included in the request result is also PDSN), or the device information of the first vehicle-mounted electronic device is a part of the device information of the first vehicle-mounted electronic device contained in the login data (for example, the device information of the first vehicle-mounted electronic device contained in the login data is PDSN and VIN, and the device information of the first vehicle-mounted electronic device included in the request result only includes PDSN); in some embodiments, the request result can be obtained by the second vehicle-mounted electronic device from the server, or by the second vehicle-mounted electronic device from the electronic device. In particular, the second vehicle-mounted electronic device and the first vehicle-mounted electronic device can be the same vehicle-mounted electronic device, or can be different vehicle-mounted electronic devices (the same below).

[0109] Step 602, obtaining the device information of the second vehicle-mounted electronic device. The device information of the second vehicle-mounted electronic device includes at least one of the unique identifier of the second vehicle-mounted electronic device (e.g., PDSN) and the unique identifier of the vehicle associated with the second vehicle-mounted electronic device (e.g., VIN) (e.g., the device information of the second vehicle-mounted electronic device includes the unique identifier of the second vehicle-mounted electronic device, and the device information of the second vehicle-mounted electronic device includes the unique identifier of the vehicle associated with the second vehicle-mounted electronic device, or the device information of the second vehicle-mounted electronic device includes the unique identifier of the second vehicle-mounted electronic device and the unique identifier of the vehicle associated with the second vehicle-mounted electronic device; the content contained in the device information of the second vehicle-mounted electronic device below is the same as that here, and will not be repeated). In some embodiments, the second vehicle-mounted electronic device directly extracts the device information stored locally. In particular, the second vehicle-mounted electronic device includes at least one device information type that is consistent with the device information type of the first vehicle-mounted electronic device, for example, the device information type of the first vehicle-mounted electronic device includes the unique identifier of the vehicle-mounted electronic device (e.g., PDSN) and the unique identifier of the vehicle (e.g., VIN), and the device information type of the second vehicle-mounted electronic device includes the unique identifier of the vehicle (e.g., VIN).

[0110] Step 603: Determine whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device. In some embodiments, the second vehicle-mounted electronic device may determine whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device.

[0111] Step 604, when it is determined that the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device, determining that the request result is a successful request;

[0112] Step 605, when it is determined that the device information of the second vehicle-mounted electronic device is inconsistent with the device information of the first vehicle-mounted electronic device, it is determined that the request result is a request failure, and a prompt message is presented at the second vehicle-mounted electronic device or the electronic device, and the prompt message is used to indicate the request result. In some embodiments, the second vehicle-mounted electronic device may determine that the request result is a request failure, and send the request result to the electronic device for presentation; or the second vehicle-mounted electronic device may determine that the request result is a request failure, and present it at the second vehicle-mounted electronic device. For example, the animation effect of the request failure is displayed in the dynamic display part of the electronic device or the second vehicle-mounted electronic device, and the timeline part displays text information including, for example, "Login failed, not the device login data"; for another example, the voice broadcast module of the electronic device or the second vehicle-mounted electronic device broadcasts the information "Login failed, not the device login data". From the above, it can be seen that it is necessary to verify whether the device information data of the first vehicle-mounted electronic device matches the device information of the current second vehicle-mounted electronic device, so as to ensure the consistency of the vehicle-mounted electronic device that provides the device data required for logging into the system and the vehicle-mounted electronic device that logs into the system based on the request result; when the device information of the first vehicle-mounted electronic device does not match the device information of the second vehicle-mounted electronic device, it is determined that the request result is a request failure, thereby improving the system security and ensuring the safe operation of the system; and a prompt message of the request result is presented at the second vehicle-mounted electronic device or the electronic device, so as to prompt the user that the reason for the failure of the request is the mismatch of device information.

[0113] Further integration Figure 7 Describes the specific method for obtaining the request result of the login request. Figure 7 As shown, the login data includes the device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device, and the step of obtaining the request result of the login request for presentation includes the following steps:

[0114] Step 701, obtain the request result of the login request; in some embodiments, the first vehicle-mounted electronic device or the second vehicle-mounted electronic device may obtain the request result of the login request from the electronic device, or the first vehicle-mounted electronic device may obtain the request result of the login request from a server, or the electronic device may obtain the request result of the login request from a server or the first vehicle-mounted electronic device.

[0115] Step 702, when it is determined that the request result is that there is no device information of the vehicle-mounted electronic device corresponding to the device information of the first vehicle-mounted electronic device, the request result is determined to be a request failure, and a prompt message is output, the prompt message is used to indicate at least one of the request result, request progress and reason for the request failure. In some embodiments, the server obtains and parses the login data, obtains the device information of the first vehicle-mounted electronic device, searches the database for whether there is device information of the vehicle-mounted electronic device corresponding to the device information of the first vehicle-mounted electronic device, and if it is determined that there is no device information of the vehicle-mounted electronic device corresponding to the device information of the first vehicle-mounted electronic device, the request result of sending the login request to the first vehicle-mounted electronic device or the electronic device is that there is no device information of the vehicle-mounted electronic device corresponding to the device information of the first vehicle-mounted electronic device, for example, "device information is not stored". The prompt message can be presented at the first vehicle-mounted electronic device or the electronic device. For example, the animation effect of the request failure is displayed in the dynamic display part of the first vehicle-mounted electronic device or the electronic device, and the timeline part displays text information including "device information is not stored".

[0116] Step 703, when it is determined that the request result is that the communication identifier of the electronic device is in an invalid state, the request result is determined to be a request failure, and a prompt message is output, wherein the prompt message is used to indicate at least one of the request result, request progress, and reason for the request failure. In some embodiments, the server obtains and parses the login data, obtains the communication identifier of the electronic device, determines whether the communication identifier of the electronic device is in a valid state, and when it is determined that the communication identifier of the electronic device is in an invalid state, the request result of sending the login request to the first vehicle-mounted electronic device or the electronic device is that the communication identifier of the electronic device is in an invalid state, for example, "Account login is invalid, please log in again". The prompt message can be presented at the first vehicle-mounted electronic device or the electronic device. For example, the animation effect of the request failure is displayed in the dynamic display part of the first vehicle-mounted electronic device or the electronic device, and the timeline part displays text information including "Account login is invalid, please log in again".

[0117] See also Figure 8 , Figure 8 This is a schematic diagram of a vehicle-mounted login device provided in an embodiment of the present application. Figure 8The vehicle-mounted login device shown includes:

[0118] Connecting unit 801;

[0119] an acquisition unit 802, wherein the connection unit 801 and the acquisition unit 802 are communicatively connected to each other, wherein the connection unit 801 establishes a connection between the first vehicle-mounted electronic device and the electronic device in response to detecting that the system login interface is opened, and the acquisition unit 802 acquires the login data based on the connection between the first vehicle-mounted electronic device and the electronic device established by the connection unit;

[0120] A request generating unit 803, wherein the request generating unit 803 and the acquiring unit 802 are communicatively connected to each other, wherein the request generating unit 803 generates a login request based on the login data acquired by the acquiring unit 802, and the login request includes the login data; and the acquiring unit 802 acquires a request result of the login request based on the login request generated by the request generating unit;

[0121] a display unit 804, wherein the display unit 804 and the acquisition unit 802 are communicatively connected to each other so that the display unit 804 presents the request result acquired by the acquisition unit 802; and

[0122] A login unit 805, wherein the login unit 805 and the acquisition unit 802 are communicatively connected to each other, wherein the login unit 805 logs into the system based on the request result in response to determining that the request result acquired by the acquisition unit 802 is a successful request.

[0123] See also Fig. 9 , Fig. 9 A schematic diagram of a vehicle login system provided in an embodiment of the present application. Fig. 9 The vehicle-mounted login system shown includes:

[0124] Connection module 901;

[0125] an acquisition module 902, wherein the connection module 901 and the acquisition module 902 are communicatively connected to each other, wherein the connection module 901 establishes a connection between the first vehicle-mounted electronic device and the electronic device in response to detecting that the system login interface is opened, and the acquisition module 902 acquires login data based on the connection between the first vehicle-mounted electronic device and the electronic device established by the connection module;

[0126] A request generation module 903, wherein the request generation module 903 and the acquisition module 902 are communicatively connected to each other, wherein the request generation module 903 generates a login request based on the login data acquired by the acquisition module 902, and the login request includes the login data; and the acquisition module 902 acquires a request result of the login request based on the login request generated by the request generation module;

[0127] a display module 904, wherein the display module 904 and the acquisition module 902 are communicatively connected to each other so that the display module 904 presents the request result acquired by the acquisition module 902; and

[0128] A login module 905, wherein the login module 905 and the acquisition module 902 are communicatively connected to each other, wherein the login module 905 logs into the system based on the request result in response to determining that the request result acquired by the acquisition module 902 is a successful request.

[0129] See also Fig.12 ,like Fig.12 As shown, in some embodiments, a computer device provided in the fourth aspect of the present application includes a display screen, a touch sensor, a memory, one or more processors, multiple applications, and one or more programs; wherein the one or more programs are stored in the memory 110; wherein the memory 110 and the processor 120 are communicatively connected to each other; the memory 110 can be used to store software programs and modules, and the processor 120 executes the software programs and modules stored in the memory 110, thereby executing the following. Figures 2 to 8 The method shown. The memory 110 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device (such as audio data, a phone book, etc.), etc. The processor 120 is the control center of the computer device, which uses various interfaces and lines to connect various parts of the entire computer device, and executes software programs and / or modules stored in the memory 110, and calls data stored in the memory 110, to perform operations such as Figures 2 to 8The method shown in the figure can monitor the computer device as a whole. Optionally, the processor 120 may include one or more processing units; preferably, the processor 120 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 120. Although not shown, the computer device may also include an input unit, a display unit, a power supply, etc., which will not be described in detail here.

[0130] The following is a description of the specific processing flow for implementing in-vehicle login using the in-vehicle login method provided by this application, in combination with usage scenarios.

[0131] (I) Usage scenario 1: Use the near field communication function to realize the in-vehicle account login and display the login process during the login process

[0132] In this embodiment, both the first vehicle-mounted electronic device and the electronic device have a near field communication (NFC) function.

[0133] like Fig.10 As shown, Fig.10The flowchart of the first vehicle-mounted electronic device logging into the system. Step 1001, the first vehicle-mounted electronic device enters the NFC login system page; Step 1002, determine whether NFC is in the on state; Step 1003, if it is determined that NFC is not in the on state, turn on NFC; determine the on state of NFC by calling the NFC state determination method, and adopt the broadcast registration monitoring method to timely obtain the changes in the near field communication function, and the monitoring mechanism broadcasts the state information of the near field communication function in the communication field when the state of the near field communication function changes. In the case of determining that NFC is not in the on state, turning on NFC also includes the following steps: based on the on state of the near field communication function, output prompt information to indicate the progress and result of the activation of the near field communication function. That is, during the activation of the near field communication function, output prompt information of the progress of the activation of the near field communication function; after the near field communication function is successfully activated, output prompt information of the progress of the successful activation of the near field communication function. Step 1004, connecting an electronic device; that is, when it is determined that NFC is turned on, outputting prompt information of the progress of the near field communication function being turned on, and establishing a connection with the electronic device; in the process of establishing a connection with the electronic device, outputting prompt information of the progress of establishing a connection with the electronic device; the prompt information may include text information, picture information, and voice broadcast information, the text information includes time information and progress prompt information, and the picture information includes dynamic picture information indicating the progress. Step 1005, determining whether the connection to the electronic device is successful via NFC; Step 1006, generating a first public key and a first private key; that is, when it is determined that the connection to the electronic device is successful, generating a first public key and a first private key, and outputting a progress prompt information that the NFC connection with the electronic device has been successfully established.Step 1007, receiving data sent by the electronic device via NFC; Step 1008, determining whether the structure of the data content is a predetermined public key transmission structure. In some embodiments, the predetermined public key transmission structure includes one or more of the "key" field and the public key field; if so, it means that the electronic device has sent the second public key, and if not, it means that the electronic device has sent the data decrypted using the first public key; Step 1009, storing the public key as the second public key; that is, after determining that the structure of the data content is a predetermined public key transmission structure, storing the public key in the data content as the second public key; Step 1010, transmitting the first public key data to the electronic device; Step 1011, decrypting the data using the first private key; that is, if it is determined that the structure of the data content is not a predetermined public key transmission structure, decrypting the data using the first private key; Step 1012, determining whether the data is predetermined confirmation information. In some embodiments, the predetermined confirmation information includes The "getdevice" field confirms the confirmation information of the transmitted data; if yes, it indicates that the data is the predetermined confirmation information, if no, it indicates that the data is verification information; step 1013, if it is determined that the data is the predetermined confirmation information, the unique identifier of the first vehicle-mounted electronic device (such as PDSN) and the unique identifier of the vehicle (such as VIN) are recorded as the device information of the first vehicle-mounted electronic device, the device information of the first vehicle-mounted electronic device is encrypted using the second public key to obtain first encrypted data, and the first encrypted data is sent to the electronic device; in the process of sending the first encrypted data, a prompt information of the progress of sending the login data is output; the prompt information may include text information, picture information, and voice broadcast information, the text information includes time information and progress prompt information, and the picture information includes dynamic picture information indicating progress, such as dynamic picture information showing that a package is being packed and the data is being transmitted. Step 1014, parse the data to obtain the unique identifier and login identifier of the first vehicle-mounted electronic device, and obtain the unique identifier of the second vehicle-mounted electronic device, the unique identifier of the first vehicle-mounted electronic device is the device information of the vehicle-mounted electronic device that successfully requests the system, and the unique identifier of the second vehicle-mounted electronic device is the device information of the current vehicle-mounted electronic device; Step 1015, determine whether the unique identifier of the second vehicle-mounted electronic device is consistent with the unique identifier of the first vehicle-mounted electronic device; Step 1016, send "success" to the electronic device; that is, when it is determined that the unique identifier of the second vehicle-mounted electronic device is consistent with the unique identifier of the first vehicle-mounted electronic device, use the login identifier to log in to the system, and send a verification result of successful verification to the electronic device; Step 1017, send "fail" to the electronic device; that is, when it is determined that the unique identifier of the second vehicle-mounted electronic device is inconsistent with the unique identifier of the first vehicle-mounted electronic device, send a verification result of failed verification to the electronic device.

[0134] like Figure 11A-11BAs shown, Figure 11A-11B This is an operation flow chart of an electronic device when the first vehicle-mounted electronic device logs into the system. Fig.11AAs shown, in step 1101, the electronic device enters the NFC login system page; in step 1102, determine whether NFC is in the on state; in step 1103, turn on NFC; that is, when it is determined that NFC is not in the on state, turn on NFC; determine the on state of NFC by calling the NFC state determination method, and adopt the broadcast registration monitoring method to timely obtain the changes in the near field communication function, and the monitoring mechanism broadcasts the status information of the near field communication function in the communication field when the state of the near field communication function changes. In the case of determining that NFC is not in the on state, turning on NFC also includes the following steps: based on the on state of the near field communication function, output prompt information to indicate the progress and result of the activation of the near field communication function. That is, during the activation of the near field communication function, output prompt information of the progress of the activation of the near field communication function; after the near field communication function is successfully activated, output prompt information of the progress of the successful activation of the near field communication function. Step 1104, connecting to the first vehicle-mounted electronic device; that is, when it is determined that NFC is in the turned-on state, outputting a prompt message of the progress of the near-field communication function being turned on, and establishing a connection with the first vehicle-mounted electronic device; Step 1105, determining whether the connection to the first vehicle-mounted electronic device is successful; Step 1106, the electronic device generates a second public key and a second private key; that is, when it is determined that the connection to the first vehicle-mounted electronic device is successfully established, outputting a progress prompt message of the successful establishment of the NFC connection with the first vehicle-mounted electronic device, and generating a second public key and a second private key.Step 1107, sending the second public key to the first vehicle-mounted electronic device; step 1108, receiving the data sent by the first vehicle-mounted electronic device; step 1109, determining whether the structure of the data content is the predetermined public key transmission structure; in some embodiments, the predetermined public key transmission structure includes one or more of the "key" field and the public key field; if so, it means that the first vehicle-mounted electronic device has sent the first public key, and if otherwise, it means that the first vehicle-mounted electronic device has sent the data decrypted using the second public key; step 1110, storing the first public key; that is, when it is determined that the structure of the data content is the predetermined public key transmission structure, the public key in the data is stored as the first public key; step 1111, after receiving the first public key of the first vehicle-mounted electronic device, sending the first public key to the first vehicle-mounted electronic device The sub-device sends a predetermined confirmation message encrypted by the first public key; in some embodiments, the predetermined confirmation message is a confirmation message including a "getdevice" field to confirm that the data can be transmitted; step 1112, use the second private key to decrypt the data, obtain the device information of the first vehicle-mounted electronic device, and obtain the communication identification of the electronic device; the device information of the first vehicle-mounted electronic device includes at least one of the unique identification of the first vehicle-mounted electronic device and the unique identification of the vehicle; and output prompt information of the progress of obtaining the device information of the first vehicle-mounted electronic device; the prompt information may include text information, picture information, and voice broadcast information, the text information includes time information, progress prompt information, and the picture information includes dynamic picture information indicating progress. Step 1113, call the cloud login interface, transmit the login data including the device information of the first vehicle-mounted electronic device and the communication identification of the electronic device user to initiate a login request to the cloud; and output prompt information of the progress of the login request during the login process.

[0135] like Fig. 11BAs shown, step 1114, receiving the request result returned by the cloud; that is, the electronic device receives the request result regarding the login request returned by the cloud; step 1115, determining whether the request result is a successful request; step 1116, sending verification information of the request result including the login identifier and the unique identifier of the first vehicle-mounted electronic device to the vehicle-mounted electronic device; that is, when it is determined that the request result is a successful request, the request result includes the unique identifier and the login identifier of the first vehicle-mounted electronic device, and a verification request including the request result is sent to the current vehicle-mounted electronic device; step 1117, receiving the verification result regarding the verification request sent by the vehicle-mounted electronic device; the vehicle-mounted electronic device is the current vehicle-mounted electronic device, which can be the first vehicle-mounted electronic device or the second vehicle-mounted electronic device; step 1118, determining whether the verification result is a successful verification; step 1119, successful login; that is, when it is determined that the verification result is a successful verification, it indicates that the first vehicle-mounted electronic device has successfully logged into the system using the login identifier, and outputs a prompt message indicating the progress of the first vehicle-mounted electronic device having successfully logged into the system. Step 1120, login failure; that is, when the verification result is determined to be a verification failure, it is determined that the first vehicle-mounted electronic device fails to log into the system, and a login failure progress prompt message of "Login failure, not the login data of the device" is output. Step 1121, obtain the failure result; that is, when the request result is determined to be a request failure, obtain the failure result; Step 1122, determine whether the failure reason of the failure result is that the device information does not exist in the database; Step 1123, determine that the request result is a request failure, and the failure reason is "the vehicle-mounted device information is not stored"; that is, when the failure reason of the failure result is indeed that the device information does not exist in the database, determine that the request result is a request failure, and output the login failure progress prompt message of the failure reason being that the vehicle-mounted device is not stored; Step 1124, determine that the request result is a request failure, and the failure reason is "the account is invalid, please log in again"; that is, when the failure reason of the failure result is not that the device information does not exist in the database, and the failure reason is that the communication identification of the electronic device is invalid, determine that the request result is a request failure, and output the login failure progress prompt message of the failure reason being that the communication identification of the electronic device is invalid.

[0136] In this embodiment, the progress prompt information includes graphic information and voice broadcast, the graphic information includes text prompt information, static picture information, and dynamic picture information, the text prompt information includes time information and progress prompt; the dynamic picture information includes: for example, when the first vehicle-mounted electronic device is sending login data to the electronic device, a dynamic picture of a packaged package transmitting data is displayed.

[0137] In this embodiment, the request progress, request result, and request failure reason of the login request are outputted at the vehicle-mounted electronic device or electronic device during the login process. In the event of a login failure, there is no need to find the source of the error by parsing the error log, and the login result is fed back to the user more intuitively and promptly.

[0138] As used in the above embodiments, the term "when..." may be interpreted to mean "if..." or "after..." or "in response to determining..." or "in response to detecting...", depending on the context. Similarly, the phrases "upon determining..." or "if (the stated condition or event) is detected" may be interpreted to mean "if determining..." or "in response to determining..." or "upon detecting (the stated condition or event)" or "in response to detecting (the stated condition or event)", depending on the context.

[0139] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk), etc.

[0140] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Claims

1. A vehicle-mounted login method, characterized in that: The method comprises the following steps: In response to detecting that both the electronic device and the first in-vehicle electronic device open the system login interface and the electronic device is close to the first in-vehicle electronic device, establishing a connection between the first in-vehicle electronic device and the electronic device; Based on the connection, acquiring login data, the login data including device information of the first vehicle-mounted electronic device, so as to identify the first vehicle-mounted electronic device; Based on the login data, generating a login request, the login request including the login data; Based on the login request, obtaining a request result of the login request for presentation; and If it is determined that the request result is successful, logging into the system based on the request result; The step of obtaining the request result of the login request so as to facilitate presentation includes the following steps: Acquire a request result of the login request, wherein the request result includes device information of the first vehicle-mounted electronic device, and the device information of the first vehicle-mounted electronic device is acquired based on the login data; Acquire device information of a second vehicle-mounted electronic device, where the device information of the second vehicle-mounted electronic device is device information directly extracted from the device's storage by the second vehicle-mounted electronic device; determining whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device; as well as When it is determined that the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device, determining that the request result is a successful request; When it is determined that the device information of the second vehicle-mounted electronic device is inconsistent with the device information of the first vehicle-mounted electronic device, the request result is determined to be a request failure, and a prompt message is presented at the second vehicle-mounted electronic device or the electronic device, wherein the prompt message is used to indicate that the reason for the failure of the request is that the device information does not match.

2. The method according to claim 1, wherein establishing a connection between the first vehicle-mounted electronic device and the electronic device comprises the following steps: Determine whether the near field communication function is enabled; as well as If it is determined that the near field communication function is in the on state, establishing a near field communication connection between the first vehicle-mounted electronic device and the electronic device; If it is determined that the near field communication function is not enabled, the near field communication function is enabled to establish a near field communication connection between the first vehicle-mounted electronic device and the electronic device.

3. The method according to claim 1 or 2, before obtaining the login data, the method further comprises the following steps: Generate a public key and a private key; the public key is used to encrypt the communication data to obtain the private data, and the private key is used to decrypt the private data to obtain the communication data.

4. The method according to claim 3, wherein obtaining the login data comprises the following steps: Acquire device information of the first vehicle-mounted electronic device and a communication identifier of the electronic device, wherein the device information of the first vehicle-mounted electronic device is obtained by encrypting the first vehicle-mounted electronic device with the public key and then decrypting the first vehicle-mounted electronic device with the private key, and the communication identifier of the electronic device is acquired via the electronic device; or Acquire device information of the first vehicle-mounted electronic device and a communication identifier of the electronic device, wherein the communication identifier of the electronic device is obtained by encrypting with the public key and then decrypting with the private key, and the device information of the first vehicle-mounted electronic device is acquired via the first vehicle-mounted electronic device; and The device information of the first vehicle-mounted electronic device and the communication identifier of the electronic device are combined to obtain the login data.

5. The method according to claim 3, wherein obtaining the request result of the login request comprises the following steps: Using the public key to encrypt the request result to obtain encrypted data; as well as The encrypted data is decrypted using the private key to obtain the requested result.

6. The method according to claim 1 or 2, wherein the request result includes a login identifier, and the logging into the system based on the request result includes the following steps: The system is logged in based on the login identifier.

7. The method according to claim 1 or 2, wherein the login data includes device information of the first vehicle-mounted electronic device and a communication identifier of the electronic device, and the step of obtaining a request result of the login request for presentation includes the following steps: Obtaining a request result of the login request; as well as If it is determined that the request result is that there is no device information of the on-board electronic device corresponding to the device information of the first on-board electronic device, determining that the request result is a request failure, and outputting prompt information, the prompt information being used to indicate at least one of the request result, request progress, and reason for the request failure; When it is determined that the request result is that the communication identification of the electronic device is in an invalid state, the request result is determined to be a request failure, and a prompt message is output, wherein the prompt message is used to indicate at least one of the request result, request progress and reason for request failure.

8. The method according to claim 1 or 2, wherein establishing a connection between the first vehicle-mounted electronic device and the electronic device further comprises the following steps: Based on the connection status between the first vehicle-mounted electronic device and the electronic device, prompt information is output to indicate the progress and result of establishing the connection between the first vehicle-mounted electronic device and the electronic device.

9. The method according to claim 1 or 2, wherein obtaining login data further comprises the following steps: Based on the acquisition status of the login data, prompt information is output to indicate the progress and result of acquiring the login data.

10. The method according to claim 2, wherein if it is determined that the near field communication function is turned on, establishing a near field communication connection between the first vehicle-mounted electronic device and the electronic device, further comprises the following steps: Output a prompt message indicating that the near field communication function has been turned on.

11. The method according to claim 2, wherein if it is determined that the near field communication function is not turned on, turning on the near field communication function so as to establish a near field communication connection between the first vehicle-mounted electronic device and the electronic device, further comprising the following steps: Based on the activation state of the near field communication function, prompt information is output to indicate the activation progress and result of the near field communication function.

12. A vehicle-mounted logging device, characterized in that: include: Connecting unit; an acquisition unit, wherein the connection unit and the acquisition unit are communicatively connected to each other, wherein the connection unit establishes a connection between the first on-vehicle electronic device and the electronic device in response to detecting that both the electronic device and the first on-vehicle electronic device open a system login interface and the electronic device is close to the first on-vehicle electronic device, and the acquisition unit acquires login data based on the connection between the first on-vehicle electronic device and the electronic device established by the connection unit, the login data including device information of the first on-vehicle electronic device, so as to identify the first on-vehicle electronic device; A request generating unit, wherein the request generating unit and the acquiring unit are communicably connected to each other, wherein the request generating unit generates a login request based on the login data acquired by the acquiring unit, the login request including the login data; and the acquiring unit acquires a request result of the login request based on the login request generated by the request generating unit; a display unit, wherein the display unit and the acquisition unit are communicatively connected to each other so that the display unit presents the request result acquired by the acquisition unit; as well as A login unit, wherein the login unit and the acquisition unit are communicably connected to each other, wherein the login unit logs into the system based on the request result when determining that the request result acquired by the acquisition unit is a successful request; The step of obtaining the request result of the login request so as to facilitate presentation includes the following steps: Acquire a request result of the login request, wherein the request result includes device information of the first vehicle-mounted electronic device, and the device information of the first vehicle-mounted electronic device is acquired based on the login data; Acquire device information of a second vehicle-mounted electronic device, where the device information of the second vehicle-mounted electronic device is device information directly extracted from the device's storage by the second vehicle-mounted electronic device; determining whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device; as well as When it is determined that the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device, determining that the request result is a successful request; When it is determined that the device information of the second vehicle-mounted electronic device is inconsistent with the device information of the first vehicle-mounted electronic device, the request result is determined to be a request failure, and a prompt message is presented at the second vehicle-mounted electronic device or the electronic device, wherein the prompt message is used to indicate that the reason for the failure of the request is that the device information does not match.

13. A vehicle-mounted login system, characterized in that: include: Connect modules; an acquisition module, wherein the connection module and the acquisition module are communicatively connected to each other, wherein the connection module establishes a connection between the first on-board electronic device and the electronic device in response to detecting that both the electronic device and the first on-board electronic device open a system login interface and the electronic device is close to the first on-board electronic device, and the acquisition module acquires login data based on the connection between the first on-board electronic device and the electronic device established by the connection module, wherein the login data includes device information of the first on-board electronic device so as to identify the first on-board electronic device; A request generation module, wherein the request generation module and the acquisition module are communicatively connected to each other, wherein the request generation module generates a login request based on the login data acquired by the acquisition module, the login request including the login data; and the acquisition module acquires a request result of the login request based on the login request generated by the request generation module; A display module, wherein the display module and the acquisition module are communicatively connected to each other so that the display module presents the request result acquired by the acquisition module; as well as A login module, wherein the login module and the acquisition module are communicably connected to each other, wherein the login module logs into the system based on the request result when determining that the request result acquired by the acquisition module is a successful request; The step of obtaining the request result of the login request so as to facilitate presentation includes the following steps: Acquire a request result of the login request, wherein the request result includes device information of the first vehicle-mounted electronic device, and the device information of the first vehicle-mounted electronic device is acquired based on the login data; Acquire device information of a second vehicle-mounted electronic device, where the device information of the second vehicle-mounted electronic device is device information directly extracted from the device's storage by the second vehicle-mounted electronic device; determining whether the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device; as well as When it is determined that the device information of the second vehicle-mounted electronic device is consistent with the device information of the first vehicle-mounted electronic device, determining that the request result is a successful request; When it is determined that the device information of the second vehicle-mounted electronic device is inconsistent with the device information of the first vehicle-mounted electronic device, the request result is determined to be a request failure, and a prompt message is presented at the second vehicle-mounted electronic device or the electronic device, wherein the prompt message is used to indicate that the reason for the failure of the request is that the device information does not match.

14. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other; wherein the memory stores program instructions; and when the program instructions are executed by the processor, the processor executes the method as described in any one of claims 1-11.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program; when the computer program runs on one or more processors, the method according to any one of claims 1 to 11 is executed.

Images