Program registration processing method and device for car machine terminal

Abstract

The embodiment of the present specification provides a program login processing method and device of a vehicle terminal, wherein the program login processing method of the vehicle terminal comprises the following steps: reading label data stored in a near field communication label of a vehicle through near field communication, starting an application program based on the label data and inputting the label data to upload to a server, receiving and displaying program identification and login account of at least one program returned by the server for performing program synchronization login of the vehicle terminal, obtaining submitted login authorization instructions and uploading to the server, so as to cooperate with program access of the vehicle terminal to perform program login of the at least one program, thereby realizing program synchronization login of the vehicle terminal.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on April 16, 2025, with application number CN202510480547.4 and title "Program Login Processing Method and Apparatus for Vehicle Terminal". Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a method and apparatus for processing program login on a vehicle-mounted terminal. Background Technology

[0003] 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 extending to online scenarios. With the continuous development of near-field communication technology, various online services provided by the internet can be initiated or processed through near-field communication, which brings convenience to users and improves the user participation rate of online services. How to initiate and process services more flexibly based on near-field communication is an increasingly important focus for users and service providers. Summary of the Invention

[0004] This specification provides one or more embodiments of a method for processing program login on a vehicle-mounted terminal, including: reading tag data stored in a vehicle's near-field communication tag via near-field communication; launching an application based on the tag data and sending 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 that is synchronously logging in on the vehicle-mounted terminal, returned by the server; and obtaining and uploading a submitted login authorization instruction to the server to facilitate program login for the at least one program in conjunction with program access on the vehicle-mounted terminal.

[0005] This specification provides one or more embodiments of another method for processing program login on a vehicle-mounted terminal, including: acquiring tag data uploaded by a user terminal from a near-field communication tag read from a vehicle; determining at least one program for synchronous program login on the vehicle-mounted terminal based on the tag data; 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; and performing program login for the at least one program based on the login authorization instruction uploaded by the user terminal, in conjunction with a program server cooperating with the program access of the vehicle-mounted terminal.

[0006] This specification provides one or more embodiments of a vehicle-mounted terminal program login processing device, including: a tag data reading module configured to read tag data stored in a vehicle's near-field communication tag via near-field communication; an application launch module configured to launch 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 the program identifier and login account of at least one program performing program synchronization login on the vehicle-mounted terminal, returned by the server; and a login authorization instruction uploading module configured to obtain a submitted login authorization instruction and upload it to the server for use in conjunction with the vehicle-mounted terminal's program access for program login of the at least one program.

[0007] This specification provides one or more embodiments of another in-vehicle terminal program login processing apparatus, including: 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, based on the tag data, at least one program to be synchronously logged in on the in-vehicle terminal; 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; and a program login module configured to perform program login for the at least one program based on the login authorization instruction uploaded by the user terminal, in conjunction with a program server and program access on the in-vehicle terminal.

[0008] This specification provides one or more embodiments of a user terminal, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: read tag data stored in a vehicle's near-field communication (NFC) tag via NFC; launch an application based on the tag data; 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 that is performing program synchronization login on the vehicle terminal, returned by the server; and obtain and upload a submitted login authorization instruction to the server for program login of the at least one program in conjunction with program access on the vehicle terminal.

[0009] This specification provides one or more embodiments of a server, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire tag data uploaded by a user terminal from near-field communication tags read from a vehicle; determine, based on the tag data, at least one program for synchronized login on a vehicle-mounted 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 synchronized 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 the program server and program access on the vehicle-mounted terminal.

[0010] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions. When executed, these instructions perform the following process: reading tag data stored on a vehicle's near-field communication (NFC) tag via NFC; launching an application based on the tag data; 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 that is synchronously logged in on the vehicle's infotainment system, returned by the server; and obtaining and uploading a submitted login authorization instruction to the server to facilitate program login for the at least one program in conjunction with program access on the vehicle's infotainment system.

[0011] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions, which, when executed, perform the following process: acquiring tag data uploaded by a user terminal from a near-field communication tag read from a vehicle; determining, based on the tag data, at least one program for synchronized login on the vehicle-mounted 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 synchronized login authorization; and, based on the login authorization instruction uploaded by the user terminal, cooperating with the program server and the program access of the vehicle-mounted terminal to perform program login for the at least one program. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 A schematic diagram illustrating the implementation environment of a program login processing method for a vehicle terminal provided in one or more embodiments of this specification; Figure 2A flowchart illustrating a method for processing program login on a vehicle-mounted terminal, provided for one or more embodiments of this specification. Figure 3 A schematic diagram of a login authorization page provided for one or more embodiments of this specification; Figure 4 This specification provides a timing diagram for a method of subroutine login processing for a vehicle terminal, which is applied to a subroutine login processing scenario, according to one or more embodiments of this specification. Figure 5 A flowchart illustrating another method for processing program login on a vehicle terminal, provided in one or more embodiments of this specification. 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; Figure 7 A schematic diagram of another embodiment of a vehicle terminal program login processing device provided in one or more embodiments of this specification; Figure 8 This specification provides a schematic diagram of the structure of a user terminal according to one or more embodiments. Figure 9 This is a schematic diagram of the structure of a server provided for one or more embodiments of this specification. Detailed Implementation

[0013] 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 with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0014] The vehicle terminal program login processing method provided in one or more embodiments of this specification is applicable to the implementation environment of synchronous program login on vehicle terminals. (Refer to...) Figure 1 The implementation environment includes at least: user terminal 101, vehicle near-field communication tag 102, server 103, and vehicle terminal 104. The user terminal 101 is used to read the tag data stored in the near-field communication tag 102 of the vehicle through near-field communication, and to cooperate with the server 103 through the application to perform synchronous login authorization. After obtaining the login authorization instruction, it uploads it to the server 103 to cooperate with the program access of the vehicle terminal 104 to perform program login for at least one program. The user terminal 101 can be a mobile phone, personal computer, tablet computer, e-book reader, VR (Virtual Reality) based information interaction device, vehicle terminal, IoT device, wearable smart device, laptop computer and desktop computer, etc. Server 103 is used to return the login account of the logged-in user and the program identifier of at least one program that performs program synchronization login on the vehicle terminal to the user terminal based on the tag data uploaded by the user terminal 101, so as to cooperate with the user terminal 101 to perform synchronization login authorization, and to obtain the login authorization instruction uploaded by the user terminal 101, so as to cooperate with the program access of the vehicle terminal 104 to perform program login of at least one program; server 103 can be a single server, or a server cluster consisting of several servers, or one or more cloud servers in a cloud computing platform; In addition, the implementation environment may also include a program server 105, which includes a program server for performing program synchronization login, used to perform program login in conjunction with the program access of the vehicle terminal 104 in conjunction with the server 103; the program server 105 may be a single server, or a server cluster consisting of several servers, or one or more cloud servers in a cloud computing platform. In this implementation environment, user terminal 101 reads the tag data stored in the vehicle's near-field communication tag 102 via near-field communication, launches the application based on the tag data, and sends the tag data to the application for uploading to server 103. After obtaining the tag data, server 103 returns the login account of the logged-in user and the program identifier of at least one program that is synchronously logged in on vehicle terminal 104 to user terminal 101 based on the tag data. User terminal 101 receives and displays the login account and program identifier, obtains the login authorization instruction, and uploads it to server 103. Server 103, based on the login authorization instruction and in conjunction with program server 105, performs program login processing in cooperation with program access on vehicle terminal 104, thereby realizing synchronous program login on vehicle terminal.

[0015] This specification provides one or more embodiments of a program login processing method for a vehicle-mounted terminal, as follows: Reference Figure 2 The vehicle terminal program login processing method provided in this embodiment specifically includes steps S202 to S208.

