CN110830418B

CN110830418B - Method and device for binding vehicle-mounted terminal and application program

Info

Publication number: CN110830418B
Application number: CN201810904839.6A
Authority: CN
Inventors: 赵华; 付宏炜; 赵明伟
Original assignee: Beiqi Foton Motor Co Ltd
Current assignee: Beiqi Foton Motor Co Ltd
Priority date: 2018-08-09
Filing date: 2018-08-09
Publication date: 2021-09-17
Anticipated expiration: 2038-08-09
Also published as: CN110830418A

Abstract

The utility model relates to a method and a device for binding a vehicle-mounted terminal and an application program.A vehicle-mounted terminal acquires the vehicle identification of the vehicle where the vehicle-mounted terminal is located and sends the vehicle identification to a vehicle-mounted terminal server when a target user initiates a service request with an application program server through the vehicle-mounted terminal; the application program server is a server corresponding to a target application program logged in by the target user; the vehicle-mounted terminal server acquires a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to an application program server; the application program server determines whether the vehicle-mounted terminal and the target application program are bound or not according to the vehicle identification, and when the vehicle-mounted terminal and the target application program are not bound, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle factory.

Description

Method and device for binding vehicle-mounted terminal and application program

Technical Field

The disclosure relates to the field of vehicle control, in particular to a method and a device for binding a vehicle-mounted terminal and an application program.

Background

The friends of the application program such as WeChat and the like share the position, the file and the like, so that the life convenience and the social application are improved, the vehicle is used as a necessary travel tool and is indispensable in the life of people, and various application information (such as position, video, pictures, documents and the like) of the application program is limited in the function of being used by the vehicle user on the vehicle-mounted terminal, so that if the various application information of the application program can be shared between the terminal (such as a computer, a mobile phone and the like) and the vehicle, the convenience can be improved, and the vehicle using experience of the vehicle user can be improved.

Before sharing multiple application information of an application program to a vehicle-mounted terminal on a vehicle, the application program of a user needs to be bound with the vehicle-mounted terminal on the vehicle, the user generally sends binding information (such as 'BD # vehicle identification') in a specified text format to a public service number of the application program, the public service number of the application program sends the binding information to an application program server corresponding to the public service number, the application program server forwards the binding information input by the user to the vehicle-mounted terminal server, the vehicle-mounted terminal server confirms the identity of a user and then completes binding, in addition, when the user is not the owner of the vehicle, the user also needs to send binding information (such as 'BDPY # vehicle identification # name') in another specified text format to the application program public service number and the application program public service number is confirmed by the owner of the vehicle, the binding can be successful, namely, in the prior art, a user needs to manually input binding information in an instruction text format including a vehicle identifier to bind a user application program with a vehicle-mounted terminal, but the method for manually inputting the binding information is complex in operation, and when the user forgets the vehicle identifier or the input binding information is incorrect, the binding is failed, so that the binding efficiency and the user experience are reduced.

Disclosure of Invention

In order to solve the problems in the prior art, the present disclosure provides a method and an apparatus for binding a vehicle-mounted terminal and an application program.

According to a first aspect of the embodiments of the present disclosure, a method for binding a vehicle-mounted terminal and an application program is provided, where the method includes: when a target user initiates a service request with an application program server through a vehicle-mounted terminal, the vehicle-mounted terminal acquires a vehicle identifier of a vehicle where the vehicle-mounted terminal is located and sends the vehicle identifier to a vehicle-mounted terminal server; the application program server is a server corresponding to a target application program logged in by the target user; the vehicle-mounted terminal server acquires a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application program server; and the application program server determines whether the vehicle-mounted terminal and the target application program are bound or not according to the vehicle identification, and binds the vehicle-mounted terminal and the target application program according to the vehicle identification and the public number of the vehicle factory when the vehicle-mounted terminal and the target application program are not bound.

Optionally, the binding, by the application server, the vehicle-mounted terminal and the target application according to the vehicle identifier and the public number of the vehicle factory includes: the application program server generates binding data of the vehicle-mounted terminal according to the vehicle identification and the public number of the vehicle factory, and sends the binding data to the vehicle-mounted terminal server; the vehicle-mounted terminal server sends the received binding data to the vehicle-mounted terminal; after the target user obtains the binding data from the vehicle-mounted terminal through the logged target application program, the application program server obtains first user information of the target user, the vehicle identification and the public number of the vehicle factory according to the binding data obtained by the target application program; and the application program server binds the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identification and the public number of the vehicle factory.

Optionally, the binding data includes two-dimensional code data, and before the target user obtains the binding data from the in-vehicle terminal through the logged-in target application program, the method further includes: the vehicle-mounted terminal generates the received two-dimensional code data into a two-dimensional code picture and displays the two-dimensional code picture; the obtaining, by the target user, the binding data from the vehicle-mounted terminal through the logged-in target application program includes: and the target user scans the two-dimensional code picture through the target application program to acquire the two-dimensional code data.

Optionally, the determining, by the application server, whether the vehicle-mounted terminal and the target application are bound according to the vehicle identifier includes: the application program server determines whether the vehicle-mounted terminal is bound with an application program according to the vehicle identification; when the application program server determines that the vehicle-mounted terminal is not bound with the application program, determining that the vehicle-mounted terminal and the target application program are not bound; when the application program server determines that the application program is bound to the vehicle-mounted terminal, second user information of a plurality of bound users corresponding to the application program bound to the vehicle-mounted terminal is acquired, and the second user information is sent to the vehicle-mounted terminal server; the vehicle-mounted terminal server forwards the received second user information to the vehicle-mounted terminal; the vehicle-mounted terminal displays a plurality of bound users corresponding to the application programs bound with the vehicle-mounted terminal to the user according to the second user information; the application program server determines whether a binding request instruction triggered by the target user according to the displayed multiple binding users is received within a preset time period, the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program, if the binding request instruction is not received when the preset time period is reached, the vehicle-mounted terminal and the target application program are determined to be bound, and if the binding request instruction is received within the preset time period, the vehicle-mounted terminal and the target application program are determined not to be bound.

According to a second aspect of the embodiments of the present disclosure, a method for binding a vehicle-mounted terminal and an application program is provided, and is applied to the vehicle-mounted terminal, and the method includes steps executed by the vehicle-mounted terminal in the method for binding the vehicle-mounted terminal and the application program according to the first aspect of the present disclosure.

According to a third aspect of the embodiments of the present disclosure, a method for binding a vehicle-mounted terminal and an application program is provided, and is applied to a vehicle-mounted terminal server.

According to a fourth aspect of the embodiments of the present disclosure, a method for binding a vehicle-mounted terminal and an application program is provided, and is applied to an application program server.

According to a fifth aspect of the embodiments of the present disclosure, there is provided an apparatus for binding an in-vehicle terminal and an application program, which is applied to an in-vehicle terminal configured to perform the steps performed by the in-vehicle terminal in the method for binding an in-vehicle terminal and an application program according to the first aspect of the present disclosure.

According to a sixth aspect of the embodiments of the present disclosure, an apparatus for binding a vehicle-mounted terminal and an application program is provided, which is applied to a vehicle-mounted terminal server, and the vehicle-mounted terminal server is configured to execute the steps executed by the vehicle-mounted terminal server in the method for binding a vehicle-mounted terminal and an application program according to the first aspect of the present disclosure.

According to a seventh aspect of the embodiments of the present disclosure, an apparatus for binding a vehicle-mounted terminal with an application program is provided, where the apparatus is applied to an application program server, and the application program server is configured to execute the steps executed by the application program server in the method for binding a vehicle-mounted terminal with an application program according to the first aspect of the present disclosure.

According to an eighth aspect of the embodiments of the present disclosure, there is provided a method for binding an in-vehicle terminal and an application program, which is applied to the in-vehicle terminal, and the method includes: when a target user initiates a service request with an application program server through a vehicle-mounted terminal, acquiring a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, sending the vehicle identifier to the vehicle-mounted terminal server, wherein the application program server is a server corresponding to a target application program logged in by the target user, so that the vehicle-mounted terminal server acquires a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application program server, so that the application program server binds the vehicle-mounted terminal and the target application program according to the vehicle identifier and the vehicle factory public number when determining that the vehicle-mounted terminal and the target application program are not bound according to the vehicle identifier.

According to a ninth aspect of the embodiments of the present disclosure, there is provided a method for binding an in-vehicle terminal and an application program, which is applied to an in-vehicle terminal server, the method including: when a target user initiates a service request with an application program server through a vehicle-mounted terminal, receiving a vehicle identifier sent by the vehicle-mounted terminal, wherein the application program server is a server corresponding to a target application program logged in by the target user, and acquiring a public number of a vehicle factory, which is in a binding relationship with the vehicle-mounted terminal in advance, according to the vehicle identifier; and sending the vehicle identification and the public number of the vehicle factory to an application program server, so that the application program server can bind the vehicle-mounted terminal and the target application program according to the vehicle identification and the public number of the vehicle factory when determining that the vehicle-mounted terminal and the target application program are not bound according to the vehicle identification.

According to a tenth aspect of the embodiments of the present disclosure, there is provided a method for binding an in-vehicle terminal and an application program, which is applied to an application program server, the method including: when a target user initiates a service request with an application program server through a vehicle-mounted terminal, receiving a vehicle identifier acquired by the vehicle-mounted terminal server from the vehicle-mounted terminal, and a public number of a vehicle factory acquired by the vehicle-mounted terminal server according to the vehicle identifier and pre-establishing a binding relationship with the vehicle-mounted terminal, wherein the application program server is a server corresponding to a target application program logged in by the target user, and determining whether the vehicle-mounted terminal and the target application program are bound or not according to the vehicle identifier; and when the fact that the vehicle-mounted terminal and the target application program are not bound is determined, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle factory.

According to an eleventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of the first aspect of the present disclosure.

According to the technical scheme, when a target user initiates a service request with an application program server through a vehicle-mounted terminal, the vehicle-mounted terminal acquires a vehicle identifier of a vehicle where the vehicle-mounted terminal is located and sends the vehicle identifier to the vehicle-mounted terminal server, and the application program server is a server corresponding to a target application program logged in by the target user; the vehicle-mounted terminal server acquires a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application program server; the application program server determines whether the vehicle-mounted terminal and the target application program are bound according to the vehicle identification, and when the vehicle-mounted terminal and the target application program are not bound, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle manufacturer.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure without limiting the disclosure. In the drawings:

FIG. 1 is a flowchart illustrating a first method for binding an application with a vehicle-mounted terminal according to an exemplary embodiment;

FIG. 2 is a flowchart illustrating a second in-vehicle terminal and application binding method according to an example embodiment;

FIG. 3 is a flowchart illustrating a third in-vehicle terminal and application binding method according to an example embodiment;

FIG. 4 is a flowchart illustrating a fourth method for binding an application with a vehicle-mounted terminal according to an example embodiment;

FIG. 5 is a flowchart illustrating a fifth in-vehicle terminal and application binding method according to an exemplary embodiment;

fig. 6 is a block diagram illustrating a structure of a binding system of an in-vehicle terminal and an application according to an exemplary embodiment.

Detailed Description

The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.

In order to solve the existing problems, the present disclosure provides a method and an apparatus for binding a vehicle-mounted terminal with an application program, where when a target user initiates a service request (such as an application information sharing request) with an application program server through the vehicle-mounted terminal, the vehicle-mounted terminal obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, and sends the vehicle identifier to the vehicle-mounted terminal server, the application program server is a server corresponding to a target application program that the target user logs in, the vehicle-mounted terminal server obtains a public number of a vehicle factory, which is in a binding relationship with the vehicle-mounted terminal in advance, according to the vehicle identifier, and sends the vehicle identifier and the public number of the vehicle factory to the application program server; the application program server determines whether the vehicle-mounted terminal and the target application program are bound according to the vehicle identification, and when the vehicle-mounted terminal and the target application program are not bound, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle manufacturer.

In the disclosure, before binding a target application (e.g., a WeChat logged in by a user A) with a vehicle-mounted terminal, an application server and a sharing function of the vehicle-mounted terminal server need to be configured, because for a certain vehicle, there is no separate application account, further, a certain vehicle-mounted terminal does not have a separate application account, when configuring the sharing function of the application server and the vehicle-mounted terminal server, it needs to be completed through a public number of a vehicle manufacturer, vehicle-mounted terminals on vehicles of the same brand or the same production batch can share a public number of the vehicle manufacturer, and after completing the configuration, the vehicle-mounted terminals of the vehicles of the same brand or the same production batch can be established with the public number of the vehicle manufacturer.

For example, the application is taken as an example to describe, when configuring the sharing function of the wechat server and the vehicle-mounted terminal server, a vehicle factory worker may complete configuration through a vehicle factory wechat public number, specifically, a vehicle factory wechat public number may be registered on a terminal (such as a mobile phone, a computer, etc.), a functional plug-in is added on a page of the vehicle factory wechat public number, then available equipment is continuously added to the vehicle factory wechat public number, and address information of the vehicle-mounted terminal server is input according to a page prompt, so that the configuration of the sharing function of the wechat server and the vehicle-mounted terminal server is completed.

The function plug-ins may include shared application information plug-ins (for example, the application information plug-ins may include a position plug-in, a picture plug-in, a video plug-in, a document plug-in, and the like), and after the function plug-ins are added, various application information (such as a position, a picture, a video, a document, and the like) on the application program may be shared to the vehicle-mounted terminal through different function plug-ins; the available device (such as a vehicle-mounted terminal) may include a device for receiving shared application information, so that a user may select a device for receiving shared application information more intuitively when sharing application information, when adding the available device, an icon and a nickname (for example, "my vehicle") of a user-defined available device may be uploaded, after adding the available device, various application information on an application program may be shared to the available device by triggering the icon of the available device, in one possible implementation, the available device may include the vehicle-mounted terminal, and at this time, the user may share the various application information on the application program to the vehicle-mounted terminal by triggering the icon of the vehicle-mounted terminal.

