Program login processing method and device for vehicle terminal

Abstract

The embodiments of this specification provide a program login processing method and device for a vehicle terminal, wherein a program login processing method for a vehicle terminal includes: reading the tag data stored in the vehicle's near-field communication tag through near-field communication, starting the application based on the tag data and passing the tag data to upload to the server, receiving and displaying the program identifier and login account of at least one program returned by the server for program synchronization login on the vehicle terminal, obtaining the submitted login authorization instruction and uploading it to the server for use in cooperating with the program access of the vehicle terminal to perform program login of at least one program, thereby realizing program synchronization login of the vehicle terminal.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a program login processing method and device for a vehicle terminal. Background Art

[0002] With the development of Internet technology and the popularization of mobile terminals, more and more users are participating in services online, and more and more services are beginning to extend to online scenarios. With the continuous development of near-field communication technology, various online services provided based on the Internet can be initiated or processed through near-field communication, which not only brings convenience to users but also increases the user participation rate of online services. How to initiate and process services more flexibly based on near-field communication is a focus of increasing attention from users and service providers. Summary of the Invention

[0003] One or more embodiments of this specification provide a method for processing program login on a vehicle terminal, comprising: reading tag data stored in a near-field communication tag of a vehicle via near-field communication. Starting an application based on the tag data, and passing the tag data to the application for uploading to a server. Receive and display the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server. Obtain a submitted login authorization instruction and upload it to the server for program login of the at least one program in conjunction with program access on the vehicle terminal.

[0004] One or more embodiments of this specification provide another method for processing program logins on an in-vehicle terminal, comprising: obtaining tag data uploaded by a user terminal and read from a near-field communication tag on a vehicle; determining, based on the tag data, at least one program for simultaneous program login on the in-vehicle terminal; returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for simultaneous login authorization; and performing program login of the at least one program in conjunction with a program server and program access by the in-vehicle terminal based on a login authorization instruction uploaded by the user terminal.

[0005] One or more embodiments of the present specification provide a program login processing device for a vehicle terminal, comprising: a tag data reading module, configured to read the tag data stored in the near-field communication tag of the vehicle through near-field communication. An application startup module, configured to start the application based on the tag data, and pass the tag data to the application for uploading to the server. A receiving module, configured to receive and display the program identifier and login account of at least one program returned by the server for program synchronization login at the vehicle terminal. A login authorization instruction uploading module, configured to obtain the submitted login authorization instruction and upload it to the server, so as to cooperate with the program access of the vehicle terminal to perform program login of the at least one program.

[0006] One or more embodiments of the present specification provide another program login processing device for a vehicle terminal, comprising: a tag data acquisition module, configured to acquire tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle. A program determination module, configured to determine at least one program for program synchronization login in the vehicle terminal based on the tag data. A return module, configured to return the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronization login authorization. A program login module, configured to perform program login of the at least one program based on the login authorization instruction uploaded by the user terminal, in combination with the program server and the program access of the vehicle terminal.

[0007] One or more embodiments of the present specification provide a user terminal, comprising: a processor; and a memory configured to store computer-executable instructions, wherein when the computer-executable instructions are executed, the processor is configured to: read tag data stored in a near-field communication tag of a vehicle through near-field communication. Start an application based on the tag data, and pass the tag data to the application for uploading to a server. Receive and display the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server. Obtain the submitted login authorization instruction and upload it to the server for program login of the at least one program in conjunction with the program access of the vehicle terminal.

[0008] One or more embodiments of this specification provide a server comprising: a processor; and a memory configured to store computer-executable instructions, wherein when executed, the computer-executable instructions cause the processor to: obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle; and, based on the tag data, determine at least one program for program synchronization login on the vehicle terminal; return the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronization login authorization; and, based on the login authorization instruction uploaded by the user terminal, perform program login for the at least one program in conjunction with program access by the vehicle terminal using a program server.

[0009] One or more embodiments of this specification provide a computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: reading tag data stored in a near-field communication tag of a vehicle through near-field communication. Starting an application based on the tag data, passing the tag data to the application for uploading to a server. Receive and display the program identifier and login account of at least one program for program synchronization login on a vehicle terminal returned by the server. Obtain a submitted login authorization instruction and upload it to the server for program login of the at least one program in conjunction with program access of the vehicle terminal.

[0010] One or more embodiments of this specification provide another computer-readable storage medium for storing computer-executable instructions. When executed, the computer-executable instructions implement the following process: obtaining tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle; determining, based on the tag data, at least one program for program synchronization login on the vehicle terminal; returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronization login authorization; and performing program login of the at least one program in conjunction with program access by the vehicle terminal, in conjunction with a program server, based on the login authorization instruction uploaded by the user terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate one or more embodiments of this specification or technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments described in this specification. Those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0012] Figure 1 A schematic diagram of an implementation environment of a program login processing method for a vehicle terminal provided in one or more embodiments of this specification;

[0013] Figure 2 A flowchart of a program login processing method for a vehicle terminal provided in one or more embodiments of this specification;

[0014] Figure 3 A schematic diagram of a login authorization page provided for one or more embodiments of this specification;

[0015] Figure 4 A processing sequence diagram of a program login processing method for an on-board terminal applied to a subroutine login processing scenario of an on-board terminal provided by one or more embodiments of this specification;

[0016] Figure 5 A flowchart of another vehicle terminal program login processing method provided in one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram of an embodiment of a program login processing device for a vehicle terminal provided in one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of another embodiment of a program login processing device for a vehicle terminal provided in one or more embodiments of this specification;

[0019] Figure 8 A schematic diagram of the structure of a user terminal provided in one or more embodiments of this specification;

[0020] Figure 9 A schematic diagram of the structure of a server provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0022] The program login processing method of the vehicle terminal provided in one or more embodiments of this specification can be applied to the implementation environment of the program synchronous login of the vehicle terminal. Figure 1 , the implementation environment at least includes: a user terminal 101, a near field communication tag 102 of a vehicle, a server 103, and a vehicle terminal 104;

[0023] The user terminal 101 is used to read tag data stored in the vehicle's near-field communication tag 102 via near-field communication, and to perform synchronous login authorization in cooperation with the server 103 through an application. After obtaining the login authorization instruction, the user terminal 101 uploads the data to the server 103 for program login of at least one program in cooperation with the program access of the vehicle terminal 104. The user terminal 101 can specifically be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality), an in-vehicle terminal, an IoT device, a wearable smart device, a laptop computer, a desktop computer, etc.

[0024] The server 103 is used to return the login account of the logged-in user and the program identifier of at least one program for program synchronization login on the vehicle terminal to the user terminal based on the tag data uploaded by the user terminal 101, thereby cooperating with the user terminal 101 to perform synchronization login authorization, and obtain the login authorization instruction uploaded by the user terminal 101 to cooperate with the program access of the vehicle terminal 104 to perform program login of at least one program; the server 103 can be a single server, a server cluster composed of multiple servers, or one or more cloud servers in a cloud computing platform;

[0025] In addition, the implementation environment may further include a program server 105, which includes a program server for performing program synchronization login, and is used to perform program login of the program in conjunction with the server 103 and the program access of the vehicle terminal 104; the program server 105 can be a single server, or a server cluster composed of several servers, or one or more cloud servers in a cloud computing platform;

[0026] In this implementation environment, the user terminal 101 reads the tag data stored in the vehicle's near-field communication tag 102 through near-field communication, starts an application based on the tag data, and passes the tag data to the application for uploading to the server 103. After obtaining the tag data, the server 103 returns the login account of the logged-in user and the program identifier of at least one program for program synchronization login on the vehicle terminal 104 to the user terminal 101 according to the tag data. The user terminal 101 receives and displays the login account and program identifier, and uploads it to the server 103 after obtaining the login authorization instruction. The server 103 performs program login processing according to the login authorization instruction in combination with the program server 105 and the program access of the vehicle terminal 104, thereby realizing program synchronization login of the vehicle terminal.

[0027] One or more embodiments of a program login processing method for a vehicle terminal provided in this specification are as follows:

[0028] Reference Figure 2The program login processing method of the vehicle terminal provided in this embodiment specifically includes steps S202 to S208.

[0029] Step S202 : reading tag data stored in the near field communication tag of the vehicle through near field communication.

[0030] In this embodiment, a near field communication component capable of performing near field communication (NFC) connection with other devices may be configured on the user terminal, and a near field communication tag may be configured on the vehicle, so as to establish a near field communication connection between the near field communication component of the user terminal and the near field communication tag of the vehicle, and then read the tag data stored in the near field communication tag of the vehicle through the near field communication connection; in addition to near field communication, it may also be Bluetooth communication, wireless network communication, infrared communication and / or radio frequency communication, and correspondingly, the near field communication component may be a Bluetooth component, wireless component, infrared component or radio frequency communication component that provides Bluetooth capability, wireless network capability, infrared communication capability or radio frequency communication capability; the near field communication tag of the vehicle may be a Bluetooth component, wireless component, infrared component or radio frequency communication component.

[0031] During specific implementation, the user terminal reads the tag data stored in the vehicle's near-field communication tag through near-field communication; during the specific execution process, the user terminal can establish a near-field communication connection with the vehicle's near-field communication tag through the user terminal's near-field communication component, and on the basis of establishing the near-field communication connection, read the tag data stored in the vehicle's near-field communication tag through the near-field communication connection; in addition to the user terminal reading the tag data stored in the vehicle's near-field communication tag through near-field communication, it can also receive tag data sent by the vehicle's near-field communication tag through near-field communication.

[0032] The tag data includes the tag identifier of the near-field communication tag, i.e., the tag data can be replaced with the tag identifier. In addition, to launch an application based on the tag data, the tag data can also include the program identifier and / or program address of the application to be launched, where the program address can be the program URL (Uniform Resource Locator). It should be noted that the tag data can include any one or more of the tag identifier, program identifier, and program address, or the tag data can also be replaced with any one or more of the tag identifier, program identifier, and program address.

[0033] During the specific execution process of the user terminal reading the tag data stored in the vehicle's near-field communication tag through near-field communication, the user terminal can call near-field communication for detection, and after detecting the near-field communication tag, establish a near-field communication connection with the near-field communication tag, and then read the stored tag data from the near-field communication tag; the vehicle's near-field communication tag can also perform detection, and after detecting the near-field communication component of the user terminal, establish a near-field communication connection with the near-field communication component, and then send the stored tag data to the near-field communication component.

[0034] Step S204: starting an application based on the tag data, and passing the tag data to the application for uploading to a server.

[0035] In a specific implementation, after the tag data stored in the near-field communication tag of the vehicle is read through near-field communication, an application is started based on the tag data, so as to upload the tag data to the server through the application; in the process of starting the application based on the tag data, the user terminal may parse the tag data to obtain a parsing result, wherein the parsing result may include a tag identifier, a program identifier and / or a program address, and then start the corresponding application in the installed application list of the user terminal according to the parsing result;

[0036] After the application is started based on the tag data, the tag data is passed to the application for uploading to the server; it should be noted that the tag data passed to the application can be all the tag data, such as passing the tag identifier, program identifier and / or program address as tag data to the application. In addition, only part of the content contained in the tag data can be passed to the application, such as passing the tag identifier in the tag data to the application.

[0037] Step S206: receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server.

[0038] In a specific implementation, the user terminal starts the application based on the tag data and passes in the tag data, and uploads the tag data to the server through the application; correspondingly, the server obtains the tag data uploaded by the user terminal and read from the near-field communication tag of the vehicle. After obtaining the tag data, the server determines at least one program for program synchronization login on the vehicle terminal based on the tag data. Since the program synchronization login is to be performed based on the login account of the logged-in user, the login account and the logged-in program often involve the privacy of the logged-in user. To perform program synchronization login on the vehicle terminal based on the login account of the logged-in user, authorization of the logged-in user is required; therefore, after the server determines at least one program for program synchronization login on the vehicle terminal based on the tag data, it cooperates with the user terminal to perform synchronization login authorization for program synchronization login of at least one program on the vehicle terminal based on the login account; correspondingly, after the application uploads the tag data to the server, the user terminal cooperates with the server through the application to perform synchronization login authorization for program synchronization login of at least one program on the vehicle terminal based on the login account; that is, step S206 can be replaced by performing synchronization login authorization for program synchronization login of at least one program on the vehicle terminal based on the login account through the application and the server, and this constitutes a new implementation method together with one or more other processing steps provided in this embodiment.

[0039] The program synchronous login includes logging into at least one program together or in parallel. The server in this embodiment includes an application server, wherein the application can be a payment application. At least one program in this embodiment can be an application running independently on the vehicle terminal. In addition, at least one program can also be a subprogram running based on a host program, wherein the host program can be installed on the vehicle terminal; the host program can be a lightweight container that carries at least one subprogram. The host program in this embodiment can be provided by the service provider that provides the application, that is, the host program can correspond to the server.

[0040] In actual applications, the program can be provided by the program service provider, that is, a third party, and the login of the program needs to be executed by the program server. In this case, in order to enhance the trust of the program service provider and enable the program server to cooperate in the synchronous login of the program on the vehicle terminal, in this embodiment, it is possible to interact with the program server in advance to obtain the authorization result submitted by the program server, and configure the calling interface of the program server based on the authorization result to realize data transmission with the program server through the calling interface; in addition, the vehicle information, the logged-in user and the program identifier of the authorized program can be associated to characterize the association between the vehicle, user and program; among them, if the vehicle information entered by the logged-in user through the vehicle subroutine of the application is obtained, the association between the vehicle information and the logged-in user is established, and the program that authorizes the vehicle type in the vehicle information is associated with the logged-in user.

[0041] Based on the association between vehicle information, logged-in users and programs, after receiving the tag data uploaded by the user terminal, the server determines at least one program for program synchronization login on the vehicle terminal according to the tag data, that is, reads at least one program associated with the logged-in user as the program for program synchronization login on the vehicle terminal.

[0042] In specific implementation, in order to improve the efficiency of program synchronous login and avoid secondary login when the vehicle terminal has already logged in some programs associated with the logged-in user, in this embodiment, the program for program synchronous login can include the program associated with the logged-in user that is not logged in. In an optional implementation provided by this embodiment, the program for program synchronous login is determined in the following manner:

[0043] Read multiple candidate programs associated with the logged-in user and the login status of each candidate program based on the tag data;

[0044] A candidate program whose login state is the unlogged-in state is determined as a program for program synchronous login.

[0045] Optionally, the tag data may also include the vehicle type, the vehicle terminal identifier, and / or the vehicle identifier. The vehicle identifier may be an identifier that uniquely identifies the vehicle, such as the vehicle VIN (Vehicle Identification Number) or the vehicle hardware device identifier.

[0046] Specifically, according to the vehicle type carried in the tag data, multiple candidate programs associated with the logged-in user and the login status of each candidate program can be read, and the candidate program in the unlogged-in state can be determined as the program for program synchronization login.

[0047] For example, the server stores the association between vehicle type, logged-in user and program. After obtaining the tag data, based on the known vehicle type and logged-in user, the server reads the associated program as a candidate program, and reads the login status of each candidate program, and determines the candidate program with a login status of not logged in as the program for program synchronization login.

[0048] In addition, it is also possible to associate only the logged-in user with the program. Then, in the process of determining at least one program for synchronous program login, there is no need to base it on the vehicle type carried by the tag data. That is, after the server obtains the tag data uploaded by the user terminal and read from the near-field communication tag of the vehicle, it responds to the tag data and determines at least one program for synchronous program login on the vehicle terminal.

[0049] Based on determining at least one program for synchronous program login on the vehicle terminal, the server returns the login account of the logged-in user and the program identifier of at least one program to the user terminal for synchronous login authorization. Correspondingly, the user terminal receives the program identifier and login account of at least one program for synchronous program login on the vehicle terminal returned by the server; the login account in this embodiment includes the account of the logged-in user to log in to the application; in addition, it can also be an identifier that represents the uniqueness of the logged-in user or is bound to the account of the logged-in application, such as the instant messaging identifier of the logged-in user.

[0050] In a specific implementation, in order to enhance the logged-in user's awareness of the program identifier and login account of at least one program displayed, the program identifier and login account of at least one program for program synchronization login on the vehicle terminal are received and displayed as returned by the server. During the display process, in order to enhance the logged-in user's awareness of the vehicle, a login authorization page may be generated and displayed based on the program identifier, login account, and vehicle type carried by the tag data. In an optional implementation manner provided by this embodiment, after the user terminal receives the program identifier and login account of at least one program for program synchronization login on the vehicle terminal as returned by the server, the program is displayed in the following manner:

[0051] Generate a login authorization list based on the program identifier and login account;

[0052] Generate and display the login authorization page based on the login authorization list and the vehicle type carried by the tag data.

[0053] During the specific execution process, the program identifier and login account of at least one program for program synchronization login on the vehicle terminal are received and returned by the server. A login authorization list is generated based on the program identifier and login account. A login authorization page is generated and displayed based on the login authorization list and the vehicle type carried by the tag data.

[0054] For example, Figure 3 The login authorization page shown displays a login authorization list 301, which includes payment programs, vehicle programs and music programs. In order to enhance the logged-in user's awareness of the login account, the communication identifier "111xxxxxxxx" bound to the application by the logged-in user can be configured after each program; in addition, the login authorization page also displays the vehicle type and confirmation control, and the logged-in user can submit the login authorization instruction through the confirmation control.

[0055] In addition to receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server, the program identifier, configuration items, and login account of at least one program for program synchronization login on the vehicle terminal returned by the server can also be received and displayed. During the specific display process, a login authorization page is generated and displayed based on the program identifier, configuration items, login account, and vehicle type;

[0056] For example, Figure 3 In the login authorization list 301 in the login authorization page shown, the configuration items of the payment program include service settings and payment settings; the configuration items of the vehicle program include smart driving settings and in-vehicle hardware settings; the configuration items of the music program include my playlist;

[0057] That is, step S206 can be replaced by receiving and displaying the program data and login account of at least one program for program synchronization login on the vehicle terminal returned by the server, and forming a new implementation method with one or more other processing steps provided in this embodiment. Optionally, the program data includes a program identifier and configuration items.

[0058] It should be noted that the configuration items of the program can be configured by the program service provider when authorizing the program, and the program configuration items can be stored in association with the program; specifically, after the server determines at least one program for program synchronization login on the vehicle terminal, it can return the login account of the logged-in user and the program data of at least one program to the user terminal for synchronization login authorization.