[0016] Step S202: Read the tag data stored in the vehicle's near-field communication tag via near-field communication.

[0017] This embodiment can configure a near-field communication (NFC) component in the user terminal to connect with other devices via NFC, and configure a NFC tag on the vehicle to establish a NFC connection between the NFC component of the user terminal and the NFC tag of the vehicle, and then read the tag data stored in the NFC tag of the vehicle through the NFC connection. In addition to NFC, it can also be Bluetooth communication, wireless network communication, infrared communication and / or radio frequency communication. Correspondingly, the NFC 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 NFC tag of the vehicle can be a Bluetooth component, wireless component, infrared component or radio frequency communication component.

[0018] In practice, the user terminal reads the tag data stored in the vehicle's near-field communication tag via near-field communication. During execution, the user terminal can establish a near-field communication connection with the vehicle's near-field communication tag through its near-field communication component. Based on the established near-field communication connection, the user terminal reads the tag data stored in the vehicle's near-field communication tag through the near-field communication connection. In addition to reading the tag data stored in the vehicle's near-field communication tag via near-field communication, the user terminal can also receive tag data sent by the vehicle's near-field communication tag via near-field communication.

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

[0020] In the specific execution process of a user terminal reading tag data stored in a vehicle's near-field communication tag via near-field communication, the user terminal can invoke near-field communication for detection. After detecting a near-field communication tag, it establishes a near-field communication connection with the tag and then reads the stored tag data from it. Alternatively, the vehicle's near-field communication tag can be used for detection. After detecting the user terminal's near-field communication component, it establishes a near-field communication connection with the component and then sends the stored tag data to it.

[0021] Step S204: Launch the application based on the tag data and pass the tag data to the application to upload it to the server.

[0022] In practice, after reading the tag data stored in the vehicle's near-field communication tag through near-field communication, the application is launched based on the tag data to upload the tag data to the server. During the process of launching the application based on the tag data, the user terminal can parse the tag data to obtain the parsing result, which may include the tag identifier, program identifier and / or program address. Then, according to the parsing result, the corresponding application in the user terminal's installed application list is launched. After launching the application 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 the tag identifier, program identifier and / or program address as tag data. In addition, only part of the tag data can be passed to the application, such as the tag identifier in the tag data.

[0023] Step S206: Receive and display the program identifier and login account of at least one program that has performed program synchronization login on the vehicle terminal, returned by the server.

[0024] In specific implementation, the user terminal launches the application based on the tag data and transmits the tag data, then uploads the tag data to the server through the application. Correspondingly, the server obtains the tag data read from the vehicle's near-field communication tag uploaded by the user terminal. 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 synchronous login is based on the login user's login account, but the login account and the program used for login often involve the login user's privacy, authorization from the login user is required. Therefore, after determining at least one program for synchronous login on the vehicle terminal based on the tag data, the server cooperates with the user terminal to perform synchronous login authorization for 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 at least one program on the vehicle terminal based on the login account. That is, step S206 can be replaced by performing synchronous login authorization for at least one program on the vehicle terminal based on the login account through the cooperation of the application and the server, and forming a new implementation method with one or more other processing steps provided in this embodiment.

[0025] The synchronized login process includes logging into at least one program simultaneously or in parallel. In this embodiment, the server 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 subroutine running on a host program, where the host program can be installed on the vehicle terminal; the host program can be a lightweight container carrying at least one subroutine. In this embodiment, the host program can be provided by the application service provider, meaning the host program can correspond to the server.

[0026] In practical applications, the program can be provided by a program service provider, i.e., a third party. Program login requires execution by the program server. In this case, to enhance the trustworthiness of the program service provider and ensure the program server cooperates in synchronous login on the vehicle terminal, this embodiment can pre-interact with the program server to obtain the authorization result submitted by the program server. Based on the authorization result, the program server's calling interface is configured to achieve data transmission with the program server through the calling interface. In addition, vehicle information, the logged-in user, and the program identifier of the authorized program can be associated to represent the relationship between the vehicle, user, and program. Specifically, if vehicle information entered by the logged-in user through the application's vehicle subroutine is obtained, an association is established between the vehicle information and the logged-in user, and the program that authorizes the vehicle type in that vehicle information is associated with the logged-in user.

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

[0028] In practical implementation, to improve the efficiency of synchronized login and avoid secondary login when the vehicle terminal has already logged into some programs associated with the logged-in user, this embodiment allows the programs for synchronized login to include programs associated with the logged-in user that are not currently logged in. In one optional implementation of this embodiment, the programs for synchronized login are determined in the following way: Based on the tag data, read the multiple candidate programs associated with the logged-in user and the login status of each candidate program; Candidate programs that are not logged in are selected as programs for program synchronization login.

[0029] Optionally, the tag data may also include vehicle type, vehicle terminal identifier, and / or vehicle identifier. The vehicle identifier can be a unique identifier representing the vehicle, such as the vehicle identification number (VIN) or vehicle hardware device number.

[0030] Specifically, based on the vehicle type carried by 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 programs that are not logged in can be identified as the programs that will be logged in synchronously.

[0031] 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, it reads the associated programs as candidate programs and reads the login status of each candidate program. The candidate program with the login status of not logged in is determined as the program to perform program synchronization login.

[0032] In addition, the login user can be associated with the program only. In this way, when determining at least one program to perform synchronous login, it is not necessary to determine the vehicle type carried by the tag data. That is, after the server obtains the tag data uploaded by the user terminal and reads it from the vehicle's near-field communication tag, it responds to the tag data to determine at least one program to perform synchronous login on the vehicle terminal.

[0033] Based on the identification of at least one program that performs synchronous 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 that performs synchronous login on the vehicle terminal returned by the server. In this embodiment, the login account includes the login user's account for logging into 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 login user's instant messaging identifier.

[0034] In specific implementation, to enhance the logged-in user's awareness of the program identifier and login account of at least one displayed program, the system receives and displays the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server. During the display process, to enhance the logged-in user's awareness of the vehicle, a login authorization page can be generated and displayed based on the program identifier, login account, and vehicle type carried by the tag data. In an optional implementation of this embodiment, after the user terminal receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server, it displays the information in the following manner: Generate a login authorization list based on the program identifier and login account; Based on the vehicle type carried by the login authorization list and tag data, generate and display the login authorization page.

[0035] In the specific execution process, the system receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal from the server. Based on the program identifier and login account, a login authorization list is generated. Based on the login authorization list and the vehicle type carried by the tag data, a login authorization page is generated and displayed.

[0036] For example, such as Figure 3 The login authorization page shown displays a login authorization list 301, which includes payment programs, vehicle programs, and music programs. To enhance the login user's awareness of their login account, the user's communication identifier "111xxxxxxxx" can be configured after each program. In addition, the login authorization page also displays vehicle types and confirmation controls, allowing the user to submit login authorization commands through the confirmation controls.

[0037] In addition to receiving and displaying the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server, it can also receive and display the program identifier, configuration items, and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server. 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. For example, such as Figure 3 In the login authorization list 301 shown on the login authorization page, the configuration items for the payment program include service settings and payment settings; the configuration items for the vehicle program include intelligent driving settings and in-vehicle hardware settings; and the configuration items for the music program include My Playlists. That is, step S206 can be replaced by receiving and displaying the program data and login account of at least one program that has performed 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 program identifiers and configuration items.

[0038] It should be noted that the program's configuration items 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 that is synchronously logged in 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 synchronous login authorization.

[0039] In addition to synchronous login authorization through the cooperation of the application and the server to synchronously log in to 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 synchronously log in to at least one program on the vehicle terminal. In this case, steps S204 to S206 can also be replaced by launching the application based on the tag data, passing the tag data to the application, and 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 with one or more other processing steps provided in this embodiment.

[0040] Step S208: Obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal for program login of at least one program.

[0041] In specific implementation, during the synchronous login authorization process of at least one program on the vehicle terminal based on the login account, the application and the server cooperate to receive and display the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, and then obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal to log in to at least one program.

[0042] In the specific implementation process, logged-in users can select all programs for synchronized login based on the login authorization page, or they can select some programs for synchronized login. This allows logged-in users to flexibly choose programs for synchronized login based on the awareness that at least one program can be logged in simultaneously, improving the user's awareness of the program synchronization login based on near-field communication. In one optional implementation of this embodiment, during 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 the program access of the vehicle terminal, if a 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 the program access of the vehicle terminal.

[0043] In addition, logged-in users can configure the program based on the program data and the login account displayed, and obtain the program configuration information. Therefore, during the upload process to the server, a login authorization command carrying the program configuration information of the target program can be uploaded to the server. That is, the login authorization command can carry the program configuration information of the target program, and the program configuration information can be obtained by entering configuration information based on the configuration items of the displayed target program.

[0044] Specifically, if a login authorization command is detected, the system reads the selected target program identifier and the program configuration information entered based on the target program's configuration items; it then uploads the target program identifier, the program configuration information, and the login account to the server. This allows users to not only select the target program for synchronized login through the login authorization page, but also to personalize the selected target program.

[0045] In practice, the user terminal obtains the submitted login authorization instruction and submits it to the server to cooperate with the vehicle terminal's program access for at least one program login. Correspondingly, the server, based on the login authorization instruction uploaded by the user terminal, combines the program server with the vehicle terminal's program access to process the login of at least one program. In the specific execution process, the server, in conjunction with the program server, coordinates with the program access of the vehicle-mounted terminal to log in to at least one program. Specifically, this can be achieved by synchronously sending the vehicle-mounted terminal identifier and login account to the program servers of each program within the at least one program, thereby coordinating with the program access of the vehicle-mounted terminal and enabling synchronous program login on the vehicle-mounted terminal. In an optional implementation of this embodiment, the server performs the following operations during the process of coordinating with the program access of the vehicle-mounted terminal to log in to at least one program: Read the vehicle terminal identifier carried by the tag data, or query the vehicle terminal identifier associated with the tag identifier; Send the login account and vehicle terminal identifier to the program server of each program to facilitate program login for the vehicle terminal.

[0046] During this process, the program on the vehicle terminal may or may not be in an access state. The program server cooperates with the program access of the vehicle terminal to log in to the program. This can be done by responding to the program access command submitted by the vehicle terminal, or by first performing a background login and then logging in to the program after detecting the program access command. The following will provide a detailed explanation of the program login performed by the program server in cooperation with the program access of the vehicle terminal in these two cases.

[0047] (1) In specific implementation, after receiving the login account and vehicle terminal identifier sent by the server, any program server can first perform background login. If it detects that the vehicle terminal corresponding to the vehicle terminal identifier has submitted a program access instruction for the corresponding program, it returns the login credentials obtained from 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 identifier. If it detects that the vehicle terminal corresponding to the vehicle terminal identifier has submitted a program access instruction, it returns the login credentials to the vehicle terminal to perform program login on the vehicle terminal.

[0048] In one optional implementation of this embodiment, the process of program server cooperating with the vehicle terminal for program login is implemented in the following way: Login credentials are generated based on the login account, and the login credentials are associated with and stored with the vehicle terminal identifier; If a program access command is detected, the login credentials are read based on the vehicle terminal identifier carried in the program access command and returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0049] During the actual execution process, after receiving the login account and vehicle terminal identifier sent by the server, the program server generates a login credential based on the login account. In order to determine the vehicle terminal that the login credential can be used for, the login credential is associated with the vehicle terminal identifier and stored. Thus, if a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the login credential associated with the vehicle terminal identifier is returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0050] (2) In specific implementation, the program server can also first store the received login account and vehicle terminal identifier. If the program access instruction uploaded by the vehicle terminal is detected, the program login of the vehicle terminal is performed based on the login account and vehicle terminal identifier. That is, the program server receives and stores the login account and vehicle terminal identifier. If the program access instruction submitted by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the background login and program login on the vehicle terminal are performed based on the login account and vehicle terminal identifier.

[0051] In one optional implementation of this embodiment, the process of program server cooperating with the vehicle terminal for program login is implemented in the following way: The login account and the vehicle terminal identifier are associated and stored together; Read the login account associated with the vehicle terminal identifier carried in the program access command uploaded by the vehicle terminal, and generate login credentials based on the login account; The login credentials are associated with and stored with the vehicle terminal identifier, and the login credentials are returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0052] During the execution process, after receiving the login account and vehicle terminal identifier sent by the server, the program server first associates and stores the login account and vehicle terminal identifier. If a program access command uploaded by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the login account associated with the vehicle terminal identifier carried in the access command is read, and a login credential is generated based on the login account. After obtaining the login credential, on the one hand, the login credential is associated and stored with the vehicle terminal identifier to complete the background login. On the other hand, the login credential is returned to the vehicle terminal to perform program login on the vehicle terminal.

[0053] In addition to the two methods mentioned above for program login in conjunction with the vehicle terminal, the program server can also generate login credentials based on the login account during the program login process in conjunction with the vehicle terminal, 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. In other words, the server and the program server cooperate to perform program login on the vehicle terminal based on the login account.

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

[0055] Furthermore, to enhance the user's awareness of the login process on the vehicle-mounted terminal, the login process can be configured based on the user's configuration information from the user's terminal. In practice, the user terminal can configure the target program and upload the configuration information to the target program server. The target program server then configures the target program running on the vehicle-mounted terminal according to the configuration information. Specifically, when the program server returns login credentials to the vehicle-mounted terminal, it can read the program configuration information associated with the login account and return both the login credentials and the configuration information to the terminal. The program configuration information associated with the login account can be obtained by the user logging into the program on the user terminal or other terminal devices and configuring the program, or it can be obtained by the user entering configuration information based on configuration items during the synchronous login authorization process, as sent by the server. This embodiment does not limit the specific details.

[0056] In addition to synchronizing the login of the vehicle terminal's program based on near-field communication, it can also synchronize the exit of the vehicle terminal's program based on near-field communication.

[0057] In practice, after the user terminal sends tag data to the application for uploading to the server, if it receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal from the server, a login authorization page is generated and displayed. Optionally, the at least one program that is synchronously logged in can be a candidate program that is not logged in. In addition, for candidate programs that are already logged in, synchronous exit can be performed to improve the efficiency of program exit.

[0058] In one optional implementation of this embodiment, if the server returns the program identifier and login account of at least one program to be exited on the vehicle terminal for synchronous program exit, then 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 at least one program to be exited on the vehicle terminal. Correspondingly, the server obtains candidate programs with a logged-in status as at least one program to be exited on the vehicle terminal for synchronous program exit, returns the program identifier and login account of at least one program to be exited to the user terminal for synchronous exit authorization, and, based on the exit authorization instruction uploaded by the user terminal and in conjunction with the program server, exits at least one program on the vehicle terminal. The program to be exited is exited; further, in an optional implementation of 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 can send a program exit reminder containing the login account and 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.

[0059] 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 described above, and can be referred to the relevant content above. This embodiment does not limit it here.

[0060] In addition to logging into the application through the user's login account and accessing the vehicle terminal's program to synchronize login with at least one program associated with the user, this embodiment can also log into the vehicle terminal based on the login account via near-field communication. This improves the convenience of logging into the vehicle terminal. Specifically, the user terminal sends tag data to the application for uploading to the server. Correspondingly, in an optional implementation of this embodiment, the server sends the login account and driving preference information to the vehicle's service provider based on the tag data, so as to log into the vehicle terminal based on the login account and configure the vehicle's driving based on the driving preference information.

[0061] In practice, the server can store the driving preference information of logged-in users. After receiving the tag data uploaded by the user's 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 associated driving preference information to the vehicle service provider. This allows the user to log in to the vehicle terminal based on the login account and configure the vehicle's driving settings based on the driving preference information. To improve the vehicle service provider's awareness of the logged-in vehicle terminal, a vehicle terminal identifier can also be sent to the vehicle service provider, allowing login to the vehicle terminal corresponding to the identifier based on the login account.

[0062] Based on the synchronized 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.

[0063] 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 forming 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 forming a new implementation method with one or more other processing steps provided in this embodiment.

[0064] In summary, the method for processing program login for one or more vehicle-mounted terminals provided in this embodiment enables synchronous program login for at least one program on the vehicle-mounted terminal by configuring a near-field communication tag in the vehicle and establishing a near-field communication connection between the user terminal of the logged-in user and the near-field communication tag, based on the logged-in user's login account. Thus, by placing the user terminal at the location of the near-field communication tag in the vehicle and through a single authorization process, at least one program can be logged in synchronously on the vehicle-mounted terminal, improving the convenience and efficiency of program login. In this process, the user terminal reads the tag data stored in the vehicle's near-field communication tag via near-field communication, launches the application based on the tag data, and sends the tag data to the application for uploading to the server. The server, based on the tag data read from the vehicle's near-field communication tag uploaded by the user terminal, determines at least one program for synchronized login on the vehicle's infotainment system. It then returns the user's login account 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 synchronized login on the vehicle's infotainment system returned by the server. Based on the program identifier, login account, and vehicle type carried in the tag data, it generates and displays a login authorization page. If a login authorization command is obtained, it uploads it to the server. The server, based on the login authorization command uploaded by the user terminal and the program server, performs synchronized login for at least one program on the vehicle's infotainment system based on the login account. This enables convenient and efficient program login on the vehicle's infotainment system via near-field communication, even when driving or riding in different vehicles, improving the flexibility and convenience of program login on the vehicle's infotainment system.

[0065] Steps S202 to S208 provided in this embodiment can be executed by a user terminal. It should be noted that the steps S202 to S208 executed by the user terminal and steps S502 to S508 executed by the server in the following embodiment can cooperate with each other during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S502 to S508 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S202 to S208 provided in this embodiment.

[0066] The following description uses the application of the vehicle terminal program login processing method provided in this embodiment in the subroutine login processing scenario of the vehicle terminal as an example to further illustrate the program login processing method of the vehicle terminal provided in this embodiment. Figure 4 As shown, the method for processing the program login of a vehicle terminal in a subroutine login scenario applied to the vehicle terminal includes the following steps.

[0067] Step S402: Read the tag data stored in the vehicle's near-field communication tag via near-field communication connection.

[0068] Step S404: Start the application based on the tag data and pass the tag data to the application for uploading to the server.

[0069] Step S410: Receive the subroutine identifier and login account of at least one subroutine that performs program synchronization login on the vehicle terminal, returned by the server.

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

[0071] Step S414: Obtain the login authorization instruction submitted by the logged-in user through the login authorization page.

[0072] Step S416: Upload the login authorization command to the server.

[0073] Steps S402 to S404 and S410 to S416 provided in this embodiment are executed by the user terminal. It should be noted that the steps S402 to S404 and S410 to S416 executed by the user terminal can cooperate with steps S406 to S408 and S418 to S420 executed by the server in the following embodiment. Therefore, when reading this embodiment, please refer to the corresponding content of steps S406 to S408 and S418 to S420 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S402 to S404 and S410 to S416 provided in this embodiment.

[0074] It should be noted that any one or more steps in steps S402 to S420 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S402 to S420 can be selected and combined with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S402 to S420 can be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0075] One or more embodiments of another method for processing program login on a vehicle-mounted terminal provided in this specification are as follows: Reference Figure 5 The vehicle terminal program login processing method provided in this embodiment specifically includes steps S502 to S508.

[0076] Step S502: Obtain tag data uploaded by the user terminal from the near-field communication tag of the vehicle.

[0077] In this embodiment, a near-field communication (NFC) component can be configured on the user terminal to establish a NFC connection with the vehicle's NFC tag, thereby reading the tag data stored on the vehicle's NFC tag. In addition to NFC, it can also be Bluetooth communication, wireless network communication, infrared communication, and / or radio frequency communication. Correspondingly, the NFC 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 NFC tag can be a Bluetooth component, wireless component, infrared component, or radio frequency communication component.

[0078] In practice, the user terminal reads the tag data stored in the vehicle's near-field communication tag via near-field communication. During execution, the user terminal can establish a near-field communication connection with the vehicle's near-field communication tag through its near-field communication component, and then read the tag data stored in the vehicle's near-field communication tag through this connection. In addition to reading the tag data stored in the vehicle's near-field communication tag via near-field communication, the user terminal can also receive tag data sent by the vehicle's near-field communication tag via near-field communication.

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

[0080] In 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, it can either call the near-field communication for detection, establish a near-field communication connection with the near-field communication tag after detecting the near-field communication tag, and then read the stored tag data from the near-field communication tag; or the vehicle's near-field communication tag can perform detection, establish a near-field communication connection with the near-field communication component after detecting the user terminal's near-field communication component, and then send the stored tag data to the near-field communication component.

[0081] In practice, after reading the tag data stored in the vehicle's near-field communication tag through near-field communication, the application is launched based on the tag data to upload the tag data to the server. During the process of launching the application based on the tag data, the user terminal can parse the tag data to obtain the parsing result, which may include the tag identifier, program identifier and / or program address. Then, according to the parsing result, the corresponding application in the user terminal's installed application list is launched. After launching the application 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 the tag identifier, program identifier and / or program address as tag data. In addition, only part of the tag data can be passed to the application, such as the tag identifier in the tag data.

[0082] Step S504: Based on the tag data, determine at least one program that performs program synchronization login on the vehicle terminal.

[0083] In practice, the user terminal launches an application based on tag data and transmits the tag data, then uploads the tag data to the server through the application. Correspondingly, the server obtains the tag data uploaded by the user terminal from the vehicle's near-field communication tag. After obtaining the tag data, the server determines at least one program for synchronized login on the vehicle's infotainment system. Since synchronized login is based on the user's login account, and the login account and the program used for login often involve the user's privacy, authorization from the user is required. Therefore, after determining at least one program for synchronized login on the vehicle's infotainment system based on the tag data, the server cooperates with the user terminal to authorize synchronized login for at least one program on the vehicle's infotainment system based on the login account. Similarly, after the application uploads the tag data to the server, the user terminal, through the application, cooperates with the server to authorize synchronized login for at least one program on the vehicle's infotainment system based on the login account.

[0084] The synchronized login process includes logging into at least one program simultaneously or in parallel. In this embodiment, the server includes an application server, where the application may be a payment application. In this embodiment, at least one program may be an application running independently on the vehicle terminal; furthermore, at least one program may be a subroutine running on a host program, where the host program may be installed on the vehicle terminal.