It should be noted that, the configuration of the sharing function of the application server and the vehicle-mounted terminal server is generally that before the vehicle leaves the factory, a vehicle factory worker completes the configuration of the sharing function, and after the configuration of the sharing function is completed, a binding relationship between the vehicle-mounted terminal on the vehicle and a vehicle factory public number corresponding to the vehicle is established, and after the user purchases the vehicle, the user only needs to bind the target application and the vehicle-mounted terminal, and after confirming that the binding is completed, the application information on the target application can be directly shared to the vehicle-mounted terminal for the vehicle to use.

Specific embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Fig. 1 is a flowchart illustrating a method for binding an in-vehicle terminal with an application according to an exemplary embodiment, where the method includes the following steps, as shown in fig. 1:

in step 101, when a target user initiates a service request with an application server through a vehicle-mounted terminal, the vehicle-mounted terminal obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, and sends the vehicle identifier to the vehicle-mounted terminal server.

The application server is a server corresponding to a target application program that the target user logs in, where the target application program may include an application program that the target user logs in on a terminal (e.g., a mobile phone, a computer, etc.) and is to be bound with the vehicle-mounted terminal, for example, the target application program may include a WeChat that user A logs in, the service request may include an application information sharing request, and the vehicle identifier may include a unique identifier (e.g., a vehicle VIN code) of the vehicle.

In a possible implementation manner, a service request button (such as "application information sharing") is preset on the vehicle-mounted terminal interface, when the vehicle-mounted terminal obtains the trigger operation of the target user on the service request button, it is determined that the target user initiates a service request with the application server through the vehicle-mounted terminal, at this time, the vehicle-mounted terminal obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, and sends the vehicle identifier to the vehicle-mounted terminal server.

In step 102, the vehicle-mounted terminal server obtains a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application program server.

Wherein, the public number of the car factory can comprise a WeChat public number of the car factory.

Because there is no separate application program account for a certain vehicle, and further, a certain vehicle-mounted terminal does not have a separate application program account, when a target application program is bound to the vehicle-mounted terminal, the binding is realized by a vehicle factory public number and a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, it needs to be noted that the vehicle factory public number is configured to the vehicle by vehicle factory workers before the vehicle leaves a factory, and before the vehicle-mounted terminal is bound to the target application program, the vehicle-mounted terminal has established a binding relationship with the vehicle factory public number in a configuration process before the vehicle leaves the factory, and in addition, vehicle-mounted terminals on vehicles of the same brand or the same production batch can share the vehicle factory public number.

Because the vehicle-mounted terminal and the vehicle-mounted terminal server transmit information through the transmission channel, and the vehicle-mounted terminals on vehicles of different brands transmit information to the vehicle-mounted terminal server through different transmission channels, in a possible implementation manner, when receiving the vehicle identifier, the vehicle-mounted terminal server can determine which brand of vehicle the vehicle-mounted terminal transmits the vehicle identifier according to the transmission channel of the vehicle identifier, and at the moment, the vehicle-mounted terminal server can acquire the public number of the vehicle factory corresponding to the vehicle brand.

In step 103, the application server determines whether the vehicle-mounted terminal and the target application program are bound according to the vehicle identification, and binds the vehicle-mounted terminal and the target application program according to the vehicle identification and the public number of the vehicle factory when the vehicle-mounted terminal and the target application program are not bound.

In this step, when the application server binds the vehicle-mounted terminal and the target application according to the vehicle identifier and the vehicle factory public number, the application server may generate binding data of the vehicle-mounted terminal according to the vehicle identifier and the vehicle factory public number, and send the binding data to the vehicle-mounted terminal server; the vehicle-mounted terminal server sends the received binding data to the vehicle-mounted terminal; after a target user acquires the binding data from the vehicle-mounted terminal through the logged target application program, the application program server acquires first user information of the target user, the vehicle identification and the public number of the vehicle factory according to the binding data acquired by the target application program; the application program server binds the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identification and the public number of the vehicle factory.

The first user information may include information such as a user name, a user nickname, a user avatar, and the like of the target user.

Considering that in the current daily life of people, functions such as convenient payment and friend adding can be realized by scanning a two-dimensional code, and scanning the two-dimensional code is a simple and quick interconnection mode, in a preferred embodiment of the present disclosure, binding of an application program and a vehicle-mounted terminal can also be realized by scanning the two-dimensional code, at this time, the binding data may include the two-dimensional code data, specifically, when the binding data includes the two-dimensional code data, the vehicle-mounted terminal may generate a two-dimensional code picture from the received two-dimensional code data and display the two-dimensional code picture, the target user may scan the two-dimensional code picture through a logged target application program to obtain the two-dimensional code data, at this time, the target application program may send first user information of the target user, a vehicle identifier corresponding to the two-dimensional code data, and a public number of the vehicle manufacturer to the application program server, so that the application server can bind the vehicle-mounted terminal and the target application according to the first user information, the vehicle identification and the public number of the vehicle factory.

In another possible implementation manner, after the vehicle-mounted terminal acquires the binding data, an identification code may be generated according to the binding data (for example, the identification code may include numbers or letters, or a combination of numbers and letters), and the identification code is displayed to a user, after the target user inputs the identification code through a logged-in target application program, the target application program acquires a vehicle identifier and a public number of a vehicle manufacturer corresponding to the identification code, and sends first user information of the target user, and the vehicle identifier and the public number of the vehicle manufacturer corresponding to the identification code to the application server, so that the application server may bind the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identifier, and the public number of the vehicle manufacturer.

In addition, when determining whether the vehicle-mounted terminal and the target application program are bound according to the vehicle identifier, the application program server may determine whether the vehicle-mounted terminal is bound with the application program according to the vehicle identifier; when the application program server determines that the vehicle-mounted terminal is not bound with the application program, determining that the vehicle-mounted terminal and the target application program are not bound; when the application program server determines that the application program is bound to the vehicle-mounted terminal, second user information of a plurality of bound users corresponding to the application program already bound to the vehicle-mounted terminal is acquired, and the second user information is sent to the vehicle-mounted terminal server; the vehicle-mounted terminal server forwards the received second user information to the vehicle-mounted terminal; the vehicle-mounted terminal displays a plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal to a user according to the second user information, the application program server determines whether a binding request instruction triggered by the target user according to the displayed plurality of bound users is received within a preset time period, the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program, if the binding request instruction is not received within the preset time period, the vehicle-mounted terminal and the target application program are determined to be bound, and if the binding request instruction is received within the preset time period, the vehicle-mounted terminal and the target application program are determined to be unbound.

The second user information may include information such as user names, user nicknames, user head images and the like of a plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal.

Before the vehicle leaves the factory, a vehicle-mounted terminal on the vehicle and a public number of the vehicle factory are already established in a binding relationship by a vehicle factory worker, so after the application program server binds the vehicle-mounted terminal and the target application program, the binding relationship is established among the vehicle-mounted terminal, the public number of the vehicle factory and the target application program, and thus when the service request is an application information sharing request, a user can share application information on the target application program to the vehicle-mounted terminal.

By adopting the method, when the vehicle-mounted terminal acquires the service request between the application program servers which are initiated by the target user through the vehicle-mounted terminal and correspond to the target application program, the vehicle identification can be actively acquired, and the target application program can be bound with the vehicle-mounted terminal without the need of manually inputting the binding information including the vehicle identification by the user, so that the simplicity and convenience of binding the application program of the user with the vehicle-mounted terminal are realized, the binding efficiency is also improved, and the user experience is further improved.

Fig. 2 is a flowchart illustrating a method for binding an in-vehicle terminal with an application according to an exemplary embodiment, where the method includes the following steps, as shown in fig. 2:

in step 201, when a target user initiates a service request with an application server through a vehicle-mounted terminal, the vehicle-mounted terminal obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, and sends the vehicle identifier to the vehicle-mounted terminal server.

In step 202, the vehicle-mounted terminal server obtains a vehicle factory public number that is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application server.

In step 203, the application server determines whether the vehicle-mounted terminal is bound with an application according to the vehicle identification.

In a possible implementation manner, the application server may search a target binding record corresponding to the vehicle identifier in a pre-stored historical binding record, determine that the vehicle-mounted terminal is bound with the application program when determining that the target binding record is found, determine that the vehicle-mounted terminal is not bound with the application program when determining that the target binding record is not found, and further determine that the vehicle-mounted terminal is not bound with the target application program.

When determining that the application program is bound to the vehicle-mounted terminal, executing step 204 to step 207;

when it is determined that the in-vehicle terminal does not bind the application, steps 208 to 212 are performed.

In step 204, the application server obtains second user information of a plurality of bound users corresponding to the applications already bound to the vehicle-mounted terminal, and sends the second user information to the vehicle-mounted terminal server.

In step 205, the vehicle-mounted terminal server forwards the received second user information to the vehicle-mounted terminal.

In step 206, the vehicle-mounted terminal presents a plurality of bound users corresponding to the application programs bound with the vehicle-mounted terminal to the user according to the second user information.

In one possible implementation manner, the vehicle-mounted terminal can present the user names, user nicknames, user head images and other information of a plurality of bound users corresponding to the application programs bound with the vehicle-mounted terminal to the user in a list manner, in this way, the user can visually see in the list which bound users have corresponding to the applications that have been bound to the in-vehicle terminal, so that when the target user determines that the target application program logged in by the target user is not bound with the vehicle-mounted terminal, a button for newly adding a binding (e.g., "newly adding a binding") may be triggered on the vehicle-mounted terminal interface, and at this time, and the vehicle-mounted terminal determines to receive the binding request instruction of the target user and sends the binding request instruction to a vehicle-mounted terminal server, and the vehicle-mounted terminal server forwards the binding request instruction to an application program server.

And the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program.

In step 207, the application server determines whether a binding request instruction triggered by the target user according to the displayed multiple binding users is received within a preset time period, where the binding request instruction is used to request to bind the vehicle-mounted terminal and the target application.

If the binding request command is not received when the preset time period is reached, execute step 213;

if the binding request command is received within the predetermined time period, step 208 to step 212 are executed.

In step 208, the application server generates two-dimensional code data according to the vehicle identifier and the public number of the vehicle manufacturer, and sends the two-dimensional code data to the vehicle-mounted terminal server.

In consideration of the fact that in the current daily life of people, functions such as convenient payment and friend adding can be achieved by scanning the two-dimensional codes, and scanning the two-dimensional codes is a simple and quick interconnection mode, in an optimal implementation mode of the method, the binding of the application program and the vehicle-mounted terminal can be achieved by scanning the two-dimensional codes.

In step 209, the in-vehicle terminal server transmits the received two-dimensional code data to the in-vehicle terminal.

In step 210, the vehicle-mounted terminal generates a two-dimensional code picture according to the received two-dimensional code data, and displays the two-dimensional code picture.

In step 211, after the target user scans the two-dimensional code picture through the logged-in target application program, the application server obtains binding information from the target application program, where the binding information includes first user information of the target user, a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, and a public number of a vehicle shop.

In this step, after the target application program scans the two-dimensional code picture, the target application program may obtain, through the two-dimensional code picture, a vehicle identifier of the vehicle-mounted terminal and a public number of a vehicle factory to be bound to the target application program, and at this time, the target application program sends the first user information, the vehicle identifier of the vehicle-mounted terminal and the public number of the vehicle factory to the application program server together.

In step 212, the application server binds the vehicle-mounted terminal and the target application according to the first user information, the vehicle identification and the public number of the vehicle factory.

In step 213, the application server determines that the in-vehicle terminal and the target application are bound.

Illustratively, taking the target application program as the WeChat registered by the A user as an example, when the user wants to share the WeChat position on the WeChat registered by the A user to the vehicle-mounted terminal, the user can press the WeChat position wanted to be shared on the WeChat registered by the A user of the terminal, then trigger the ' on ' button, select the ' position plug-in corresponding to the WeChat position, then select the available equipment button (such as the icon of the available equipment ' my vehicle ') for receiving the position information, after selecting the available equipment button, the user selects the public WeChat number of the workshop WeChat for receiving the WeChat position, at this time, the WeChat position on the WeChat registered by the A user is sent to the WeChat signal of the workshop, and then the public WeChat position is sent to the vehicle-mounted terminal bound with the target application program, so that the vehicle can set the navigation destination as the WeChat position, the foregoing examples are illustrative only, and the disclosure is not limited thereto.

Fig. 3 is a flowchart illustrating a method for binding an application program with a vehicle-mounted terminal, which is applied to the vehicle-mounted terminal, according to an exemplary embodiment, and as shown in fig. 3, the method includes the following steps:

in step 301, when a target user initiates a service request with an application server through a vehicle-mounted terminal, a vehicle identifier of a vehicle where the vehicle-mounted terminal is located is obtained.

In a possible implementation manner, a service request button (such as "application information sharing") is preset on the vehicle-mounted terminal interface, and when the vehicle-mounted terminal obtains the trigger operation of the target user on the service request button, it is determined that the target user initiates a service request with the application server through the vehicle-mounted terminal, and at this time, the vehicle-mounted terminal obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal is located.

In step 302, the vehicle identifier is sent to a vehicle-mounted terminal server, so that the vehicle-mounted terminal server obtains a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and the vehicle identifier and the vehicle factory public number are sent to an application program server, so that the application program server binds the vehicle-mounted terminal and the target application program according to the vehicle identifier and the vehicle factory public number when determining that the vehicle-mounted terminal and the target application program are not bound according to the vehicle identifier.

