Application program login method and device and electronic equipment

Abstract

The invention provides an application program login method and device and electronic equipment, and relates to the technical field of data processing. The method is applied to a scene of synchronous login of a system application program and a third-party application program of the vehicle-mounted equipment, the system application program and the third-party application program are installed on the vehicle-mounted equipment, and the method comprises the steps that a first account number of the system application program is acquired, and the first account number is an account number logged in by the system application program; a second account number is transmitted to the third-party application program through a first interface, the second account number and the first account number have a binding relation, and the second account number is the account number of the third-party application program; and logging in the second account number on the third-party application program. According to the method, after the user logs in the system account of the system application program, the user can quickly log in the third-party application program, synchronous login of the system application program of the vehicle-mounted equipment and the third-party application program is realized, the user operation is simple and convenient, and the experience feeling is improved.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and specifically, to a method, apparatus, and electronic device for application program login. Background Art

[0002] More and more vehicle-mounted devices integrate various third-party application programs, and each third-party application program has its own account system. The system application program of the vehicle-mounted device is not interoperable with these third-party application program account systems. If a user wants to log in to a third-party application program, they need to click on the third-party application program to log in. If the user wants to log in to multiple third-party application programs, they need to switch between different third-party applications multiple times to log in, which makes the user's operation cumbersome and reduces the experience.

[0003] Therefore, after the system application program on the vehicle-mounted device is logged in, how to achieve automatic login of the third-party application programs that need to be logged in on the vehicle-mounted device is an urgent problem to be solved. Summary of the Invention

[0004] Embodiments of this application provide a method, apparatus, and electronic device for application program login. This method enables the user to automatically synchronize and log in to the third application program bound to the first account after logging in to the first account of the system application program, thus avoiding the process of the user clicking on the third-party application program to log in again, making the user's operation simple and improving the experience.

[0005] In a first aspect, embodiments of this application provide a method for application program login. The method is applied to a vehicle-mounted device on which a system application program and third-party application programs are installed. The method includes:

[0006] Obtain a first account of the system application program, where the first account is the account logged in to the system application program;

[0007] Transmit a second account to the third-party application program through a first interface. The second account has a binding relationship with the first account, and the second account is the account of the third-party application program;

[0008] Log in to the second account on the third-party application program.

[0009] In a second aspect, embodiments of this application provide an apparatus for application program login, including:

[0010] An obtaining unit, configured to obtain a first account of the system application program, where the first account is the account logged in to the system application program;

[0011] A transceiver unit, configured to transmit the second account to the third-party application through a first interface, where the second account has a binding relationship with the first account, and the second account is an account of the third-party application;

[0012] A login unit, configured to log in to the second account on the third-party application.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0014] A processor, adapted to implement computer instructions; and,

[0015] A memory, storing computer instructions, and the computer instructions are adapted to be loaded and executed by the processor to perform the method of the first aspect above.

[0016] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are read and executed by a processor of a computer device, the computer device is caused to execute the method of the first aspect above.

[0017] In a fifth aspect, an embodiment of the present application provides a computer program product or a computer program, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method of the first aspect above.

[0018] In the above technical solution, after the user logs in to the first account on the system application of the in-vehicle device, the in-vehicle device obtains the second account of the third-party application bound to the first account, and transmits the second account to the third-party application through the first interface, and logs in to the second account on the third-party application, realizing that after the user logs in to the first account on the system application, the third application bound to the first account can be automatically synchronously logged in, thus avoiding the process of the user clicking to log in to the third-party application again, making the user operation simple and improving the experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 An optional schematic diagram of the system architecture involved in an embodiment of the present application;

[0020] Figure 2 A method for logging in to another third-party application using a third-party application;

[0021] Figure 3 A schematic flowchart of a method for logging in to an application provided by an embodiment of the present application;

[0022] Figure 4 Shows a schematic flowchart for determining whether to authorize an account binding process;

[0023] Figure 5 Is a schematic flowchart of the process after the user cancels the authorization for the second account to bind to the first account provided by an embodiment of the present application;

[0024] Figure 6 Is a schematic flowchart of a method for application program login provided by an embodiment of the present application;

[0025] Figure 7 Is a schematic flowchart of a method for a third - party application program to authorize account binding provided by an embodiment of the present application;

[0026] Figure 8 Shows a schematic structural block diagram of a system application program and a third - party application program;

[0027] Figure 9 Is a schematic block diagram of a device according to an embodiment of the present application;

[0028] Figure 10 Is a schematic block diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0029] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application.

[0030] Figure 1 Is an optional schematic diagram of a system architecture 100 related to an embodiment of the present application. As Figure 1 Shown, the system architecture 100 includes a vehicle 110, an in - vehicle device 120 installed on the vehicle 110, and a server 130 connected to the in - vehicle device 120. Among them, the in - vehicle device 120 and the server 130 can be directly or indirectly connected through wireless communication.

[0031] The in - vehicle device 120 is installed with a system application program and a plurality of third - party application programs. Among them, the system application program is where the vehicle system manages users. Its functions include login and registration of the vehicle system, password modification, obtaining user information, modifying user information, and some extended services. The system application program is, for example, the user center of the in - vehicle device.

[0032] The third - party application program refers to an application program that needs to be downloaded and installed, and can include connection application programs, such as email, instant messaging, navigation; business application programs, such as mobile banking services, bill payment; life application programs, health monitoring, digital reading and social networking, online shopping, etc. For example Figure 1 Shown email, WeChat, etc.

[0033] The system application and third-party applications will be further elaborated through a specific example below.

[0034] For example, if the service provider of in-vehicle device 120 is manufacturer A, the system application on the in-vehicle device can obtain some system services provided by manufacturer A. Third-party applications such as social software and video playback software downloaded and installed on the in-vehicle device 120 have service providers different from those of the system application. For example, the service provider of the social software is manufacturer B, and the service provider of the video playback software is manufacturer C. Each third-party application will have its own account system, and there is no intercommunication between the system application of the in-vehicle device and these third-party application account systems.

[0035] It should be understood that the system architecture 100 is only for illustration and does not impose any limitation on this application. Other in-vehicle devices may also be included in the system architecture 100.

[0036] It should be understood that the in-vehicle device may also be referred to as an in-vehicle terminal, and the in-vehicle terminal may include an on-board computer or an on-board unit (OBU), etc. The in-vehicle terminal may also be an application (APP) on the terminal, an APP on an intelligent rearview mirror, an APP or a mini-program on a mobile phone, etc., which is not limited herein.

[0037] It should also be understood that the above description of the in-vehicle terminal applies to terminal devices. For example, there are also the above problems with the system application and third-party applications on terminal devices. Each third-party application will have its own account system, and there is no intercommunication between the system application of the terminal device and these third-party application account systems.