[0059] In addition to cooperating with the application and the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account, the program identifier of at least one program can also be added to the tag data to enable the application to perform synchronous login authorization for at least one program on the vehicle terminal; in this case, steps S204 to S206 can also be replaced by starting the application based on the tag data, passing the tag data to the application, displaying the login account of the logged-in user and the program identifier of at least one program carried by the tag data through the application, and forming a new implementation method together with one or more other processing steps provided in this embodiment.

[0060] Step S208 , obtaining the submitted login authorization instruction and uploading it to the server, so as to cooperate with the program access of the vehicle terminal to perform program login of the at least one program.

[0061] During specific implementation, the application cooperates with the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account. After receiving and displaying the program identifier and login account of at least one program for synchronous program login on the vehicle terminal returned by the server, the submitted login authorization instruction is obtained and uploaded to the server for use in cooperating with the program access of the vehicle terminal to perform program login for at least one program.

[0062] During the specific execution process, the logged-in user can select all programs for program synchronous login based on the login authorization page, or can select some programs for program synchronous login. In this way, the logged-in user can flexibly select the program for program synchronous login based on the perception of at least one program that can be logged in synchronously, and improve the logged-in user's perception of program synchronous login based on near-field communication. In an optional implementation manner provided by this embodiment, in the process of obtaining the submitted login authorization instruction and uploading it to the server for program login of at least one program in conjunction with program access of the vehicle terminal, if the login authorization instruction is detected, the target program identifier selected by the logged-in user is read, and the target program identifier and the login account are uploaded to the server for program login of the target program corresponding to the target program identifier in conjunction with program access of the vehicle terminal.

[0063] In addition, the logged-in user can also configure the program based on the display of program data and login account to obtain program configuration information. Therefore, in the process of uploading to the server, the login authorization instruction carrying the program configuration information of the target program can be uploaded to the server, that is, the login authorization instruction can carry the program configuration information of the target program, and the program configuration information can be obtained by entering the configuration information based on the configuration items of the displayed target program.

[0064] Specifically, if a login authorization instruction is detected, the selected target program identifier and the program configuration information entered based on the configuration items of the target program are read; the target program identifier, the program configuration information and the login account are uploaded to the server, so that in addition to selecting the target program for program synchronous login through the login authorization page, the selected target program can also be personalized.

[0065] In a specific implementation, the user terminal obtains the submitted login authorization instruction and submits it to the server for cooperating with the program access of the vehicle terminal to perform program login of at least one program. Correspondingly, the server performs login processing of at least one program in combination with the program server and the program access of the vehicle terminal according to the login authorization instruction uploaded by the user terminal;

[0066] During the specific execution process, the server, in conjunction with the program server, cooperates with the program access of the vehicle terminal to perform program login of at least one program. Specifically, the vehicle terminal identifier and login account can be synchronously sent to the program server of each program in the at least one program to cooperate with the program access of the vehicle terminal to perform program login, thereby realizing synchronous program login on the vehicle terminal. In an optional implementation manner provided by this embodiment, the server performs the following operations during the process of cooperating with the program access of the vehicle terminal to perform program login of at least one program:

[0067] Read the vehicle terminal identification carried by the tag data, or query the vehicle terminal identification associated with the tag identification;

[0068] Send the login account and vehicle terminal identification to the program server of each program to cooperate with the program access of the vehicle terminal for program login.

[0069] During this process, the program on the vehicle terminal may be in an access state or not. The program server cooperates with the program access of the vehicle terminal to log in the program. It may be to log in the program in response to the program access instruction submitted by the vehicle terminal through the program, or it may be to log in the background first and then log in the program after detecting the program access instruction. The following specifically explains the program login performed by the program server in cooperation with the program access of the vehicle terminal in these two cases.

[0070] (1) In specific implementation, after any program server receives the login account and vehicle terminal identification sent by the server, it can first perform background login. If it detects that the vehicle terminal corresponding to the vehicle terminal identification submits a program access instruction for the corresponding program, it returns the login credentials obtained by the background login to the vehicle terminal to perform program login on the vehicle terminal; that is: the program server first performs background login based on the login account and vehicle terminal identification. If it detects that the vehicle terminal corresponding to the vehicle terminal identification submits a program access instruction, it returns the login credentials to the vehicle terminal to perform program login on the vehicle terminal.

[0071] In an optional implementation provided by this embodiment, the program server cooperates with the vehicle terminal to log in the program in the following manner:

[0072] Generate login credentials based on the login account, and associate the login credentials with the vehicle terminal identifier for storage;

[0073] If a program access instruction is detected, the login credentials are read according to the vehicle terminal identification carried in the program access instruction and returned to the vehicle terminal to log in the program on the vehicle terminal.

[0074] During the specific execution process, after the program server receives the login account and vehicle terminal identification sent by the server, it generates a login credential based on the login account. In order to determine the vehicle terminal for which the login credential can be used, the login credential is associated with the vehicle terminal identification and stored. In this way, if a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identification is detected, the login credential associated with the vehicle terminal identification is returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0075] (2) In specific implementation, the program server may also first store the received login account and vehicle terminal identification, and if a program access instruction uploaded by the vehicle terminal is detected, the program login to the vehicle terminal is performed based on the login account and the vehicle terminal identification; that is, the program server receives and stores the login account and the vehicle terminal identification, and if a program access instruction submitted by the vehicle terminal corresponding to the vehicle terminal identification is detected, the background login and the program login on the vehicle terminal are performed based on the login account and the vehicle terminal identification.

[0076] In an optional implementation provided by this embodiment, the program server cooperates with the vehicle terminal to log in the program in the following manner:

[0077] Associate and store the login account and vehicle terminal ID;

[0078] Read the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generate login credentials based on the login account;

[0079] The login credentials are associated with the vehicle terminal identification and stored, and the login credentials are returned to the vehicle terminal for program login on the vehicle terminal.

[0080] During the specific execution process, after the program server receives the login account and vehicle terminal identification sent by the server, it first associates and stores the login account and the vehicle terminal identification. If it detects a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identification, it reads the login account associated with the vehicle terminal identification carried by the access instruction, and generates a login credential based on the login account. After obtaining the login credential, on the one hand, it associates and stores the login credential with the vehicle terminal identification to complete the background login. On the other hand, it returns the login credential to the vehicle terminal to log in to the program on the vehicle terminal.

[0081] In addition to the above two methods of program login in cooperation with the vehicle terminal's program access, the program server can also generate login credentials based on the login account, associate the login credentials with the vehicle terminal identifier, and return the login credentials to the vehicle terminal corresponding to the vehicle terminal identifier to perform program login on the vehicle terminal, that is, the server and the program server cooperate to perform program login on the vehicle terminal according to the login account.

[0082] It should be noted that in addition to sending the login account and vehicle terminal identifier to the program server, if the login authorization instruction carries program configuration information, the server also sends the program configuration information to the program server. When returning the login credentials to the vehicle terminal, the program server can return the login credentials and associated program configuration information to the vehicle terminal to facilitate program login and configuration on the vehicle terminal. The vehicle terminal first logs in to the program based on the login credentials, and then configures the program based on the program configuration information. The program configuration information refers to the program for which it is sent to the corresponding program server.

[0083] In addition, in order to improve the logged-in user's awareness of the program logged into the vehicle terminal, the program logged into the vehicle terminal can also be configured based on the program configuration information of the program configured by the logged-in user through the user terminal; in the specific execution process, the user terminal can configure the program through the target program and upload the program configuration information to the target program server; the target program server configures and processes the target program running on the vehicle terminal according to the program configuration information. Specifically, when the program server returns the login credentials to the vehicle terminal, it can read the program configuration information associated with the login account and return the login credentials and program configuration information to the vehicle terminal; wherein, the program configuration information associated with the login account can be obtained by the logged-in user logging into the program on the user terminal or other terminal device and configuring the program, or it can be obtained by the logged-in user entering the configuration information based on the configuration items in the synchronous login authorization process sent by the server. This embodiment is not limited here.

[0084] In addition to synchronously logging into the program of the vehicle terminal based on near-field communication, synchronously exiting the program of the vehicle terminal can also be performed based on near-field communication.

[0085] In specific implementations, after the user terminal passes tag data to the application for upload to the server, if the server returns the program ID and login account of at least one program that is being logged in synchronously on the vehicle terminal, a login authorization page is generated and displayed. Optionally, the at least one program being logged in synchronously is a candidate program that is not logged in. Furthermore, for logged-in candidate programs, synchronous exit can be performed, thereby improving program exit efficiency through synchronous exit.

[0086] In an optional implementation manner provided by this embodiment, if the program identifier and login account of at least one program to be exited for program synchronous exit on the vehicle terminal are received from the server, the program identifier and login account of at least one program to be exited are displayed, the submitted exit authorization instruction is obtained and uploaded to the server to exit the program of at least one program to be exited on the vehicle terminal. Correspondingly, the server obtains a candidate program with a login status of logged in as at least one program to be exited for program synchronous exit on the vehicle terminal, returns the program identifier and login account of at least one program to be exited to the user terminal for synchronous exit authorization, and performs at least one exit authorization on the vehicle terminal in combination with the program server according to the exit authorization instruction uploaded by the user terminal. Program exit of the program to be exited; further, in an optional implementation manner provided by this embodiment, in the process of exiting at least one program to be exited on the vehicle terminal in conjunction with the program server, the server may send a program exit reminder containing a login account and a vehicle terminal identifier to the program server of each program to be exited, so as to exit the program to be exited on the vehicle terminal. Correspondingly, in the process of exiting the program to be exited on the vehicle terminal, the program server of any program to be exited first queries the login credentials associated with the vehicle terminal identifier, then marks the login credentials as invalid, and then sends an exit reminder to any program to be exited on the vehicle terminal corresponding to the vehicle terminal identifier, so as to exit any program to be exited on the vehicle terminal.