When the application server binds the vehicle-mounted terminal and the target application program according to the vehicle identifier and the vehicle factory public number, the vehicle-mounted terminal receives binding data of the vehicle-mounted terminal, which is generated by the application server and is acquired by the vehicle-mounted terminal server from the application server, according to the vehicle identifier and the vehicle factory public number, after a target user acquires the binding data from the vehicle-mounted terminal through a logged target application program, the application server can obtain first user information of the target user, the vehicle identifier and the vehicle factory public number according to the binding data acquired by the target application program, so that the application server can bind the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identifier and the vehicle factory public number.

When the application server determines that the application program is bound to the vehicle-mounted terminal according to the vehicle identifier, the vehicle-mounted terminal receives second user information (the second user information may include user names, user nicknames, user head images and other information of a plurality of bound users) of a plurality of bound users corresponding to the application program already bound to the vehicle-mounted terminal, which is acquired by the vehicle-mounted terminal server from the application server, and displays the plurality of bound users corresponding to the application program already bound to the vehicle-mounted terminal to a user according to the second user information.

In a possible implementation manner, the vehicle-mounted terminal can display information such as user names, user nicknames, user head portraits and the like of a plurality of bound users corresponding to the application programs bound with the vehicle-mounted terminal to the user in a list manner, so that the user can visually see which bound users corresponding to the application programs bound with the vehicle-mounted terminal exist in the list, when the target user determines that the target application program logged in by the target user is not bound with the vehicle-mounted terminal, a newly-added binding button (such as 'newly-added binding') can be triggered on an interface of the vehicle-mounted terminal, at this time, the vehicle-mounted terminal determines to receive a binding request instruction of the target user and sends the binding request instruction to a vehicle-mounted terminal server, so that the vehicle-mounted terminal server forwards the binding request instruction to the application program server, and when the application program server receives the binding request instruction within a preset time period, binding the vehicle-mounted terminal and the target application program according to the vehicle identification and the public number of the vehicle factory, wherein the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program.

By way of example, taking the target application program as the WeChat registered by the A user as an example, when the user wants to share the WeChat location registered by the A user to the vehicle-mounted terminal, the user can press the WeChat location registered by the A user of the terminal to the vehicle-mounted terminal, then trigger the "on" button, select the "location plug-in" corresponding to the WeChat location, then select the available device button (such as the icon of the available device "my vehicle") for receiving the location information, and after selecting the available device button, the user selects the Milliserhouse WeChat public number for receiving the WeChat location, at this time, the WeChat location on the WeChat of the A user is sent to the Millishouse WeChat public number, which then sends the WeChat location to the vehicle-mounted terminal bound with the target application program, so that the vehicle can set the navigation destination to the WeChat location, the foregoing examples are illustrative only, and the disclosure is not limited thereto.

Fig. 4 is a flowchart illustrating a method for binding an application program with a vehicle-mounted terminal, which is applied to a vehicle-mounted terminal server, according to an exemplary embodiment, and as shown in fig. 4, the method includes the following steps:

in step 401, when a target user initiates a service request with an application server through a vehicle-mounted terminal, a vehicle identifier sent by the vehicle-mounted terminal is received.

The application server is a server corresponding to a target application program logged in by the target user, where the target application program may include an application program to be bound with the vehicle-mounted terminal, where the target application program is logged in by the target user on a terminal (such as a mobile phone, a computer, and the like), for example, the target application program may include a WeChat logged in by a user A, the service request may include an application information sharing request, the vehicle identifier is an identifier of a vehicle where the vehicle-mounted terminal is located, and the vehicle identifier may include a unique identifier (such as a vehicle VIN code) of the vehicle.

In a possible implementation manner, a service request button (such as "application information sharing") is preset on the vehicle-mounted terminal interface, and when the vehicle-mounted terminal obtains a trigger operation of a target user on the service request button, the vehicle-mounted terminal determines that the target user initiates a service request with the application server through the vehicle-mounted terminal, and at this time, the vehicle-mounted terminal server receives the vehicle identifier sent by the vehicle-mounted terminal.

In step 402, a public number of the vehicle factory, which is in a binding relationship with the vehicle-mounted terminal in advance, is obtained according to the vehicle identifier.

In step 403, the vehicle identifier and the garage public number are sent to an application server, so that the application server binds the vehicle-mounted terminal and the target application according to the vehicle identifier and the garage public number when determining that the vehicle-mounted terminal and the target application are not bound according to the vehicle identifier.

By adopting the method, when the service request between the application program servers corresponding to the target application program, which is initiated by the target user through the vehicle-mounted terminal, is obtained, the vehicle-mounted terminal server can receive the vehicle identification sent by the vehicle-mounted terminal, so that the user can bind the target application program and the vehicle-mounted terminal without manually inputting the binding information including the vehicle identification, the simplicity and convenience of binding the application program of the user and the vehicle-mounted terminal are realized, the binding efficiency is also improved, and the user experience is further improved.

Fig. 5 is a flowchart illustrating a method for binding an in-vehicle terminal with an application, which is applied to an application server, according to an exemplary embodiment, and as shown in fig. 5, the method includes the following steps:

in step 501, when a target user initiates a service request with an application server through a vehicle-mounted terminal, a vehicle identifier acquired by the vehicle-mounted terminal server from the vehicle-mounted terminal is received, and a public number of a vehicle factory, which is acquired by the vehicle-mounted terminal server according to the vehicle identifier and is in a binding relationship with the vehicle-mounted terminal in advance, is received.

The application server is a server corresponding to a target application program logged in by the target user, the target application program may include an application program to be bound with the vehicle-mounted terminal, where the target application program is logged in by the target user on a terminal (such as a mobile phone, a computer, and the like), for example, the target application program may include a WeChat logged in by a user A, the service request may include an application information sharing request, the vehicle identifier may include a unique identification code (such as a vehicle VIN code) of a vehicle, and the public number of the vehicle factory may include a public number of the WeChat of the vehicle factory.

In a possible implementation manner, a service request button (such as "application information sharing") is preset on the vehicle-mounted terminal interface, when the vehicle-mounted terminal obtains the triggering operation of the service request button by the target user, it is determined that the target user initiates a service request with the application server through the vehicle-mounted terminal, at this time, the application server receives a vehicle identifier obtained by the vehicle-mounted terminal server from the vehicle-mounted terminal, and a public number of a vehicle factory, which is obtained by the vehicle-mounted terminal server according to the vehicle identifier and is in a binding relationship with the vehicle-mounted terminal in advance, of the vehicle-mounted terminal.

It should be further noted that, for a certain vehicle, there is no separate application program account, and further, a certain vehicle-mounted terminal does not have a separate application program account, so when it is desired to bind a target application program with the vehicle-mounted terminal, it is also necessary to implement binding by a vehicle factory public number and combining with a vehicle identifier of a vehicle where the vehicle-mounted terminal is located, where the vehicle factory public number is configured in advance by vehicle factory workers to the vehicle before the vehicle leaves a factory, and before binding the vehicle-mounted terminal with the target application program, the vehicle-mounted terminal has established a binding relationship with the vehicle factory public number in a configuration process before the vehicle leaves the factory, and in addition, vehicle-mounted terminals on vehicles of the same brand or the same production batch may share one vehicle factory public number.

In step 502, it is determined whether the in-vehicle terminal and the target application are bound according to the vehicle identifier.

In this step, the application server may determine whether the vehicle-mounted terminal is bound with an application according to the vehicle identifier; when the application program server determines that the vehicle-mounted terminal is not bound with the application program, determining that the vehicle-mounted terminal and the target application program are not bound; the application program server acquires second user information of a plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal when determining that the application program is bound with the vehicle-mounted terminal, and sends the second user information to the vehicle-mounted terminal server, so that the vehicle-mounted terminal server forwards the received second user information to the vehicle-mounted terminal, the vehicle-mounted terminal displays the plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal to a user according to the second user information, the application program server determines whether a binding request instruction triggered by the user according to the displayed plurality of bound users is received within a preset time period, the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program, and if the binding request instruction is not received when the preset time period is reached, the vehicle-mounted terminal and the target application program are bound, and if the binding request instruction is received within the preset time period, determining that the vehicle-mounted terminal and the target application program are not bound.

In this step, when the application server determines whether the vehicle-mounted terminal is bound with the application program according to the vehicle identifier, one possible implementation manner may be that the application server searches a target binding record corresponding to the vehicle identifier in a pre-stored historical binding record, determines that the vehicle-mounted terminal is bound with the application program when determining that the target binding record is found, determines that the vehicle-mounted terminal is not bound with the application program when determining that the target binding record is not found, and further may determine that the vehicle-mounted terminal is not bound with the target application program.

In step 503, when it is determined that the vehicle-mounted terminal and the target application program are not bound, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle factory.

In this step, the application server may generate binding data of the vehicle-mounted terminal according to the vehicle identifier and the public number of the vehicle manufacturer, and send the binding data to the vehicle-mounted terminal server; enabling the vehicle-mounted terminal server to send the received binding data to the vehicle-mounted terminal; after a target user obtains the binding data from the vehicle-mounted terminal through the logged target application program, the application program server obtains first user information, the vehicle identification and the vehicle factory public number of the target user according to the binding data obtained by the target application program, so that the application program server can bind the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identification and the vehicle factory public number.

Considering that in the current daily life of people, functions such as convenient payment and friend adding can be realized by scanning a two-dimensional code, and scanning the two-dimensional code is a simple and quick interconnection mode, in a preferred embodiment of the present disclosure, binding of an application program and a vehicle-mounted terminal can also be realized by scanning the two-dimensional code, at this time, the binding data may include the two-dimensional code data, specifically, when the binding data includes the two-dimensional code data, the vehicle-mounted terminal may generate a two-dimensional code picture from the received two-dimensional code data and display the two-dimensional code picture, the target user may scan the two-dimensional code picture through a logged target application program to obtain the two-dimensional code data, at this time, the application server receives first user information of the target user, a vehicle identifier corresponding to the two-dimensional code data, and a public number of the vehicle factory, which are sent by the target application program, and then binding the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identification and the public number of the vehicle factory.

In another possible implementation manner, after the vehicle-mounted terminal acquires the binding data, an identification code may be generated according to the binding data (for example, the identification code may include numbers or letters, or a combination of numbers and letters), and the identification code is presented to a user, after the target user inputs the identification code through a logged-in target application program, the application server receives a vehicle identifier and a public number of a vehicle factory corresponding to the identification code sent by the target application program, and first user information of the target user, and then binds the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identifier, and the public number of the vehicle factory.

By adopting the method, when a target user initiates a service request between the application program servers corresponding to the target application program through the vehicle-mounted terminal, the application program server can receive the vehicle identification acquired by the vehicle-mounted terminal server from the vehicle-mounted terminal, and the target application program can be bound with the vehicle-mounted terminal without the need of manually inputting the binding information including the vehicle identification by the user, so that the binding simplicity of the application program of the user and the vehicle-mounted terminal is realized, the binding efficiency is also improved, and the user experience is further improved.

The present disclosure also provides an apparatus for binding a vehicle-mounted terminal and an application program, which is applied to a vehicle-mounted terminal configured to execute the steps executed by the vehicle-mounted terminal in the method for binding a vehicle-mounted terminal and an application program described in the embodiment shown in fig. 3 in the present disclosure.

The present disclosure also provides an apparatus for binding a vehicle-mounted terminal and an application program, which is applied to a vehicle-mounted terminal server configured to execute the steps executed by the vehicle-mounted terminal server in the method for binding a vehicle-mounted terminal and an application program described in the embodiment shown in fig. 4 in the present disclosure.

The present disclosure also provides an apparatus for binding a vehicle-mounted terminal and an application program, which is applied to an application server configured to execute the steps executed by the application server in the method for binding a vehicle-mounted terminal and an application program described in the embodiment shown in fig. 5 in the present disclosure.

With regard to the apparatuses in the above-described embodiments, the specific manner in which each execution subject (in-vehicle terminal, in-vehicle terminal lever server, application server) operates has been described in detail in the embodiments of the method relating to the binding of the in-vehicle terminal with the application, and will not be described in detail here.

Fig. 6 is a block diagram illustrating a structure of a system 600 for binding a vehicle-mounted terminal and an application according to an exemplary embodiment, where the system includes: a vehicle-mounted terminal 601, a vehicle-mounted terminal server 602, and an application server 603.

The vehicle-mounted terminal 601 is configured to, when a target user initiates a service request with the application server 603 through the vehicle-mounted terminal 601, obtain a vehicle identifier of a vehicle where the vehicle-mounted terminal 601 is located by the vehicle-mounted terminal 601, and send the vehicle identifier to the vehicle-mounted terminal server 602.

The application server 603 is a server corresponding to a target application program that the target user logs in, where the target application program may include an application program that the target user logs in on a terminal (e.g., a mobile phone, a computer, etc.) and is to be bound to the vehicle-mounted terminal 601, for example, the target application program may include a WeChat that user A logs in, the service request may include an application information sharing request, and the vehicle identifier may include a unique identifier (e.g., a vehicle VIN code) of the vehicle.

In a possible implementation manner, a service request button (such as "application information sharing") is preset on the interface of the vehicle-mounted terminal 601, when the vehicle-mounted terminal 601 obtains the trigger operation of the target user on the service request button, it is determined that the target user initiates a service request with the application server 603 through the vehicle-mounted terminal 601, at this time, the vehicle-mounted terminal 601 obtains a vehicle identifier of a vehicle where the vehicle-mounted terminal 601 is located, and sends the vehicle identifier to the vehicle-mounted terminal server 602.

The vehicle-mounted terminal server 602 is configured to obtain a car factory public number that is in a binding relationship with the vehicle-mounted terminal 601 in advance according to the vehicle identifier, and send the vehicle identifier and the car factory public number to the application server 603;