[0085] In practical applications, the program can be provided by a program service provider, i.e., a third party. Program login requires execution by the program server. In this case, to enhance the trustworthiness of the program service provider and ensure the program server cooperates in synchronous login on the vehicle terminal, this embodiment can pre-interact with the program server to obtain the authorization result submitted by the program server. Based on the authorization result, the program server's calling interface is configured to achieve data transmission with the program server through the calling interface. In addition, vehicle information, the logged-in user, and the program identifier of the authorized program can be associated to represent the relationship between the vehicle, user, and program. Specifically, if vehicle information entered by the logged-in user through the application's vehicle subroutine is obtained, an association is established between the vehicle information and the logged-in user, and the program that authorizes the vehicle type in that vehicle information is associated with the logged-in user.

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

[0087] In practical implementation, to improve the efficiency of synchronized login and avoid secondary login when the vehicle terminal has already logged into some programs associated with the logged-in user, this embodiment allows the programs for synchronized login to include programs associated with the logged-in user that are not currently logged in. In one optional implementation of this embodiment, the programs for synchronized login are determined in the following way: Based on the tag data, read the multiple candidate programs associated with the logged-in user and the login status of each candidate program; Candidate programs that are not logged in are selected as programs for program synchronization login.

[0088] Optionally, the tag data may also include vehicle type, vehicle terminal identifier, and / or vehicle identifier. The vehicle identifier can be a unique identifier representing the vehicle, such as the vehicle identification number (VIN) or vehicle hardware device number.

[0089] Specifically, based on the vehicle type carried by 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 programs that are not logged in can be identified as the programs that will be logged in synchronously.

[0090] 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, it reads the associated programs as candidate programs and reads the login status of each candidate program. The candidate program with the login status of not logged in is determined as the program to perform program synchronization login.

[0091] In addition, the login user can be associated with the program only. In this way, when determining at least one program to perform synchronous login, it is not necessary to determine the vehicle type carried by the tag data. That is, after the server obtains the tag data uploaded by the user terminal and reads it from the vehicle's near-field communication tag, it responds to the tag data to determine at least one program to perform synchronous login on the vehicle terminal.

[0092] 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.

[0093] Based on the identification of at least one program that performs synchronous 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 that performs synchronous login on the vehicle terminal returned by the server. In this embodiment, the login account includes the login user's account for logging into 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 login user's instant messaging identifier.

[0094] In specific implementation, to enhance the logged-in user's awareness of the program identifier and login account of at least one displayed program, the system receives and displays the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server. During the display process, to enhance the logged-in user's awareness of the vehicle, a login authorization page can be generated and displayed based on the program identifier, login account, and vehicle type carried by the tag data. In an optional implementation of this embodiment, after the user terminal receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server, it displays the information in the following manner: Generate a login authorization list based on the program identifier and login account; Based on the vehicle type carried by the login authorization list and tag data, generate and display the login authorization page.

[0095] In the specific execution process, the system receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal from the server. Based on the program identifier and login account, a login authorization list is generated. Based on the login authorization list and the vehicle type carried by the tag data, a login authorization page is generated and displayed.

[0096] For example, such as Figure 3 The login authorization page shown displays a login authorization list 301, which includes payment programs, vehicle programs, and music programs. To enhance the login user's awareness of their login account, the user's communication identifier "111xxxxxxxx" can be configured after each program. In addition, the login authorization page also displays vehicle types and confirmation controls, allowing the user to submit login authorization commands through the confirmation controls.

[0097] In addition to receiving and displaying the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server, it can also receive and display the program identifier, configuration items, and login account of at least one program that is synchronously logged in on the vehicle terminal, returned by the server. 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. For example, such as Figure 3 The login authorization list 301 on the login authorization page shows that the configuration items for the payment program include service settings and payment devices; the configuration items for the vehicle program include intelligent driving settings and in-vehicle hardware settings; and the configuration items for the music program include my playlists.

[0098] It should be noted that the program's configuration items 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 that is synchronously logged in 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 synchronous login authorization.

[0099] In addition to synchronous login authorization based on login account for at least one program on the vehicle terminal through the cooperation of the application and the server, the program identifier of at least one program can also be added to the tag data to enable the application to synchronously log in to at least one program on the vehicle terminal.

[0100] Step S508: Based on the login authorization instruction uploaded by the user terminal, and in conjunction with the program server and the program access of the vehicle terminal, perform program login for at least one program.

[0101] In specific implementation, during the synchronous login authorization process of at least one program on the vehicle terminal based on the login account, the application and the server cooperate to receive and display the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal, and then obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal to log in to at least one program.

[0102] In the specific implementation process, logged-in users can select all programs for synchronized login based on the login authorization page, or they can select some programs for synchronized login. This allows logged-in users to flexibly choose programs for synchronized login based on the awareness that at least one program can be logged in simultaneously, improving the user's awareness of the program synchronization login based on near-field communication. In one optional implementation of this embodiment, during 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 the program access of the vehicle terminal, if a 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 the program access of the vehicle terminal.

[0103] In addition, logged-in users can configure the program based on the program data and the login account displayed, and obtain the program configuration information. Therefore, during the upload process to the server, a login authorization command carrying the program configuration information of the target program can be uploaded to the server. That is, the login authorization command can carry the program configuration information of the target program, and the program configuration information can be obtained by entering configuration information based on the configuration items of the displayed target program.

[0104] Specifically, if a login authorization command is detected, the system reads the selected target program identifier and the program configuration information entered based on the target program's configuration items; it then uploads the target program identifier, the program configuration information, and the login account to the server. This allows users to not only select the target program for synchronized login through the login authorization page, but also to personalize the selected target program.

[0105] In practice, the user terminal obtains the submitted login authorization instruction and submits it to the server to cooperate with the vehicle terminal's program access for at least one program login. Correspondingly, the server, based on the login authorization instruction uploaded by the user terminal, combines the program server with the vehicle terminal's program access to process the login of at least one program. In the specific execution process, the server, in conjunction with the program server, coordinates with the program access of the vehicle-mounted terminal to log in to at least one program. Specifically, this can be achieved by synchronously sending the vehicle-mounted terminal identifier and login account to the program servers of each program within the at least one program, thereby coordinating with the program access of the vehicle-mounted terminal and enabling synchronous program login on the vehicle-mounted terminal. In an optional implementation of this embodiment, the server performs the following operations during the process of coordinating with the program access of the vehicle-mounted terminal to log in to at least one program: Read the vehicle terminal identifier carried by the tag data, or query the vehicle terminal identifier associated with the tag identifier; Send the login account and vehicle terminal identifier to the program server of each program to facilitate program login for the vehicle terminal.

[0106] During this process, the program on the vehicle terminal may or may not be in an access state. The program server cooperates with the program access of the vehicle terminal to log in to the program. This can be done by responding to the program access command submitted by the vehicle terminal, or by first performing a background login and then logging in to the program after detecting the program access command. The following will provide a detailed explanation of the program login performed by the program server in cooperation with the program access of the vehicle terminal in these two cases.

[0107] (1) In specific implementation, after receiving the login account and vehicle terminal identifier sent by the server, any program server can first perform background login. If it detects that the vehicle terminal corresponding to the vehicle terminal identifier has submitted a program access instruction for the corresponding program, it returns the login credentials obtained from 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 identifier. If it detects that the vehicle terminal corresponding to the vehicle terminal identifier has submitted a program access instruction, it returns the login credentials to the vehicle terminal to perform program login on the vehicle terminal.

[0108] In one optional implementation of this embodiment, the process of program server cooperating with the vehicle terminal for program login is implemented in the following way: Login credentials are generated based on the login account, and the login credentials are associated with and stored with the vehicle terminal identifier; If a program access command is detected, the login credentials are read based on the vehicle terminal identifier carried in the program access command and returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0109] During the actual execution process, after receiving the login account and vehicle terminal identifier sent by the server, the program server generates a login credential based on the login account. In order to determine the vehicle terminal that the login credential can be used for, the login credential is associated with the vehicle terminal identifier and stored. Thus, if a program access instruction uploaded by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the login credential associated with the vehicle terminal identifier is returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0110] (2) In specific implementation, the program server can also first store the received login account and vehicle terminal identifier. If the program access instruction uploaded by the vehicle terminal is detected, the program login of the vehicle terminal is performed based on the login account and vehicle terminal identifier. That is, the program server receives and stores the login account and vehicle terminal identifier. If the program access instruction submitted by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the background login and program login on the vehicle terminal are performed based on the login account and vehicle terminal identifier.

[0111] In one optional implementation of this embodiment, the process of program server cooperating with the vehicle terminal for program login is implemented in the following way: The login account and the vehicle terminal identifier are associated and stored together; Read the login account associated with the vehicle terminal identifier carried in the program access command uploaded by the vehicle terminal, and generate login credentials based on the login account; The login credentials are associated with and stored with the vehicle terminal identifier, and the login credentials are returned to the vehicle terminal to log in to the program on the vehicle terminal.

[0112] During the execution process, after receiving the login account and vehicle terminal identifier sent by the server, the program server first associates and stores the login account and vehicle terminal identifier. If a program access command uploaded by the vehicle terminal corresponding to the vehicle terminal identifier is detected, the login account associated with the vehicle terminal identifier carried in the access command is read, and a login credential is generated based on the login account. After obtaining the login credential, on the one hand, the login credential is associated and stored with the vehicle terminal identifier to complete the background login. On the other hand, the login credential is returned to the vehicle terminal to perform program login on the vehicle terminal.

[0113] In addition to the two methods mentioned above for program login in conjunction with the vehicle terminal, the program server can also generate login credentials based on the login account during the program login process in conjunction with the vehicle terminal, 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. In other words, the server and the program server cooperate to perform program login on the vehicle terminal based on the login account.

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

[0115] Furthermore, to enhance the user's awareness of the login process on the vehicle-mounted terminal, the login process can be configured based on the user's configuration information from the user's terminal. In practice, the user terminal can configure the target program and upload the configuration information to the target program server. The target program server then configures the target program running on the vehicle-mounted terminal according to the configuration information. Specifically, when the program server returns login credentials to the vehicle-mounted terminal, it can read the program configuration information associated with the login account and return both the login credentials and the configuration information to the terminal. The program configuration information associated with the login account can be obtained by the user logging into the program on the user terminal or other terminal devices and configuring the program, or it can be obtained by the user entering configuration information based on configuration items during the synchronous login authorization process, as sent by the server. This embodiment does not limit the specific details.

[0116] In addition to synchronizing the login of the vehicle terminal's program based on near-field communication, it can also synchronize the exit of the vehicle terminal's program based on near-field communication.

[0117] In practice, after the user terminal sends tag data to the application for uploading to the server, if it receives the program identifier and login account of at least one program that is synchronously logged in on the vehicle terminal from the server, a login authorization page is generated and displayed. Optionally, the at least one program that is synchronously logged in can be a candidate program that is not logged in. In addition, for candidate programs that are already logged in, synchronous exit can be performed to improve the efficiency of program exit.

[0118] In one optional implementation of this embodiment, if the server returns the program identifier and login account of at least one program to be exited on the vehicle terminal for synchronous program exit, then 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 at least one program to be exited on the vehicle terminal. Correspondingly, the server obtains candidate programs with a logged-in status as at least one program to be exited on the vehicle terminal for synchronous program exit, returns the program identifier and login account of at least one program to be exited to the user terminal for synchronous exit authorization, and, based on the exit authorization instruction uploaded by the user terminal and in conjunction with the program server, exits at least one program on the vehicle terminal. The program to be exited is exited; further, in an optional implementation of 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 can send a program exit reminder containing the login account and 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.

[0119] 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 described above, and can be referred to the relevant content above. This embodiment does not limit it here.

[0120] In addition to logging into the application through the user's login account and accessing the vehicle terminal's program to synchronize login with at least one program associated with the user, this embodiment can also log into the vehicle terminal based on the login account via near-field communication. This improves the convenience of logging into the vehicle terminal. Specifically, the user terminal sends tag data to the application for uploading to the server. Correspondingly, in an optional implementation of this embodiment, the server sends the login account and driving preference information to the vehicle's service provider based on the tag data, so as to log into the vehicle terminal based on the login account and configure the vehicle's driving based on the driving preference information.

[0121] In practice, the server can store the driving preference information of logged-in users. After receiving the tag data uploaded by the user's 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 associated driving preference information to the vehicle service provider. This allows the user to log in to the vehicle terminal based on the login account and configure the vehicle's driving settings based on the driving preference information. To improve the vehicle service provider's awareness of the logged-in vehicle terminal, a vehicle terminal identifier can also be sent to the vehicle service provider, allowing login to the vehicle terminal corresponding to the identifier based on the login account.

[0122] Based on the synchronized 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.

[0123] In summary, the method for processing program login for one or more vehicle-mounted terminals provided in this embodiment enables synchronous program login for at least one program on the vehicle-mounted terminal by configuring a near-field communication tag in the vehicle and establishing a near-field communication connection between the user terminal of the logged-in user and the near-field communication tag, based on the logged-in user's login account. Thus, by placing the user terminal at the location of the near-field communication tag in the vehicle and through a single authorization process, at least one program can be logged in synchronously on the vehicle-mounted terminal, improving the convenience and efficiency of program login. In this process, the user terminal reads the tag data stored in the vehicle's near-field communication tag via near-field communication, launches the application based on the tag data, and sends the tag data to the application for uploading to the server. The server, based on the tag data read from the vehicle's near-field communication tag uploaded by the user terminal, determines at least one program for synchronized login on the vehicle's infotainment system. It then returns the user's login account 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 synchronized login on the vehicle's infotainment system returned by the server. Based on the program identifier, login account, and vehicle type carried in the tag data, it generates and displays a login authorization page. If a login authorization command is obtained, it uploads it to the server. The server, based on the login authorization command uploaded by the user terminal and the program server, performs synchronized login for at least one program on the vehicle's infotainment system based on the login account. This enables convenient and efficient program login on the vehicle's infotainment system via near-field communication, even when driving or riding in different vehicles, improving the flexibility and convenience of program login on the vehicle's infotainment system.

[0124] The following description uses the application of the vehicle terminal program login processing method provided in this embodiment in the subroutine login processing scenario of the vehicle terminal as an example to further illustrate the program login processing method of the vehicle terminal provided in this embodiment. Figure 4 As shown, the method for processing the program login of a vehicle terminal in a subroutine login scenario applied to the vehicle terminal includes the following steps.

[0125] Step S406: Based on the tag data, read at least one sub-application associated with the logged-in user that performs program synchronization login on the vehicle terminal.

[0126] Step S408: Return the login account of the logged-in user's login application and the program identifier of at least one subroutine to the user terminal.

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

[0128] Step S420: Send the login account and vehicle terminal identifier to each subroutine server to facilitate subroutine login for the vehicle terminal's subroutine access.

[0129] The following is an embodiment of a vehicle-mounted terminal program login processing device provided in this specification: In the above embodiments, a method for processing program login for a vehicle terminal is provided, and correspondingly, a device for processing program login for a vehicle terminal is also provided, which will be described below with reference to the accompanying drawings.

[0130] Reference Figure 6 This illustration shows a schematic diagram of an embodiment of a vehicle terminal program login processing device provided in this embodiment.

[0131] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0132] This embodiment provides a program login processing device for a vehicle-mounted terminal, the device comprising: The tag data reading module 602 is configured to read tag data stored in the near-field communication tag of the vehicle via near-field communication; Application startup module 604 is configured to launch an application based on the tag data and pass the tag data to the application for uploading to the server. The receiving module 606 is configured to receive and display the program identifier and login account of at least one program that performs program synchronization login on the vehicle terminal, returned by the server. The login authorization instruction upload module 608 is configured to obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal for program login of at least one program.

[0133] Another embodiment of the vehicle terminal program login processing device provided in this specification is as follows: In the above embodiments, another method for processing program login for a vehicle terminal is provided. Correspondingly, a device for processing program login for a vehicle terminal is also provided, which will be described below with reference to the accompanying drawings.

[0134] Reference Figure 7 This illustration shows a schematic diagram of an embodiment of a vehicle terminal program login processing device provided in this embodiment.

[0135] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0136] This embodiment provides a program login processing device for a vehicle-mounted terminal, the device comprising: The tag data acquisition module 702 is configured to acquire tag data uploaded by the user terminal and read from the vehicle's near-field communication tag; The program determination module 704 is configured to determine, based on the tag data, at least one program that performs program synchronization login on the vehicle terminal; 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; The program login module 708 is configured to perform program login for at least one program based on the login authorization instruction uploaded by the user terminal, in conjunction with the program server and the program access of the vehicle terminal.

[0137] This specification provides the following embodiment of a user terminal: Corresponding to the above-described method for processing program login on a vehicle-mounted terminal, based on the same technical concept, one or more embodiments of this specification also provide a user terminal for executing the above-described method for processing program login on a vehicle-mounted terminal. Figure 8 This is a schematic diagram of the structure of a user terminal provided for one or more embodiments of this specification.

[0138] This embodiment provides a user terminal, including: like Figure 8As shown, user terminals can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memories 802. The memories 802 may store one or more application programs or data. The memories 802 can be temporary or persistent storage. The application programs stored in the memories 802 may include one or more modules (not shown), each module including a series of computer-executable instructions from the user terminal. Furthermore, the processor 801 may be configured to communicate with the memories 802 and execute the series of computer-executable instructions stored in the memories 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, etc.

[0139] In one 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 for use in the user terminal, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: The tag data stored in the vehicle's near-field communication tag is read through near-field communication. The application is launched based on the tag data, and the tag data is passed to the application to upload it to the server. Receive and display the program identifier and login account of at least one program that has performed program synchronization login on the vehicle terminal, returned by the server; Obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal for program login of at least one program.

[0140] This specification provides the following server implementation example: Corresponding to the other vehicle terminal program login processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a server for executing the vehicle terminal program login processing method provided above. Figure 9 This is a schematic diagram of the structure of a server provided for one or more embodiments of this specification.

[0141] This embodiment provides a server, including: like Figure 9As shown, servers can vary significantly due to differences in configuration or performance. They may include one or more processors 901 and memory 902, with memory 902 storing one or more application programs or data. Memory 902 can be temporary or persistent storage. The application programs stored in memory 902 may include one or more modules (not shown), each module comprising a series of computer-executable instructions for the server. Furthermore, processor 901 may be configured to communicate with memory 902, executing the series of computer-executable instructions stored in 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, etc.

[0142] In one specific embodiment, the server includes 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 for use in the server, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Acquire tag data uploaded by the user terminal from the near-field communication tag of the vehicle; Based on the tag data, at least one program that performs program synchronization login on the vehicle terminal is identified. 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; Based on the login authorization command uploaded by the user terminal, and in conjunction with the program server and the program access of the vehicle terminal, the program login of at least one program is performed.

[0143] This specification provides an embodiment of a computer-readable storage medium as follows: Corresponding to the above-described method for processing program login on a vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0144] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: The tag data stored in the vehicle's near-field communication tag is read through near-field communication. The application is launched based on the tag data, and the tag data is passed to the application to upload it to the server. Receive and display the program identifier and login account of at least one program that has performed program synchronization login on the vehicle terminal, returned by the server; Obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal for program login of at least one program.

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

[0146] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the above-described method for processing program login on a vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0147] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: Acquire tag data uploaded by the user terminal from the near-field communication tag of the vehicle; Based on the tag data, at least one program that performs program synchronization login on the vehicle terminal is identified. 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; Based on the login authorization command uploaded by the user terminal, and in conjunction with the program server and the program access of the vehicle terminal, the program login of at least one program is performed.

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

[0149] This specification provides an example of a computer program product as follows: Corresponding to the above-described method for processing program login on a vehicle terminal, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0150] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: The tag data stored in the vehicle's near-field communication tag is read through near-field communication. The application is launched based on the tag data, and the tag data is passed to the application to upload it to the server. Receive and display the program identifier and login account of at least one program that has performed program synchronization login on the vehicle terminal, returned by the server; Obtain the submitted login authorization instruction and upload it to the server to cooperate with the program access of the vehicle terminal for program login of at least one program.

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

[0152] Another example of a computer program product provided in this specification is as follows: Corresponding to the other vehicle terminal program login processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0153] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: Acquire tag data uploaded by the user terminal from the near-field communication tag of the vehicle; Based on the tag data, at least one program that performs program synchronization login on the vehicle terminal is identified. 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; Based on the login authorization command uploaded by the user terminal, and in conjunction with the program server and the program access of the vehicle terminal, the program login of at least one program is performed.

[0154] It should be noted that the embodiments of another computer program product described in this specification and the embodiments of another vehicle terminal program login processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

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

[0156] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than those shown in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some embodiments, parallel processing of multi-vehicle terminal program login is possible or may be advantageous.

[0157] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as 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 should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0158] The controller can be implemented in any suitable manner. For example, it 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, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0160] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0161] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied 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.

[0162] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0163] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0164] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0166] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0167] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. 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 memory (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, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0168] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0169] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data class. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can reside in local and remote computer storage media, including storage devices.

[0170] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for processing program login on a vehicle-mounted terminal, applied to a user terminal, the method comprising: The tag data stored in the vehicle's near-field communication tag is read through near-field communication. The application is launched based on the tag data, and the tag data is passed to the application to upload it to the server. The application works in conjunction with the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user determined based on the vehicle identifier in the tag data. The system obtains and uploads a login authorization command carrying the program configuration information of at least one program to the server, so that the server reads the vehicle terminal identifier carried in the tag data and sends the login account of at least one program, the vehicle terminal identifier, and the program configuration information to the program server of each program to cooperate with the program access of the vehicle terminal to perform program login and program configuration of at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of at least one program displayed on the login authorization page.

2. The method for processing program login of a vehicle-mounted terminal according to claim 1, wherein the step of performing program login for at least one program in conjunction with program access of the vehicle-mounted terminal includes: A login credential is generated based on the login account, and the login credential is associated with and stored with the vehicle terminal identifier; If a program access command is detected, the login credentials are read according to the vehicle terminal identifier carried by the program access command and returned to the vehicle terminal to perform program login on the vehicle terminal.

3. The method for processing program login on a vehicle-mounted terminal according to claim 1, wherein the step of performing program login for at least one program in conjunction with program access on the vehicle-mounted terminal includes: The login account and the vehicle terminal identifier are associated and stored together; Read the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generate a login credential based on the login account; The login credentials are associated with and stored with the vehicle terminal identifier, and the login credentials are returned to the vehicle terminal to log in to the program on the vehicle terminal.

4. The method for processing program login on a vehicle-mounted terminal according to claim 1, wherein the synchronous login authorization, which involves the application cooperating with the server to perform synchronous login of at least one program on the vehicle-mounted terminal based on the login account, includes: Receive the program identifier and login account returned by the server; A login authorization list is generated based on the program identifier and the login account; Based on the login authorization list and the vehicle type carried by the tag data, a login authorization page is generated and displayed.

