Device login method, device, equipment and storage medium

Abstract

The present application relates to the field of server technology, and provides a device login method, apparatus, device and storage medium. The method obtains device information of a terminal device in response to a login request of a terminal device to an application software; queries a storage space for a unique identifier corresponding to the terminal device according to the device information, wherein the storage space includes an application software cache, a local storage and a keychain password management system; generates a unique identifier if the storage space does not include the unique identifier; establishes a login connection with the terminal device according to the unique identifier, user data is not easily lost, and the unique identifier corresponds to a unique terminal device, so that the server can accurately identify the identity of the login device, thereby improving login security.

Description

Technical Field

[0001] The present invention relates to the field of server technology, and in particular to a device login method, apparatus, device and storage medium. Background Art

[0002] In recent years, with the development of computer technology, terminal devices such as smart phones have become indispensable products in daily life. Various application software (Application, APP) are installed on the terminal devices. Users can log in to the APP on the terminal devices by entering their account numbers and other methods, and realize various functions after logging in.

[0003] At present, most terminal device operating systems do not have specific control methods for login devices, and the server cannot limit the number of terminal devices that log in. When the terminal device logs in, the server will obtain a value through the application developer identifier (Identifier For Vendor, IDFV) to identify the terminal device. The value obtained for all applications from the same developer is the same, and the value will be deleted at the same time when the APP is deleted.

[0004] However, the device login method in the prior art cannot accurately determine whether the terminal device can be logged in, user data is easily lost, and the security is poor. Summary of the invention

[0005] The present application provides a device login method, apparatus, device and storage medium, thereby solving the technical problems in the prior art of device login methods, such as the inability to accurately determine whether a terminal device can be logged in, easy loss of user data and poor security.

[0006] In a first aspect, the present application provides a device login method, comprising:

[0007] In response to a login request from a terminal device to an application software, obtaining device information of the terminal device;

[0008] According to the device information, query the storage space for a unique identifier corresponding to the terminal device, wherein the storage space includes an application software cache, a local storage, and a keychain password management system;

[0009] If the storage space does not include the unique identifier, generating a unique identifier;

[0010] A login connection is established with the terminal device according to the unique identifier.

[0011] Here, the device login method provided by the present application can determine whether login is allowed through the unique identifier corresponding to the terminal device when verifying the login device. The unique identifier here can be saved in the application software cache, local storage and keychain password management system. Even if the APP is deleted, the keychain password management system still has the unique identifier, and the terminal device login will not fail due to the deletion of the APP, user data is not easily lost, and the unique identifier corresponds to a unique terminal device. The server can accurately identify the identity of the login device, thereby improving login security.

[0012] Optionally, before establishing a login connection with the terminal device according to the unique identifier, the method further includes:

[0013] If the unique identifier exists in the storage space, the unique identifier is obtained.

[0014] Here, the present application is aimed at a terminal device that has been pre-logged in or has saved a unique identifier, and can obtain the unique identifier corresponding to the terminal device, so as to accurately verify the login of the terminal device based on the unique identifier.

[0015] Optionally, after generating a unique identifier if the storage space does not include the unique identifier, the method further includes:

[0016] The unique identifier is saved in the software cache, local storage and keychain password management system respectively.

[0017] Here, after generating a unique identifier for a new terminal device, the present application can save the unique identifier to the software cache, local storage, and keychain password management system. Since the user information may be lost when the APP is deleted due to the unique identifier being saved in the software cache and local storage, in order to ensure the security and reliability of user information, the unique identifier is also saved in the keychain password management system. Even if the APP-related information in the operating system is deleted, the terminal device can still be logged in and authenticated based on the unique identifier saved in the keychain password management system.

[0018] Optionally, establishing a login connection with the terminal device according to the unique identifier includes:

[0019] Determine a login mode corresponding to the login request, wherein the login mode includes single sign-on, single device login, and multi-device login;

[0020] A login connection is established with the terminal device according to the login method and the unique identifier.

[0021] Among them, this application can set different login methods, including single sign-on, single device login and multi-device login, to meet the different needs of users, ensure the security of login and user experience, and improve the flexibility of device login.

[0022] Optionally, determining a login mode corresponding to the login request includes:

[0023] The login method corresponding to the login request is determined according to at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

[0024] Here, this application can determine the current login method based on the login type corresponding to the preset terminal device, the device login type set by the APP, or the login type corresponding to the login account, etc., to meet the user's login needs for different scenarios.