[0087] During this process, the user terminal can generate and display an exit authorization page based on the program identifier, login account and vehicle type of the program to be exited. The specific process of generating the exit authorization page is similar to the specific process of generating the login authorization page mentioned above. Please refer to the above relevant content. This embodiment is not limited here.

[0088] In addition to logging into the application through the login account of the logged-in user and cooperating with the program access of the vehicle terminal to perform program synchronous login of at least one program associated with the logged-in user, this embodiment can also log in to the vehicle terminal based on the login account through near-field communication, thereby improving the convenience of the logged-in user logging into the vehicle terminal. Specifically, the user terminal transmits tag data to the application to upload it to the server. Correspondingly, in an optional implementation manner provided by this embodiment, the server sends the login account and driving preference information to the vehicle service provider to which the vehicle belongs based on the tag data, so as to log in to the vehicle terminal based on the login account and configure the vehicle driving based on the driving preference information.

[0089] During the specific implementation process, the server may store the logged-in user's driving preference information. After receiving the tag data uploaded by the user terminal, the server determines the vehicle service provider based on the vehicle terminal identifier carried in the tag data, and sends the login account and the driving preference information associated with the login account to the vehicle service provider, so that the user can log in to the vehicle terminal based on the login account and configure the vehicle driving configuration based on the driving preference information. To enhance the vehicle service provider's awareness of the logged-in vehicle terminal, the vehicle terminal identifier may also be sent to the vehicle service provider, so that the user can log in to the vehicle terminal corresponding to the vehicle terminal identifier based on the login account.

[0090] Based on the program synchronization login of at least one program associated with the logged-in user on the vehicle terminal according to the login account, the program data of each program can be viewed through the vehicle terminal. If the program includes a payment program, payment processing can also be performed based on the payment program.

[0091] It should be noted that step S208 can be replaced by obtaining the submitted login authorization instruction and uploading it to the server, so as to perform program synchronization login of at least one program of the vehicle terminal according to the login account, and form a new implementation method with one or more other processing steps provided in this embodiment. Alternatively, step S208 can also be replaced by obtaining the submitted login authorization instruction and uploading it to the server, and form a new implementation method with one or more other processing steps provided in this embodiment.

[0092] In summary, the program login processing method for one or more vehicle terminals provided in this embodiment, by configuring a near-field communication tag on the vehicle, enables a user terminal of a logged-in user to establish a near-field communication connection with the near-field communication tag, thereby realizing synchronous program login of at least one program on the vehicle terminal according to the login account of the logged-in user. In this way, by placing the user terminal at the location of the near-field communication tag of the vehicle and performing a one-time authorization process, at least one program can be synchronously logged into the vehicle terminal, thereby improving the convenience and efficiency of program login.

[0093] During this process, the user terminal reads the tag data stored in the vehicle's near-field communication tag through near-field communication, starts an application based on the tag data, and passes the tag data to the application for uploading to the server. The server determines at least one program for program synchronization login on the vehicle terminal based on the tag data read from the vehicle's near-field communication tag uploaded by the user terminal, and returns the login account of the logged-in user and the program identifier of at least one program to the user terminal. The user terminal receives the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server, generates and displays a login authorization page based on the program identifier, login account and vehicle type carried in the tag data, and uploads the login authorization instruction to the server if obtained. The server performs program synchronization login on at least one program on the vehicle terminal based on the login account according to the login authorization instruction uploaded by the user terminal and the program server. In this way, when driving or riding in different vehicles, program login on the vehicle terminal can be conveniently and efficiently performed through near-field communication connection, thereby improving the flexibility and convenience of program login on the vehicle terminal.

[0094] The above-mentioned steps S202 to S208 provided in this embodiment can be executed by the user terminal. It should be noted that the above-mentioned steps S202 to S208 executed by the user terminal and the steps S502 to S508 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S502 to S508 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S202 to S208 provided in this embodiment.

[0095] The following is an example of an application of a vehicle terminal program login processing method provided by this embodiment in a vehicle terminal subroutine login processing scenario to further illustrate the vehicle terminal program login processing method provided by this embodiment. Figure 4 As shown, the program login processing method of the vehicle terminal applied to the subroutine login processing scenario of the vehicle terminal specifically includes the following steps.

[0096] Step S402 : reading tag data stored in the near field communication tag of the vehicle through a near field communication connection.

[0097] Step S404: starting an application based on the tag data, and passing the tag data to the application for uploading to the server.

[0098] Step S410: receiving the subprogram identifier and login account of at least one subprogram for program synchronization login on the vehicle terminal returned by the server.

[0099] Step S412: Generate and display a login authorization page based on the program identifier, login account, and vehicle type carried in the tag data.

[0100] Step S414: obtaining the login authorization instruction submitted by the login user through the login authorization page.

[0101] Step S416: Upload the login authorization instruction to the server.

[0102] The above-mentioned steps S402 to S404 and steps S410 to S416 provided in this embodiment are executed by the user terminal. It should be noted that the above-mentioned steps S402 to S404 and steps S410 to S416 executed by the user terminal and steps S406 to S408 and steps S418 to S420 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S406 to S408 and steps S418 to S420 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding contents of steps S402 to S404 and steps S410 to S416 provided in this embodiment.

[0103] It should be noted that any one of the steps or any combination of multiple steps in steps S402 to S420 can be combined with any one of the steps S202 to S208 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or multiple technical features can be selected in steps S402 to S420 and combined with any one or multiple technical features provided in steps S202 to S208 to form a new implementation method; or, any one or multiple technical features in steps S402 to S420 can also be replaced with any one or multiple technical features provided in steps S202 to S208 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0104] One or more embodiments of another vehicle terminal program login processing method provided in this specification are as follows:

[0105] Reference Figure 5 The program login processing method of the vehicle terminal provided in this embodiment specifically includes steps S502 to S508.

[0106] Step S502: Acquire tag data uploaded by the user terminal and read from the near field communication tag of the vehicle.

[0107] In this embodiment, a near field communication component that can perform near field communication (NFC) connection with other devices can be configured in the user terminal to establish a near field communication connection with the vehicle's near field communication tag through the near field communication component, so as to read the tag data stored in the vehicle's near field communication tag through the near field communication connection; in addition to near field communication, it can also be Bluetooth communication, wireless network communication, infrared communication and / or radio frequency communication. Correspondingly, the near field communication component can be a Bluetooth component, wireless component, infrared component or radio frequency communication component that provides Bluetooth capability, wireless network capability, infrared communication capability or radio frequency communication capability; the vehicle's near field communication tag can be a Bluetooth component, wireless component, infrared component or radio frequency communication component.

[0108] During specific implementation, the user terminal reads the tag data stored in the vehicle's near-field communication tag through near-field communication; during the specific execution process, the user terminal can establish a near-field communication connection with the vehicle's near-field communication tag through the near-field communication component of the user terminal, and then, on the basis of establishing the near-field communication connection, read the tag data stored in the vehicle's near-field communication tag through the near-field communication connection; in addition to the user terminal reading the tag data stored in the vehicle's near-field communication tag through near-field communication, it can also receive tag data sent by the vehicle's near-field communication tag through near-field communication.

[0109] The tag data includes the tag identifier of the near-field communication tag, that is, the tag data can be replaced by the tag identifier; in addition, to launch an application based on the tag data, the tag data can also include the program identifier and / or program address of the application to be launched. It should be noted that the tag data can include any one or more of the tag identifier, program identifier, and program address, or the tag data can also be replaced by any one or more of the tag identifier, program identifier, and program address.

[0110] During the specific execution process, when the user terminal reads the tag data stored in the vehicle's near-field communication tag through near-field communication, the user terminal can call near-field communication for detection, and after detecting the near-field communication tag, establish a near-field communication connection with the near-field communication tag, and then read the stored tag data from the near-field communication tag; the vehicle's near-field communication tag can also perform detection, and after detecting the user terminal's near-field communication component, establish a near-field communication connection with the near-field communication component, and then send the stored tag data to the near-field communication component.

[0111] In a specific implementation, after the vehicle's near-field communication tag stores tag data, the application is started based on the tag data to upload the tag data to the server through the application; in the process of starting the application based on the tag data, the user terminal may parse the tag data to obtain a parsing result, wherein the parsing result may include a tag identifier, a program identifier and / or a program address, and then start the corresponding application in the installed application list of the user terminal based on the parsing result;

[0112] After the application is started based on the tag data, the tag data is passed to the application for uploading to the server; it should be noted that the tag data passed to the application can be all the tag data, such as passing the tag identifier, program identifier and / or program address as tag data to the application. In addition, only part of the content contained in the tag data can be passed to the application, such as passing the tag identifier in the tag data to the application.

[0113] Step S504: Determine at least one program for program synchronization login on the vehicle terminal based on the tag data.

[0114] During specific implementation, the user terminal starts the application based on the tag data and passes in the tag data, and uploads the tag data to the server through the application; correspondingly, the server obtains the tag data uploaded by the user terminal and read from the near-field communication tag of the vehicle. After obtaining the tag data, the server determines at least one program for synchronous login on the vehicle terminal based on the tag data. Since the program synchronous login is based on the login account of the logged-in user, the login account and the logged-in program often involve the privacy of the logged-in user, the login user's authorization is required to perform synchronous login on the vehicle terminal based on the login account of the logged-in user; therefore, after the server determines at least one program for synchronous login on the vehicle terminal based on the tag data, it cooperates with the user terminal to perform synchronous login authorization for synchronous login of at least one program on the vehicle terminal based on the login account; correspondingly, after the application uploads the tag data to the server, the user terminal cooperates with the server through the application to perform synchronous login authorization for synchronous login of at least one program on the vehicle terminal based on the login account.

[0115] The program synchronous login includes logging in to at least one program simultaneously or in parallel. The server in this embodiment includes an application server, where the application can be a payment application. In this embodiment, at least one program can be an application running independently on the vehicle terminal. Furthermore, at least one program can be a subprogram running based on a host program, where the host program can be installed on the vehicle terminal.

[0116] In actual applications, the program can be provided by the program service provider, that is, a third party, and the login of the program needs to be executed by the program server. In this case, in order to enhance the trust of the program service provider and enable the program server to cooperate in the synchronous login of the program on the vehicle terminal, in this embodiment, it is possible to interact with the program server in advance to obtain the authorization result submitted by the program server, and configure the calling interface of the program server based on the authorization result to realize data transmission with the program server through the calling interface; in addition, the vehicle information, the logged-in user and the program identifier of the authorized program can be associated to characterize the association between the vehicle, user and program; among them, if the vehicle information entered by the logged-in user through the vehicle subroutine of the application is obtained, the association between the vehicle information and the logged-in user is established, and the program that authorizes the vehicle type in the vehicle information is associated with the logged-in user.

[0117] Based on the association between vehicle information, logged-in users and programs, after receiving the tag data uploaded by the user terminal, the server determines at least one program for program synchronization login on the vehicle terminal according to the tag data, that is, reads at least one program associated with the logged-in user as the program for program synchronization login on the vehicle terminal.

[0118] In specific implementation, in order to improve the efficiency of program synchronous login and avoid secondary login when the vehicle terminal has already logged in some programs associated with the logged-in user, in this embodiment, the program for program synchronous login can include the program associated with the logged-in user that is not logged in. In an optional implementation provided by this embodiment, the program for program synchronous login is determined in the following manner:

[0119] Read multiple candidate programs associated with the logged-in user and the login status of each candidate program based on the tag data;

[0120] A candidate program whose login state is the unlogged-in state is determined as a program for program synchronous login.

[0121] Optionally, the tag data may also include the vehicle type, the vehicle terminal identifier, and / or the vehicle identifier. The vehicle identifier may be an identifier that uniquely identifies the vehicle, such as the vehicle VIN (Vehicle Identification Number) or the vehicle hardware device identifier.

[0122] Specifically, according to the vehicle type carried in the tag data, multiple candidate programs associated with the logged-in user and the login status of each candidate program can be read, and the candidate program in the unlogged-in state can be determined as the program for program synchronization login.

[0123] For example, the server stores the association between vehicle type, logged-in user and program. After obtaining the tag data, based on the known vehicle type and logged-in user, the server reads the associated program as a candidate program, and reads the login status of each candidate program, and determines the candidate program with a login status of not logged in as the program for program synchronization login.

[0124] In addition, it is also possible to associate only the logged-in user with the program. Then, in the process of determining at least one program for synchronous program login, there is no need to base it on the vehicle type carried by the tag data. That is, after the server obtains the tag data uploaded by the user terminal and read from the near-field communication tag of the vehicle, it responds to the tag data and determines at least one program for synchronous program login on the vehicle terminal.

[0125] Step S506: Return the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization.

[0126] Based on determining at least one program for synchronous program login on the vehicle terminal, the server returns the login account of the logged-in user and the program identifier of at least one program to the user terminal for synchronous login authorization. Correspondingly, the user terminal receives the program identifier and login account of at least one program for synchronous program login on the vehicle terminal returned by the server; the login account in this embodiment includes the account of the logged-in user to log in to the application; in addition, it can also be an identifier that represents the uniqueness of the logged-in user or is bound to the account of the logged-in application, such as the instant messaging identifier of the logged-in user.

[0127] In a specific implementation, in order to enhance the logged-in user's awareness of the program identifier and login account of at least one program displayed, the program identifier and login account of at least one program for program synchronization login on the vehicle terminal are received and displayed as returned by the server. During the display process, in order to enhance the logged-in user's awareness of the vehicle, a login authorization page may be generated and displayed based on the program identifier, login account, and vehicle type carried by the tag data. In an optional implementation manner provided by this embodiment, after the user terminal receives the program identifier and login account of at least one program for program synchronization login on the vehicle terminal as returned by the server, the program is displayed in the following manner:

[0128] Generate a login authorization list based on the program identifier and login account;

[0129] Generate and display the login authorization page based on the login authorization list and the vehicle type carried by the tag data.

[0130] During the specific execution process, the program identifier and login account of at least one program for program synchronization login on the vehicle terminal are received and returned by the server. A login authorization list is generated based on the program identifier and login account. A login authorization page is generated and displayed based on the login authorization list and the vehicle type carried by the tag data.

[0131] For example, Figure 3 The login authorization page shown displays a login authorization list 301, which includes payment programs, vehicle programs and music programs. In order to enhance the logged-in user's awareness of the login account, the communication identifier "111xxxxxxxx" bound to the application by the logged-in user can be configured after each program; in addition, the login authorization page also displays the vehicle type and confirmation control, and the logged-in user can submit the login authorization instruction through the confirmation control.

[0132] In addition to receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server, the program identifier, configuration items, and login account of at least one program for program synchronization login on the vehicle terminal returned by the server can also be received and displayed. During the specific display process, a login authorization page is generated and displayed based on the program identifier, configuration items, login account, and vehicle type;

[0133] For example, Figure 3 In the login authorization list 301 in the login authorization page shown, the configuration items of the payment program include service settings and payment devices; the configuration items of the vehicle program include smart driving settings and in-vehicle hardware settings; and the configuration items of the music program include my playlist.

[0134] It should be noted that the configuration items of the program can be configured by the program service provider when authorizing the program, and the program configuration items can be stored in association with the program; specifically, after the server determines at least one program for program synchronization login on the vehicle terminal, it can return the login account of the logged-in user and the program data of at least one program to the user terminal for synchronization login authorization.

[0135] In addition to cooperating with the application and the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account, the program identifier of at least one program can also be added to the tag data to enable the application to perform synchronous login authorization for at least one program on the vehicle terminal.

[0136] Step S508 : According to the login authorization instruction uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the at least one program.

[0137] During specific implementation, the application cooperates with the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account. After receiving and displaying the program identifier and login account of at least one program for synchronous program login on the vehicle terminal returned by the server, the submitted login authorization instruction is obtained and uploaded to the server for use in cooperating with the program access of the vehicle terminal to perform program login for at least one program.

[0138] During the specific execution process, the logged-in user can select all programs for program synchronous login based on the login authorization page, or can select some programs for program synchronous login. In this way, the logged-in user can flexibly select the program for program synchronous login based on the perception of at least one program that can be logged in synchronously, and improve the logged-in user's perception of program synchronous login based on near-field communication. In an optional implementation manner provided by this embodiment, in the process of obtaining the submitted login authorization instruction and uploading it to the server for program login of at least one program in conjunction with program access of the vehicle terminal, if the login authorization instruction is detected, the target program identifier selected by the logged-in user is read, and the target program identifier and the login account are uploaded to the server for program login of the target program corresponding to the target program identifier in conjunction with program access of the vehicle terminal.

[0139] In addition, the logged-in user can also configure the program based on the display of program data and login account to obtain program configuration information. Therefore, in the process of uploading to the server, the login authorization instruction carrying the program configuration information of the target program can be uploaded to the server, that is, the login authorization instruction can carry the program configuration information of the target program, and the program configuration information can be obtained by entering the configuration information based on the configuration items of the displayed target program.

[0140] Specifically, if a login authorization instruction is detected, the selected target program identifier and the program configuration information entered based on the configuration items of the target program are read; the target program identifier, the program configuration information and the login account are uploaded to the server, so that in addition to selecting the target program for program synchronous login through the login authorization page, the selected target program can also be personalized.

[0141] In a specific implementation, the user terminal obtains the submitted login authorization instruction and submits it to the server for cooperating with the program access of the vehicle terminal to perform program login of at least one program. Correspondingly, the server performs login processing of at least one program in combination with the program server and the program access of the vehicle terminal according to the login authorization instruction uploaded by the user terminal;

[0142] During the specific execution process, the server, in conjunction with the program server, cooperates with the program access of the vehicle terminal to perform program login of at least one program. Specifically, the vehicle terminal identifier and login account can be synchronously sent to the program server of each program in the at least one program to cooperate with the program access of the vehicle terminal to perform program login, thereby realizing synchronous program login on the vehicle terminal. In an optional implementation manner provided by this embodiment, the server performs the following operations during the process of cooperating with the program access of the vehicle terminal to perform program login of at least one program:

[0143] Read the vehicle terminal identification carried by the tag data, or query the vehicle terminal identification associated with the tag identification;

[0144] Send the login account and vehicle terminal identification to the program server of each program to cooperate with the program access of the vehicle terminal for program login.

[0145] During this process, the program on the vehicle terminal may be in an access state or not. The program server cooperates with the program access of the vehicle terminal to log in the program. It may be to log in the program in response to the program access instruction submitted by the vehicle terminal through the program, or it may be to log in the background first and then log in the program after detecting the program access instruction. The following specifically explains the program login performed by the program server in cooperation with the program access of the vehicle terminal in these two cases.

[0146] (1) In specific implementation, after any program server receives the login account and vehicle terminal identification sent by the server, it can first perform background login. If it detects that the vehicle terminal corresponding to the vehicle terminal identification submits a program access instruction for the corresponding program, it returns the login credentials obtained by the background login to the vehicle terminal to perform program login on the vehicle terminal; that is: the program server first performs background login based on the login account and vehicle terminal identification. If it detects that the vehicle terminal corresponding to the vehicle terminal identification submits a program access instruction, it returns the login credentials to the vehicle terminal to perform program login on the vehicle terminal.

[0147] In an optional implementation provided by this embodiment, the program server cooperates with the vehicle terminal to log in the program in the following manner:

[0148] Generate login credentials based on the login account, and associate the login credentials with the vehicle terminal identifier for storage;

[0149] If a program access instruction is detected, the login credentials are read according to the vehicle terminal identification carried in the program access instruction and returned to the vehicle terminal to log in the program on the vehicle terminal.

[0150] During the specific execution process, after the program server receives the login account and vehicle terminal identification sent by the server, it generates a login credential based on the login account. In order to determine the vehicle terminal for which the login credential can be used, the login credential is associated with the vehicle terminal identification and stored. In this way, if a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identification is detected, the login credential associated with the vehicle terminal identification is returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0151] (2) In specific implementation, the program server may also first store the received login account and vehicle terminal identification, and if a program access instruction uploaded by the vehicle terminal is detected, the program login to the vehicle terminal is performed based on the login account and the vehicle terminal identification; that is, the program server receives and stores the login account and the vehicle terminal identification, and if a program access instruction submitted by the vehicle terminal corresponding to the vehicle terminal identification is detected, the background login and the program login on the vehicle terminal are performed based on the login account and the vehicle terminal identification.

[0152] In an optional implementation provided by this embodiment, the program server cooperates with the vehicle terminal to log in the program in the following manner:

[0153] Associate and store the login account and vehicle terminal ID;

[0154] Read the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generate login credentials based on the login account;

[0155] The login credentials are associated with the vehicle terminal identification and stored, and the login credentials are returned to the vehicle terminal for program login on the vehicle terminal.

[0156] During the specific execution process, after the program server receives the login account and vehicle terminal identification sent by the server, it first associates and stores the login account and the vehicle terminal identification. If it detects a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identification, it reads the login account associated with the vehicle terminal identification carried by the access instruction, and generates a login credential based on the login account. After obtaining the login credential, on the one hand, it associates and stores the login credential with the vehicle terminal identification to complete the background login. On the other hand, it returns the login credential to the vehicle terminal to log in to the program on the vehicle terminal.

[0157] In addition to the above two methods of program login in cooperation with the vehicle terminal's program access, the program server can also generate login credentials based on the login account, associate the login credentials with the vehicle terminal identifier, and return the login credentials to the vehicle terminal corresponding to the vehicle terminal identifier to perform program login on the vehicle terminal, that is, the server and the program server cooperate to perform program login on the vehicle terminal according to the login account.

[0158] It should be noted that in addition to sending the login account and vehicle terminal identifier to the program server, if the login authorization instruction carries program configuration information, the server also sends the program configuration information to the program server. When returning the login credentials to the vehicle terminal, the program server can return the login credentials and associated program configuration information to the vehicle terminal to facilitate program login and configuration on the vehicle terminal. The vehicle terminal first logs in to the program based on the login credentials, and then configures the program based on the program configuration information. The program configuration information refers to the program for which it is sent to the corresponding program server.

[0159] In addition, in order to improve the logged-in user's awareness of the program logged into the vehicle terminal, the program logged into the vehicle terminal can also be configured based on the program configuration information of the program configured by the logged-in user through the user terminal; in the specific execution process, the user terminal can configure the program through the target program and upload the program configuration information to the target program server; the target program server configures and processes the target program running on the vehicle terminal according to the program configuration information. Specifically, when the program server returns the login credentials to the vehicle terminal, it can read the program configuration information associated with the login account and return the login credentials and program configuration information to the vehicle terminal; wherein, the program configuration information associated with the login account can be obtained by the logged-in user logging into the program on the user terminal or other terminal device and configuring the program, or it can be obtained by the logged-in user entering the configuration information based on the configuration items in the synchronous login authorization process sent by the server. This embodiment is not limited here.

[0160] In addition to synchronously logging into the program of the vehicle terminal based on near-field communication, synchronously exiting the program of the vehicle terminal can also be performed based on near-field communication.

[0161] In specific implementations, after the user terminal passes tag data to the application for upload to the server, if the server returns the program ID and login account of at least one program that is being logged in synchronously on the vehicle terminal, a login authorization page is generated and displayed. Optionally, the at least one program being logged in synchronously is a candidate program that is not logged in. Furthermore, for logged-in candidate programs, synchronous exit can be performed, thereby improving program exit efficiency through synchronous exit.

[0162] In an optional implementation manner provided by this embodiment, if the program identifier and login account of at least one program to be exited for program synchronous exit on the vehicle terminal are received from the server, the program identifier and login account of at least one program to be exited are displayed, the submitted exit authorization instruction is obtained and uploaded to the server to exit the program of at least one program to be exited on the vehicle terminal. Correspondingly, the server obtains a candidate program with a login status of logged in as at least one program to be exited for program synchronous exit on the vehicle terminal, returns the program identifier and login account of at least one program to be exited to the user terminal for synchronous exit authorization, and performs at least one exit authorization on the vehicle terminal in combination with the program server according to the exit authorization instruction uploaded by the user terminal. Program exit of the program to be exited; further, in an optional implementation manner provided by this embodiment, in the process of exiting at least one program to be exited on the vehicle terminal in conjunction with the program server, the server may send a program exit reminder containing a login account and a vehicle terminal identifier to the program server of each program to be exited, so as to exit the program to be exited on the vehicle terminal. Correspondingly, in the process of exiting the program to be exited on the vehicle terminal, the program server of any program to be exited first queries the login credentials associated with the vehicle terminal identifier, then marks the login credentials as invalid, and then sends an exit reminder to any program to be exited on the vehicle terminal corresponding to the vehicle terminal identifier, so as to exit any program to be exited on the vehicle terminal.

[0163] During this process, the user terminal can generate and display an exit authorization page based on the program identifier, login account and vehicle type of the program to be exited. The specific process of generating the exit authorization page is similar to the specific process of generating the login authorization page mentioned above. Please refer to the above relevant content. This embodiment is not limited here.

[0164] In addition to logging into the application through the login account of the logged-in user and cooperating with the program access of the vehicle terminal to perform program synchronous login of at least one program associated with the logged-in user, this embodiment can also log in to the vehicle terminal based on the login account through near-field communication, thereby improving the convenience of the logged-in user logging into the vehicle terminal. Specifically, the user terminal transmits tag data to the application to upload it to the server. Correspondingly, in an optional implementation manner provided by this embodiment, the server sends the login account and driving preference information to the vehicle service provider to which the vehicle belongs based on the tag data, so as to log in to the vehicle terminal based on the login account and configure the vehicle driving based on the driving preference information.

[0165] During the specific implementation process, the server may store the logged-in user's driving preference information. After receiving the tag data uploaded by the user terminal, the server determines the vehicle service provider based on the vehicle terminal identifier carried in the tag data, and sends the login account and the driving preference information associated with the login account to the vehicle service provider, so that the user can log in to the vehicle terminal based on the login account and configure the vehicle driving configuration based on the driving preference information. To enhance the vehicle service provider's awareness of the logged-in vehicle terminal, the vehicle terminal identifier may also be sent to the vehicle service provider, so that the user can log in to the vehicle terminal corresponding to the vehicle terminal identifier based on the login account.

[0166] Based on the program synchronization login of at least one program associated with the logged-in user on the vehicle terminal according to the login account, the program data of each program can be viewed through the vehicle terminal. If the program includes a payment program, payment processing can also be performed based on the payment program.

[0167] In summary, the program login processing method for one or more vehicle terminals provided in this embodiment, by configuring a near-field communication tag on the vehicle, enables a user terminal of a logged-in user to establish a near-field communication connection with the near-field communication tag, thereby realizing synchronous program login of at least one program on the vehicle terminal according to the login account of the logged-in user. In this way, by placing the user terminal at the location of the near-field communication tag of the vehicle and performing a one-time authorization process, at least one program can be synchronously logged into the vehicle terminal, thereby improving the convenience and efficiency of program login.

[0168] During this process, the user terminal reads the tag data stored in the vehicle's near-field communication tag through near-field communication, starts an application based on the tag data, and passes the tag data to the application for uploading to the server. The server determines at least one program for program synchronization login on the vehicle terminal based on the tag data read from the vehicle's near-field communication tag uploaded by the user terminal, and returns the login account of the logged-in user and the program identifier of at least one program to the user terminal. The user terminal receives the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server, generates and displays a login authorization page based on the program identifier, login account and vehicle type carried in the tag data, and uploads the login authorization instruction to the server if obtained. The server performs program synchronization login on at least one program on the vehicle terminal based on the login account according to the login authorization instruction uploaded by the user terminal and the program server. In this way, when driving or riding in different vehicles, program login on the vehicle terminal can be conveniently and efficiently performed through near-field communication connection, thereby improving the flexibility and convenience of program login on the vehicle terminal.

[0169] The following is an example of an application of a vehicle terminal program login processing method provided by this embodiment in a vehicle terminal subroutine login processing scenario to further illustrate the vehicle terminal program login processing method provided by this embodiment. Figure 4 As shown, the program login processing method of the vehicle terminal applied to the subroutine login processing scenario of the vehicle terminal specifically includes the following steps.

[0170] Step S406: Read at least one sub-application associated with the logged-in user for program synchronization login on the vehicle terminal according to the tag data.

[0171] Step S408: Return the login account of the user who logged into the application and the program identifier of at least one subprogram to the user terminal.

[0172] Step S418: Read the vehicle terminal identification carried in the tag data according to the login authorization instruction uploaded by the user terminal.

[0173] Step S420: Send the login account and vehicle terminal identification to each subprogram server to cooperate with the subprogram access of the vehicle terminal to perform subprogram login.

[0174] This specification provides an embodiment of a program login processing device for a vehicle terminal as follows:

[0175] In the above embodiment, a program login processing method for a vehicle terminal is provided. Correspondingly, a program login processing device for a vehicle terminal is also provided, which will be described below with reference to the accompanying drawings.

[0176] Reference Figure 6 , which shows a schematic diagram of an embodiment of a program login processing device for a vehicle terminal provided by this embodiment.

[0177] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0178] This embodiment provides a program login processing device for a vehicle terminal, the device comprising:

[0179] The tag data reading module 602 is configured to read the tag data stored in the near field communication tag of the vehicle through near field communication;

[0180] An application startup module 604 is configured to start an application based on the tag data and pass the tag data to the application for uploading to a server;

[0181] The receiving module 606 is configured to receive and display the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server;

[0182] The login authorization instruction uploading module 608 is configured to obtain the submitted login authorization instruction and upload it to the server, so as to be used for program login of the at least one program in conjunction with the program access of the vehicle terminal.

[0183] Another embodiment of a program login processing device for a vehicle terminal provided in this specification is as follows:

[0184] In the above embodiment, another program login processing method for a vehicle terminal is provided. Correspondingly, a program login processing device for a vehicle terminal is also provided, which will be described below with reference to the accompanying drawings.

[0185] Reference Figure 7 , which shows a schematic diagram of an embodiment of a program login processing device for a vehicle terminal provided by this embodiment.

[0186] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0187] This embodiment provides a program login processing device for a vehicle terminal, the device comprising:

[0188] The tag data acquisition module 702 is configured to acquire tag data uploaded by a user terminal and read from a near field communication tag of a vehicle;

[0189] A program determination module 704 is configured to determine at least one program for program synchronization login on the vehicle terminal based on the tag data;

[0190] The return module 706 is configured to return the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization;

[0191] The program login module 708 is configured to perform program login of the at least one program according to the login authorization instruction uploaded by the user terminal, in combination with the program server and the program access of the vehicle terminal.

[0192] An embodiment of a user terminal provided in this specification is as follows:

[0193] Corresponding to the above-described method for processing program login for a vehicle terminal, based on the same technical concept, one or more embodiments of this specification further provide a user terminal, which is used to execute the above-described method for processing program login for a vehicle terminal. Figure 8 A schematic diagram of the structure of a user terminal provided in one or more embodiments of this specification.

[0194] This embodiment provides a user terminal, including:

[0195] like Figure 8 As shown, user terminals can vary significantly due to configuration or performance differences and may include one or more processors 801 and memory 802. Memory 802 may store one or more applications or data. Memory 802 may be either transient or persistent. Applications stored in memory 802 may include one or more modules (not shown), each of which may comprise a series of computer-executable instructions within the user terminal. Furthermore, processor 801 may be configured to communicate with memory 802 to execute the series of computer-executable instructions within memory 802 on the user terminal. The user terminal may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, and the like.

[0196] In a specific embodiment, the user terminal includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions in the user terminal, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following:

[0197] Reading tag data stored in a near-field communication tag of a vehicle through near-field communication;

[0198] Starting an application based on the tag data, and passing the tag data to the application for uploading to a server;

[0199] receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server;

[0200] The submitted login authorization instruction is obtained and uploaded to the server for use in coordinating the program access of the vehicle terminal to perform program login of the at least one program.

[0201] A server embodiment provided in this specification is as follows:

[0202] Corresponding to the above-described another vehicle terminal program login processing method, based on the same technical concept, one or more embodiments of this specification further provide a server, which is used to execute the above-described vehicle terminal program login processing method. Figure 9 A schematic diagram of the structure of a server provided in one or more embodiments of this specification.

[0203] This embodiment provides a server, including:

[0204] like Figure 9 As shown, servers can vary significantly depending on their configuration or performance. They may include one or more processors 901 and memory 902. Memory 902 may store one or more applications or data. Memory 902 may be either ephemeral or persistent. Applications stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions within the server. Furthermore, processor 901 may be configured to communicate with memory 902 to execute the series of computer-executable instructions within memory 902 on the server. The server may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, and the like.

[0205] In a specific embodiment, the server includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions in the server, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following:

[0206] Obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle;

[0207] Determining at least one program for program synchronization login on the vehicle terminal according to the tag data;

[0208] Returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization;

[0209] According to the login authorization instruction uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the at least one program.

[0210] An embodiment of a computer-readable storage medium provided in this specification is as follows:

[0211] Corresponding to the above-described method for processing program login of a vehicle terminal, based on the same technical concept, one or more embodiments of this specification further provide a computer-readable storage medium.

[0212] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented:

[0213] Reading tag data stored in a near-field communication tag of a vehicle through near-field communication;

[0214] Starting an application based on the tag data, and passing the tag data to the application for uploading to a server;

[0215] receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server;

[0216] The submitted login authorization instruction is obtained and uploaded to the server for use in coordinating the program access of the vehicle terminal to perform program login of the at least one program.

[0217] It should be noted that the embodiment of a computer-readable storage medium in this specification and the embodiment of a program login processing method for a vehicle terminal in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0218] Another embodiment of a computer-readable storage medium provided in this specification is as follows:

[0219] Corresponding to the above-described method for processing program login for another vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0220] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented:

[0221] Obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle;

[0222] Determining at least one program for program synchronization login on the vehicle terminal according to the tag data;

[0223] Returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization;

[0224] According to the login authorization instruction uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the at least one program.

[0225] It should be noted that the embodiment of another computer-readable storage medium in this specification and the embodiment of another program login processing method for a vehicle terminal in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0226] An embodiment of a computer program product provided in this specification is as follows:

[0227] Corresponding to the above-described method for processing program login for a vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0228] A computer program product comprising a computer program / instructions, which, when executed by a processor, implements the following steps:

[0229] Reading tag data stored in a near-field communication tag of a vehicle through near-field communication;

[0230] Starting an application based on the tag data, and passing the tag data to the application for uploading to a server;

[0231] receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server;

[0232] The submitted login authorization instruction is obtained and uploaded to the server for use in coordinating the program access of the vehicle terminal to perform program login of the at least one program.

[0233] It should be noted that the embodiment of a computer program product in this specification and the embodiment of a program login processing method for a vehicle terminal in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0234] Another computer program product embodiment provided in this specification is as follows:

[0235] Corresponding to the above-described method for processing program login for another vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0236] A computer program product comprising a computer program / instructions, which, when executed by a processor, implements the following steps:

[0237] Obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle;

[0238] Determining at least one program for program synchronization login on the vehicle terminal according to the tag data;

[0239] Returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization;

[0240] According to the login authorization instruction uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the at least one program.

[0241] It should be noted that the embodiment of another computer program product in this specification and the embodiment of another program login processing method for a vehicle terminal in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0242] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are similar to the method embodiment, so the description is relatively simple. For relevant content in the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the partial description of the method embodiment.

[0243] The foregoing description describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than that described in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In some embodiments, program login processing and parallel processing of multiple vehicle terminals are also possible or may be advantageous.

[0244] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using physical hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly performed using software called a "logic compiler." This is similar to the software compilers used during program development. Before compilation, the original code must be written in a specific programming language, called a Hardware Description Language (HDL). There are many types of HDL, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that simply by programming a method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0245] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the memory control logic. Those skilled in the art will also appreciate that, in addition to implementing the controller purely in computer-readable program code, the controller can also be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing the various functions included therein can also be considered as structures within the hardware component. Alternatively, the means for implementing the various functions can be considered both a software module implementing the method and a structure within the hardware component.

[0246] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0247] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0248] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0249] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0250] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0251] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0252] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0253] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0254] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0255] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising at least one ..." does not exclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the element.

