CN113645263B - Account binding method and device - Google Patents
Account binding method and device Download PDFInfo
- Publication number
- CN113645263B CN113645263B CN202010393751.XA CN202010393751A CN113645263B CN 113645263 B CN113645263 B CN 113645263B CN 202010393751 A CN202010393751 A CN 202010393751A CN 113645263 B CN113645263 B CN 113645263B
- Authority
- CN
- China
- Prior art keywords
- vehicle
- account
- background
- binding
- party application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000012795 verification Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides an account binding method and device, wherein the method comprises the following steps: the method comprises the steps that a vehicle factory background receives an account binding instruction initiated by a vehicle factory application for a third party application; the vehicle factory background sends a first binding request to a third party application background according to the account binding instruction, wherein the first binding request comprises a vehicle identification code; if the third party application background determines that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives a second binding request sent by the third party application background; the background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the second binding request so as to acquire binding result information; and the vehicle factory background sends the binding result information to the third party application background so that the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information. The invention can realize that the account numbers of the vehicle factory application and the account numbers of the third party application are mutually bound through the vehicle factory background and the third party application background.
Description
Technical Field
The invention relates to the technical field of vehicle internet of things interaction systems, in particular to an account binding method and an account binding device.
Background
In the existing vehicle-mounted system of the Internet of things of vehicles, an open source native Android operating system developed by Google corporation is generally used, and the open source property and the freedom of source codes provided by the Android operating system are mainly obtained, so that the vehicle-mounted system can directly apply various third-party open software or related applications, and interaction and user experience of the vehicle-mounted system of the Internet of things of vehicles are improved. For a user using a vehicle, besides applications developed by a vehicle manufacturer in daily use, applications of multiple third parties, such as music applications or shopping applications, are usually used, and multiple accounts are involved in multiple applications, so in the vehicle internet of things vehicle-mounted system, when the vehicle user needs to log in other third party applications to experience more scenes, such as listening to music or shopping, the user needs to log in according to accounts of the music applications and shopping applications, that is, the user needs to log in one by one according to different accounts, which brings inconvenience, not only affects user experience, but also may bring safety problems if the user operates in the driving process.
Disclosure of Invention
The invention aims to solve the technical problem that a vehicle internet of things system needs to log in one by one for different third party applications in the prior art, and provides an account binding method, an account binding device, computer equipment and a readable storage medium, so that account association and binding of a vehicle factory application account and a third party application account are realized.
The first aspect of the present invention provides an account binding method, which is applied to a third party application background, and the method includes:
the method comprises the steps that a third party application background receives a first binding request sent by a vehicle factory background, wherein the first binding request is sent after the vehicle factory background receives an account binding instruction for the third party application initiated by a vehicle end vehicle factory application, and the first binding request comprises a vehicle identification code;
the third party application background verifies whether the vehicle machine end is logged in the third party application account according to the vehicle identification code;
if the vehicle-mounted terminal logs in the third party application account, the third party application background sends a second binding request to the vehicle-mounted factory background, so that the vehicle-mounted factory background establishes a binding relationship between the third party application account and the vehicle-mounted factory application account according to the second binding request;
The third party application background receives the binding result information sent by the vehicle factory background;
and the third party application background establishes a binding relation between the third party application account and the vehicle factory application account according to the binding result information.
Optionally, the third party application background sends the second binding request to the vehicle factory background, including:
the third party application background acquires a third party application account identifier, and acquires a vehicle factory application account identifier corresponding to the vehicle identification code from the vehicle factory background;
the third party application background generates the second binding request, wherein the second binding request comprises the third party application account identifier and the vehicle factory application account identifier;
and the third party application background sends the second binding request to the vehicle factory background so that the vehicle factory background establishes a binding relation between the third party application account and the vehicle factory application account according to the third party application account identification and the vehicle factory application account identification.
Optionally, if the vehicle-mounted terminal does not log in the account of the third party application, the third party application background generates account login indication information, where the account login indication information is used to instruct the vehicle-mounted terminal vehicle factory application to display an account login interface of the third party application;
And the third party application background sends the account login indication information to the vehicle factory background, so that the vehicle factory background sends the account login indication information to the vehicle-machine-end vehicle factory application.
Optionally, the third party application background obtains a vehicle factory application account identifier corresponding to the vehicle identifier code from the vehicle factory background, including:
the third party application background sends the vehicle identification code and the authentication key to the vehicle factory background so that the vehicle factory background confirms the corresponding vehicle factory application account identification and verifies the authentication key according to the vehicle identification code, wherein the authentication key is distributed to the vehicle factory background when the third party application is accessed to the vehicle machine side;
and after the authentication key passes through the verification of the vehicle factory background, the third party application background receives the vehicle factory application account identification corresponding to the vehicle identification code sent by the vehicle factory background.
Optionally, after the third party application background establishes the binding relationship between the third party application account and the vehicle factory application account according to the binding result information, the method further includes:
the third party application background generates binding feedback information;
And the third party application background sends the binding feedback information to the third party application, so that the third party application displays that the account number of the vehicle-factory application and the account number of the third party application are bound according to the binding feedback information.
The second aspect of the present invention provides an account binding method, which is applied to a background of a vehicle factory, and the method includes:
the method comprises the steps that a vehicle factory background receives an account binding instruction which is initiated by a vehicle factory application at a vehicle machine end and aims at a third party application;
the vehicle factory background sends a first binding request to a third party application background according to the account binding indication, wherein the first binding request comprises a vehicle identification code;
if the third party application background determines that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives a second binding request sent by the third party application background;
the background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the second binding request so as to acquire binding result information;
and the vehicle factory background sends the binding result information to the third party application background so that the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information.
Optionally, the second binding request includes the third party application account identifier and the vehicle factory application account identifier of the vehicle machine side, and the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request, including:
and the background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the third party application account identification and the vehicle factory application account identification.
Optionally, the method further comprises:
if the third party application background determines that the vehicle machine end does not log in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives account number login indication information sent by the third party application background;
and the background of the automobile manufacturer sends the account login indication information to the automobile engine end automobile manufacturer application so that the automobile engine end automobile manufacturer application displays an account login interface of the third party application according to the account login indication information.
Optionally, the vehicle factory application account identifier of the vehicle machine side included in the second binding request is obtained through the following modes:
the vehicle factory background receives the vehicle identification code and the authentication key sent by the third party application background, wherein the authentication key is distributed by the vehicle factory background when the third party application is accessed to the vehicle machine end;
The background of the vehicle factory verifies whether the authentication key passes or not;
and if the authentication key passes through verification, the vehicle factory background sends the vehicle factory application account identification corresponding to the vehicle identification code to the third party application background.
Optionally, after the vehicle factory background establishes the binding relationship between the third party application account and the vehicle factory application account according to the second binding request to obtain the binding result information, the method further includes:
and the background of the garage sends the binding result information to the garage application so that the garage application displays that the account number of the garage application and the account number of the third party application are bound according to the binding result information.
A third aspect of the present invention provides an account binding apparatus, the apparatus being applied to a third party application background, including:
the first receiving module is used for receiving a first binding request sent by a vehicle factory background;
the verification module is used for verifying whether the vehicle machine end is logged in the third party application account according to the vehicle identification code;
the sending module is used for sending a second binding request to the vehicle factory background so that the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request;
The second receiving module is used for receiving the binding result information sent by the background of the vehicle factory;
and the account binding module is used for establishing a binding relationship between the third party application account and the vehicle-factory application account according to the binding result information.
A fourth aspect of the present invention provides an account binding apparatus, the apparatus being applied to a vehicle factory background, including:
the first receiving module is used for receiving an account binding instruction for a third party application initiated by the vehicle-end vehicle factory application;
the sending module is used for sending a first binding request to a third party application background according to the account binding indication, wherein the first binding request comprises a vehicle identification code;
the second receiving module is used for determining that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code in the third party application background and receiving a second binding request sent by the third party application background;
the account binding module is used for establishing a binding relation between the third party application account and the vehicle-factory application account according to the second binding request so as to acquire binding result information;
and the binding feedback module is used for sending the binding result information to the third party application background so that the third party application background establishes and establishes a binding relation between the third party application account and the vehicle factory application account according to the binding result information.
The account binding method provided by the invention can be applied to a vehicle factory background, wherein the vehicle factory background receives an account binding instruction for a third party application initiated by a vehicle machine end vehicle factory application; the vehicle factory background sends a first binding request to a third party application background according to the account binding instruction, wherein the first binding request comprises a vehicle identification code; if the third party application background determines that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives a second binding request sent by the third party application background; the background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the second binding request so as to acquire binding result information; and the vehicle factory background sends the binding result information to the third party application background so that the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information.
According to the account binding method provided by the invention, the account of the vehicle factory application and the account of the third party application can be mutually bound through the background of the vehicle factory and the background of the third party application, so that after the associated account binding is established, a vehicle user can log in one account to log in the vehicle factory application and the associated third party application, and the login is realized without repeated input and login, so that the use experience of the user and the safety of the driving process can be greatly improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an account binding system in an account binding method according to an embodiment of the present invention;
FIG. 2 is an interactive schematic diagram of an account binding process in an account binding method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a method for obtaining a second binding request in an account binding method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an account binding method for obtaining a vehicle-factory application account identifier according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an architecture of an account binding device applied to a third party application background according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of an architecture of an account binding device applied to a background of a vehicle factory according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the invention, shall fall within the scope of protection of the invention.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The embodiment of the invention provides an account binding method, which can be applied to an interaction environment of an account binding system shown in fig. 1, wherein the account binding system comprises a vehicle factory background, a third party application background and a vehicle machine end, wherein the vehicle machine end is provided with a vehicle factory application and a third party application, and it can be understood that the vehicle factory application can be an application independently developed by a vehicle manufacturer, and the third party application can comprise, but is not limited to, third party applications developed by other third party manufacturers, such as real-time communication, shopping or music and the like. The vehicle-mounted terminal and the vehicle factory background, the vehicle-mounted terminal and the third party application background and the vehicle factory background and the third party application background can be in communication connection. Note that, the communication connection manner may include, but is not limited to, connection manners such as a WIFI network, a 3G network, a 4G network, and even a 5G network, which are not limited herein.
The vehicle terminal may be a terminal device integrated on a vehicle, and in this embodiment, the vehicle terminal is illustrated by taking the terminal device integrated on the vehicle as an example; the vehicle factory background and the third party application background can be understood as mutually independent servers, and the vehicle factory background can be used for receiving information sent by the vehicle factory application and the third party application background on the vehicle machine side, or sending information to the vehicle factory application or the third party application background on the vehicle machine side, and the third party application background can be used for receiving information sent by the third party application and the vehicle factory background on the vehicle machine side, or sending information to the third party application and the vehicle factory background on the vehicle machine side, and the information can comprise information such as prompt information, instruction information or request information, and the like, and the information is not limited herein. In the embodiment of the present invention, the architecture in fig. 1 is merely illustrative, and in an actual device deployment scenario, a server may be implemented by an independent server or a server cluster formed by a plurality of servers, or a cloud server, and there may be multiple deployment modes for devices. For example, the server may be a server cluster, and may include at least two independent servers having different functions. Or servers of different functions may be integrated into one server. In the embodiment of the present invention, for convenience of explanation, the embodiment of the present invention may be explained by integrating servers with different functions in one server, that is, by integrating a vehicle factory background and a third party application background in one server, and specifically, as shown in fig. 2, the account binding method may include the following steps:
Step 01: the driver application initiates an account binding indication for the third party application.
In one application scenario, a vehicle user initiates an account binding instruction for a third party application through a vehicle factory application at a vehicle machine end, and the account binding instruction is used for indicating a vehicle factory background to initiate an account binding request to the third party application background. In an application scenario, a vehicle user may input an account binding request on a display panel on a vehicle side, that is, the vehicle user may click a third party application to be bound in a login interface of the vehicle side, specifically, for example, the current user may want to bind a certain music application account, and click a certain music application already accessed on the vehicle side, which is understood to be used only for example and not limited herein.
Step 02: the vehicle factory application initiates an account binding instruction to the vehicle factory background.
After the driver's application obtains the intention of the vehicle user to bind the account of the third party application, the driver's application sends an account binding instruction initiated by the vehicle user to the driver's background.
Step 03: and the vehicle factory background receives an account binding instruction initiated by the vehicle factory application at the vehicle machine end.
After the vehicle factory application initiates the account binding instruction to the vehicle factory background, the vehicle factory background can receive the account binding instruction initiated by the vehicle machine end vehicle factory application.
Step 04: and the vehicle factory background sends a first binding request to the third party application background according to the account binding instruction, wherein the first binding request comprises the vehicle identification code.
In one embodiment, after the vehicle factory background receives an account binding instruction for a third party application initiated by a vehicle end vehicle factory application, the vehicle factory background can send a first binding request to the third party application background, wherein the first binding request can comprise a vehicle identification code, and the third party application background can verify whether the current vehicle factory application logs in a third party application account needing binding or not through the vehicle identification code. In this embodiment, the vehicle identification code may be specifically obtained according to a vehicle identification number, which may be understood as a vehicle VIN code (Vehicle Identification Number), as those skilled in the art of vehicles may know that the VIN code is generally composed of a set of character strings including english and numerals, and is used to identify unique identity information of the vehicle, and correspondingly, may identify the manufacturer, engine, chassis serial number, other performance, and other data of the vehicle, so that different vehicle identification codes may be obtained according to VIN codes of different vehicles.
In one embodiment, the vehicle identification code may also be obtained by encrypting the MD5 algorithm, specifically, the MD5 encryption with a 32-bit capital may be performed on the basis of obtaining the vehicle VIN code or the vehicle identification code may be encrypted by another encryption algorithm, which is not limited herein. Therefore, the vehicle VIN code is encrypted to obtain the vehicle identification code, so that the vehicle identification code cannot be directly obtained through the vehicle VIN code, and the safety of the vehicle identification code can be improved.
Step 05: the vehicle factory background sends a first binding request to a third party application background.
Step 06: and the third party application background verifies whether the vehicle machine end is logged in the third party application account according to the vehicle identification code contained in the first binding request.
After the vehicle factory background sends the first binding request to the third party application background, the third party application background can receive the first binding request sent by the vehicle factory background, so that the third party application background verifies whether the vehicle machine end is logged in the third party application account according to the vehicle identification code.
In this embodiment, the third party application background needs to check whether the vehicle factory application has logged in the third party application account number to be bound, and it can be understood that the third party application background can check whether the vehicle factory application has logged in the third party application account number to be bound by verifying the vehicle identification code sent by the vehicle factory background, specifically, the third party application background can determine whether the vehicle factory application corresponding to the vehicle machine end has logged in the third party application account number according to the result information accepted by the accounterexchange service module in the program.
Step 07: after the third party application background verifies that the vehicle machine end is logged in the third party application account, the third party application background obtains the third party application account identification and the vehicle factory application account identification corresponding to the vehicle identification code, and a second binding request is generated.
After the third party application background verifies that the vehicle machine end has logged in the third party application account, the third party application background may acquire the third party application account identifier and the vehicle factory application account identifier corresponding to the vehicle identification code, and generate a second binding request, and in an embodiment, as shown in fig. 3, the method may specifically include the following steps:
step 071: and the third party application background acquires the third party application account identification, and acquires the vehicle factory application account identification corresponding to the vehicle identification code from the vehicle factory background.
In this embodiment, it may be understood that after the driver's application has logged into the third party application account, the third party application background may directly obtain the third party application account identifier bound to the driver's application.
The third party application background needs to obtain the vehicle factory application account identifier corresponding to the vehicle identifier code from the vehicle factory background, and in an embodiment, as shown in fig. 4, may specifically include:
step 0711: the third party application background sends the vehicle identification code and the authentication key to the vehicle factory background so that the vehicle factory background confirms the corresponding vehicle factory application account identification and verifies the authentication key according to the vehicle identification code, wherein the authentication key is distributed by the vehicle factory background when the third party application is accessed to the vehicle machine end.
In the step, a third party application background sends a vehicle identification code and an authentication key to a vehicle factory background, wherein the vehicle identification code is used for indicating the vehicle factory background to confirm a vehicle factory application account number identification corresponding to the vehicle identification code; and the authentication key is used for indicating the background of the vehicle factory to send the vehicle factory application account identification corresponding to the vehicle identification code to the third party application background after the background of the vehicle factory verifies that the authentication key passes.
Step 0712: and after the authentication key passes through the background verification of the vehicle factory, the third party application background receives the vehicle factory application account identification corresponding to the vehicle identification code sent by the background of the vehicle factory.
In one embodiment, the authentication KEY may be allocated to a vehicle factory background when the third party application accesses the vehicle machine end, and in this embodiment, it may be understood that, in a front stage of the third party application accessing the vehicle factory background at the vehicle machine end, the third party application background needs to apply for authentication to the vehicle factory background, where applying for the authentication process may generate the authentication KEY, in one embodiment, the authentication KEY may be understood as AK (i.e. app_key), and when the third party application background obtains the authentication KEY, the third party application background may request information from the vehicle factory background through the authentication KEY to obtain corresponding request information, for example, the third party application background may obtain the vehicle factory application account identifier corresponding to the vehicle identifier according to the authentication KEY. In this embodiment, after the authentication key is passed by the factory background authentication, the third party application background receives the factory application account identifier corresponding to the vehicle identification code sent by the factory background. It can be understood that in this embodiment, the vehicle-factory application account identifier corresponding to the vehicle identification code is obtained by sending the authentication key through the third-party application background, so that other unauthorized applications can be prevented from being illegally obtained, and further the security of the process of obtaining the data information is improved.
In one embodiment, after the third party application background obtains the corresponding vehicle factory application account identifier, the third party application background can also verify whether the corresponding account identifier information is legal, specifically, can check whether the obtained account identifier information is empty or accords with a preset rule, and if not, can terminate the process in advance.
Step 072: the third party application background generates a second binding request, wherein the second binding request comprises a third party application account identifier and a vehicle factory application account identifier.
In one embodiment, after the third party application background obtains the vehicle factory application account identifier corresponding to the vehicle identification code, the third party application background may generate a second binding request according to the third party application account identifier and the vehicle factory application account identifier, that is, the second binding request may include the third party application account identifier and the vehicle factory application account identifier.
Step 08: and the third party application background sends the second binding request to the vehicle factory background.
And the third party application background sends the second binding request to the vehicle factory background so that the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request.
In this embodiment, after the third party application background generates the second binding request, the third party application background may send the second binding request to the vendor background, and specifically, the third party application background may call the third party application account identifier and the vendor application account identifier in the program to initiate the second binding request through the accounterexchange manager module, and the vendor background may receive the second binding request sent by the third party application.
Step 09: and the background of the vehicle factory establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request.
After the second binding request is obtained, the driver's back office may establish a binding relationship between the third party application account and the driver's application account according to the second binding request, specifically, in one embodiment, the second binding request may include a third party application account identifier and a driver's application account identifier, where the third party application account identifier and the driver's application account identifier may be understood as a third party application account identifier ID and a driver's application account identifier ID, respectively, and then the driver's back office may establish a binding relationship between the third party application account and the driver's application account according to the third party application account identifier ID and the driver's application account identifier ID, specifically, the driver's back office may establish a binding relationship between the driver's account ID and the third party application account ID of 1 pair or even 1 pair of n and store the binding relationship into a database.
The second binding request may include, in addition to the third party application account ID and the vehicle-factory application account ID, information such as, but not limited to, a nickname and/or a head portrait.
In one embodiment, after the vehicle background acquires the corresponding vehicle factory application account identifier and the third party application account identifier, the vehicle factory background can verify whether the corresponding account identifier information is legal, specifically, can verify whether the acquired account identifier information is empty or accords with a preset rule, and if not, can terminate the flow in advance.
Step 10: and the vehicle factory background sends the binding result information to the third party application background.
After the binding relation between the third party application account and the vehicle factory application account is established in the vehicle factory background, the vehicle factory background can generate binding result information at the moment and send the binding result information to the third party application background, so that the binding relation between the third party application account and the vehicle factory application account is established by the third party application background according to the binding result information.
Step 11: and the third party application background establishes a binding relation between the third party application account and the vehicle factory application account according to the binding result information.
After the binding result information sent by the vehicle factory background is obtained, that is, the third party application background is known that the vehicle factory background has established a binding relationship, at this time, the third party application background can establish the binding relationship between the third party application account and the vehicle factory application account according to the binding result information, that is, the third party application background can establish the binding relationship between the third party application account and the vehicle factory application account according to the third party application account identification and the vehicle factory application account identification.
In one embodiment, the third party application background may establish a binding relationship between the vehicle-factory account ID and the third party application account ID in 1-to-1, or even in 1-to-n, and store the binding relationship in the database, and specifically, the third party application background may call the Save Relationship interface through the program portion to establish a binding relationship between the third party application account and the vehicle-factory application account. In the embodiment, the third party application background also establishes the binding relation between the third party application account and the vehicle factory application account according to the binding result information sent by the vehicle factory background, and stores the binding account information into the database, so that the information intercommunication between the vehicle factory application account and the third party application account associated account can be realized, namely the transmission of the associated account data is realized.
In the above embodiment, the account number of the vehicle factory application and the account number of the third party application can be established in a binding relationship through the vehicle factory background and the third party application background, so that after the mutual binding of the account number of the vehicle factory application and the account number of the third party application is established, a vehicle user can log in only one account number in the vehicle background or the third party application background, and the login of the vehicle factory application and the related third party application can be realized without repeated input login, and the use experience of the user and the safety of the driving process can be greatly improved. In addition, the account binding process is mainly integrated at the server end of the vehicle factory background and the third party application background, so that the workload of directly docking and developing at the vehicle machine end can be simplified, and the workload of directly developing at the vehicle machine end is reduced. In addition, in the process of acquiring the vehicle factory application account identification, an authentication key which is distributed in advance by the vehicle factory background when the third party application is accessed to the vehicle machine end is adopted, so that the transmission safety of the vehicle factory background and the third party application background interface can be improved; meanwhile, the authentication server does not need to be deployed again, and the workload of docking the corresponding vehicle factory background and the third party application background can be reduced.
Step 12: the factory background sends binding result information to the factory application.
In one embodiment, the vendor background establishes a binding relationship between the third party application account and the vendor application account according to the second binding request, and the vendor background may generate binding result information, where the binding result information is used to indicate that the vendor background has completed establishing the binding relationship between the third party application account and the vendor application account according to the second binding request, and the vendor background may send the binding result information to the vendor application, so that the vendor application displays that the vendor application account and the third party application account have been bound according to the binding result information. After the binding result is received by the vehicle factory application, the account binding result can be displayed on a bullet frame of the vehicle-mounted display screen, so that a vehicle user can timely know the account binding state in the background of the vehicle factory.
Step 13: the third party application background sends binding feedback information to the third party application.
In one embodiment, after the third party application background establishes the binding relationship between the third party application account and the vehicle-factory application account according to the binding result information, the third party application background may generate binding feedback information, where the binding feedback information is used to indicate that the third party application background has completed establishing the binding relationship between the third party application account and the vehicle-factory application account according to the binding result information, and the third party application background may send the binding feedback information to the third party application, so that the third party application displays that the vehicle-factory application account and the third party application account are already bound according to the binding feedback information, and specifically, may display the binding result on a frame of a vehicle-machine display screen, so that a vehicle user may be timely aware of an account binding state in the third party application background.
In one embodiment, if the vehicle terminal does not log in the account of the third party application, the third party application background generates account login indication information, where the account login indication information is used to indicate the vehicle terminal vehicle factory application to display an account login interface of the third party application, and the third party application background sends the account login indication information to the vehicle factory background, so that the vehicle factory background sends the account login indication information to the vehicle terminal vehicle factory application. Thus, the user can check whether the login is abnormal or whether the input login information is abnormal or not according to the login instruction information, or remind the user to re-login.
In one embodiment, if the third party application background determines that the vehicle terminal does not log in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives the account number login indication information sent by the third party application background; the background of the automobile manufacturer sends the account login indication information to the automobile manufacturer application at the automobile end so that the automobile manufacturer application at the automobile end displays an account login interface of the third party application according to the account login indication information, and therefore a user can be reminded to log in again on the current account login interface, and real-time interaction of information is improved.
In an embodiment, as shown in fig. 5, an account binding device is provided, where the device is applied to a third party application background, and includes:
the first receiving module 01 is used for receiving a first binding request sent by a vehicle factory background;
the verification module 02 is used for verifying whether the vehicle machine end is logged in the third party application account according to the vehicle identification code;
the sending module 03 is configured to send a second binding request to the garage background, so that the garage background establishes a binding relationship between the third party application account and the garage application account according to the second binding request;
the second receiving module 04 is used for receiving the binding result information sent by the background of the vehicle factory;
and the account binding module 05 is used for establishing a binding relationship between the third party application account and the vehicle factory application account according to the binding result information.
In one embodiment, as shown in fig. 6, an account binding device is provided, where the device is applied to a vehicle factory background, and includes:
the first receiving module 11 is configured to receive an account binding instruction for a third party application initiated by a vehicle factory application at a vehicle end;
a sending module 12, configured to send a first binding request to a third party application background according to an account binding instruction, where the first binding request includes a vehicle identifier;
The second receiving module 13 is configured to determine, in the background of the third party application, that the vehicle machine end has logged in an account of the third party application according to the vehicle identifier, and receive a second binding request sent by the background of the third party application;
the account binding module 14 is configured to establish a binding relationship between the third party application account and the vehicle-factory application account according to the second binding request, so as to obtain binding result information;
and the binding feedback module 15 is used for sending the binding result information to the third party application background so that the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information.
It should be noted that, the specific limitation of the account binding device may be referred to the limitation of the account binding method, and will not be described herein. All or part of the modules in the account binding device can be realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor of the computer device, or may be stored in software in a memory of the computer device, so that the processor may call and execute operations corresponding to the above modules.
In an embodiment, as shown in fig. 7, a computer device 6 is provided, which includes a memory 62, a processor 61, and a computer program 63 stored in the memory 62 and capable of running on the processor 61, where the processor executes the computer program 63 to implement steps of a third party application background or a vehicle factory background in the account binding method of the above embodiment, for example, steps 01-13 shown in fig. 2, or steps 071-072 shown in fig. 3, or steps 0711-0712 shown in fig. 4, which are not repeated herein. Alternatively, the processor 61 implements the functions of the modules in the embodiment of the account binding device when executing the computer program 63, for example, the functions of the first receiving module 01, the verification module 02, the sending module 03, the second receiving module 04, and the account binding module 05 applied to the third party application background device shown in fig. 5, or the functions of the first receiving module 11, the sending module 12, the second receiving module 13, the account binding module 14, and the binding feedback module 15 applied to the vehicle and factory background device shown in fig. 6, which are not repeated here.
In an embodiment, a readable storage medium is provided, where the readable storage medium stores a computer program 63, where the computer program 63 when executed by the processor 61 implements the steps of the third party application background or the vehicle factory background in the account binding method of the foregoing embodiment, for example, steps 01-13 shown in fig. 2, steps 071-072 shown in fig. 3, or steps 0711-0712 shown in fig. 4, which are not repeated herein. Alternatively, the processor 61 implements the functions of the modules in the embodiment of the account binding device when executing the computer program 63, for example, the functions of the first receiving module 01, the verification module 02, the sending module 03, the second receiving module 04, and the account binding module 05 applied to the third party application background device shown in fig. 5, or the functions of the first receiving module 11, the sending module 12, the second receiving module 13, the account binding module 14, and the binding feedback module 15 applied to the vehicle and factory background device shown in fig. 6, which are not repeated here.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal architecture of the apparatus is divided into different functional units or modules to perform all or part of the functions described above.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (10)
1. An account binding method, the method comprising:
the method comprises the steps that a third party application background receives a first binding request sent by a vehicle factory background, wherein the first binding request is sent after the vehicle factory background receives an account binding instruction for the third party application initiated by a vehicle end vehicle factory application, and the first binding request comprises a vehicle identification code;
The third party application background verifies whether the vehicle machine end is logged in the third party application account according to the vehicle identification code;
if the vehicle-mounted terminal logs in the third party application account, the third party application background sends a second binding request to the vehicle-mounted factory background, so that the vehicle-mounted factory background establishes a binding relationship between the third party application account and the vehicle-mounted factory application account according to the second binding request;
the third party application background receives the binding result information sent by the vehicle factory background;
the third party application background establishes a binding relation between the third party application account and the vehicle factory application account according to the binding result information;
the third party application background sending the second binding request to the vehicle factory background, comprising:
the third party application background acquires a third party application account identifier, and acquires a vehicle factory application account identifier corresponding to the vehicle identification code from the vehicle factory background;
the third party application background generates the second binding request, wherein the second binding request comprises the third party application account identifier and the vehicle factory application account identifier;
and the third party application background sends the second binding request to the vehicle factory background so that the vehicle factory background establishes a binding relation between the third party application account and the vehicle factory application account according to the third party application account identification and the vehicle factory application account identification.
2. The account binding method of claim 1, wherein,
if the vehicle-mounted terminal does not log in the account of the third-party application, the third-party application background generates account login indication information, wherein the account login indication information is used for indicating the vehicle-mounted terminal vehicle factory application to display an account login interface of the third-party application;
and the third party application background sends the account login indication information to the vehicle factory background, so that the vehicle factory background sends the account login indication information to the vehicle-machine-end vehicle factory application.
3. The account binding method according to claim 1 or 2, wherein the third party application background obtains a vehicle factory application account identifier corresponding to the vehicle identifier code from the vehicle factory background, including:
the third party application background sends the vehicle identification code and the authentication key to the vehicle factory background so that the vehicle factory background confirms the corresponding vehicle factory application account identification and verifies the authentication key according to the vehicle identification code, wherein the authentication key is distributed to the vehicle factory background when the third party application is accessed to the vehicle machine side;
and after the authentication key passes through the verification of the vehicle factory background, the third party application background receives the vehicle factory application account identification corresponding to the vehicle identification code sent by the vehicle factory background.
4. The account binding method according to any one of claims 1-2, wherein after the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information, the method further comprises:
the third party application background generates binding feedback information;
and the third party application background sends the binding feedback information to the third party application, so that the third party application displays that the account number of the vehicle-factory application and the account number of the third party application are bound according to the binding feedback information.
5. An account binding method, the method comprising:
the method comprises the steps that a vehicle factory background receives an account binding instruction which is initiated by a vehicle factory application at a vehicle machine end and aims at a third party application;
the vehicle factory background sends a first binding request to a third party application background according to the account binding indication, wherein the first binding request comprises a vehicle identification code;
if the third party application background determines that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives a second binding request sent by the third party application background;
The background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the second binding request so as to acquire binding result information;
the vehicle factory background sends the binding result information to the third party application background so that the third party application background establishes a binding relationship between the third party application account and the vehicle factory application account according to the binding result information;
the second binding request includes the third party application account identifier and the vehicle factory application account identifier of the vehicle machine side, and the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request, including:
and the background of the vehicle factory establishes a binding relation between the third party application account and the vehicle factory application account according to the third party application account identification and the vehicle factory application account identification.
6. The account binding method of claim 5, wherein the method further comprises:
if the third party application background determines that the vehicle machine end does not log in the account number of the third party application according to the vehicle identification code, the vehicle factory background receives account number login indication information sent by the third party application background;
And the background of the automobile manufacturer sends the account login indication information to the automobile engine end automobile manufacturer application so that the automobile engine end automobile manufacturer application displays an account login interface of the third party application according to the account login indication information.
7. The account binding method according to claim 5 or 6, wherein the second binding request includes a vehicle factory application account identifier of the vehicle machine side, and the account binding method is obtained by:
the vehicle factory background receives the vehicle identification code and the authentication key sent by the third party application background, wherein the authentication key is distributed by the vehicle factory background when the third party application is accessed to the vehicle machine end;
the background of the vehicle factory verifies whether the authentication key passes or not;
and if the authentication key passes through verification, the vehicle factory background sends the vehicle factory application account identification corresponding to the vehicle identification code to the third party application background.
8. The account binding method of claim 7, wherein after the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request to obtain binding result information, the method further comprises:
And the background of the garage sends the binding result information to the garage application so that the garage application displays that the account number of the garage application and the account number of the third party application are bound according to the binding result information.
9. An account binding device, wherein the device is applied to a third party application background, and comprises:
the first receiving module is used for receiving a first binding request sent by a vehicle factory background;
the verification module is used for verifying whether the vehicle machine end is logged in the third party application account according to the vehicle identification code;
the sending module is used for sending a second binding request to the vehicle factory background so that the vehicle factory background establishes a binding relationship between the third party application account and the vehicle factory application account according to the second binding request;
the second receiving module is used for receiving the binding result information sent by the background of the vehicle factory;
the account binding module is used for establishing a binding relationship between the third party application account and the vehicle-factory application account according to the binding result information;
the account binding device is configured to implement the method of claim 1.
10. An account binding device, wherein the device is applied to a car factory background, and comprises:
The first receiving module is used for receiving an account binding instruction for a third party application initiated by the vehicle-end vehicle factory application;
the sending module is used for sending a first binding request to a third party application background according to the account binding indication, wherein the first binding request comprises a vehicle identification code;
the second receiving module is used for determining that the vehicle machine end is logged in the account number of the third party application according to the vehicle identification code in the third party application background and receiving a second binding request sent by the third party application background;
the account binding module is used for establishing a binding relation between the third party application account and the vehicle-factory application account according to the second binding request so as to acquire binding result information;
the binding feedback module is used for sending the binding result information to the third party application background so that the third party application background establishes a binding relation between the third party application account and the vehicle factory application account according to the binding result information;
the account binding device is configured to implement the method according to claim 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010393751.XA CN113645263B (en) | 2020-05-11 | 2020-05-11 | Account binding method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010393751.XA CN113645263B (en) | 2020-05-11 | 2020-05-11 | Account binding method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113645263A CN113645263A (en) | 2021-11-12 |
| CN113645263B true CN113645263B (en) | 2024-04-16 |
Family
ID=78415440
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010393751.XA Active CN113645263B (en) | 2020-05-11 | 2020-05-11 | Account binding method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113645263B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105024975A (en) * | 2014-04-23 | 2015-11-04 | 腾讯科技（北京）有限公司 | Account number login method, device and system |
| CN107507309A (en) * | 2017-08-24 | 2017-12-22 | 东峡大通（北京）管理咨询有限公司 | A kind of shared bicycle method for unlocking and server |
| US9954867B1 (en) * | 2015-12-15 | 2018-04-24 | Amazon Technologies, Inc. | Verification of credential reset |
| CN109910783A (en) * | 2019-02-22 | 2019-06-21 | Oppo广东移动通信有限公司 | Control method for vehicle and Related product |
| CN110830418A (en) * | 2018-08-09 | 2020-02-21 | 北汽福田汽车股份有限公司 | Method and device for binding vehicle-mounted terminal and application program |
| WO2020087778A1 (en) * | 2018-11-02 | 2020-05-07 | 深圳壹账通智能科技有限公司 | Multiple system login method, apparatus, computer device and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239307B (en) * | 2013-06-08 | 2018-07-27 | 腾讯科技（深圳）有限公司 | user information storage method and system |
| US20150287068A1 (en) * | 2014-04-08 | 2015-10-08 | Group Cash Network Llc Limited Liability Company New York | System and method for pooling and converting purchase rewards to cash for end-users |
| US20190050551A1 (en) * | 2017-08-09 | 2019-02-14 | Facebook, Inc. | Systems and methods for authenticating users |
-
2020
- 2020-05-11 CN CN202010393751.XA patent/CN113645263B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105024975A (en) * | 2014-04-23 | 2015-11-04 | 腾讯科技（北京）有限公司 | Account number login method, device and system |
| US9954867B1 (en) * | 2015-12-15 | 2018-04-24 | Amazon Technologies, Inc. | Verification of credential reset |
| CN107507309A (en) * | 2017-08-24 | 2017-12-22 | 东峡大通（北京）管理咨询有限公司 | A kind of shared bicycle method for unlocking and server |
| CN110830418A (en) * | 2018-08-09 | 2020-02-21 | 北汽福田汽车股份有限公司 | Method and device for binding vehicle-mounted terminal and application program |
| WO2020087778A1 (en) * | 2018-11-02 | 2020-05-07 | 深圳壹账通智能科技有限公司 | Multiple system login method, apparatus, computer device and storage medium |
| CN109910783A (en) * | 2019-02-22 | 2019-06-21 | Oppo广东移动通信有限公司 | Control method for vehicle and Related product |
Non-Patent Citations (2)
| Title |
|---|
| Sara Bysko ; Jolanta Krystek.A Game Theory Approach for Solving the New Concept of Car Sequencing Problem.2019 5th International Conference on Control,Automation and Robotics.2019,全文. * |
| 汽车移动物联网通信平台的研究;吴斌;中国优秀硕士学位论文数据库;20131116;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113645263A (en) | 2021-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108810894B (en) | Terminal authorization method, device, computer equipment and storage medium | |
| CN107710672B (en) | Software distribution processing device, software distribution processing method, and vehicle | |
| CN107135218B (en) | Login state obtaining and sending method, credential configuration method, client and server | |
| CN111107073B (en) | Application automatic login method and device, computer equipment and storage medium | |
| CN103051630A (en) | Method, device and system for implementing authorization of third-party application based on open platform | |
| CN109474600B (en) | Account binding method, system, device and equipment | |
| CN109196891B (en) | Method, terminal and server for managing subscription data set | |
| CN113709695B (en) | Authorization method and system for vehicle use | |
| CN112800393B (en) | Authorization authentication method, software development kit generation method, device and electronic equipment | |
| CN108449315A (en) | Ask calibration equipment, method and the computer readable storage medium of legitimacy | |
| CN111159657A (en) | Application program authentication method and system | |
| CN112860778A (en) | Database management method, device, equipment and medium for desktop application program | |
| CN111565182A (en) | Vehicle diagnosis method and device and storage medium | |
| CN115643564A (en) | FOTA upgrading method, device, equipment and storage medium for automobile safety | |
| CN105791249A (en) | Third-party application processing method, device and system | |
| JP2017208859A (en) | SYSTEM, Vehicle, and Software Distribution Processing Method | |
| CN113645263B (en) | Account binding method and device | |
| CN111030816A (en) | Authentication method and device for access platform of evidence obtaining equipment and storage medium | |
| CN106326723A (en) | Method and device for certifying APK (Android Package) signature | |
| CN114666112B (en) | Communication authentication method, device, electronic equipment and storage medium | |
| JP6802279B2 (en) | Transmission of messages to be displayed to the display device of a car | |
| JP6672243B2 (en) | Data providing system, data providing device, data providing method, and data providing program | |
| CN111338674A (en) | Instruction processing method, device and equipment | |
| CN114640491A (en) | Communication method and system | |
| CN114553764A (en) | Automobile gateway route configuration system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |