CN116340913A

CN116340913A - Login method, electronic equipment and computer readable storage medium

Info

Publication number: CN116340913A
Application number: CN202210187315.6A
Authority: CN
Inventors: 蒋传遐
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-12-23
Filing date: 2022-02-28
Publication date: 2023-06-27

Abstract

The application is applicable to the field of equipment management, and provides a login method, electronic equipment and a computer readable storage medium. In the login method provided by the embodiment of the application, the first device may send a verification request of the second account to the server in a state of logging in the first account. Subsequently, if the server returns the first information, the first equipment exits the first account and logs in the second account; if the server returns the second information, the first device may keep the state of logging in the first account, or the first device may also exit the first account and automatically enter the state of not logging in the account. Through the method, the first equipment can reduce the operation required to be executed by the user when the user switches the accounts corresponding to different user spaces, improves the use experience of the user, and has strong usability and practicability.

Description

Login method, electronic equipment and computer readable storage medium

Technical Field

The present disclosure relates to the field of device management, and in particular, to a login method, an electronic device, and a computer readable storage medium.

Background

With the continuous expansion of the usage scenes of electronic devices, it is more common for multiple users to share one electronic device.

In a scenario where multiple users share one electronic device, personal data related to user privacy may be generated when the user uses the electronic device. Therefore, in order to protect privacy security of different users, the electronic device may adopt a multi-user space scheme, different users use different user spaces, and different user spaces are isolated from each other.

In the current scheme of multi-user space, if a user needs to switch the user space, the user needs to control the electronic equipment to exit the current user space, and the selection and login verification operations are re-executed, so that the operation is complex and the user experience is poor.

Disclosure of Invention

The embodiment of the application provides a login method, electronic equipment and a computer readable storage medium, which can solve the problems of complex operation and poor user experience when users switch different user spaces in the existing scheme of multi-user space.

In a first aspect, an embodiment of the present application provides a login method, which is applied to a first device, and includes:

logging in a first account and displaying a first interface;

detecting an account switching operation of a user;

responding to the account switching operation, and sending a verification request of a second account to a server, wherein when the first equipment sends the verification request, the first equipment is in a state of logging in the first account;

If the first information returned by the server is obtained, the first account is withdrawn, the second account is logged in, and a second interface is displayed, wherein the first information is used for indicating that the second account passes verification;

if the second information returned by the server is obtained, the state of logging in the first account is kept, or the first account is withdrawn and is switched to the state of not logging in the account, wherein the second information is used for indicating that the verification of the second account fails.

It should be noted that in the embodiment of the present application, one or more user spaces may be provided on the first device, and each user space may correspond to one or more accounts.

The account number is used for managing the authority of the user to access the user space. If the first equipment logs in an account corresponding to a certain user space, the user can access the user space on the first equipment and use an application program in the user space; if the first device does not log into an account in a user space, the user cannot access the user space on the first device and cannot use the application program in the user space.

Thus, the first device logging into a certain user space can be understood as an account of the first device logging into the user space; switching different user spaces by the first device may be understood as switching different accounts by the first device.

After the first device logs in the first account, the first device may open a user space corresponding to the first account (hereinafter referred to as a first user space) to the user, and display a first interface.

At this point, the user may access the first user space and use the application within the first user space.

Then, if the user wants to switch to another user space, the user can perform an account switching operation on the first device.

After detecting the account switching operation, the first device may send a verification request of the second account to the server in a state of logging in the first account. Alternatively, it may be understood that the first device sends a verification request of the second account to the server based on the first user space.

After receiving the verification request of the second account, the server may verify the second account. The verification mode of the second account can comprise any one or a combination of a plurality of verification modes such as password verification, face verification, fingerprint verification, two-dimensional code verification, verification code verification and the like.

Subsequently, if the second account is authenticated, the server may send first information to the first device, the first information being used to indicate that the second account is authenticated.

After receiving the first information, the first device may log out of the first account, log in to the second account, display the second interface, and open a user space corresponding to the second account (hereinafter referred to as a second user space for short) to the user.

If the second account fails to verify, the server may send second information to the first device, the second information indicating that the second account fails to verify.

After receiving the second information, the first device may keep the state of logging in the first account, or exit the first account, and switch to the state of not logging in the account.

That is, in the login method provided in the embodiment of the present application, the first device may verify the second account in the first user space. Under the condition that the verification of the second account fails, the first equipment can directly reside in the first user space, and the user does not need to execute the operation of selecting and verifying the first account again, so that the operation required to be executed by the user is greatly reduced, and the use experience of the user can be effectively improved.

In addition, since the user performs the account switching operation on the first device, the user currently using the first device may not be the user spatially corresponding to the first user.

Therefore, in order to protect the private data in the first user space, the first device may also exit the first account and automatically switch to a state of not logging in the account to enter the guest space when the second account fails to be verified.

The above-mentioned guest space may be understood as a user space that does not require login; alternatively, the guest space may be understood as a user space common to all users.

Subsequently, the user may directly access the guest space using the application in the guest space.

By the login method, the first device can protect private data in the first user space, reduce operations required to be executed by the user, and effectively improve the use experience of the user.

In a possible implementation manner of the first aspect, the sending, in response to the account switching operation, a verification request of the second account to the server includes:

responding to the account switching operation, and displaying an information input box in the first interface;

acquiring verification information of the second account input in the information input box;

and sending a verification request of the second account to the server, wherein the verification request comprises the verification information.

After detecting the account switching operation, the first device may display an information input box in the first interface, and the user may input verification information of the second account in the information input box.

The verification information of the second account may include any one or more of account name, password, fingerprint data, verification code and the like of the second account.

After the first device obtains the verification information of the second account, the first device may send a verification request of the second account to the server, where the verification request carries the verification information of the second account.

After receiving the verification request, the server verifies the verification information of the second account carried in the verification request, so as to determine to send the first information or the second information to the first equipment.

In a possible implementation manner of the first aspect, the logging in the second account if the first information returned by the server is obtained includes:

receiving first information returned by the server, wherein the first information comprises an auxiliary certificate, and the auxiliary certificate is associated with the second account;

sending a login request to the server, the login request including the auxiliary credential;

Receiving login credentials returned by the server;

and logging in the second account according to the login credentials.

It should be noted that, after the second account passes the verification, the server may generate the auxiliary credential, and establish the association relationship between the auxiliary credential and the second account.

The server may then send first information to the first device, the first information carrying the auxiliary credential therein.

After receiving the first information returned by the server, the first device can exit the first account and enter the login flow of the second account.

In the login process of the second account, the first device may send a login request to the server, where the login request carries the auxiliary credential.

After receiving the login request, the server verifies the auxiliary certificate carried in the login request.

When the verification of the auxiliary credential carried in the login request fails, the server may not respond to the login request.

When the auxiliary credential carried in the login request passes the verification, the server can generate the login credential and establish the association relationship between the login credential and the second account.

The server may then send the login credentials to the first device.

After receiving the login credentials, the first device may save the login credentials, login the second account, display a second interface, and open a second user space to the user.

The expression form of the certificate (token) can be set according to actual requirements. For example, in some embodiments, the token may be a string of characters that may include any one or more of the presentation elements of letters, numbers, symbols, etc.

By the method, when the first equipment can verify the second account in the first user space, the server can send the auxiliary credentials to the first equipment to prove that the second account is verified.

Subsequently, the first device exits the first user space and enters the login process of the second account. At this time, the first device can log in the second account based on the auxiliary credentials, so that the user does not need to input verification information of the second account again, operations required to be executed by the user are reduced, and the use experience of the user is improved.

In a possible implementation manner of the first aspect, the receiving the first information returned by the server and sending a login request to the server include:

The login process corresponding to the first account receives first information returned by the server;

the login process corresponding to the first account transfers the auxiliary certificate in the first information and the account identification of the second account to the account synchronization process of the first equipment;

the account synchronization process sends the auxiliary certificate to a login process corresponding to the second account;

and the login process corresponding to the second account sends a login request to the server based on the auxiliary certificate.

It should be noted that, after the first device detects the above-mentioned account switching operation, the login process corresponding to the first account may send a verification request of the second account to the server.

After the second account passes the verification, the server may return first information to the login process corresponding to the first account, where the first information carries an auxiliary credential.

Because the login process corresponding to the first account cannot log in the second account, the login process corresponding to the first account needs to transmit the auxiliary credentials to the login process corresponding to the second account.

However, in order to secure privacy security of the user, the first user space and the second user space are isolated user spaces.

At this time, the login process corresponding to the first account cannot directly transfer the auxiliary credential to the login process corresponding to the second account.

Therefore, in this embodiment of the present application, a system space may be set on the first device, and an account synchronization process is set in the system space, where the account synchronization process resides in a system background of the first device, and the account synchronization process may perform data interaction with each user space.

At this time, the login process corresponding to the first account may transmit the auxiliary credential and the account identifier of the second account to the account synchronization process, and the account synchronization process transmits the auxiliary credential to the login process corresponding to the second account.

After the login process corresponding to the second account receives the auxiliary credential, the login process corresponding to the second account may send a login request to the server based on the auxiliary credential.

By the method, even if the first user space and the second user space are isolated from each other, the login process corresponding to the first account can safely transmit the auxiliary credentials to the login process corresponding to the second account by means of the transfer capability of the account synchronization process, so that the problem that the login process corresponding to the first account and the login process corresponding to the second account cannot perform data interaction is solved.

In a possible implementation manner of the first aspect, the sending, by the account synchronization process, the auxiliary credential to a login process corresponding to the second account includes:

the account synchronization process searches a user space corresponding to the second account according to the account identifier;

if the user space corresponding to the second account is found, the account synchronization process sends the auxiliary certificate to a login process of the user space corresponding to the second account;

if the user space corresponding to the second account is not found, the account synchronization process creates a new user space, establishes an association relationship between the new user space and the account identifier, and sends the auxiliary certificate to a login process of the new user space.

It should be noted that, after the account synchronization process described above obtains the auxiliary credential and the account identifier of the second account, the user space corresponding to the second account (i.e., the second user space) may be searched according to the account identifier of the second account.

At this time, if the account synchronization process can find the second user space in the first device, the account synchronization process may call an application programming interface (Application Programming Interface, API) corresponding to the second user space, so that the first device starts a process related to the second user space, including a login process corresponding to the second account.

After the first device starts the login process corresponding to the second account, the account synchronization process may send the auxiliary credential to the login process corresponding to the second account.

If the account synchronization process cannot find the second user space in the first device, the account synchronization process can create a new user space as the second user space, and an association relationship between the second user space and the account identifier of the second account is established.

The account synchronization process may then invoke an API corresponding to the second user space (i.e., the newly created user space described above) to cause the first device to initiate a process associated with the second user space, including a login process corresponding to the second account.

By the method, the account synchronization process can help the user to establish the second user space under the condition that the first equipment is not provided with the second user space, the user does not need to establish the second user space by himself, the operation of the user is simplified, and the use experience of the user is improved.

In a possible implementation manner of the first aspect, the user data corresponding to the first account is different from the user data corresponding to the second account.

It should be noted that, in order to ensure privacy security of different users, user data in different user spaces may be independent of each other and isolated from each other.

At this time, the user data in the first user space and the user data in the second user space are different user data, the first user space cannot access the user data recorded in the second user space, and the second user space cannot access the user data recorded in the first user space.

Alternatively, it may be understood that the user data corresponding to the first account and the user data corresponding to the second account are different user data.

Illustratively, assuming that the first user space and the second user space are installed with the same browser, user A accesses Web page A using the browser in the first user space and user B accesses Web page B using the browser in the second user space.

At this time, the browsing record of the web page A is stored in the browsing record of the first user space, and the browsing record of the web page B is not stored; the browsing records of the webpage B are stored in the second user space, and the browsing records of the webpage A are not stored.

In a possible implementation manner of the first aspect, the first interface and the second interface are different interfaces.

It should be noted that, in an actual application scenario, the first user space and the second user space may be installed with different applications, so that the first interface and the second interface display different contents.

Alternatively, the first user space and the second user space may be installed with the same application program, but icons and controls corresponding to the same application program may be placed at different positions, so that the first interface and the second interface display different contents.

For example, in one example, a first user space has a music application installed and a second user space does not have the music application installed. At this time, an icon of the music application may be displayed in the first interface, and an icon of the music application may not be displayed in the second interface, thereby causing a difference between the first interface and the second interface.

In another example, the first user space and the second user space are each installed with a music application. However, in the first interface, the icon of the music application is placed at the left edge of the first interface; in the second interface, the icon of the music application is placed at the right edge of the second interface, resulting in a difference between the first interface and the second interface.

In a second aspect, an embodiment of the present application provides a login method, which is applied to a server, and includes:

receiving a verification request of a second account sent by first equipment;

verifying the second account;

if the second account passes the verification, first information is sent to the first equipment;

and if the second account verification fails, sending second information to the second equipment.

It should be noted that, in the embodiment of the present application, the account corresponding to each user space on the first device may be an account set by the cloud, and the server in the cloud may provide an account verification service for the first device.

When a user wants to log in to the second user space on the first device, the user can perform an account switching operation on the first device.

The first device may send a request for authentication of the second account to the server in response to the account switch operation.

When the server receives the verification request of the second account sent by the first device, the server can verify the second account.

The verification mode of the second account comprises any one or a combination of a plurality of verification modes such as password verification, face verification, fingerprint verification, two-dimensional code verification, verification code verification and the like.

Then, if the second account passes the verification, the server may send first information to the first device, where the first information is used to indicate that the second account passes the verification.

If the second account fails to verify, the server may send second information to the first device, where the second information is used to indicate that the second account fails to verify.

When the first device receives the first information, the first device can log in the second account to open a second user space to the user. In addition, since the server has already verified the second account, the first device may directly use the cloud service related to the second account, such as the cloud space of the second account, provided by the server.

When the first device receives the second information, the first device may reside in the first user space to keep the state of logging in the first account, or the first device may also exit the first account, switch to the state of not logging in the account, and enter the guest space.

In a possible implementation manner of the second aspect, the sending, if the second account passes verification, first information to the first device includes:

if the second account passes verification, generating an auxiliary certificate, and establishing an association relation between the auxiliary certificate and the second account;

The first information is sent to the first device, the first information including the auxiliary credential.

It should be noted that, after the second account passes the verification, the server may generate an auxiliary credential, and establish an association relationship between the auxiliary credential and the second account, where the auxiliary credential may be used to indicate that the second account passes the verification.

The presentation form of the auxiliary certificate (token) can be set according to actual requirements. For example, in some embodiments, the auxiliary token may be a string of characters that may include any one or more of the presentation elements of letters, numbers, symbols, etc.

The server may then send first information to the first device, the first information carrying the auxiliary credential.

In a possible implementation manner of the second aspect, after the sending the first information to the first device, the first information includes the auxiliary credential, the method further includes:

receiving a login request sent by the first device, wherein the login request comprises the auxiliary credential;

responding to the login request, generating login credentials, and establishing an association relationship between the login credentials and the second account;

And sending the login credential to the first device.

It should be noted that, since the auxiliary credential is used to indicate that the second account is verified, after the first device receives the auxiliary credential, the first device may send a login request to the server, where the login request carries the auxiliary credential, and the login request is used to request to login to the second account.

After the server receives the login request sent by the first device, the server may verify the auxiliary credential in the login request. The verification mode can comprise any one or more of signature verification, validity verification and character string comparison peer-to-peer verification modes.

When the verification of the auxiliary credential in the login request fails, the server may not respond to the login request.

When the auxiliary certificate in the login request passes the verification, the server can generate a login certificate, and the association relation between the login certificate and the second account is established.

The server may then send the login credentials to the first device.

When the first device receives the login credentials, the first device may save the login credentials, login the second account according to the login credentials, and open a second user space to the user.

By the method, after the first equipment is switched to the second user space, the first equipment can log in the second user space directly based on the auxiliary credentials, and the user does not need to execute login verification operation again, so that the operation required to be executed by the user is effectively reduced, and the use experience of the user can be improved.

In a third aspect, an embodiment of the present application provides a login apparatus, which may be applied to a first device, where the apparatus includes:

the account login module is used for logging in the first account and displaying a first interface;

the operation detection module is used for detecting the account switching operation of the user;

the authentication request module is used for responding to the account switching operation and sending an authentication request of a second account to a server, wherein when the first equipment sends the authentication request, the first equipment is in a state of logging in the first account;

the account switching module is used for exiting the first account and logging in the second account if the first information returned by the server is acquired, and displaying a second interface, wherein the first information is used for indicating that the second account passes verification;

and the failure response module is used for keeping the state of logging in the first account if the second information returned by the server is acquired, or backing out the first account and switching to the state of not logging in the account, wherein the second information is used for indicating that the second account fails to verify.

In a possible implementation manner of the third aspect, the authentication manner of the second account includes any one or a combination of multiple of password authentication, face authentication, fingerprint authentication, two-dimensional code authentication and verification code authentication.

In a possible implementation manner of the third aspect, the authentication request module is specifically configured to:

In a possible implementation manner of the third aspect, the account switching module is specifically configured to:

receiving login credentials returned by the server;

and logging in the second account according to the login credentials.

In a possible implementation manner of the third aspect, the user data corresponding to the first account is different from the user data corresponding to the second account.

In a possible implementation manner of the third aspect, the first interface and the second interface are different interfaces.

In a fourth aspect, an embodiment of the present application provides a login device, which may be applied to a server, where the device includes:

the request receiving module is used for receiving a verification request of the second account sent by the first equipment;

the account verification module is used for verifying the second account;

the first response module is used for sending first information to the first equipment if the second account passes verification;

and the second response module is used for sending second information to the second equipment if the second account fails to verify.

In a possible implementation manner of the fourth aspect, the verification manner of the second account includes any one or a combination of multiple of password verification, face verification, fingerprint verification, two-dimensional code verification and verification code verification.

In a possible implementation manner of the fourth aspect, the first response module is specifically configured to:

In a possible implementation manner of the fourth aspect, the apparatus further includes:

a login request module, configured to receive a login request sent by the first device, where the login request includes the auxiliary credential;

the login credential module is used for responding to the login request, generating a login credential and establishing an association relation between the login credential and the second account;

and the certificate sending module is used for sending the login certificate to the first equipment.

In a fifth aspect, embodiments of the present application provide an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the electronic device being configured to implement the method according to any one of the first aspect and the possible implementation manner of the first aspect, or to implement the method according to any one of the second aspect and the possible implementation manner of the second aspect, when the computer program is executed.

In a sixth aspect, embodiments of the present application provide a computer readable storage medium configured to store a computer program, where the computer program when executed by a processor implements a method as in any one of the first aspect and the possible implementation manner of the first aspect, or implements a method as in any one of the second aspect and the possible implementation manner of the second aspect.

In a seventh aspect, embodiments of the present application provide a computer program product configured to, when run on an electronic device, cause the electronic device to perform the method as described in any one of the first aspect and the possible implementation manner of the first aspect, or to implement the method as described in any one of the second aspect and the possible implementation manner of the second aspect.

In an eighth aspect, embodiments of the present application provide a chip system, where the chip system includes a memory and a processor, where the processor is configured to execute a computer program stored in the memory to implement the method according to any one of the first aspect and the possible implementation manner of the first aspect, or to implement the method according to any one of the second aspect and the possible implementation manner of the second aspect.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

in the existing multi-user space scheme, the first device needs to withdraw from the first account first, and then verify the second account. Subsequently, under the condition that the second account fails to verify, if the user wants to return to the first account or enter a state of not logging in the account, the user needs to execute operations of selection and logging in verification again, the operation is complex, and the user experience is poor.

In the login method provided by the application, when the first device detects the account switching operation of the user, a login request of the second account can be sent to the server in a state of logging in the first account. Subsequently, if the server returns the first information, the first equipment exits the first account and logs in the second account; if the server returns the second information, the first device can keep the state of logging in the first account, and does not exit the first account, or exits the first account, and automatically enters the state of not logging in the account.

That is, in the login method provided by the present application, the first device may verify the second account in a state of logging in the first account. If the second account fails to be verified, the first device can keep the state of logging in the first account, the user does not need to execute selection and logging in the first account again, the operation required to be executed by the user is greatly reduced, and the use experience of the user can be effectively improved.

Or if the second account fails to verify, the first device can also exit the first account to help the user to automatically switch to a state of not logging in the account, and on the premise of ensuring the privacy security of the first account, the operation required to be executed by the user is reduced, so that the use experience of the user is improved, and the method has strong usability and practicability.

Drawings

Fig. 1 is a schematic structural diagram of a sharing device according to an embodiment of the present application;

fig. 2 is a flow chart of a login method according to an embodiment of the present application;

fig. 3 is a system architecture diagram of a login system according to an embodiment of the present application;

fig. 4 is a signaling interaction diagram of a login method according to an embodiment of the present application;

FIG. 5 is a system architecture diagram of another login system according to an embodiment of the present application;

FIG. 6 is a schematic diagram of another scenario provided in an embodiment of the present application;

fig. 7 is a schematic view of another scenario provided in an embodiment of the present application;

fig. 8 is a schematic view of another scenario provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of another scenario provided in an embodiment of the present application;

FIG. 10 is a schematic view of another scenario provided in an embodiment of the present application;

FIG. 11 is a schematic view of another scenario provided in an embodiment of the present application;

FIG. 12 is a schematic view of another scenario provided in an embodiment of the present application;

fig. 13 is a schematic view of another scenario provided in an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

For example, in a home scenario, a scenario may occur in which multiple users share one smart large screen; in a travel scenario, a scenario may occur in which a plurality of users share one car-mounted device.

In the scenario where multiple users share one electronic device, personal data related to user privacy may be generated when the users use the electronic device. For example, when a user uses a shared electronic device, personal data related to user privacy such as audio playback records, video playback records, browser access records, and the like may be generated.

Therefore, in order to protect privacy security of users, the electronic device may adopt a scheme of multi-user space, and a plurality of user spaces are set on the electronic device. The processes, instances, and user data of different user spaces are independent of each other.

At this time, different users use different user spaces, and the different user spaces are isolated from each other, so that privacy security of different users is protected.

In the scheme of the current multi-user space, if the user needs to switch the user space, the user needs to control the electronic equipment to exit the current user space, and select another user space for login verification.

If login verification fails, the user wants to return to the original user space or login visitor space, and then the user needs to re-execute selection and login verification operations after switching the user space, so that the operation is complex and the user experience is poor.

In view of this, the embodiment of the present application provides a login method, where when a sharing device is in a first user space and the sharing device detects a space switching operation of a user, the sharing device may perform login verification on the user based on the first user space. When the login verification is passed, the sharing device logs in to the second user space. When login verification fails, the sharing device resides in the first user space, or automatically enters the visitor space, so that steps required to be operated by a user are reduced, the use experience of the user is improved, and the method has strong usability and practicability.

The login method provided by the embodiment of the application may be applied to a sharing device, where the sharing device may include any one or more of a mobile phone, a tablet computer, a vehicle-mounted device, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a personal digital assistant (personal digital assistant, PDA), a netbook, and other electronic devices, and the specific type of the sharing device is not limited in this application.

Referring to fig. 1, fig. 1 schematically illustrates a structure of a sharing device 100 provided in an embodiment of the present application.

As shown in fig. 1, the sharing device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, a user identification module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the sharing device 100, or may be used to transfer data between the sharing device 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other shared devices, such as AR devices, etc.