[0038] The terminal device (user equipment, UE) can be a wireless terminal device or a wired terminal device. The wireless terminal device can refer to a device with wireless transceiver functions. The terminal device can be a mobile phone, a tablet (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an intelligent voice interaction device, an intelligent household appliance, an in-vehicle terminal, an aircraft, etc., which is not limited herein.

[0039] A client can be deployed on the terminal device. The client can run on the terminal device in the form of a browser or in the form of an independent APP. The specific presentation form of the client is not limited here.

[0040] The server 130 can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The server can also become a node of the blockchain.

[0041] There can be one or more servers. When there are multiple servers, at least two servers are used to provide different services, and / or at least two servers are used to provide the same service, such as providing the same service in a load balancing manner. The embodiments of the present application do not limit this.

[0042] In the above system 100, when a user wants to log in to a third-party application, they need to click on the third-party application to log in. If the user wants to log in to multiple third-party applications, they need to switch logins multiple times between different third-party applications, making the user's operation cumbersome and reducing the experience.

[0043] Currently, in the prior art, different third-party applications can be associated based on the same account. For example, a third-party application for social use can be used to log in to a third-party application for shopping. The following describes this method. As Figure 2 shown, Figure 2 A method 200 for logging in to a third-party application B using a third-party application A is shown. First, the user opens the login interface of the client of the third-party application B on the mobile phone. Among the login methods, the user can select "Log in using application A" to trigger the application A login mode and execute the following steps.

[0044] Step 210, the client of the third-party application B sends information requesting a QR code to the background of the application A.

[0045] The information requesting the QR code is a link obtained on the open platform of the application A to generate a login QR code.

[0046] Step 220, the background of the application A generates a QR code according to the received information requesting the QR code.

[0047] The background of the application A adds necessary request parameters to the QR code link according to the access requirements of the open platform to generate a corresponding login QR code.

[0048] Step 230, the client of the third-party application B scans the QR code.

[0049] Step 240, complete the login of the third-party application B on the mobile phone.

[0050] On a third-party application that requires login, display the login QR code of Application A. After scanning the login QR code and completing the login process on the mobile device, the QR code interface will be redirected to a specified target link. This specified target link also requires filling in the link parameters for generating the login QR code so that it will jump to the specified page of the third-party application after successful login.

[0051] Step 250, the background of Application A sends the login status to the client. The login status means that the third-party application has completed login using Application A.

[0052] Step 260, the client of the third-party Application B receives and saves the login status.

[0053] In the prior art, although it is possible to use the account of one third-party application to log in to other third-party applications, it still cannot solve the problem that in the case of multiple third-party applications, after logging in to the system account of the system application, it is impossible to quickly log in to the third-party application.

[0054] Therefore, the present application proposes a method for logging in to an application. This method can be applied to the login of the system application and third-party applications of in-vehicle devices, realizing that in the case of multiple third-party applications, after the user logs in to the system account of the system application, they can quickly log in to the third-party application, achieving the synchronous login of the system application and third-party applications of the in-vehicle device, avoiding the process of the user having to switch between different third-party applications multiple times when wanting to log in to multiple third-party applications, making the user operation simple and improving the experience.

[0055] The following describes the solution provided in the embodiments of the present application with reference to the accompanying drawings.

[0056] Figure 3 It is a schematic flowchart of a method 300 for logging in to an application provided in an embodiment of the present application. This method 300 can be applied to the scenario of synchronous login of the system application and third-party applications of an in-vehicle device, and the system application and the third-party application are installed on the in-vehicle device. Method 300 can be executed by any electronic device with data processing capabilities. For example, this electronic device can be implemented as a server or a computer. Hereinafter, it is described by taking this electronic device as an in-vehicle device as an example. As Figure 3 shown, method 300 can include steps 310 to 330.

[0057] S310, log in to the first account of the system application on the in-vehicle device. The first account is the account for logging in to the system application.

[0058] S320, the in-vehicle device transmits a second account to a third-party application through a first interface. The second account has a binding relationship with the first account, and the second account is the account of the third-party application.

[0059] S330, the in-vehicle device logs in to the second account on the third-party application.

[0060] In this method 300, after the user logs in to the first account on the system application of the in-vehicle device, the in-vehicle device obtains the second account of the third-party application bound to the first account, and transmits the second account to the third-party application through the first interface, and logs in to the second account on the third-party application, realizing that after the user logs in to the first account on the system application, the third application bound to the first account can be automatically synchronously logged in, thus avoiding the process of the user clicking to log in to the third-party application again, making the user operation simple and improving the experience.

[0061] The method 300 will be described in detail step by step below.

[0062] In step S310, the in-vehicle device obtains the first account of the system application. The first account is the account logged in to the system application, including:

[0063] The user logs in to the first account on the system application of the in-vehicle device;

[0064] The in-vehicle device detects the first account logged in to the system application.

[0065] Optionally, before step S320 where the in-vehicle device transmits the second account to the third-party application through the first interface, it further includes:

[0066] The in-vehicle device obtains the first relationship table stored locally. The first relationship table stores the binding relationship between the first account and the second account; or,

[0067] The in-vehicle device sends a request message to the system server of the in-vehicle device. The request message is used to request the system server to find the account of the third application bound to the first account;

[0068] The in-vehicle device receives a reply message sent by the system server. The reply message includes the second account bound to the first account.

[0069] Optionally, the second account can be one account or multiple accounts. When the first account is bound to one second account, the second account obtained by the in-vehicle device is one; when the first account is bound to multiple second accounts, the second accounts obtained by the in-vehicle device are multiple.

[0070] If the first account of the in-vehicle device system application is bound to the second accounts of multiple third-party applications, then, after logging in to the first account in the system application, the second accounts of multiple third-party applications can be obtained, so that multiple third-party applications can be logged in simultaneously, avoiding the process of having to switch between different third-party applications multiple times when the user wants to log in to multiple third-party applications, making the user operation simple and improving the experience.

[0071] Optionally, the second account includes indication information for indicating the third-party application logged in by the second account.

[0072] Optionally, when the second account does not include indication information, when the in-vehicle device obtains the second account bound to the first account, the indication information for indicating the third-party application logged in by the second account needs to be obtained simultaneously.

[0073] For example, the second account includes indication information, and only the binding relationship between the first account and the second account is saved in the first relationship table; the second account does not include indication information, and the binding relationship between the first account and the second account is saved in the first relationship table, and at the same time, the indication information of the third-party application logged in by the second account is saved.

[0074] Optionally, when the in-vehicle device does not obtain the second account bound to the first account, it further includes:

[0075] On the management interface of the system application, display the third-party applications installed on the in-vehicle device;

[0076] Determine the third-party application selected by the user to be bound;

[0077] Display the login interface of the third-party application;

[0078] Obtain the login account of the user logging in to the third-party application as the second account;

[0079] Establish the binding relationship between the first account and the second account.

[0080] Optionally, establishing the binding relationship between the first account and the second account includes:

[0081] The in-vehicle device obtains the third-party application that the user needs to log in to;

[0082] The in-vehicle device obtains the login interface of the third-party application through the second interface;

[0083] The in-vehicle device logs in to the third-party application, and the login account of the third-party application is the second account;

[0084] After the third-party application completes the login, the in-vehicle device transmits the login status of the second account to the system application through the third interface;

[0085] The in-vehicle device establishes a binding relationship between the first account and the second account in the system application;

[0086] The in-vehicle device sends a first message to the system server of the in-vehicle device, and the first message is used to instruct the system server to record the binding relationship between the first account and the second account.

[0087] Optionally, the in-vehicle device can use multiple login methods to log in to the third-party application, such as using the account password login method, the mobile phone number verification code login method, the QR code login, and other methods. Among them, the account, mobile phone number, and QR code can all be the second account.

[0088] It should be understood that the second interface is an interface for the system application to launch the third-party application for login. Its function is communication between different processes, and the specific implementation of this interface can be defined by those skilled in the art.

[0089] Optionally, after the in-vehicle device logs in to the third-party application, it further includes:

[0090] On the login interface of the third-party application, display a first pop-up message, and the first pop-up message is used to prompt the user whether to authorize the binding process initiated by the system application;

[0091] When the user authorizes the binding process initiated by the system application, the in-vehicle device transmits the login status of the second account to the system application through the third interface.

[0092] Optionally, after the in-vehicle device logs in to the third-party application, it further includes:

[0093] On the login interface of the third-party application, display a first pop-up message, and the first pop-up message is used to prompt the user whether to authorize the binding process initiated by the system application;

[0094] When the user does not authorize the binding process initiated by the system application, transmit a message indicating authorization failure to the system application through the third interface.

[0095] It should be understood that the second interface is an interface for the third-party application to call back the system application. Its function is communication between different processes, and the specific implementation of this interface can be defined by those skilled in the art.

[0096] Specifically, the above two embodiments mainly describe the process in which the user initiates an account binding process to the third-party application through the first interface in the system application of the in-vehicle device, and the user needs to determine whether to bind in the third-party application. For example Figure 4As shown Figure 4 shows a schematic flowchart for determining whether to authorize an account binding process. Specifically, it includes the following steps:

[0097] S410, the user actively initiates an account binding process from the system application of the in-vehicle device to the third-party application through the first interface;

[0098] S420, when the third-party application receives an account binding request, it needs to log in to the third-party application. The login account of the third-party application is the second account, and the in-vehicle device needs to determine whether the second account has been authorized for binding;

[0099] S430, if the authorization process for the second account has not been executed, the third-party application displays a first pop-up message, which is used to prompt the user whether to authorize the second account binding process initiated by the system application;

[0100] S440, if the user does not authorize, close the first pop-up message, terminate the second account binding process, and return the identification information of authorization failure to the system application through the third interface.

[0101] S450, after the user confirms authorization, the second account can be bound. Each time the user initiates an account binding from the system application of the in-vehicle device through the first interface, if not authorized, an authorization window needs to be popped up.

[0102] S460, when the third-party application receives an account binding request and determines that it has been authorized, it continues with the binding process.

[0103] S470, the in-vehicle device continues the binding process in the third-party application. When the third-party application completes the login, the in-vehicle device transmits the login status of the second account to the system application through the third interface; the in-vehicle device establishes a binding relationship between the first account and the second account in the system application; the in-vehicle device sends a first message to the system server of the in-vehicle device, and the first message is used to instruct the system server to record the binding relationship between the first account and the second account.

[0104] In step S320, the in-vehicle device transmits the second account to the third-party application through the first interface.

[0105] After the in-vehicle device obtains the second account bound to the first account, it transmits the second account to the third-party application through the first interface.

[0106] It should be understood that the first interface is an interface for the system application to transmit the second account to the third-party application. Its function is inter-process communication, and the specific implementation of this interface can be defined by those skilled in the art.

[0107] In step S330 , the in-vehicle device logs in to the second account on the third-party application.

[0108] The vehicle-mounted device transmits the second account to the third-party application through the first interface. After the third-party application obtains the second account, it logs in to the second account to achieve synchronous login of the third application and the system application.

[0109] Optionally, the method further includes:

[0110] In the third-party application, the authorization information of the account of the third-party application is recorded, and the authorization information includes the account of each third-party application that is authorized by the user to bind the account of the system application.

[0111] Optionally, the authorization information also includes the authorization period of the third-party application account.

[0112] Optionally, within a third-party application, authorization information of multiple accounts of the third-party application may be recorded, and the authorization period of each account of the third-party application may be the same or different.

[0113] For example, the authorization period may be measured in months, such as 3 months, or in days, such as 90 days.

[0114] Optionally, the method further includes:

[0115] When the authorization period of the second account in the authorization information reaches a preset value, a second pop-up message is displayed in the third-party application, and the second pop-up message is used to prompt the user whether to continue to authorize the second account to be bound to the first account of the system application.

[0116] Specifically, after logging in to open a third-party application or using a third-party application, if the authorization period of the second account has expired, a second pop-up message will be displayed, asking the user whether to continue to authorize the second account to bind to the first account of the system application. If the user continues to authorize, the binding status will be maintained and the authorization period will be updated. If the user does not authorize, a message can be sent to the system application through the third interface to unbind the first account from the second account. After the user cancels the authorization, when the system application initiates the binding again, the authorization mechanism process needs to be repeated.

[0117] It should be understood that after logging in to open a third-party application or while using a third-party application, if it is found that the authorization period of the second account has expired, a second pop-up message will be displayed, asking the user whether to continue to authorize the second account to bind to the first account of the system application. If the user does not authorize, the authorization status of the second account will be cleared in the authorization information, and it does not mean logging out of the third application.

[0118] Optionally, the method further includes:

[0119] When the user cancels the authorization for the second account to bind to the first account, the binding relationship between the first account and the second account is released in the system application;

[0120] A fourth message is sent to the system server, where the fourth message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

[0121] Optionally, the method further includes:

[0122] After the user cancels the authorization to bind the second account to the first account, if the system application again transmits the second account to the third application through the third interface for login, the third application needs to display the first pop-up message again. The first pop-up message is used to prompt the user whether to authorize the binding process initiated by the system application.

[0123] Specifically, for a deauthorized second account, if the system application again transmits the second account to a third application through a third interface for login before reauthorization, a pop-up window will be displayed again to prompt the user whether to authorize.

[0124] In order to understand the above embodiment more clearly, Figure 5 , specifically explain the process after the user cancels the authorization to bind the second account to the first account, such as Figure 5 As shown, the specific steps include:

[0125] S510, in the third application, the user cancels the authorization for the second account to be bound to the first account;

[0126] S520, the in-vehicle device clears the authorization status information of the second account from the authorization information in the third application;

[0127] S530, the vehicle-mounted device releases the binding relationship between the second account and the first account through the system application via the third interface;

[0128] S540, the vehicle-mounted device releases the binding relationship between the second account and the first account in the system application;

[0129] S550, the vehicle-mounted device transmits the second account to the third application through the third interface again through the system application for login;

[0130] S560: The vehicle-mounted device does not find the authorization information of the second account in the third application program, and the switching fails.

[0131] S570: The vehicle-mounted device transmits the switching failure information to the system application via the third interface.

[0132] Optionally, the method further includes:

[0133] The in-vehicle device receives a request message for the first account to log out of the system application;

[0134] The in-vehicle device obtains a second account bound to the first account, where the second account is an account of a third-party application;

[0135] The in-vehicle device transmits the second account to the third-party application through a fourth interface;

[0136] The in-vehicle device logs out of the second account on the third-party application.

[0137] When the user logs out of the system application on the in-vehicle device, the in-vehicle device obtains the second account bound to the first account, transmits the second account to the third-party application through the fourth interface, and logs out of the second account on the third-party application, realizing the synchronous logout of the system application and the third-party application.

[0138] It should be understood that the fourth interface is an interface for the system application to transmit the logout to the third-party application. Its function is communication between different processes, and the specific implementation of this interface can be defined by those skilled in the art.

[0139] Optionally, the method further includes:

[0140] When the information of the second account changes, the account information change information is transmitted to the system application through a third interface;

[0141] A second message is sent to the system server of the in-vehicle device. The second message includes the account information change information, and the second message is used for the system server to update the information of the second account.

[0142] Specifically, when there is a change in the status of the second account in the third-party application, such as whether the login state has expired or whether the membership status has changed, it will be notified to the system application through the third interface, and then the system application sends a second message to the system server for the system server to update the changed information of the second account.

[0143] Optionally, the method further includes:

[0144] When the second account of the third application logs out, the in-vehicle device transmits a message that the second account has logged out to the system application through the third interface;

[0145] The in-vehicle device unbinds the binding relationship between the first account and the second account in the system application;

[0146] The in-vehicle device sends a third message to the system server, and the third message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

[0147] Specifically, when the second account logs out of the third application, the login state of the second account in the third application is cleared. After the clearance, the vehicle-mounted device transmits a message indicating the logout of the second account to the system application through the third interface. The vehicle-mounted device unbinds the binding relationship between the first account and the second account in the system application and deletes the second account. The vehicle-mounted device sends a third message to the system server, and the third message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

[0148] When the vehicle-mounted device establishes a binding relationship between the first account and the second account in the system application, if the user does not log in to the system application but opens a third-party application, the third-party application can obtain the third-party application account bound to the system application and log in.

[0149] Optionally, the method further includes:

[0150] The vehicle-mounted device runs a third-party application, and the third-party application is not logged in to any account.

[0151] The vehicle-mounted device obtains the second account of the third-party application bound to the first account logged in to the system application.

[0152] The vehicle-mounted device logs in to the second account of the third-party application bound to the first account on the third-party application.

[0153] Optionally, the method further includes:

[0154] The vehicle-mounted device runs a third-party application, and the third-party application is logged in to a third account.

[0155] The vehicle-mounted device obtains the second account of the third-party application bound to the first account logged in to the system application.

[0156] The vehicle-mounted device determines whether the second account bound to the first account is the same as the third account.

[0157] When the second account is different from the third account, a third pop-up message is displayed, and the third pop-up message is used to prompt the user whether to switch to the second account.

[0158] The above two embodiments respectively describe the process in which if the user does not log in to the system application but opens a third-party application, the third-party application can obtain the third-party application account bound to the system application and log in.

[0159] Specifically, if the account information read by the in-vehicle device from the system application is empty, no processing is performed; if the in-vehicle device reads the bound account information from the system application and it is inconsistent with the account information in the third-party application, the user will be prompted whether to switch to the bound account information; if the in-vehicle device reads the bound account information from the system application and it is consistent with the account information in the third-party application, no processing is performed; if the account information in the third-party application is empty, that is, the user only opens the third-party application but does not log in to the third-party application, then it directly switches to the bound account read by the in-vehicle device from the system application.

[0160] The above method 300 describes the process of initiating synchronous login by the system application of the in-vehicle device. The process of initiating synchronous login can also be performed within the third-party application. The process of initiating synchronous login within the third-party application is not specifically described below.

[0161] Figure 6 FIG. 600 is a schematic flowchart of a method 600 for application program login provided by an embodiment of the present application. The method 600 is applied to the scenario of synchronous login between the system application and the third-party application of the in-vehicle device, and the system application and the third-party application are installed on the in-vehicle device. The method 600 can be executed by any electronic device with data processing capabilities. For example, the electronic device can be implemented as a server or a computer. The following takes the in-vehicle device as an example for description. As Figure 6 shown, the method 600 may include steps 610 to 640.

[0162] S610, the in-vehicle device logs in to the second account within the third-party application. The second account is bound to the first account, and the first account is the login account of the application center of the in-vehicle device.

[0163] S620, the in-vehicle device transmits the second account to the system application through the first interface within the third-party application.

[0164] S630, the system application of the in-vehicle device receives the second account and obtains the first account bound to the second account;

[0165] S640, the in-vehicle device logs in to the first account within the system application.

[0166] In this method 600, the user logs in to the second account within a third-party application. The in-vehicle device transmits the second account to the system application through a first interface within the third-party application. After the system application of the in-vehicle device receives the second account, the in-vehicle device obtains the first account bound to the second account, and the in-vehicle device logs in to the first account in the system application. This realizes that after the user logs in to the second account in the third application, the system application bound to the second account can be automatically synchronized for login, thus avoiding the process of the user clicking to log in to the system application again, making the user operation simple and improving the experience.

[0167] Optionally, this method further includes:

[0168] Within the third-party application, log in to the second account, and the second account is not bound to the first account.

[0169] The in-vehicle device displays a fourth pop-up message within the third-party application, and the fourth pop-up message is used to prompt the user whether to authorize the system application to bind the second account.

[0170] When the user authorizes the binding of the second account, the in-vehicle device transmits the second account to the system application through the first interface.

[0171] Specifically, if the second account logged in within the third-party application has not been authorized for binding, after the second account is logged in within the third-party application, the in-vehicle device displays a fourth pop-up message within the third-party application, and the fourth pop-up message is used to prompt the user whether to authorize the system application to bind the second account. When the user authorizes the binding of the second account, the in-vehicle device transmits the second account to the system application through the first interface. The specific process of the third-party application authorizing account binding is as Figure 7 shown Figure 7 This is a schematic flowchart of a method 700 for authorizing account binding by a third-party application provided by an embodiment of the present application. Method 700 includes the following steps:

[0172] S710, the in-vehicle device logs in to the second account within the third-party application;

[0173] S720, the in-vehicle device determines whether the second account is authorized for binding;

[0174] S730, if the second account is not authorized, the in-vehicle device determines whether the fourth pop-up message has been displayed, and the fourth pop-up message is used to prompt the user whether to authorize the system application to bind the second account;

[0175] S740, if the second account has been authorized, then perform step S770 to transmit the second account to the system application;

[0176] S750, when the fourth pop-up message has not been displayed before, display the fourth pop-up message;

[0177] If the fourth pop-up message has been displayed before, if the user wants to authorize at this time, they can go to the settings to enable authorization. That is to say, the fourth pop-up message of the authorization box only pops up once and will not pop up again after cancellation, so as to avoid popping up the authorization window every time the user logs in to a third-party application, which affects the user experience.

[0178] S760, the user authorizes the system application to bind the second account;

[0179] S770, transmit the second account to the system application;

[0180] S780, record the authorization information of the second account.

[0181] Optionally, the method further includes:

[0182] When the user does not authorize to bind the second account, a prompt is displayed on the interface of the third-party application. The prompt is used to prompt the user that when they need to authorize to bind the second account, they can authorize to bind the second account in the system settings center of the in-vehicle device.

[0183] After the user cancels the authorization, a prompt is displayed, prompting the user that if they want to authorize, they can go to the settings to enable authorization. That is to say, the authorization box only pops up once and will not pop up again after cancellation, so as to avoid popping up the authorization window every time the user logs in to a third-party application, which affects the user experience.

[0184] Optionally, the method further includes:

[0185] Run a third-party application, and the third-party program has no account logged in;

[0186] Obtain the second account of the third-party application bound by the system application;

[0187] On the third-party application, log in to the second account of the third-party application bound by the system application.

[0188] The login method of the application provided by the embodiment of the present application can also be applied to the scenario of multiple display screens of a vehicle-mounted device. When there are multiple screens on the vehicle-mounted device, the same account can be quickly logged in to the same application on all screens automatically, reducing the operation of logging in to each application one by one every time and reducing the repeated login operations on multiple screens. For example, there is a first display screen and a second display screen on the vehicle-mounted device. The second display screen is at least one display screen, the first display screen is the main display screen and can control other display screens, and the second display screen is the auxiliary display screen. The first display screen can control the second display screen to synchronize the information of the first display screen. The content displayed on the first display screen and the second display screen may be the same or different. When the content displayed on the first display screen and the second display screen is the same, for example, the first display screen includes a system application and a third-party application A, and the second display screen also includes a system application and a third-party application A. When the user synchronously logs in to the system application and the third-party application A on the first display screen, the first display screen can trigger the second display screen to synchronously log in to the system application and the third-party application A on the second display screen. When the content displayed on the first display screen and the second display screen is different, for example, the first display screen includes a system application and a third-party application A, and the second display screen also includes a third-party application A. When the user synchronously logs in to the system application and the third-party application A on the first display screen, the first display screen can trigger the second display screen to synchronously log in to the third-party application A on the second display screen.

[0189] The above methods 300 and 600 respectively describe the processes of how a vehicle-mounted device initiates synchronous login in a system application and a third-party application. Whether the vehicle-mounted device initiates synchronous login in a system application or in a third-party application, it is required that the system application and the third-party application can communicate with each other. The following specifically describes the process of how the system application and the third-party application communicate.

[0190] The system application can integrate a software development kit (SDK). The SDK is used to provide interfaces such as account binding, account switching, logout, and authorization status synchronization; the third-party application provides services such as account binding, account switching, logout, and authorization status synchronization to the system application. As Figure 8 shown, Figure 8 shows a schematic structural block diagram of the system application and the third-party application. In Figure 8Among them, the application center includes an account binding interface, an account switching interface, a logout interface, and an authorization status synchronization interface. The application center integrates the SDK. In the embodiments of this application, the application center can also be referred to as the client. The third-party application provides account binding services, account switching services, logout services, and authorization status synchronization services to the system application. In the embodiments of this application, the third-party application can also be referred to as the server.

[0191] The Binder mechanism (Binder is a way of inter-process communication in the Android system) is used for communication between the system application and the third-party application. The communication interface is defined as the AIDL type to facilitate interface calls and data interaction between the system application and the third-party application using the Binder mechanism.

[0192] Same login and same logout involve three operations: account login, logout, and account switching. Therefore, corresponding interfaces are defined in the system application interface definition:

[0193] Account login interface: login(), directly pull up the login QR code, such as the second interface in the above text;

[0194] Logout interface: logout(String vuid), clear the logged-in account information, such as the fourth interface in the above text.

[0195] Account switching interface: switchAccount(KTAccountInfo newAccout,KTAccountInfooldAccout), switch to the new account and renew in the background, such as the first interface in the above text.

[0196] After the third-party application completes the same login and same logout business process, it also needs to call back the result to the system application. Therefore, an additional result callback interface is required:

[0197] Same login and same logout result callback interface: setAccountListener(in IKTAccountListenerAidllistener), such as the third interface in the above text.

[0198] The specific AIDL interface definition is as follows:

[0199] The system application calls the AIDL interface of the third-party application:

[0200] interface IKTAccountRemoteAidl{

[0201] void setAccountListener(in IKTAccountListenerAidl listener);

[0202] void login();

[0203] void logout(in String vuid);

[0204] void switchAccount(inout KTAccountInfo newAccout,inout KTAccountInfo oldAccout);

[0205] }

[0206] The AIDL interface for third - party applications to call back the system application:

[0207] interface IKTAccountListenerAidl{

[0208] void onLoginCallback(boolean success,inout KTAccountInfo accout);

[0209] void onAccountChanged(inout KTAccountInfo accout);

[0210] void onLogoutCallback(String vuid);

[0211] void onAuthChanged(int authStatus,String vuid);

[0212] }

[0213] When the system application SDK is initialized, it needs to establish a Binder channel with the third - party application through the binder mechanism. After the channel is established, it is necessary to obtain the AIDL instance provided by the third - party application. This instance will provide the ADIL business object for logging in and out. After obtaining the ADIL business object for logging in and out of the third - party application, this AIDL object is actually the AIDL interface (IKTAccountRemoteAidl) object for the system application to call the third - party application mentioned above. Through this AIDL object, the interface services for logging in and out of the third - party application can be called.

[0214] If the establishment of the Binder channel fails, retry can be performed, with an interval of 5000ms for each retry, and a total of 6 retries.

[0215] The SDK mainly encapsulates the business interfaces for logging in and out externally to the system application, and callbacks the account information and account status obtained by the SDK through the AIDL interface to the system application through the external interface of the SDK.

[0216] The external business interfaces of the SDK are as follows:

[0217] public interface IKTAccountService{

[0218] / **

[0219] * Register an account detector

[0220] * @param listener Account detector

[0221] * /

[0222] void registerAccountListener(IKTAccountListener listener);

[0223] / **

[0224] * Deregister an account detector

[0225] * @param listener Account detector

[0226] * /

[0227] void unregisterAccountListener(IKTAccountListener listener);

[0228] / **

[0229] * Open the QR code login binding interface

[0230] * This method will verify the execution thread. Do not call it on the main thread, otherwise an exception will be thrown

[0231] * /

[0232] boolean login()throws IllegalThreadStateException;

[0233] / **

[0234] * Logout and unbind

[0235] * This method verifies the executing thread. Do not call it on the main thread, otherwise an exception will be thrown.

[0236] * @param vuid The vuid to be unbound.

[0237] * /

[0238] boolean logout(String vuid) throws IllegalThreadStateException;

[0239] / **

[0240] * Switch the bound account

[0241] * This method verifies the executing thread. Do not call it on the main thread, otherwise an exception will be thrown.

[0242] * @param account The new account to switch to.

[0243] * /

[0244] Boolean switchAccount(KTAccount account) throws IllegalThreadStateException;

[0245] / **

[0246] * Get the currently bound account

[0247] * @return The currently bound account

[0248] * /

[0249] KTAccount getAccount();

[0250] }

[0251] The callback interface of the SDK to the outside is as follows:

[0252] public interface IKTAccountListener{

[0253] / **

[0254] * Callback for the result of QR code login and binding

[0255] * @param success Whether the login is successful

[0256] * @param account The logged-in account

[0257] * /

[0258] void onLoginCallback(boolean success, KTAccount account);

[0259] / **

[0260] * Callback for account information change

[0261] * @param account The changed account information

[0262] * /

[0263] void onAccountChanged(KTAccount account);

[0264] / **

[0265] * Callback for logout and unbinding

[0266] * @param yuid The yuid to be unbound

[0267] * /

[0268] void onLogoutCallback(String vuid);

[0269] / **

[0270] * In the non-binding process, if another account is logged in within the APP, this method will be triggered to let the system trigger the binding process.*

[0271] * /

[0272] void notifyBind();

[0273] / **

[0274] * When the authorization changes, the status is called back to the system side through this method

[0275] * @param authStatus The authorization status, and the values are defined as follows

[0276] * @see KTAccountBindAuthStatus#AUTH_STATE_REJECT_LOGIN_BIND

[0277] * @see KTAccountBindAuthStatus#AUTH_STATE_REJECT_SWITCH_ACCOUNT

[0278] *@see KTAccountBindAuthStatus#AUTH_STATE_REJECT_RENEW_AUTH

[0279] *@see KTAccountBindAuthStatus#AUTH_STATE_REMOVE_AUTH

[0280] *@param yuid Account ID

[0281] * /

[0282] void onAuthChanged(int authStatus, String vuid);

[0283] }

[0284] The third - party application mainly provides the AIDL object of the third - party application, and the implementation of the business interfaces for logging in and out together. It also provides the remote object of the business, which is the business AIDL object mentioned above. The implementation of the business interfaces for logging in and out together is in the AIDL object for logging in and out together.

[0285] The AIDL object of the third - party application is defined as follows:

[0286] private static class IKTVideoRemoteServiceStub extends IKTVideoRemoteServiceAidl.Stub{

[0287] KTAccountRemoteStub accountRemote;

[0288] KTHistoryRemoteStub historyRemote;

[0289] KTGeneralRemoteStub generalRemote;

[0290] @Override

[0291] public void init(){

[0292] accountRemote = new KTAccountRemoteStub();

[0293] generalRemote = new KTGeneralRemoteStub();

[0294] historyRemote = new KTHistoryRemoteStub();}

[0295] @Override

[0296] public void release() throws RemoteException {

[0297] if (accountRemote != null) {

[0298] accountRemote.setAccountListener(null);}

[0299] if (generalRemote != null) {

[0300] generalRemote.setCallback(null);}

[0301] accountRemote = null; generalRemote = null; historyRemote = noll;}

[0302] @Override

[0303] public IKTAccountRemoteAidl getAccountRemote() {

[0304] return accountRemote;

[0305] @Override

[0306] public IKTHistoryRemoteAidl getHistoryRemote() { return historyRemote;}

[0307] @override

[0308] public IKTGeneralRemoteAidl getGeneralRemote() { return generalRemote;}

[0309] }

[0310] The AIDL objects for the same login and logout on the server side are defined as follows:

[0311] private static IKTAccountListenerAidl accountListenerAidl;

[0312] private final static LoginStatusListenerProxy loginStatusListenerProxy = new LoginStatusListenerProxy();

[0313] private final static AccountstatusListenerProxy accountStatusListenerProxy = new AccountStatusListenerProxy();

[0314] private final static AccountBindAuthStatusListenerProxy accountAuthStatusListenerProxy = new AccountBindAuthStatusListenerProxy();

[0315] @Override

[0316] public void setAccountListener(IKTAccountListenerAidl listener) {

[0317] accountListenerAidl = listener; if (listener != null) {

[0318] KTAccountRemoteManager.getInstance().setRemoteLoginStatusListener(loginStatusListenerProxy);

[0319] KTAccountRemoteManager.getInstance().setRemoteAccountStatusListener(accountStatusListenerProxy);

[0320] KTAccountRemoteManager.getInstance().setRemoteAccountAuthStatusListener(accountAuthStatusListenerProxy);} else {

[0321] KTAccountRemoteManager.getInstance().setRemoteLoginStatusListener(nutl);

[0322] KTAccountRemoteManager.getInstance().setRemoteAccountStatusListener(null);

[0323] KTAccountRemoteManager.getInstance().setRemoteAccountAuthStatusListener(null);}

[0324] @override

[0325] public void login() throws RemoteException{

[0326] KTAccountRemoteManager.getInstance().login();

[0327] @Override

[0328] public void logout(String vuid){

[0329] KTAccountRemoteManager.getInstance().loadLocalAccount();

[0330] / / If the return value is false, it means that the logged-out account is different from the account logged in to the APP. The Logout callback is triggered here by itself

[0331] if (KTAccountRemoteManager.getInstance().logout(vuid)){

[0332] return;}

[0333] if (accountListenerAidl == null) {

[0334] KTLog.e(TAG, msg; "[VideoRemote] logout callback fail, listener is null"); return;}

[0335] try {

[0336] accountListenerAidl.onLogoutCallback(vuid);} catch (RemoteException e) {

[0337] KTLog.printStackTrace(e);}

[0338] @Override

[0339] public void switchAccount(KTAccountInfo newAccount, KTAccountInfo oldAccount) {

[0340] KTAccountRemoteManager.getInstance().loadLocalAccount();

[0341] KTAccountRemoteManager.getInstance().switchAccount(newAccount, oldAccount);

[0342] }

[0343] The specific implementation manners of the present application have been described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above implementation manners. Within the technical concept scope of the present application, various simple modifications can be made to the technical solutions of the present application, and these simple modifications all fall within the protection scope of the present application. For example, for the various specific technical features described in the above specific implementation manners, they can be combined in any appropriate manner without contradiction. To avoid unnecessary repetition, the present application will not separately describe various possible combination manners. Again, for example, any combination can be made between various different implementation manners of the present application, as long as it does not violate the idea of the present application, it should also be regarded as the parameters disclosed by the present application.

[0344] It should also be understood that in the various method embodiments of the present application, the magnitudes of the serial numbers of the above processes do not indicate the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. It should be understood that these serial numbers can be interchanged under appropriate circumstances, so that the embodiments of the present application described can be implemented in an order other than those shown or described.

[0345] As described above in conjunction with Figures 1 to 8 , the method embodiments of the present application have been described in detail. Below, in conjunction with Figure 9 and Figure 10 , the apparatus embodiments of the present application will be described in detail.

[0346] Figure 9 FIG. is a schematic block diagram of an apparatus 800 according to an embodiment of the present application. The apparatus 800 can implement the functions of the in-vehicle device in the above method. As Figure 9 shown, the apparatus 800 may include a processing unit 810, a transceiver unit 820, and a login unit 830.

[0347] An obtaining unit 810 is configured to obtain a first account of the system application, where the first account is an account logged in to the system application;

[0348] A transceiver unit 820 is configured to transmit the second account to the third-party application through a first interface, where the second account has a binding relationship with the first account, and the second account is an account of the third-party application;

[0349] A login unit 830 is configured to log in to the second account on the third-party application.

[0350] In some embodiments, the apparatus further includes a display unit and a processing unit:

[0351] The display unit is configured to display the third-party applications installed on the in-vehicle device on the management interface of the system application when the second account bound to the first account is not obtained;

[0352] The processing unit is configured to detect the third-party application to be bound selected by the user;

[0353] The display unit is further configured to display the login interface of the third-party application;

[0354] The obtaining unit 810 is configured to obtain the login account of the user logging in to the third-party application as the second account;

[0355] The processing unit is configured to establish a binding relationship between the first account and the second account.

[0356] In some embodiments, the transceiver unit 820 is configured to transmit the login status of the second account to the system application through a third interface after the third-party application completes the login;

[0357] The processing unit is configured to establish a binding relationship between the first account and the second account in the system application;

[0358] The transceiver unit 820 is further configured to send a first message to the system server of the vehicle-mounted device, and the first message is used to instruct the system server to record the binding relationship between the first account and the second account.

[0359] In some embodiments, before logging in to the third-party application, there is further a display unit 840, which is configured to:

[0360] On the login interface of the third-party application, display a first pop-up message for prompting the user whether to authorize the binding process initiated by the system application;

[0361] The acquisition unit 810 is further configured to acquire the binding process authorized by the third-party application for the system application to initiate.

[0362] In some embodiments, before logging in to the third-party application, the display unit 840 is further configured to:

[0363] On the login interface of the third-party application, display a first pop-up message for prompting the user whether to authorize the binding process initiated by the system application;

[0364] The transceiver unit 820 is further configured to transmit a message indicating authorization failure to the system application through the third interface when the third-party application does not authorize the binding process initiated by the system application.

[0365] In some embodiments, the acquisition unit 810 is further configured to:

[0366] In the third-party application, record the authorization information of the account of the third-party application, where the authorization information includes whether the user authorizes the binding of the account of the third-party application to the account of the system application.

[0367] In some embodiments, the display unit 840 is further configured to:

[0368] When the authorization period of the second account in the authorization information reaches a preset value, display a second pop-up message in the third-party application for prompting the user whether to continue to authorize the binding of the second account to the first account of the system application.

[0369] In some embodiments, the transceiver unit 820 is further configured to:

[0370] Receiving a request message from the first account to exit the system application;

[0371] The acquisition unit 810 is further used to: acquire a second account bound to the first account, where the second account is an account of the third-party application;

[0372] The transceiver unit 820 is also used for:

[0373] transmitting the second account to the third-party application via a fourth interface;

[0374] The login unit 830 is further used to log out of the second account on the third-party application.

[0375] In some embodiments, the transceiver unit 820 is further configured to:

[0376] When the information of the second account is changed, the account information change information is transmitted to the system application through the third interface;

[0377] A second message is sent to the system server of the vehicle-mounted device, where the second message includes the account information change information, and the second message is used by the system server to update the information of the second account.

[0378] In some embodiments, the transceiver unit 820 is further configured to:

[0379] When the second account of the third application is logged out, a message of the second account being logged out is transmitted to the system application through the third interface;

[0380] Unbinding the binding relationship between the first account and the second account in the system application;

[0381] A third message is sent to the system server, where the third message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

[0382] In some embodiments, the acquisition unit 810 is further configured to:

[0383] When the user cancels the authorization for the second account to bind to the first account, the binding relationship between the first account and the second account is released in the system application;

[0384] A fourth message is sent to the system server, where the fourth message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

[0385] In some embodiments, the obtaining unit 810 is further configured to:

[0386] Run the third-party application, and the third-party application is not logged in to any account;

[0387] Obtain the second account of the third-party application bound to the first account logged in to the system application;

[0388] On the third-party application, log in to the second account of the third-party application bound to the first account.

[0389] In some embodiments, the obtaining unit 810 is further configured to:

[0390] Obtain the second account of the third-party application bound to the first account logged in to the system application;

[0391] Determine whether the second account is the same as the third account;

[0392] The display unit 840 is further configured to:

[0393] When the second account of the third-party application bound to the system application is different from the third account, display a third pop-up message for prompting the user whether to switch to the second account of the third-party application bound to the system application.

[0394] It should be understood that the device embodiments and the method embodiments can correspond to each other, and similar descriptions can refer to the method embodiments. To avoid repetition, they are not described herein again. Specifically, when in this embodiment, the device 500 can correspond to the execution subject of the above method of the embodiments of the present application, the foregoing and other operations and / or functions of each module in the device 500 respectively correspond to the respective method flows in the above method. For the sake of brevity, they are not described herein again.

[0395] In the foregoing, the apparatuses and systems of the embodiments of the present application have been described from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that these functional modules can be implemented in the form of hardware, or in the form of instructions in software, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application can be completed by the integrated logic circuit in the hardware of the processor and / or instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps in the above method embodiments.

[0396] As Figure 10 is a schematic block diagram of an electronic device 900 provided by an embodiment of the present application.

[0397] As Figure 10 shown, the electronic device 900 may include:

[0398] A memory 910 and a processor 920. The memory 910 is used to store a computer program and transmit the program code to the processor 920. In other words, the processor 920 can call and run the computer program from the memory 910 to implement the method in the embodiments of the present application.

[0399] For example, the processor 920 can be used to execute the steps of each execution subject in the above method 300 according to the instructions in the computer program.

[0400] In some embodiments of the present application, the processor 920 may include, but is not limited to:

[0401] A general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and so on.

[0402] In some embodiments of the present application, the memory 910 includes, but is not limited to:

[0403] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double DataRate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synch link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0404] In some embodiments of the present application, the computer program can be divided into one or more modules, which are stored in the memory 910 and executed by the processor 920 to complete the method provided by the present application. The one or more modules can be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device 900.

[0405] Optionally, the electronic device 900 may further include:

[0406] A communication interface 930, which can be connected to the processor 920 or the memory 910.

[0407] Among them, the processor 920 can control the communication interface 930 to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. By way of example, the communication interface 930 can include a transmitter and a receiver. The communication interface 930 can further include an antenna, and the number of antennas can be one or more.

[0408] It should be understood that each component in the electronic device 900 is connected through a bus system. Among them, the bus system includes not only a data bus, but also a power bus, a control bus, and a status signal bus.

[0409] According to one aspect of the present application, a communication device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the encoder executes the method of the above method embodiment.

[0410] According to one aspect of the present application, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by the computer, the computer can execute the method of the above method embodiment. Or rather, the embodiment of the present application also provides a computer program product including instructions. When the instructions are executed by the computer, the computer executes the method of the above method embodiment.

[0411] According to another aspect of the present application, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method of the above method embodiment.

[0412] In other words, when implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that the computer can access or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0413] It should be understood that in the embodiment of the present application, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based only on A, and B can also be determined based on A and / or other information.

[0414] In the description of the present application, unless otherwise specified, "at least one" means one or more, and "plurality" means two or more than two. In addition, "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0415] It should also be understood that the first, second, etc. descriptions appearing in the embodiments of the present application are only used for illustration and distinction of the description objects, without any distinction of order, nor do they indicate any special limitation on the number of devices in the embodiments of the present application, and cannot constitute any limitation on the embodiments of the present application.

[0416] It should also be understood that the specific features, structures or characteristics related to the embodiments in the specification are included in at least one embodiment of the present application. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0417] In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or device.

[0418] It is understandable that in the specific implementation of this application, data related to terminal device information may be involved. When the above embodiments of this application are applied to specific products or technologies, it is necessary to obtain permission or consent from the terminal device, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0419] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the function of that module or unit.

[0420] Those of ordinary skill in the art can realize that the modules and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0421] In several embodiments provided in the present application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the module is only a logical function division, and there can be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or modules can be in an electrical, mechanical, or other form.

[0422] The module described as a separate component may or may not be physically separated, and the component shown as a module may or may not be a physical module, that is, it can be located in one place, or can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, in each embodiment of the present application, the various functional modules can be integrated in a processing module, or each module can exist physically separately, or two or more modules can be integrated in one module.

[0423] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the rights indication information.

Claims

1. A method for application program login, which is applied to an in-vehicle device. The in-vehicle device is installed with a system application program and a third-party application program, and is characterized in that, Including: Obtain a first account of the system application, where the first account is the account logged in to the system application; Transmit a second account to the third-party application through a first interface, where the second account has a binding relationship with the first account, and the second account is the account of the third-party application; Log in to the second account on the third-party application.

2. The method according to claim 1, wherein When the second account bound to the first account is not obtained, the method further includes: On the management interface of the system application, display the third-party applications installed on the in-vehicle device; Determine the third-party application to be bound selected by the user; Display the login interface of the third-party application; Obtain the login account of the user logging in to the third-party application as the second account; Establish a binding relationship between the first account and the second account.

3. The method according to claim 2, characterized in that, The establishment of the binding relationship between the first account and the second account includes: After the third-party application completes the login, transmit the login status of the second account to the system application through a third interface; Establish a binding relationship between the first account and the second account in the system application; Send a first message to the system server of the in-vehicle device, where the first message is used to instruct the system server to record the binding relationship between the first account and the second account.