[0256] One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data classes. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In distributed computing environments, program modules may be located in local and remote computer storage media, including storage devices.

[0257] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A program login processing method for a vehicle terminal, comprising: Reading tag data stored in a near-field communication tag of a vehicle through near-field communication; Starting an application based on the tag data, and passing the tag data to the application for uploading to a server; receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server; The at least one program includes a candidate program in a non-logged-in state among a plurality of candidate programs associated with the logged-in user determined according to the tag data; If a login authorization instruction is detected, the selected target program identifier and the login account are uploaded to the server for program login of the target program corresponding to the target program identifier in conjunction with program access of the vehicle terminal.

2. The program login processing method for a vehicle terminal according to claim 1, wherein the step of performing program login of a target program corresponding to the target program identifier in conjunction with program access of the vehicle terminal comprises: Reading the vehicle terminal identification carried by the tag data; The login account and the vehicle terminal identifier are sent to the program server of the target program to facilitate program access of the vehicle terminal for program login.

3. The program login processing method for a vehicle terminal according to claim 2, wherein the program login is performed in conjunction with the program access of the vehicle terminal, comprising: Generate a login credential based on the login account, and associate the login credential with the vehicle terminal identifier for storage; If a program access instruction is detected, the login credential is read according to the vehicle terminal identification carried in the program access instruction and returned to the vehicle terminal to perform program login on the vehicle terminal.

4. The program login processing method for a vehicle terminal according to claim 2, wherein the program login is performed in conjunction with the program access of the vehicle terminal, comprising: Associating and storing the login account and the vehicle terminal identifier; Reading the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generating a login credential based on the login account; The login credential is associated with the vehicle terminal identifier and stored, and the login credential is returned to the vehicle terminal to perform program login on the vehicle terminal.

5. The program login processing method for an in-vehicle terminal according to claim 1, wherein the receiving, returned by the server, the program identifier and login account of at least one program for program synchronous login on the in-vehicle terminal and displaying the received program identifier and login account, comprises: receiving the program identifier and the login account returned by the server; Generate a login authorization list according to the program identifier and the login account; A login authorization page is generated and displayed based on the login authorization list and the vehicle type carried by the tag data.

6. The program login processing method of the vehicle terminal according to claim 1, wherein the login authorization instruction carries the program configuration information of the target program; The program configuration information is obtained by entering configuration information based on the displayed configuration items of the target program. 7 . The program login processing method for a vehicle terminal according to claim 1 , wherein the target program identifier is read after the login authorization instruction is detected.

8. The program login processing method of the vehicle terminal according to claim 1, wherein the program for synchronous program login includes a program in a non-logged-in state associated with the login user; The program is determined in the following manner: reading, based on the tag data, a plurality of candidate programs associated with the logged-in user and a login status of each candidate program; A candidate program whose login status is the unlogged-in state is determined as the program for performing program synchronous login.

9. The program login processing method for an in-vehicle terminal according to claim 1, further comprising: starting an application based on the tag data and transferring the tag data to the application for uploading to a server. If the program identifier of at least one program to be exited and the login account number for program synchronous exit at the vehicle terminal are received from the server, the program identifier of the at least one program to be exited and the login account number are displayed; The submitted exit authorization instruction is obtained and uploaded to the server, so as to cooperate with the vehicle terminal to exit the at least one program to be exited.

10. The program login processing method for the vehicle terminal according to claim 9, wherein any of the at least one program to be exited is exited in the following manner, including: Querying the login credentials associated with the vehicle terminal identification and marking the login credentials as invalid; An exit reminder is issued to any of the programs to be exited, so that the program of any of the programs to be exited is exited at the vehicle terminal.

11. The program login processing method of the vehicle terminal according to claim 1, wherein the at least one program includes a subroutine running based on the host program; The host program is installed in the vehicle terminal.

12. The program login processing method of the vehicle terminal according to claim 1, further comprising: Performing program configuration through the target program and uploading program configuration information to the target program server; The target program server performs configuration processing on the target program running on the vehicle terminal according to the program configuration information.

13. A program login processing method for a vehicle terminal, comprising: Obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle; Determining at least one program for program synchronization login on the vehicle terminal based on the tag data; the at least one program includes a candidate program in a non-logged-in state among a plurality of candidate programs associated with the logged-in user; Returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization; According to the login account and the selected target program identifier uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the target program corresponding to the target program identifier.

14. The program login processing method for a vehicle terminal according to claim 13, wherein the program server cooperates with the program access of the vehicle terminal to perform program login of the target program corresponding to the target program identifier, comprising: Reading the vehicle terminal identification carried by the tag data; The login account and the vehicle terminal identifier are sent to the program server of the target program to facilitate program access of the vehicle terminal for program login.

15. The program login processing method for a vehicle terminal according to claim 14, wherein the program login is performed in conjunction with the program access of the vehicle terminal, comprising: Generate a login credential based on the login account, and associate the login credential with the vehicle terminal identifier for storage; If a program access instruction is detected, the login credential is read according to the vehicle terminal identification carried in the program access instruction and returned to the vehicle terminal to perform program login on the vehicle terminal.

16. The program login processing method for a vehicle terminal according to claim 14, wherein the program login is performed in conjunction with the program access of the vehicle terminal, comprising: Associating and storing the login account and the vehicle terminal identifier; Reading the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generating a login credential based on the login account; The login credential is associated with the vehicle terminal identifier and stored, and the login credential is returned to the vehicle terminal to perform program login on the vehicle terminal.

17. The program login processing method for an in-vehicle terminal according to claim 13, wherein determining at least one program for program synchronous login in the in-vehicle terminal based on the tag data comprises: reading, based on the tag data, a plurality of candidate programs associated with the logged-in user and a login status of each candidate program; A candidate program whose login state is the unlogged-in state is determined as a program for program synchronous login.

18. The program login processing method of the vehicle terminal according to claim 13, further comprising: Acquire a candidate program whose login status is logged in as at least one program to be exited for program synchronous exit at the vehicle terminal; Returning the program identifier of the at least one program to be exited and the login account to the user terminal for synchronous exit authorization; According to the exit authorization instruction uploaded by the user terminal, the at least one program to be exited on the vehicle terminal is exited in conjunction with the program server.

19. The program login processing method for a vehicle terminal according to claim 18, wherein any of the at least one program to be exited is exited in the following manner, including: Querying the login credentials associated with the vehicle terminal identification and marking the login credentials as invalid; An exit reminder is issued to any of the programs to be exited, so that the program of any of the programs to be exited is exited at the vehicle terminal.

20. The program login processing method of the vehicle terminal according to claim 13, further comprising: The login account and driving preference information are sent to the vehicle service provider to which the vehicle belongs, so as to log in to the vehicle terminal based on the login account and perform driving configuration of the vehicle based on the driving preference information.

21. A program login processing device for a vehicle terminal, comprising: a tag data reading module, configured to read tag data stored in a near-field communication tag of a vehicle through near-field communication; an application startup module, configured to start an application based on the tag data, and pass the tag data to the application for uploading to a server; a receiving module configured to receive and display a program identifier and a login account of at least one program for program synchronization login on the vehicle terminal returned by the server; the at least one program includes a candidate program in a non-logged-in state among a plurality of candidate programs associated with the login user determined according to the tag data; The login authorization instruction uploading module is configured to upload the selected target program identifier and the login account to the server if a login authorization instruction is detected, so as to cooperate with the program access of the vehicle terminal to perform program login of the target program corresponding to the target program identifier.

22. A program login processing device for a vehicle terminal, comprising: a tag data acquisition module configured to acquire tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle; A program determination module is configured to determine at least one program for program synchronization login on the vehicle terminal based on the tag data; the at least one program includes a candidate program that is not logged in among multiple candidate programs associated with the logged-in user; a return module configured to return the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization; The program login module is configured to perform program login of the target program corresponding to the target program identifier according to the login account and the selected target program identifier uploaded by the user terminal, in combination with the program server and the program access of the vehicle terminal.

23. A user terminal, comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: Reading tag data stored in a near-field communication tag of a vehicle through near-field communication; Starting an application based on the tag data, and passing the tag data to the application for uploading to a server; receiving and displaying the program identifier and login account of at least one program for program synchronization login on the vehicle terminal returned by the server; The at least one program includes a candidate program in a non-logged-in state among a plurality of candidate programs associated with the logged-in user determined according to the tag data; If a login authorization instruction is detected, the selected target program identifier and the login account are uploaded to the server for program login of the target program corresponding to the target program identifier in conjunction with program access of the vehicle terminal.

24. A server comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: Obtain tag data uploaded by a user terminal and read from a near-field communication tag of a vehicle; Determining at least one program for program synchronization login on the vehicle terminal based on the tag data; the at least one program includes a candidate program in a non-logged-in state among a plurality of candidate programs associated with the logged-in user; Returning the login account of the logged-in user and the program identifier of the at least one program to the user terminal for synchronous login authorization; According to the login account and the selected target program identifier uploaded by the user terminal, the program server cooperates with the program access of the vehicle terminal to perform program login of the target program corresponding to the target program identifier.

25. A computer-readable storage medium for storing computer-executable instructions, wherein the computer-executable instructions implement the steps of the method of claim 1 or claim 13 when executed.

Images