5. The method for processing program login of a vehicle terminal according to claim 1, wherein the program identifier of the at least one program is read after the login authorization instruction is detected.

6. The vehicle terminal program login processing method according to claim 1, wherein the at least one program is determined in the following manner: Based on the tag data, read the multiple candidate programs associated with the logged-in user and the login status of each candidate program; Candidate programs that are not logged in are identified as at least one program for program synchronization login.

7. The method for processing program login of a vehicle-mounted terminal according to claim 1, after the step of launching the application based on the tag data and passing the tag data to the application to upload to the server, further includes: If the server returns the program identifier of at least one program to be exited and the login account of the program to be exited on the vehicle terminal, then the program identifier of the at least one program to be exited and the login account of the login account are displayed. Obtain the submitted exit authorization instruction and upload it to the server to cooperate with the vehicle terminal in exiting the program of at least one program to be exited.

8. The method for processing program login on a vehicle terminal according to claim 7, wherein any one of the at least one programs to be exited exits in the following manner: Query the login credentials associated with the vehicle terminal identifier and mark the login credentials as invalid; An exit reminder is sent to any of the programs to be exited, so that the program to be exited can be exited on the vehicle terminal.

9. The method for processing program login of a 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 on the vehicle terminal.

10. The method for processing program login on a vehicle-mounted terminal according to claim 1, further comprising: Configure the program through at least one program and upload the program configuration information to the program server of each program; The program server of each program configures at least one program running on the vehicle terminal according to the program configuration information.

11. A method for processing program login on a vehicle-mounted terminal, applied to a server, the method comprising: Acquire tag data uploaded by the user terminal from the near-field communication tag of the vehicle; Based on the vehicle identifier in the tag data, at least one program that performs program synchronization login on the vehicle terminal is identified; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user. In conjunction with the user terminal, synchronous login authorization is performed to synchronize the login of at least one program on the vehicle terminal based on the login account of the logged-in user. Based on the login authorization instruction uploaded by the user terminal carrying the program configuration information of at least one program, the vehicle terminal identifier carried by the tag data is read, and the login account, the vehicle terminal identifier and the program configuration information are sent to the program server of each program to cooperate with the program access of the vehicle terminal to perform program login and program configuration of at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of at least one program displayed on the login authorization page.

12. The method for processing program login of a vehicle-mounted terminal according to claim 11, wherein the step of performing program login of the at least one program in conjunction with program access of the vehicle-mounted terminal includes: A login credential is generated based on the login account, and the login credential is associated with and stored with the vehicle terminal identifier; If a program access command is detected, the login credentials are read according to the vehicle terminal identifier carried by the program access command and returned to the vehicle terminal to perform program login on the vehicle terminal.

13. The method for processing program login of a vehicle-mounted terminal according to claim 11, wherein the step of performing program login of the at least one program in conjunction with program access of the vehicle-mounted terminal includes: The login account and the vehicle terminal identifier are associated and stored together; Read the login account associated with the vehicle terminal identifier carried in the program access instruction uploaded by the vehicle terminal, and generate a login credential based on the login account; The login credentials are associated with and stored with the vehicle terminal identifier, and the login credentials are returned to the vehicle terminal to log in to the program on the vehicle terminal.

14. The method for processing program login on a vehicle-mounted terminal according to claim 11, wherein determining at least one program for synchronous program login on the vehicle-mounted terminal based on the vehicle identifier in the tag data includes: Based on the tag data, read the multiple candidate programs associated with the logged-in user and the login status of each candidate program; Candidate programs that are not logged in are selected as programs for program synchronization login.

15. The method for processing program login of a vehicle-mounted terminal according to claim 11, further comprising: Candidate programs with a login status of "login" are selected as at least one program to be exited during program synchronization on the vehicle terminal. Return the program identifier of the at least one program to be exited and the login account to the user terminal for synchronized exit authorization; Based on the exit authorization command uploaded by the user terminal, the program server performs the program exit of at least one program to be exited on the vehicle terminal.

16. The method for processing program login on a vehicle-mounted terminal according to claim 15, wherein any one of the at least one programs to be exited exits in the following manner: Query the login credentials associated with the vehicle terminal identifier and mark the login credentials as invalid; An exit reminder is sent to any of the programs to be exited, so that the program to be exited can be exited on the vehicle terminal.

17. The method for processing program login of a vehicle-mounted terminal according to claim 11, further comprising: The system sends the login account and driving preference information to the vehicle service provider to log in to the vehicle terminal based on the login account and configure the vehicle's driving settings based on the driving preference information.

18. A program login processing device for a vehicle-mounted terminal, running on a user terminal, the device comprising: The tag data reading module is configured to read tag data stored in the vehicle's near-field communication tags via near-field communication; The application startup module is configured to launch the application based on the tag data and pass the tag data to the application for uploading to the server. The receiving module is configured to cooperate with the server through the application to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user determined according to the vehicle identifier in the tag data. The login authorization instruction upload module is configured to obtain a submitted login authorization instruction carrying the program configuration information of at least one program and upload it to the server, so that the server reads the vehicle terminal identifier carried in the tag data and sends the login account of the at least one program, the vehicle terminal identifier, and the program configuration information to the program server of each program, so as to cooperate with the program access of the vehicle terminal to perform program login and program configuration of the at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of the at least one program displayed on the login authorization page.

19. A program login processing device for a vehicle-mounted terminal, running on a server, the device comprising: The tag data acquisition module is configured to acquire tag data uploaded by the user terminal and read from the vehicle's near-field communication tag; The program determination module is configured to determine at least one program that performs program synchronization login on the vehicle terminal based on the vehicle identifier in the tag data; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user; The return module is configured to cooperate with the user terminal to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account of the logged-in user; The program login module is configured to read the vehicle terminal identifier carried in the tag data according to the login authorization instruction uploaded by the user terminal, which carries the program configuration information of at least one program, and send the login account, the vehicle terminal identifier, and the program configuration information to the program server of each program to cooperate with the program access of the vehicle terminal to perform program login and program configuration of at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of at least one program displayed on the login authorization page.

20. A user terminal, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: The tag data stored in the vehicle's near-field communication tag is read through near-field communication. The application is launched based on the tag data, and the tag data is passed to the application to upload it to the server. The application works in conjunction with the server to perform synchronous login authorization for at least one program on the vehicle terminal based on the login account; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user determined based on the vehicle identifier in the tag data. The system obtains and uploads a login authorization command carrying the program configuration information of at least one program to the server, so that the server reads the vehicle terminal identifier carried in the tag data and sends the login account of at least one program, the vehicle terminal identifier, and the program configuration information to the program server of each program to cooperate with the program access of the vehicle terminal to perform program login and program configuration of at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of at least one program displayed on the login authorization page.

21. A server, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Acquire tag data uploaded by the user terminal from the near-field communication tag of the vehicle; Based on the vehicle identifier in the tag data, at least one program that performs program synchronization login on the vehicle terminal is identified; the at least one program includes candidate programs that are not logged in among multiple candidate programs associated with the logged-in user. In conjunction with the user terminal, synchronous login authorization is performed to synchronize the login of at least one program on the vehicle terminal based on the login account of the logged-in user. Based on the login authorization instruction uploaded by the user terminal carrying the program configuration information of at least one program, the vehicle terminal identifier carried by the tag data is read, and the login account, the vehicle terminal identifier and the program configuration information are sent to the program server of each program to cooperate with the program access of the vehicle terminal to perform program login and program configuration of at least one program; the program configuration information is obtained by entering configuration information based on the configuration items of at least one program displayed on the login authorization page.

22. A computer-readable storage medium for storing computer-executable instructions that, when executed, implement the steps of the method of claim 1 or claim 11.

Images