[0025] Optionally, establishing a login connection with the terminal device according to the login mode and the unique identifier includes:

[0026] If the login mode is single sign-on, a single sign-on connection is established with the terminal device according to the unique identifier.

[0027] Optionally, establishing a login connection with the terminal device according to the login mode and the unique identifier includes:

[0028] If the login mode is single-device login, a login connection is established with the terminal device according to preset binding information between the terminal device and the unique identifier.

[0029] Optionally, establishing a login connection with the terminal device according to the login mode and the unique identifier includes:

[0030] If the login mode is multi-device login, a login connection is established with the terminal device according to a preset device binding list and a binding unique identifier corresponding to the preset device binding list.

[0031] In a second aspect, the present application provides a device login apparatus, comprising:

[0032] A first acquisition module, configured to acquire device information of the terminal device in response to a login request of the terminal device to the application software;

[0033] A query module, used to query the unique identifier corresponding to the terminal device in the storage space according to the device information, wherein the storage space includes application software cache, local storage and keychain password management system;

[0034] A generating module, configured to generate a unique identifier if the storage space does not include the unique identifier;

[0035] A login connection module is used to establish a login connection with the terminal device according to the unique identifier.

[0036] Optionally, after the login connection module establishes a login connection with the terminal device according to the unique identifier, the apparatus further includes:

[0037] The second acquisition module is used to acquire the unique identifier if the unique identifier exists in the storage space.

[0038] Optionally, if the storage space does not include the unique identifier, after the generating module generates the unique identifier, the apparatus further includes:

[0039] The storage module is used to save the unique identifier to the software cache, local storage and keychain password management system respectively.

[0040] Optionally, the login connection module is specifically used for:

[0041] Determine a login mode corresponding to the login request, wherein the login mode includes single sign-on, single device login, and multi-device login;

[0042] A login connection is established with the terminal device according to the login method and the unique identifier.

[0043] Optionally, the login connection module is further specifically used for:

[0044] The login method corresponding to the login request is determined according to at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

[0045] Optionally, the login connection module is further specifically used for:

[0046] If the login mode is single sign-on, a single sign-on connection is established with the terminal device according to the unique identifier.

[0047] Optionally, the login connection module is further specifically used for:

[0048] If the login mode is single-device login, a login connection is established with the terminal device according to preset binding information between the terminal device and the unique identifier.

[0049] Optionally, the login connection module is further specifically used for:

[0050] If the login mode is multi-device login, a login connection is established with the terminal device according to a preset device binding list and a binding unique identifier corresponding to the preset device binding list.

[0051] In a third aspect, the present application provides a device login device, including: at least one processor and a memory;

[0052] The memory stores computer-executable instructions;

[0053] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the device login method as described in the first aspect and various possible designs of the first aspect.

[0054] In a fourth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions. When a processor executes the computer execution instructions, the device login method described in the first aspect and various possible designs of the first aspect is implemented.

[0055] In a fifth aspect, the present invention provides a computer program product, including a computer program, which, when executed by a processor, implements the device login method as described in the first aspect and various possible designs of the first aspect.

[0056] The device login method, apparatus, device and storage medium provided by the present application, wherein when verifying the login device, the method can determine whether login is allowed by the unique identifier corresponding to the terminal device, and the unique identifier here can be saved in the application software cache, local storage and keychain password management system. Even if the APP is deleted, the keychain password management system still has the unique identifier, and the terminal device login will not fail due to the deletion of the APP, and user data is not easily lost. Moreover, the unique identifier corresponds to a unique terminal device, and the server can accurately identify the identity of the login device, thereby improving login security. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0058] Figure 1 A schematic diagram of a device login system architecture provided in an embodiment of the present application;

[0059] Figure 2 A schematic diagram of a device login method provided in an embodiment of the present application;

[0060] Figure 3 A flowchart of another device login method provided in an embodiment of the present application;

[0061] Figure 4 A schematic diagram of the structure of a device login device provided in an embodiment of the present application;

[0062] Figure 5 A schematic diagram of the structure of a device login device provided in an embodiment of the present application.

[0063] The above drawings show clear embodiments of the present disclosure, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present disclosure in any way, but to illustrate the concepts of the present disclosure to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0064] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0065] The terms "first", "second", "third", and "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0066] In the login system of many APPs, it is necessary to limit the number of login devices. Some existing operating systems do not provide a complete device login solution. For example, some operating systems have a "sandbox" feature, local data is easily lost, and local device records are inaccurate, which makes login device restrictions prone to errors. Existing device authentication solutions mostly use the method of sending a token from the server to the client. This method has the risk of client loss, cannot limit the number of login devices, and cannot determine whether the device is a new device. The existing technology can obtain a value to identify the terminal device through the IDFV method, but the value obtained by all applications of the same developer is the same. When there are multiple APPs from the same developer on the terminal device, the use will be inaccurate, or the announcement identifier can also be used to distinguish the terminal devices, but the user can turn off the announcement tracking in the system settings, and then the result is a null value, which cannot be used for user tracking. At this stage, there is no complete login solution to deal with different login requirements such as: single sign-on, single device login, and multi-device login. It is impossible to accurately determine whether the terminal device can log in, user data is easily lost, and security is poor.

[0067] In order to solve the above problems, an embodiment of the present application provides a device login method, apparatus, device and storage medium, wherein the method generates a unique identifier for a terminal device and permanently stores the unique identifier, providing a complete solution for restricting login devices from the generation of the terminal device unique identifier to storage and determination.

[0068] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of user data and other information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0069] Optional, Figure 1 A schematic diagram of a device login system architecture provided in an embodiment of the present application. Figure 1 In the above architecture, the above architecture includes at least one of a data acquisition device 101, a processing device 102 and a display device 103.

[0070] It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the architecture of the device login system. In other feasible implementations of the present application, the above architecture may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently, which can be determined according to the actual application scenario and is not limited here. Figure 1 The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0071] In a specific implementation process, the data acquisition device 101 may include an input / output interface and may also include a communication interface. The data acquisition device 101 may be connected to the processing device via the input / output interface or the communication interface.

[0072] When verifying the login device, the processing device 102 can determine whether to allow login through the unique identifier corresponding to the terminal device. The unique identifier here can be saved in the application software cache, local storage and keychain password management system. Even if the APP is deleted, the keychain password management system still has the unique identifier.

[0073] The display device 103 may also be a touch display screen or a screen of a terminal device, which is used to receive user instructions while displaying the above content to achieve interaction with the user.

[0074] It should be understood that the above-mentioned processing device can be implemented by a processor reading instructions in a memory and executing the instructions, or it can be implemented by a chip circuit.

[0075] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0076] The technical solution of the present application is described in detail below in conjunction with specific embodiments:

[0077] Optionally, Figure 2 A schematic diagram of a device login method provided in an embodiment of the present application. The execution subject of the embodiment of the present application can be Figure 1 The processing device 102 in the embodiment may be a server, and the specific execution subject may be determined according to the actual application scenario. Figure 2 As shown, the method comprises the following steps:

[0078] S201: In response to a login request from a terminal device to an application software, obtaining device information of the terminal device.

[0079] The user can log in by entering account information such as account number and password on the terminal device, or log in by means of a verification code, and send a login request to the server. Optionally, if the user logs in for the first time, a login request is sent through registration.

[0080] Optionally, the embodiment of the present application can establish https communication with the cloud through a server storage accessor, including a local data upload function and a remote data download function.

[0081] Optionally, during the data transmission and registration and login process, the embodiment of the present application can implement the encryption function through an encryption encryptor. In a possible implementation, the AES128 method is used for encryption and decryption. First, the data to be encrypted is converted into the NSData data type, and then encrypted by the encryption method using the AES128 method. The encryption is performed on the terminal device side. The decryption is performed on the server. The key is agreed in advance by the server and the terminal device and is hard-coded in the program.

[0082] Optionally, the device information may be one or more of an identity document (ID) of the terminal device, a device name, a device model, a name, a color, and a city where the user's geographic location is located.

[0083] S202: Query the storage space for the unique identifier corresponding to the terminal device according to the device information.

[0084] Among them, the storage space includes application cache, local storage and keychain password management system.

[0085] Among them, since some operating systems use a sandbox system, when the APP is deleted, the APP-related information will also be deleted. Therefore, the unique identifier should not only be stored locally in the APP, but also in the keychain password management system (keychain)

[0086] Optionally, when querying, you can use the Keychain accessor to query whether the device information of the terminal device and the corresponding unique identifier exist in the keychain. The Keychain accessor is responsible for accessing and encrypting the keychain. When accessing, you need to enter a key. The key must be consistent when depositing and withdrawing. The key is stored in the APP.

[0087] Among them, the unique identifier in the embodiment of the present application can be represented by uuid.

[0088] Optionally, the uuid is generated by the encapsulation system CFUUIDCreate method, and each device has a unique uuid.

[0089] Optionally, when a login request from a new terminal device is received, if the uuid corresponding to the terminal device is not found, a uuid is generated.

[0090] Optionally, when querying, first check whether there is a unique identifier in the running APP cache. If it exists, get it directly, otherwise search in the local storage. If it does not exist, search in the keychain. If not, generate a new one and store it.

[0091] S203: If the storage space does not include a unique identifier, generate a unique identifier.

[0092] Optionally, before establishing a login connection with the terminal device according to the unique identifier, the method further includes:

[0093] If a unique identifier exists in the storage space, obtain the unique identifier.

[0094] Here, the embodiment of the present application is aimed at a terminal device that has been pre-logged in or has saved a unique identifier, and can obtain the unique identifier corresponding to the terminal device, so as to accurately verify the login of the terminal device based on the unique identifier.

[0095] S204: Establishing a login connection with the terminal device according to the unique identifier.

[0096] Optionally, a login connection is established with the terminal device based on the unique identifier, including: determining a login method corresponding to the login request, wherein the login methods include single sign-on, single device login and multi-device login; and establishing a login connection with the terminal device based on the login method and the unique identifier.

[0097] Among them, the embodiments of the present application can set different login methods, including single sign-on, single device login and multi-device login, to meet the different needs of users, ensure the security of login and user experience, and improve the flexibility of device login.

[0098] Optionally, determining the login method corresponding to the login request includes: determining the login method corresponding to the login request based on at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

[0099] Here, the embodiment of the present application can determine the current login method according to the login type corresponding to the preset terminal device, or the device login type set by the APP, or the login type corresponding to the login account, etc., to meet the user's login needs for different scenarios.

[0100] Optionally, a login connection is established with the terminal device according to the login method and the unique identifier, including: if the login method is single sign-on, a single sign-on connection is established with the terminal device according to the unique identifier.

[0101] In a possible implementation, single sign-on means that only one terminal device with the same account can log in and access the backend at the same time.

[0102] When the user logs in, the uuid is encrypted in the encryptor and then uploaded to the server using the server storage accessor. If the server does not have it, it is directly stored. If the server has the old uuid, it is overwritten. All subsequent APP requests must bring the local uuid to the server. If the server determines that it is inconsistent with the server, the transaction is prohibited. At this time, if the old login device uuid is different from the server, the transaction will be prohibited, ensuring that only one uuid is currently valid, that is, single sign-on.

[0103] Optionally, a login connection is established with the terminal device according to the login method and the unique identifier, including: if the login method is single-device login, a login connection is established with the terminal device according to preset binding information between the terminal device and the unique identifier.

[0104] Optionally, the preset device binding list includes a one-to-one correspondence between device information of the terminal device and the uuid of the terminal device.

[0105] In one possible implementation, single-device login refers to binding an account to a single terminal device, and other terminal devices cannot log in except this terminal device.

[0106] First, the new device determiner is used to determine: if the uuid does not exist locally, it is directly determined to be a new device, and the uuid is generated and stored locally.

[0107] Secondly, bind a new device: You can ask the user to confirm whether to bind the terminal device through a pop-up window on the terminal device's APP. Inform the user that there can only be one device that can be logged in. After binding, the old device will become invalid, and SMS verification is required at this time.

[0108] Request verification after login: All subsequent APP requests must carry the local uuid to the server. If the server determines that it is inconsistent with the server, the transaction will be prohibited, and the user will be informed to choose whether to rebind. SMS verification is required at this time.

[0109] Optionally, a login connection is established with the terminal device according to the login method and the unique identifier, including: if the login method is multi-device login, a login connection is established with the terminal device according to a preset device binding list and a binding unique identifier corresponding to the preset device binding list.

[0110] The preset device binding list can be determined according to actual conditions, and the present application embodiment does not impose any specific restrictions on this. The preset device binding list can be preset by a user.

[0111] In a possible implementation, multiple devices are logged in, and the number of devices that can be logged in is limited: an account is bound to multiple terminal devices, and the upper limit of binding n can be set, and only the terminal devices in the binding list can log in. Among them, n is an arbitrary positive integer.

[0112] Preset device binding list: a list of uuids and device information of all devices that have logged in under the server account. uuids and device information are bound one by one.

[0113] Device information acquirer: Get the system information of the current mobile phone, including device model, name, color, and the city where the user is located.

[0114] Device binding: When the uuid does not exist locally, the acquired data is compared with the device information in the server binding list. There are two situations:

[0115] If there is no identical one, it is considered to be a brand new device, and a pop-up window will be displayed to ask the user whether to bind. If the user confirms to bind, the uuid and device information will be uploaded and saved in the binding list.

[0116] If there are the same ones, it is considered that the old device has lost the local UUID information by resetting the phone or other operations. At this time, the UUID corresponding to the remote device information is obtained and overwritten with the local UUID.

[0117] Device restriction: When the number of devices in the account binding list reaches the specified value n, new devices cannot be bound. If the uuid of the user when logging in is not in the device list, the user cannot log in.

[0118] The device login method provided in the embodiment of the present application can determine whether login is allowed through the unique identifier corresponding to the terminal device when verifying the login device. The unique identifier here can be saved in the application software cache, local storage and keychain password management system. Even if the APP is deleted, the keychain password management system still has the unique identifier, and the terminal device login will not fail due to the deletion of the APP, and user data is not easily lost. Moreover, the unique identifier corresponds to a unique terminal device, and the server can accurately identify the identity of the login device, thereby improving login security.

[0119] Optionally, the unique identifier in the embodiment of the present application is permanently stored after being generated, which improves the security of user information. Figure 3 Another device login method provided in the embodiment of the present application is as follows: Figure 3 As shown, the method includes:

[0120] S301: In response to a login request from a terminal device to an application software, obtaining device information of the terminal device.

[0121] S302: According to the device information, query the storage space for the unique identifier corresponding to the terminal device.

[0122] Among them, storage space includes application cache, local storage and keychain password management system;

[0123] S303: If the storage space does not include a unique identifier, generate a unique identifier.

[0124] Optionally, the implementation of step S301 to step S303 is similar to the implementation of step S201 to step S203, and the embodiment of the present application does not make any specific limitation.

[0125] S304: Save the unique identifier to the software cache, local storage and keychain password management system respectively.

[0126] S305: Establish a login connection with the terminal device according to the unique identifier.

[0127] Here, after generating a unique identifier for a new terminal device, the embodiment of the present application can save the unique identifier to the software cache, local storage and keychain password management system. Since the user information may be lost when the APP is deleted when the unique identifier is saved in the software cache and local storage, in order to ensure the security and reliability of user information, the unique identifier is also saved in the keychain password management system. Even if the APP-related information in the operating system is deleted, the terminal device can still be logged in and authenticated based on the unique identifier saved by the keychain password management system.

[0128] Figure 4 A schematic diagram of the structure of a device login device provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the device of the embodiment of the present application includes: a first acquisition module 401, a query module 402, a generation module 403 and a login connection module 404. The device login device here can be the above-mentioned processing device, processor, server itself, or a chip or integrated circuit that realizes the functions of the processing device, processor, and server. It should be noted here that the division of the first acquisition module 401, the query module 402, the generation module 403 and the login connection module 404 is only a division of logical functions. Physically, the two can be integrated or independent.

[0129] The first acquisition module is used to obtain device information of the terminal device in response to a login request of the terminal device to the application software;

[0130] A query module, used to query the storage space for the unique identifier corresponding to the terminal device according to the device information, wherein the storage space includes the application software cache, local storage and keychain password management system;

[0131] A generating module, used for generating a unique identifier if the storage space does not include the unique identifier;

[0132] The login connection module is used to establish a login connection with the terminal device according to the unique identifier.

[0133] Optionally, after the login connection module establishes a login connection with the terminal device according to the unique identifier, the apparatus further includes:

[0134] The second acquisition module is used to acquire the unique identifier if there is a unique identifier in the storage space.

[0135] Optionally, if the storage space does not include the unique identifier, after the generation module generates the unique identifier, the apparatus further includes:

[0136] The storage module is used to save the unique identifier to the software cache, local storage and keychain password management system respectively.

[0137] Optionally, the login connection module is specifically used for:

[0138] Determine the login method corresponding to the login request, where the login methods include single sign-on, single device login, and multi-device login;

[0139] A login connection is established with the terminal device based on the login method and unique identifier.

[0140] Optionally, the login connection module is further specifically used for:

[0141] The login method corresponding to the login request is determined according to at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

[0142] Optionally, the login connection module is further specifically used for:

[0143] If the login method is single sign-on, a single sign-on connection is established with the terminal device based on the unique identifier.

[0144] Optionally, the login connection module is further specifically used for:

[0145] If the login method is single-device login, a login connection is established with the terminal device according to the preset binding information between the terminal device and the unique identifier.

[0146] Optionally, the login connection module is further specifically used for:

[0147] If the login method is multi-device login, a login connection is established with the terminal device according to the preset device binding list and the binding unique identifier corresponding to the preset device binding list.

[0148] refer to Figure 5, which shows a schematic diagram of the structure of a device login device 500 suitable for implementing the embodiment of the present disclosure, and the device login device 500 may be a terminal device or a server. The terminal device may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (PMPs), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The device login device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0149] like Figure 5 As shown, the device login device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 to a random access memory (RAM) 503. Various programs and data required for the operation of the device login device 500 are also stored in the RAM 503. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0150] Typically, the following devices may be connected to the I / O interface 505: input devices 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 508 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 509. The communication devices 509 may allow the device login device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The device login device 500 having various devices is shown, but it should be understood that it is not required to implement or have all the devices shown. More or fewer devices may be implemented or have instead.

[0151] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0152] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0153] The above-mentioned computer-readable medium may be included in the above-mentioned device login device; or it may exist independently without being assembled into the device login device.

[0154] The computer-readable medium carries one or more programs. When the one or more programs are executed by the device login device, the device login device executes the method shown in the above embodiment.

[0155] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0156] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0157] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0158] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0159] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0160] The device login device of the embodiment of the present application can be used to execute the technical solutions in the above-mentioned method embodiments of the present application. Its implementation principles and technical effects are similar and will not be repeated here.

[0161] An embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement any of the above-mentioned device login methods.

[0162] An embodiment of the present application also provides a computer program product, including a computer program, which is used to implement any of the above-mentioned device login methods when the computer program is executed by a processor.

[0163] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0164] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0165] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0166] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A device login method, It is characterized in that include: In response to a login request from a terminal device to an application software, obtaining device information of the terminal device; According to the device information, query the storage space for a unique identifier corresponding to the terminal device, wherein the storage space includes an application software cache, a local storage, and a keychain password management system; If the storage space does not include the unique identifier, generating a unique identifier and saving the unique identifier in a keychain password management system; Establishing a login connection with the terminal device according to the unique identifier; The establishing a login connection with the terminal device according to the unique identifier includes: Determine a login mode corresponding to the login request, wherein the login mode includes single sign-on, single device login, and multi-device login; Establishing a login connection with the terminal device according to the login method and the unique identifier; The determining a login method corresponding to the login request includes: The login method corresponding to the login request is determined according to at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

2. The method according to claim 1, It is characterized in that Before establishing a login connection with the terminal device according to the unique identifier, the method further includes: If the unique identifier exists in the storage space, the unique identifier is obtained.

3. The method according to claim 1, It is characterized in that After generating a unique identifier if the storage space does not include the unique identifier, the method further includes: The unique identifier is saved in the software cache and the local storage respectively.

4. The method according to any one of claims 1 to 3, It is characterized in that The establishing a login connection with the terminal device according to the login mode and the unique identifier includes: If the login mode is single sign-on, a single sign-on connection is established with the terminal device according to the unique identifier.

5. The method according to any one of claims 1 to 3, It is characterized in that The establishing a login connection with the terminal device according to the login mode and the unique identifier includes: If the login mode is single-device login, a login connection is established with the terminal device according to preset binding information between the terminal device and the unique identifier.

6. The method according to any one of claims 1 to 3, It is characterized in that The establishing a login connection with the terminal device according to the login mode and the unique identifier includes: If the login mode is multi-device login, a login connection is established with the terminal device according to a preset device binding list and a binding unique identifier corresponding to the preset device binding list.

7. A device login device, It is characterized in that include: A first acquisition module, configured to acquire device information of the terminal device in response to a login request of the terminal device to the application software; A query module, used to query the unique identifier corresponding to the terminal device in the storage space according to the device information, wherein the storage space includes application software cache, local storage and keychain password management system; A generating module, configured to generate a unique identifier if the storage space does not include the unique identifier; A storage module, used to save the unique identifier to a keychain password management system; A login connection module, used to establish a login connection with the terminal device according to the unique identifier; The login connection module is specifically used for: Determine a login mode corresponding to the login request, wherein the login mode includes single sign-on, single device login, and multi-device login; Establishing a login connection with the terminal device according to the login method and the unique identifier; The login connection module is also specifically used for: The login method corresponding to the login request is determined according to at least one of a first preset login type corresponding to the application software, a second preset login type corresponding to the terminal device, and a third preset login type corresponding to the login account.

8. A device login device, It is characterized in that include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the device login method according to any one of claims 1 to 6.

9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the device login method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images