Because there is no separate application program account for a certain vehicle, and further, a certain vehicle-mounted terminal 601 does not have a separate application program account, when a target application program is bound to the vehicle-mounted terminal 601, the binding is also implemented by a vehicle factory public number and a vehicle identifier of the vehicle where the vehicle-mounted terminal 601 is located, it should be noted that the vehicle factory public number is configured to the vehicle by vehicle factory staff in advance before the vehicle leaves a factory, and before the vehicle-mounted terminal 601 is bound to the target application program, the vehicle-mounted terminal 601 has established a binding relationship with the vehicle factory public number in a configuration process before the vehicle leaves the factory, and in addition, the vehicle-mounted terminals 601 on vehicles of the same brand or the same production batch can share the vehicle factory public number.

In the system, since the vehicle-mounted terminal 601 and the vehicle-mounted terminal server 602 transmit information through a transmission channel, and the vehicle-mounted terminals 601 on vehicles of different brands transmit information to the vehicle-mounted terminal server 602 through different transmission channels, in a possible implementation manner, when receiving the vehicle identifier, the vehicle-mounted terminal server 602 can determine which brand of vehicle the vehicle-mounted terminal 601 transmits the vehicle identifier according to the transmission channel of the vehicle identifier, and at this time, the vehicle-mounted terminal server 602 can acquire the station public number corresponding to the vehicle brand.

The application server 603 is configured to determine whether the vehicle-mounted terminal 601 and the target application are bound according to the vehicle identifier, and bind the vehicle-mounted terminal 601 and the target application according to the vehicle identifier and the public number of the car park when the vehicle-mounted terminal 601 and the target application are not bound.

When the application server 603 binds the vehicle-mounted terminal 601 and the target application according to the vehicle identifier and the vehicle factory public number, the application server 603 may generate binding data of the vehicle-mounted terminal 601 according to the vehicle identifier and the vehicle factory public number, and send the binding data to the vehicle-mounted terminal server 602; the vehicle-mounted terminal server 602 sends the received binding data to the vehicle-mounted terminal 601; after a target user acquires the binding data from the vehicle-mounted terminal 601 through the logged target application program, the application program server 603 obtains first user information of the target user, the vehicle identifier and the public number of the vehicle factory according to the binding data acquired by the target application program; the application server 603 binds the vehicle-mounted terminal 601 and the target application according to the first user information, the vehicle identifier and the public number of the vehicle factory.

Considering that in the current daily life of people, functions such as convenient payment and friend adding can be realized by scanning a two-dimensional code, and scanning the two-dimensional code is a simple and quick interconnection manner, in a preferred embodiment of the present disclosure, binding of an application program and a vehicle-mounted terminal 601 can also be realized by scanning the two-dimensional code, at this time, the binding data may include two-dimensional code data, specifically, when the binding data includes the two-dimensional code data, the vehicle-mounted terminal 601 may generate a two-dimensional code picture from the received two-dimensional code data and display the two-dimensional code picture, the target user may scan the two-dimensional code picture through a logged-in target application program to obtain the two-dimensional code data, at this time, the application server 603 receives first user information of the target user, a vehicle identifier corresponding to the two-dimensional code data, and a public number of the vehicle factory, which are sent by the target application program, so that the application server 603 can bind the in-vehicle terminal 601 and the target application according to the first user information and the vehicle identification and the public number of the car factory.

In another possible implementation manner, after obtaining the binding data, the vehicle-mounted terminal 601 may generate an identification code according to the binding data (for example, the identification code may include numbers or letters, or a combination of numbers and letters), and present the identification code to a user, and after the target user inputs the identification code through a logged-in target application program, the target application program obtains a vehicle identifier and a public number of a vehicle manufacturer corresponding to the identification code, and sends first user information of the target user and the vehicle identifier and the public number of the vehicle manufacturer corresponding to the identification code to the application server 603, so that the application server 603 may bind the vehicle-mounted terminal 601 and the target application program according to the first user information and the vehicle identifier and the public number of the vehicle manufacturer.

In addition, the application server 603 may determine whether the in-vehicle terminal 601 is bound with an application program according to the vehicle identifier when determining whether the in-vehicle terminal 601 and the target application program are bound according to the vehicle identifier; when the application server 603 determines that the vehicle-mounted terminal 601 is not bound with the application, determining that the vehicle-mounted terminal 601 and the target application are not bound; when determining that the application program is bound to the vehicle-mounted terminal 601, the application server 603 obtains second user information of a plurality of bound users corresponding to the application program already bound to the vehicle-mounted terminal 601, and sends the second user information to the vehicle-mounted terminal server 602; the vehicle-mounted terminal server 602 forwards the received second user information to the vehicle-mounted terminal 601; the vehicle-mounted terminal 601 displays a plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal 601 to a user according to the second user information, the application server 603 determines whether a binding request instruction triggered by the user according to the plurality of bound users corresponding to the displayed application program bound with the vehicle-mounted terminal 601 is received within a preset time period, the binding request instruction is used for requesting to bind the vehicle-mounted terminal 601 and the target application program, if the binding request instruction is not received when the preset time period is reached, it is determined that the vehicle-mounted terminal 601 and the target application program are bound, and if the binding request instruction is received within the preset time period, it is determined that the vehicle-mounted terminal 601 and the target application program are not bound.

The second user information may include information such as user names, user nicknames, user head images, and the like of a plurality of bound users corresponding to the application program that has been bound to the in-vehicle terminal 601.

The application server 603 may search a target binding record corresponding to the vehicle identifier in a pre-stored historical binding record when determining whether the vehicle-mounted terminal 601 is bound with the application program according to the vehicle identifier, determine that the vehicle-mounted terminal 601 is bound with the application program when determining that the target binding record is found, determine that the vehicle-mounted terminal 601 is not bound with the application program when determining that the target binding record is not found, and further determine that the vehicle-mounted terminal 601 is not bound with the target application program.

When the vehicle-mounted terminal 601 presents a plurality of bound users bound with the vehicle-mounted terminal 601 to a user according to the second user information, a possible implementation manner may be that the vehicle-mounted terminal 601 presents information such as user names, user nicknames, user head portraits, and the like of the plurality of bound users corresponding to the application program bound with the vehicle-mounted terminal 601 to a target user in a list manner, so that the target user can visually see what bound users correspond to the application program bound with the vehicle-mounted terminal 601 in the list, so that the target user can trigger a new binding button (such as "new binding") on an interface of the vehicle-mounted terminal 601 when determining that the target application program is not bound with the vehicle-mounted terminal 601, at this time, the vehicle-mounted terminal 601 determines to receive a binding request instruction of the user and sends the binding request instruction to the vehicle-mounted terminal server 602, the vehicle-mounted terminal server 602 forwards the binding request instruction to the application server 603, where the binding request instruction is used to request to bind the vehicle-mounted terminal 601 and the target application.

Since the vehicle terminal 601 on the vehicle and the public number of the vehicle factory are already established in a binding relationship by the vehicle factory staff before the vehicle leaves the factory, after the application server 603 binds the vehicle terminal 602 and the target application, the binding relationship is established among the vehicle terminal 601, the public number of the vehicle factory, and the target application, so that when the service request is an application information sharing request, the user can share the application information on the target application to the vehicle terminal 601, specifically, the user can send the application information to be shared to the public number of the vehicle factory through the target application, and then the public number of the vehicle factory sends the application information to the vehicle terminal bound with the target application for the vehicle to use.

Illustratively, taking the target application program as the WeChat registered by the A user as an example, when the user wants to share the WeChat location registered by the A user to the vehicle-mounted terminal 601, the user can press the WeChat location registered by the A user of the terminal to be shared, then trigger the "on" button, select the "location plug-in" corresponding to the WeChat location, then select the available device button (such as the icon of the available device "my vehicle") for receiving the location information, and after selecting the available device button, the user selects the Milliserhouse WeChat public number for receiving the WeChat location, at this time, the WeChat location on the WeChat of the A user is sent to the Millishouse WeChat signal, which in turn sends the WeChat location to the vehicle-mounted terminal 601 bound with the target application program, so that the vehicle can set the navigation destination to the WeChat location, the foregoing examples are illustrative only, and the disclosure is not limited thereto.

By adopting the system, when the vehicle-mounted terminal acquires the service request between the application program servers which are initiated by the target user through the vehicle-mounted terminal and correspond to the target application program, the vehicle identification can be actively acquired, the target application program can be bound with the vehicle-mounted terminal without manually inputting the binding information including the vehicle identification by the user, the simplicity and convenience of binding the application program of the user with the vehicle-mounted terminal are realized, the binding efficiency is also improved, and the user experience is further improved.

The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.

It should be noted that, in the foregoing embodiments, various features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various combinations that are possible in the present disclosure are not described again.

In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.

Claims

1. A method for binding a vehicle-mounted terminal and an application program is characterized by comprising the following steps:

when a target user initiates a service request with an application program server through a vehicle-mounted terminal, the vehicle-mounted terminal acquires a vehicle identifier of a vehicle where the vehicle-mounted terminal is located and sends the vehicle identifier to a vehicle-mounted terminal server; the application program server is a server corresponding to a target application program logged in by the target user;

the vehicle-mounted terminal server acquires a vehicle factory public number which is in a binding relationship with the vehicle-mounted terminal in advance according to the vehicle identifier, and sends the vehicle identifier and the vehicle factory public number to the application program server;

the application program server determines whether the vehicle-mounted terminal and the target application program are bound or not according to the vehicle identification, and when the vehicle-mounted terminal and the target application program are not bound, the vehicle-mounted terminal and the target application program are bound according to the vehicle identification and the public number of the vehicle factory;

wherein the step of binding the vehicle-mounted terminal and the target application program by the application program server according to the vehicle identification and the public number of the vehicle factory comprises the following steps:

the application program server generates binding data of the vehicle-mounted terminal according to the vehicle identification and the public number of the vehicle factory, and sends the binding data to the vehicle-mounted terminal server;

the vehicle-mounted terminal server sends the received binding data to the vehicle-mounted terminal;

after the target user obtains the binding data from the vehicle-mounted terminal through the logged target application program, the application program server obtains first user information of the target user, the vehicle identification and the public number of the vehicle factory according to the binding data obtained by the target application program;

and the application program server binds the vehicle-mounted terminal and the target application program according to the first user information, the vehicle identification and the public number of the vehicle factory.

2. The method of claim 1, wherein the binding data comprises two-dimensional code data, and before the target user acquires the binding data from the in-vehicle terminal through the logged-in target application, the method further comprises:

the vehicle-mounted terminal generates the received two-dimensional code data into a two-dimensional code picture and displays the two-dimensional code picture;

the obtaining, by the target user, the binding data from the vehicle-mounted terminal through the logged-in target application program includes:

and the target user scans the two-dimensional code picture through the target application program to acquire the two-dimensional code data.

3. The method of claim 1, wherein the determining, by the application server, whether the in-vehicle terminal and the target application are bound according to the vehicle identifier comprises:

the application program server determines whether the vehicle-mounted terminal is bound with an application program according to the vehicle identification;

when the application program server determines that the vehicle-mounted terminal is not bound with the application program, determining that the vehicle-mounted terminal and the target application program are not bound;

when the application program server determines that the application program is bound to the vehicle-mounted terminal, second user information of a plurality of bound users corresponding to the application program bound to the vehicle-mounted terminal is acquired, and the second user information is sent to the vehicle-mounted terminal server; the vehicle-mounted terminal server forwards the received second user information to the vehicle-mounted terminal; the vehicle-mounted terminal displays a plurality of bound users corresponding to the application programs bound with the vehicle-mounted terminal to the user according to the second user information; the application program server determines whether a binding request instruction triggered by the target user according to the displayed multiple binding users is received within a preset time period, the binding request instruction is used for requesting to bind the vehicle-mounted terminal and the target application program, if the binding request instruction is not received when the preset time period is reached, the vehicle-mounted terminal and the target application program are determined to be bound, and if the binding request instruction is received within the preset time period, the vehicle-mounted terminal and the target application program are determined not to be bound.

4. A method for binding a vehicle-mounted terminal and an application program, which is applied to the vehicle-mounted terminal, and comprises the steps executed by the vehicle-mounted terminal in the method for binding the vehicle-mounted terminal and the application program according to any one of claims 1 to 3.

5. A method for binding a vehicle-mounted terminal and an application program, which is applied to a vehicle-mounted terminal server, and comprises the steps executed by the vehicle-mounted terminal server in the method for binding the vehicle-mounted terminal and the application program according to any one of claims 1 to 3.

6. A method for binding a vehicle-mounted terminal and an application program, which is applied to an application program server, and comprises the steps executed by the application program server in the method for binding the vehicle-mounted terminal and the application program according to any one of claims 1 to 3.

7. The device for binding the vehicle-mounted terminal and the application program is applied to the vehicle-mounted terminal, and the vehicle-mounted terminal comprises:

a computer-readable storage medium having stored thereon a computer program;

a processor for executing the computer program to implement the steps performed by the in-vehicle terminal in the method for binding the in-vehicle terminal and the application program according to any one of claims 1 to 3.

8. The device for binding the vehicle-mounted terminal and the application program is applied to a vehicle-mounted terminal server, and the vehicle-mounted terminal server comprises:

a computer-readable storage medium having stored thereon a computer program;

a processor for executing the computer program to implement the steps performed by the vehicle terminal server in the method for binding the vehicle terminal and the application program according to any one of claims 1 to 3.

9. The device for binding the vehicle-mounted terminal and the application program is applied to an application program server, and the application program server comprises:

a computer-readable storage medium having stored thereon a computer program;

a processor for executing the computer program to implement the steps performed by the application server in the method for binding the vehicle-mounted terminal and the application according to any one of claims 1 to 3.