It should be understood that the interfacing relationship between the modules illustrated in the embodiment of the present invention is only illustrative, and does not limit the structure of the sharing device 100. In other embodiments of the present application, the sharing device 100 may also use different interfacing manners in the foregoing embodiments, or a combination of multiple interfacing manners.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the shared device 100. The charge management module 140 may also supply power to the shared devices through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the sharing device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the shared device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied on the shared device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc. as applied on the shared device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of sharing device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that sharing device 100 may communicate with a network and other devices via wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The sharing device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the sharing device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The sharing device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the sharing device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the sharing device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The sharing device 100 may support one or more video codecs. In this way, the sharing device 100 may play or record video in multiple encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Intelligent awareness of the shared device 100, etc. applications may be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the shared device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the sharing device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications of the shared device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The sharing device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The sharing device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the sharing device 100 listens to telephone calls or voice information, voice can be heard by placing the receiver 170B close to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The sharing device 100 may be provided with at least one microphone 170C. In other embodiments, the sharing device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the sharing device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile shared device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The sharing device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the sharing device 100 detects the touch operation intensity according to the pressure sensor 180A. The sharing device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the shared device 100. In some embodiments, the angular velocity of the shared device 100 about three axes (i.e., x, y, and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. Illustratively, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the sharing apparatus 100, calculates the distance to be compensated by the lens module according to the angle, and allows the lens to counteract the shake of the sharing apparatus 100 by the reverse motion, thereby realizing anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the sharing device 100 calculates altitude from barometric pressure values measured by the barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The sharing device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the sharing device 100 is a flip-top machine, the sharing device 100 may detect the opening and closing of the flip-top according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the sharing device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the sharing device 100 is stationary. The method can also be used for identifying the gesture of the sharing equipment, and is applied to the applications such as horizontal and vertical screen switching, pedometers and the like.

A distance sensor 180F for measuring a distance. The sharing device 100 may measure the distance by infrared or laser. In some embodiments, the sharing device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The sharing device 100 emits infrared light outward through the light emitting diode. The sharing device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the sharing device 100. When insufficient reflected light is detected, the sharing device 100 may determine that there is no object in the vicinity of the sharing device 100. The sharing device 100 can use the proximity light sensor 180G to detect that the user holds the sharing device 100 close to the ear for talking, so as to automatically extinguish the screen for power saving. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The sharing device 100 may adaptively adjust the display screen 194 brightness based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the shared device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The sharing device 100 may utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the shared device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, shared device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, the shared device 100 heats the battery 142 when the temperature is below another threshold to avoid low temperatures causing the shared device 100 to shut down abnormally. In other embodiments, when the temperature is below a further threshold, the sharing device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the sharing device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The sharing device 100 may receive key inputs, generate key signal inputs related to user settings and function controls of the sharing device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be contacted and separated from the sharing device 100 by inserting into the SIM card interface 195 or extracting from the SIM card interface 195. The sharing device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The sharing device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the sharing device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the shared device 100 and cannot be separated from the shared device 100.

It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the sharing device 100. In other embodiments of the present application, the sharing device 100 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The login method provided in the embodiment of the present application will be described in detail below with reference to the sharing device shown in fig. 1 and the flowchart shown in fig. 2. As shown in fig. 2, the login method includes:

step S201, when the sharing device is in a first user space and the sharing device detects space switching operation of a user, the sharing device performs login verification on the user based on the first user space; the space switching operation is used for requesting to log in the second user space;

if the login verification is passed, the sharing device executes step S202; if the login authentication fails, the sharing device executes step S204.

In this embodiment of the present application, one or more user spaces may be disposed on the sharing device (i.e., the first device) and each user space may correspond to one or more login accounts (i.e., the accounts).

The login account may be a local account locally set by the sharing device, or the login account may be a cloud account set by a server in the cloud.

The login account is used for managing the authority of the user to access the user space. If the sharing device logs in a login account of a certain user space, a user can access the user space on the sharing device and use an application program in the user space; if the sharing device does not log in the login account of a certain user space, the user cannot access the user space on the sharing device, and cannot use the application program in the user space.

Therefore, the sharing device logging in a certain user space can be understood as a login account of the sharing device logging in the user space; switching different user spaces by the sharing device may be understood as switching different login accounts by the sharing device.

When the shared device is in the first user space, if the user wants to switch to the second user space, the user may perform a space switching operation on the shared device.

At this time, the sharing device may perform login authentication on the user in the first user space in response to the space switching operation of the user (i.e., the above-described account switching operation).

The login verification is used for verifying whether the user has authority to login the login account in the second user space. The login verification may include any one or a combination of a plurality of verification modes such as password verification, face verification, fingerprint verification, two-dimensional code verification, verification code verification and the like.

When the sharing device performs login verification on the user, the login verification can be performed on the user locally, or the login verification can be performed on the user by cooperating with a cloud server.

In some embodiments, the login account of the second user space is a destination local account locally set by the sharing device.

At this point, the sharing device may authenticate the user locally.

Illustratively, it is assumed that the second user space described above is associated with a destination local account number that is locally set by the sharing device.

When the sharing device detects the space switching operation of the user, the sharing device can search the verification information corresponding to the target local account locally, and verify the identity information input by the user according to the verification information.

The identity information may include one or more of login password, face information, fingerprint information, two-dimensional code, verification code, and the like.

The verification information may include one or more of verification passwords, face information, fingerprint information, two-dimensional codes, verification codes and other types of information stored in the sharing device in advance.

If the identity information passes the verification, the sharing device may execute step S202, wherein the step indicates that the user has authority to log in the target sample local account; if the authentication of the identity information fails, it indicates that the user has no authority to log in to the target local account, and the sharing device may execute step S204.

In other embodiments, the login account of the second user space is a target cloud account (i.e., the second account) set by the server in the cloud.

At this time, the sharing device may cooperate with the cloud server to perform login verification on the user together.

Illustratively, it is assumed that the second user space is associated with a target cloud account set by a server in the cloud.

When the sharing device detects the space switching operation of the user, the sharing device may send the identity information (i.e., the authentication information of the second account) input by the user to the server.

After receiving the identity information, the server can search verification information corresponding to the target cloud account locally in the server, and verify the identity information according to the verification information.

If the identity information passes the verification, the user is authorized to log in the target cloud account, and the server can return a first verification result (namely the first information) to the sharing equipment; if the authentication of the identity information fails, the server may return a second authentication result (i.e., the second information) to the sharing device, wherein the second authentication result indicates that the user cannot log in the target cloud account.

The first verification result is used for indicating that login verification is passed, and the second verification result is used for indicating that login verification fails.

When the sharing device receives the first verification result, the sharing device may perform step S202; when the sharing device receives the second verification result, the sharing device may perform step S204.

Step S202, the sharing device transmits an auxiliary certificate to a system space of the sharing device based on the first user space; the secondary credential is used to log into the second user space.

As described above, the different user spaces are independent of each other, so the first user space cannot directly transfer the result of login verification to the second user space.

Therefore, in the embodiment of the present application, a system space may be provided in the sharing device. The processes of the system space reside in the system background of the sharing device, and the system space can perform data interaction with each user space.

After the user login verification passes, the sharing device may pass the auxiliary credential to the system space of the sharing device based on the first user space.

The auxiliary certificate can be used for proving that the login verification of the user passes; alternatively, the above-mentioned auxiliary credentials may be understood as a login account for logging into the second user space.

The auxiliary credential may be a credential locally generated by the sharing device, or the auxiliary credential may be a credential returned by the server to the sharing device.

When the sharing device locally performs login verification on the user, the sharing device may generate an auxiliary credential after the login verification is passed.

When the sharing device cooperates with the cloud server to perform login verification on the user, the server can send an auxiliary certificate to the sharing device after the login verification is passed.

In addition, the auxiliary credential may be sent by the server to the sharing device; alternatively, the auxiliary credential may be actively requested by the sharing device from the server.

For example, in one example, after the user login verification passes, the server may return a first verification result to the sharing device, where the first verification result carries the auxiliary credential.

In another example, after the user login verification passes, the server may return a first verification result to the shared device; the sharing device may send an auxiliary credential request to the server after receiving the first verification result; the server, upon receiving the secondary credential request, may send the secondary credential to the sharing device.

Step S203, the sharing device logs in the second user space according to the auxiliary credentials in the system space.

After the system space of the sharing device obtains the auxiliary credential, the system space of the sharing device may initiate a second user space to which the auxiliary credential is transferred.

After the second user space acquires the auxiliary credential, the second user space can log in a login account corresponding to the second user space according to the auxiliary credential.

When the login account corresponding to the second user space is the target local account, the sharing device can verify the auxiliary certificate locally.

The verification mode can be set according to actual requirements. For example, the verification may include any one or more of signature verification, validity verification, and string-to-peer verification.

If the auxiliary certificate passes the verification, the sharing device can log in the target local account in the second user space and open the second user space to the user. Subsequently, the user may access the second user space using the application in the second user space.

If the auxiliary credential verification fails, the sharing device may perform a preset login failure operation. For example, the sharing device may display a login interface prompting the user to re-perform login verification.

When the login account corresponding to the second user space is the target cloud account, the sharing device may send the auxiliary credential to the server.

After receiving the auxiliary credential, the server may verify the auxiliary credential locally at the server.

If the secondary credential verification fails, the server may not respond to the secondary credential.

If the auxiliary credential passes the verification, the server may send a login credential to the share, where the login credential is used to prove that the sharing device successfully logs in to the target cloud account.

After receiving the login credentials, the sharing device may save the login credentials and open a second user space to the user. Subsequently, the user may access the second user space, use the application program in the second user space, and use cloud services provided by the cloud server, such as cloud space, based on the login credentials.

In step S204, the sharing device resides in the first user space, or exits the first user space and enters the guest space.

When the user login verification fails, the user is indicated to have no authority to log in the login account corresponding to the second user space, and no authority to enter the second user space is indicated.

At this time, the sharing device may reside in the first user space, or the sharing device may exit the first user space and enter the guest space.

In some embodiments, the sharing device may refuse to switch to the second user space, residing in the first user space, after the user login authentication fails.

In the existing scheme of multi-user space, when the sharing device switches the second user space, the sharing device needs to close the first user space currently logged in first, start the second user space, and log in and verify the user in the second user space.

In these schemes, once the user login verification fails, the user wants to return to the first user space, the sharing device needs to close the second user space first, start the first user space, re-perform the login verification on the user in the first user space, the operation is extremely complicated, the sharing device needs to repeatedly switch different user spaces, a great deal of time is consumed, and the user experience is extremely poor.

In the login method provided by the embodiment of the application, when the user wants to switch to the second user space, the sharing device can perform login verification on the user in the first user space. If login verification fails, the sharing device can directly reside in the first user space, login verification is not required to be repeatedly performed on the user, and different user spaces are not required to be repeatedly switched, so that operations required to be executed by the user are effectively reduced, time consumed by switching different user spaces is reduced, and use experience of the user is improved.

In other embodiments, the sharing device may exit the first user space into the guest space after the user login authentication fails.

It will be appreciated that, since the user performs a space switching operation on the shared device, the user currently using the shared device may not be the user spatially corresponding to the first user.

Thus, to protect private data in the first user space, the sharing device may exit the first user space and automatically enter the guest space after the user login authentication fails.

By the method, the sharing device can avoid repeatedly switching different user spaces, improve the use experience of the user, protect the private data in the first user space and guarantee the privacy safety of the user.

In summary, in the login method provided in the embodiment of the present application, when the sharing device is in the first user space and the space switching operation of the user is detected, the sharing device may perform login verification on the user based on the first user space. If the login verification is passed, the sharing device can log in the second user space; if login verification fails, the sharing device can reside in the first user space or automatically jump to the visitor space, and the user does not need to manually switch different user spaces and carry out login authentication again, so that the operation of the user is reduced, the use experience of the user can be effectively improved, and the method has strong usability and practicability.

During the process of the sharing device logging in the second user space, the first user space can transmit the auxiliary credential to the system space, and the system space transfers the auxiliary credential to the second user space. In this way, the sharing device can transmit the auxiliary credential from the first user space to the second user under the condition that the first user space and the second user space do not directly perform data interaction, so that the first user space and the second user space can maintain a mutually isolated state, and privacy security of the first user space and the second user space is ensured.

In conjunction with the description of the above embodiments, another login method is provided in the embodiments of the present application. Fig. 3 shows a login system to which the login method is applied, where the login system includes a server and a sharing device.

The server has a login verification function and can assist the sharing device to carry out login verification on the user.

The sharing device includes a first user space and a system space, and in some embodiments, a second user space may be further included in the sharing device.

The first user space and the second user space may be understood as user usage systems corresponding to different users, and different user spaces correspond to different processes, instances, and user data.

The user data is data generated in the running process of the application program in the user space. For example, the user data may include a web browsing record of a browser record, a music playing record of a music application record, a video playing record of a video application record, and the like.

The user data of different user spaces are isolated from each other, i.e. the user data in the first user space and the user data in the second user space are isolated from each other.

Furthermore, the first user space and the second user space may be installed with the same application or different applications. However, the processes and instances generated by the first user space running application are independent of the processes and instances generated by the second user space running application.

For example, the first user space and the second user space may have the same video application installed, but the process that occurs when the first user space runs the video application and the process that occurs when the second user space runs the video application are two separate processes.

For another example, during the login verification process, the first user space may start a login process corresponding to the first user space, and the second user space may also start a login process corresponding to the second user space. However, the login process corresponding to the first user space and the login process corresponding to the second user space are two independent processes.

The processes of the system space reside in the system background of the sharing device, and the system space can perform data interaction with each user space.

For example, an account synchronization process may be set in the system space, where the account synchronization process may reside in a system background, and the system space may perform data interaction with a login process corresponding to the first user space and a corresponding login process of the second user space based on the account synchronization process.

As shown in fig. 4, the login method includes:

step 400, a first user space of the sharing device detects a space switching operation of a user.

In this embodiment, the user space currently logged in by the sharing device (i.e., the first device) is the first user space. When the user wants to switch user space, the user may perform a space switching operation (i.e., the account switching operation described above) on the shared device.

When the first user space detects the space switching operation, the login process corresponding to the first user space can perform login verification on the user.

For example, as shown in fig. 5, in the login system shown in fig. 5, the vehicle-mounted device 51 may be understood as the sharing device, the mobile phone 52 logs in the target cloud account, and the server 53 may perform login verification on the user in cooperation with the vehicle-mounted device 51.

As shown in fig. 6, the user space in which the in-vehicle device 51 is currently logged in is the first user space, and a control 512 is displayed on the display interface 511 of the in-vehicle device 51.

When the user wants to switch the user space, the user can click on control 512 on in-vehicle device 51. At this time, as shown in fig. 7, the in-vehicle device 51 may display a user management window 513 in response to a click operation by the user, the user management window 513 having a "switch account" control 514 displayed therein.

After the user clicks the "switch account" control 514, the in-vehicle device 51 may perform login authentication for the user.

In step 401, a first user space of the sharing device cooperates with a cloud server to perform login verification on a user.

In the login verification process, the login process corresponding to the first user space can cooperate with a cloud server to perform login verification on the user.

The login verification is used for verifying the identity of the user, and verifying whether the user has permission to login the target cloud account corresponding to the second user space (namely, the second account). The login verification may include any one or a combination of a plurality of verification modes such as password verification, face verification, fingerprint verification, two-dimensional code verification, verification code verification and the like.

For example, as shown in fig. 8, the server 53 may perform login authentication for the user by a two-dimensional code authentication method in cooperation with the above-described in-vehicle apparatus 51.

After the user clicks the "switch account" control 514, the in-vehicle device 51 may send a two-dimensional code request to the server 53.

The server 53 may generate a two-dimensional code after receiving the two-dimensional code request, where the two-dimensional code carries a two-dimensional code identifier. Then, the server 53 may transmit the two-dimensional code to the in-vehicle apparatus 51.

After the in-vehicle device 51 receives the two-dimensional code, the in-vehicle device 51 may display the two-dimensional code on the display interface 511.

Alternatively, in other implementations, the vehicle-mounted device 51 may locally generate a two-dimensional code, where the two-dimensional code carries the two-dimensional code identifier.

Then, the in-vehicle device 51 may display the two-dimensional code on the display interface 511, and transmit the two-dimensional code to the server 53.

After viewing the two-dimensional code, the user can scan the two-dimensional code displayed by the in-vehicle device 51 using the mobile phone 52.

At this time, as shown in fig. 9 and 10, the in-vehicle device 51 may prompt the user to "login", the mobile phone 52 may display a consultation interface 521 to the user, prompt the user in the consultation interface 521 to "you are authorizing another device/browser to login account by scanning the two-dimensional code", and provide a "cancel" control 522 and a "login" control 523.

After the user clicks the "login" control 523, the mobile phone 52 may send the two-dimensional code identifier and account credentials obtained by resolving the two-dimensional code to the server 53. The account credentials are used to prove that the handset 52 has logged into the target cloud account.

After receiving the two-dimensional code identifier and the account credential, the server 53 may verify the two-dimensional code identifier and the account credential.

If the two-dimensional code identifier received by the server 53 is consistent with the issued two-dimensional code and the account credential is legal, the server 53 may determine that the login verification is passed.

If the two-dimensional code identifier received by the server 53 is inconsistent with the issued two-dimensional code identifier, or the account credential is an illegal credential, the server 53 may determine that login verification fails.

In another example, after the user clicks the "switch account" control 514, as shown in fig. 11, the in-vehicle device 51 may present an information input box 515 to the user in response to the clicking operation of the user, where the information input box may be used to input the account name and password of the target cloud account, and provide a "confirm" control 516 and a "cancel" control 517.

After the user inputs the account name "11123456789" and the password "123456" of the target cloud account (i.e., the verification information of the second account described above), and clicks the "confirm" control 516, the in-vehicle device 51 may send the account name "11123456789" and the password "123456" to the server 53.

At this time, as shown in fig. 9, the in-vehicle apparatus 51 may prompt the user that it is logging in.

After the server 53 receives the account name "11123456789" and the password "123456", the verification password corresponding to the account name "11123456789" is locally queried at the server.

Subsequently, if the check password queried by the server is consistent with the password "123456" received by the server, the server may determine that the login verification is passed.

If the verification password queried by the server is inconsistent with the password "123456" received by the server, the server may determine that login authentication failed.

In other examples, the vehicle device and the server may also perform login verification through other verification manners. The verification mode adopted by the sharing device and the server is not limited in the embodiment of the application.

After the sharing device and the server perform login verification on the user, if the login verification is passed, the sharing device may perform step 402; if login authentication fails, the server may perform step 412.

Step 402, after the login verification is passed, the server sends the auxiliary credential to the first user space of the shared device.

After the login verification is passed, the server may send a secondary credential (token) to the first user space of the shared device.

The expression form of the auxiliary token can be set according to actual requirements. For example, in some embodiments, the auxiliary token may be a string of characters that may include any one or more of the presentation elements of letters, numbers, symbols, etc.

The auxiliary token may be a token that is sent to the first user space of the sharing device by the server after the login verification is passed; alternatively, the auxiliary token may be a token that the first user space of the shared device actively requests from the server after the login verification is passed.

The auxiliary token may be used to log in the target cloud account, so in some embodiments, in order to avoid that other electronic devices steal the auxiliary token to log in the target cloud account, the sharing device may also send the device identifier of the device to the server.

After the login verification is passed, the server generates an auxiliary token, the server can associate the auxiliary token with the device identifier and the target cloud account corresponding to the second user space, and only the shared device can use the auxiliary token to login the target cloud account, and other electronic devices cannot use the auxiliary token to login the target cloud account.

Step 403, the first user space of the sharing device transmits the auxiliary credential and the account identifier of the target cloud account to the system space of the sharing device.

The account identifier may be determined by the sharing device based on a spatial switching operation of the user, or the account identifier may be sent to the sharing device by the server.

For example, in one example, the user may enter an account name and a password of the target cloud account on the sharing device, and log into the second user space by way of password login. At this time, the sharing device may determine the account identifier of the target cloud account according to the account name of the target cloud account in response to the operation of the user.

In another example, after the login verification is passed, the server may also send an account identifier of the target cloud account to the sharing device when sending the auxiliary token to the sharing device.

After the first user space acquires the auxiliary credential, the login process corresponding to the first user space can transmit the auxiliary credential and the account identification of the target cloud account to the account synchronization process of the system space.

It can be understood that in the existing user space login scheme, the sharing device needs to close the first user space first, then start the second user space to perform login verification, and the first user space and the second user space cannot survive at the same time, so that the login process corresponding to the first user space cannot transfer data to the login process corresponding to the second user space in the survival period.

In addition, since the first user space and the second user space of the sharing device are isolated from each other, even if the first user space and the second user space survive at the same time, the login process corresponding to the first user space cannot transfer data to the login process corresponding to the second user space, and the login process corresponding to the second user space cannot access the data stored in the first user space.

In the login method provided by the embodiment of the application, the login process corresponding to the first user space can use the system space of the shared device as a transfer station, the auxiliary token and the account identification are transferred to the account synchronization process of the system space, and the account synchronization process of the system space transfers the auxiliary token and the account identification to the login process corresponding to the second user space.

By the method, even if the first user space and the second user space are different and survive, the first user space and the second user space are isolated from each other, the login process corresponding to the first user space can safely transmit the auxiliary token and the account identification to the login process corresponding to the second user space by means of the transfer capability of the system space, and the problem that the first user space and the second user space cannot perform data interaction is solved.

Step 404, the system space of the sharing device closes the first user space of the sharing device.

After the account synchronization process of the system space obtains the auxiliary token and the account identifier, the first user space of the sharing device can be closed, the process and the instance corresponding to the first user space are ended, and the system resource of the sharing device is saved.

Step 405, searching a user space corresponding to the target cloud account by using a system space of the sharing device.

Subsequently, the account synchronization process of the system space can search the user space corresponding to the account identifier on the sharing device.

In some embodiments, the account synchronization process of the system space may find the user space corresponding to the account identifier on the sharing device.

At this time, the account synchronization process of the system space may determine the user space corresponding to the account identifier as the second user space.

In other embodiments, the user space corresponding to the target cloud account may not be set on the sharing device.

At this time, the account synchronization process of the system space cannot find the user space corresponding to the account identifier on the sharing device, and the account synchronization process of the system space can create a new user space, determine the new user space as a second user space, and establish an association relationship between the second user space and the account identifier.

The process of creating a new user space by the sharing device may be understood as a process of allocating system resources for the new user space by the sharing device, such as allocating storage space for the new user space by the sharing device, creating an application program interface (Application Programming Interface, API) corresponding to the new user space, and the like.

Subsequently, the account synchronization process of the system space can start the process related to the new user space through the API corresponding to the new user space.

Step 406, the system space of the sharing device starts the second user space of the sharing device.

After the account synchronization process of the system space finds the second user space, the second user space can be started by calling an API corresponding to the second user space.

After the account synchronization process of the system space invokes the API corresponding to the second User space, the sharing device may start a process related to the second User space, such as a login process corresponding to the second User space, a User Interface (UI) display process, and so on.

Step 407, the system space of the sharing device communicates the auxiliary credential to the second user space of the sharing device.

After the sharing device starts the login process corresponding to the second user space, the account synchronization process of the system space may transmit the auxiliary token to the login process corresponding to the second user space.

Step 408, the second user space of the shared device sends a login request to the server, the login request comprising the auxiliary credential.

After the auxiliary token is acquired, a login process corresponding to the second user space may send a login request to the server.

The login request includes the auxiliary token. In some embodiments, the login request further includes a device identifier of the electronic device and/or a target cloud account corresponding to the second user space.

Step 409, the server verifies the auxiliary certificate.

After receiving the login request, the server may verify the auxiliary token in the login request.

The verification mode can comprise any one or more of signature verification, validity verification and character string comparison peer-to-peer verification modes.

For example, the server may compare the received auxiliary token with the issued auxiliary token in terms of a string. If the auxiliary token received by the server is consistent with the auxiliary token issued by the server, the server can judge that the auxiliary token passes the verification; if the auxiliary token received by the server is inconsistent with the auxiliary token issued by the server, the server can determine that the auxiliary token fails to check.

In addition, when the auxiliary token is bound with the device identifier of the sharing device and/or the target cloud account, the login request may further include the device identifier of the sharing device and/or the target cloud account corresponding to the second user space.

At this time, the server may check, in addition to checking the body of the auxiliary token, whether the device identifier of the sharing device is consistent with the device identifier bound by the auxiliary token, and/or whether the target cloud account sent by the sharing device is consistent with the cloud account bound by the auxiliary token.

If the body of the auxiliary token passes the verification, the device identifier of the sharing device is consistent with the device identifier bound by the auxiliary token, and the target cloud account sent by the sharing device is consistent with the cloud account bound by the auxiliary token, the server can determine that the auxiliary token passes the verification, and the second user space of the sharing device can log in the target cloud account.

If the body verification of the auxiliary token fails, the device identifier of the sharing device is inconsistent with the device identifier bound by the auxiliary token, or the target cloud account sent by the sharing device is inconsistent with the cloud account bound by the auxiliary token, the server can determine that the auxiliary token fails to verify, and the second user space of the sharing device cannot log in the target cloud account.

Step 410, after the auxiliary credential passes the verification, the server sends the login credential to the second user space of the sharing device.

When the auxiliary token check passes, the server may send a login token to the second user space of the shared device.

Step 411, log into a second user space of the shared device.

After the second user space receives the login token, the login process corresponding to the second user space can store the login token, log in the second user space of the sharing device, and complete the login process of the second user space.

Subsequently, the user may access the second user space, use the application program in the second user space, and use cloud services provided by the cloud server, such as cloud space, based on the target cloud account.

For example, as shown in fig. 12, after the in-vehicle device 51 receives the login token described above, the in-vehicle device 51 may open the second user space to the user, and display the display interface 518 of the second user space.

Subsequently, the user may use the application in the second user space and use the cloud service provided by the server based on the target cloud account.

Step 412, after the login verification fails, the server sends a second verification result to the first user space of the sharing device.

In some embodiments, a scenario may occur where login authentication fails. At this time, the server may transmit the second authentication result (i.e., the above-described second information) to the first user space of the sharing device.

The second verification result is used for indicating login verification failure.

Step 413, the sharing device resides in the first user space.

When the first user space receives the second verification result, the login process corresponding to the first user space can directly reside in the first user space without switching other user spaces, so that the time consumed by frequently switching the user spaces is saved.

Illustratively, the scenario shown in FIG. 11 is taken as an example. After the user inputs the account name "11123456789" and the password "123456" and clicks the "confirm" control 516, the in-vehicle device 51 may send the account name and the password to the server 53.

After the server 53 receives the account name "11123456789" and the password "123456", the verification password corresponding to the account name "11123456789" is locally queried in the server 53.

Subsequently, assuming that the server 53 inquires that the check password corresponding to the account name "11123456789" is "654321" and is inconsistent with the password "123456" input by the user, the server 53 may send a second verification result to the vehicle-mounted device 51, and notify the vehicle-mounted device 51 that login verification fails.

As shown in fig. 13, after receiving the second verification result, the in-vehicle device 51 may display "password error, please log in again after confirming the password", and reside in the first user space on the display screen of the in-vehicle device 51.

Thereafter, the user may continue to attempt to log into the second user space, or the user may cancel logging into the second user space and continue to use the first user space.

In addition, in some embodiments, in the process of implementing step 401, when the server performs login verification on the user, in addition to verifying the identity of the user, authority verification may also be performed on the target cloud account, so as to verify whether the target cloud account has authority to log in the sharing device.

In the login verification process, the sharing device may send the device identifier of the device to the server.

The server may query whether the target cloud account has the use right of the sharing device according to the device identifier of the sharing device.

If the server inquires that the target cloud account has the use authority of the sharing device and the identity verification of the user passes, the server can judge that the login verification passes.

If the server inquires that the target cloud account does not have the use authority of the sharing device, or the identity verification of the user fails, the server can judge that the login verification fails.

The server may query the permission of the target cloud account in any one or more of white list query, black list query, administrator query, and the like.

For example, assume a certain smart large screen is a shared device. In one example, the smart screen is provided with a white list, and the administrator account of the smart screen adds account a and account B to the white list, granting account a and account B permission to use the smart screen.

Subsequently, if the user logs in the account A on the intelligent large screen, the server can search the white list corresponding to the intelligent large screen according to the equipment identifier of the intelligent large screen.

Then, the server can find the account A in the white list, so the server can determine that the account A has the right to use the intelligent large screen.

If the user logs in the account C on the intelligent large screen, the server does not inquire the account C in the white list, and the server can determine that the account C does not have the authority to use the intelligent large screen.

In another example, the smart large screen is provided with a blacklist, and the account number D and the account number E are added to the blacklist by the administrator account number of the smart large screen, so that the account number D and the account number E are prohibited from using the smart large screen.

Subsequently, if the user logs in the account number D on the intelligent large screen, the server can search the blacklist corresponding to the intelligent large screen according to the equipment identifier of the intelligent large screen.

Then, the server can find the account number D in the blacklist, so the server can determine that the account number D does not have the authority to use the intelligent large screen.

If the user logs in the account number F on the intelligent large screen, the server does not inquire the account number F in the blacklist, and the server can determine that the account number F has the authority to use the intelligent large screen.

In other examples, the server may query whether the target cloud account has the usage rights of the sharing device in other manners.

In summary, in the login method provided in the embodiment of the present application, the login account of the second user space may be a target cloud account set by the server, and the sharing device may cooperate with the server to perform login verification on the user.

In the login verification process, the server can verify the authority of the target cloud account in addition to the identity of the user. At this time, an administrator of the sharing device can access the server through the cloud account with the management authority, remotely add or delete the authority of using the sharing device of other cloud accounts, and directly operate the sharing device without the administrator, thereby greatly improving the flexibility of device management.

In addition, because the login account of the second user space is the target cloud account, after the sharing device logs in the second user space, the user can directly use the cloud service provided by the server based on the target cloud account, the user does not need to log in the cloud account again, and the operation burden of the user is reduced.

In addition, if login verification fails, the sharing device can reside in the first user space, and users are not required to manually switch different user spaces and perform login authentication again, so that the operation of the users is reduced, the use experience of the users can be effectively improved, and the sharing device has strong usability and practicability.

It should be understood that the order of steps in the foregoing embodiments does not mean that the order of execution of the steps should be determined by the functions and internal logic, and should not be construed as limiting the implementation of the embodiments of the present application.

In the practical application process, the sharing device may implement the login method described in any of the above embodiments, or the sharing device may implement a combination of the above embodiments.

Furthermore, the steps described in the above embodiments are not all necessary, and the sharing device may implement some or all of the steps, and/or add some steps, and/or replace some steps in the actual implementation process. The embodiment of the application does not limit the specific implementation of the login method for the sharing device.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/electronic device and method may be implemented in other manners. For example, the apparatus/electronic device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable storage medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable storage medium may include content that is subject to appropriate increases and decreases as required by jurisdictions and by jurisdictions in which such computer readable storage medium does not include electrical carrier signals and telecommunications signals.

Finally, it should be noted that: the foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A login method applied to a first device, comprising:

logging in a first account and displaying a first interface;

detecting an account switching operation of a user;

2. The method of claim 1, wherein the authentication of the second account includes any one or more of password authentication, face authentication, fingerprint authentication, two-dimensional code authentication, and authentication code authentication.

3. The method of claim 1 or 2, wherein the sending, in response to the account switching operation, a verification request for a second account to a server comprises:

4. A method according to any one of claims 1 to 3, wherein the logging in the second account if the first information returned by the server is obtained includes:

receiving login credentials returned by the server;

And logging in the second account according to the login credentials.

5. The method of claim 4, wherein receiving the first information returned by the server and sending a login request to the server comprise:

6. The method of claim 5, wherein the account synchronization process sending the auxiliary credential to a login process corresponding to the second account comprises:

7. The method of any of claims 1-6, wherein the user data corresponding to the first account is different from the user data corresponding to the second account.

8. The method of any one of claims 1 to 7, wherein the first interface and the second interface are different interfaces.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the method of any one of claims 1 to 8 when the computer program is executed.

10. A computer readable storage medium configured to store a computer program, characterized in that the computer program when executed by a processor implements the method of any one of claims 1 to 8.

11. A chip system comprising a memory and a processor configured to execute a computer program stored in the memory to implement the method of any one of claims 1 to 8.