4. The method according to claim 1, wherein Before logging in to the third-party application, the method further includes: On the login interface of the third-party application, display a first pop-up message, where the first pop-up message is used to prompt the user whether to authorize the binding process initiated by the system application; The third-party application authorizes the binding process initiated by the system application.

5. The method according to claim 1, wherein Before logging in to the third-party application, the method further includes: On the login interface of the third-party application, display a first pop-up message, where the first pop-up message is used to prompt the user whether to authorize the binding process initiated by the system application; When the third-party application does not authorize the binding process initiated by the system application, transmit a message indicating authorization failure to the system application through a third interface.

6. The method according to claim 5, characterized in that, The method further includes: In the third-party application, record the authorization information of the account of the third-party application, where the authorization information includes whether the user authorizes the binding of the account of the third-party application and the account of the system application.

7. The method according to claim 5, characterized in that The method further includes: When the authorization period of the second account in the authorization information reaches a preset value, in the third-party application, display a second pop-up message, where the second pop-up message is used to prompt the user whether to continue to authorize the binding of the second account and the first account of the system application.

8. The method according to claim 1, wherein The method further includes: Receive a request message for the first account to log out of the system application; Obtain the second account bound to the first account; Transmit the second account to the third-party application through a fourth interface; Log out of the second account on the third-party application.

9. The method according to claim 1, characterized in that, The method further includes: When the information of the second account is changed, the account information change information is transmitted to the system application through the third interface; A second message is sent to the system server of the vehicle-mounted device, where the second message includes the account information change information, and the second message is used by the system server to update the information of the second account.

10. The method according to claim 1, characterized in that, The method further comprises: When the second account of the third-party application is logged out, a message of the second account being logged out is transmitted to the system application through a third interface; Unbinding the binding relationship between the first account and the second account in the system application; A third message is sent to the system server, where the third message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

11. The method according to any one of claims 1 to 10, characterized in that, The method further comprises: When the user cancels the authorization for the second account to bind to the first account, the binding relationship between the first account and the second account is released in the system application; A fourth message is sent to the system server, where the fourth message is used to instruct the system server to unbind the binding relationship between the first account and the second account.

12. The method according to claim 1, wherein The method further comprises: Running the third-party application, where the third-party application is not logged into any account; Obtaining the second account of the third-party application bound to the first account logged in by the system application; On the third-party application, log in to the second account of the third-party application bound to the first account.

13. The method according to claim 1, wherein The method further comprises: Running the third-party application, where the third-party application has logged into a third account; Obtaining a second account of the third-party application bound to the first account logged in by the system application; determining whether the second account is the same as the third account; When the second account is different from the third account, a third pop-up message is displayed, where the third pop-up message is used to prompt the user whether to switch to the second account.

14. A device for synchronously logging in a system application and a third-party application of a terminal device, characterized in that, include: An acquiring unit, configured to acquire a first account of the system application, where the first account is an account used by the system application to log in; a transceiver unit, configured to transmit a second account to the third-party application through the first interface, wherein the second account is bound to the first account and the second account is an account of the third-party application; A login unit is used to log in to the second account on the third-party application.

15. An electronic device, characterized in that, The method comprises a processor and a memory, wherein the memory stores instructions, and when the processor runs the instructions, the processor executes the method according to any one of claims 1 to 12.

Images