Login device management method and apparatus, and device

Abstract

The present application provides a login device management method and apparatus, and a device. The method comprises: receiving an account login event of a target account logging in to a corresponding application client on a target device; acquiring a list of commonly used trusted devices; when the number of commonly used devices is less than a quantity threshold value, adding target device information of the target device carried in the account login event to the list of commonly used trusted devices; and when the number of commonly used devices is greater than or equal to the quantity threshold value, moving first device information of a first device with the earliest login time in the list of commonly used trusted devices from the list of commonly used trusted devices to a list of verified devices, and adding the target device information to the list of commonly used trusted devices, wherein the device types of devices in the list of commonly used trusted devices and the list of verified devices are commonly used trusted device types and verified device types, respectively, and the commonly used trusted devices and the verified devices correspond to different management strategies in different service scenarios. Thus, the diversity and convenience of login device management modes are improved.

Description

Login device management method, device and equipment

[0001] Priority information

[0002] This application claims priority to Chinese patent application number "202311560670.4" filed on November 21, 2023, entitled "Login Device Management Method, Apparatus and Equipment", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The embodiments of the present application relate to the technical field of device management, and in particular to a login device management method, apparatus, and device. Background Art

[0004] With the development of device management technology, users can use the same account to log in to the same client based on multiple login devices, where the login device can be a mobile phone, computer and other terminal devices.

[0005] Currently, when a user logs in to the same client using the same account through multiple login devices, the client can display the multiple login devices. However, the existing technology has the problem of a relatively single management method for login devices. Summary of the Invention

[0006] The present application provides a login device management method, apparatus and equipment to improve the diversity and convenience of login device management methods.

[0007] In the first aspect, the present application provides a login device management method, the method comprising: receiving an account login event of a target account logging into an application client corresponding to a target device; in response to the account login event, obtaining a list of commonly used trusted devices of the target account, and determining whether the number of commonly used devices in the list of commonly used trusted devices is less than a quantity threshold; when the number of commonly used devices is less than the quantity threshold, adding the target device information of the target device carried in the account login event to the list of commonly used trusted devices; when the number of commonly used devices is greater than or equal to the quantity threshold, moving the first device information of the first device from the list of commonly used trusted devices to the list of verified devices of the target account, and adding the target device information to the list of commonly used trusted devices; the first device is the device with the earliest login time in the list of commonly used trusted devices; wherein, the device type of the device in the commonly used trusted device list is a commonly used trusted device type, and the device type of the device in the verified device list is a verified device type, and devices of the commonly used trusted device type and devices of the verified device type correspond to different management strategies in different business scenarios.

[0008] In the second aspect, the present application provides a login device management device, including a first receiving module for receiving an account login event of a target account logging into an application client corresponding to a target device; an acquisition judgment module for obtaining a commonly used trusted device list of the target account in response to the account login event, and judging whether the number of commonly used devices in the commonly used trusted device list is less than a quantity threshold; a first adding module for adding the target device information of the target device carried in the account login event to the commonly used trusted device list when the number of commonly used devices is less than the quantity threshold; an adding moving module for moving the first device information of the first device from the commonly used trusted device list to the verified device list of the target account when the number of commonly used devices is greater than or equal to the quantity threshold, and adding the target device information to the commonly used trusted device list; the first device is the device with the earliest login time in the commonly used trusted device list; wherein, the device type of the device in the commonly used trusted device list is a commonly used trusted device type, and the device type of the device in the verified device list is a verified device type, and devices of the commonly used trusted device type and devices of the verified device type correspond to different management policies in different business scenarios.

[0009] In a third aspect, the present application provides an electronic device comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as in the first aspect or its various implementations.

[0010] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method in the first aspect or its various implementations.

[0011] In a fifth aspect, the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect or its various implementations.

[0012] In a sixth aspect, the present application provides a computer program, which enables a computer to execute the method in the first aspect or its various implementations.

[0013] Through the technical solution of the present application, the electronic device can receive an account login event of the target account logging into the application client corresponding to the target device. In response to the account login event, the target account's commonly used trusted device list can be obtained, and it can be determined whether the number of commonly used devices in the commonly used trusted device list is less than the number threshold: when the number of commonly used devices is less than the number threshold, the electronic device can add the target device information of the target device carried in the account login event to the commonly used trusted device list; when the number of commonly used devices is greater than or equal to the number threshold, the electronic device can move the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and add the target device information to the commonly used trusted device list, wherein the first device is the device with the earliest login time in the commonly used trusted device list, the device type of the device in the commonly used trusted device list is the commonly used trusted device type, the device type of the device in the verified device list is the verified device type, and devices of the commonly used trusted device type and devices of the verified device type correspond to different management policies in different business scenarios. In the above process, the electronic device can classify the login devices into two types: commonly used trusted device types and verified device types, and add the target device to the commonly used trusted device list according to the number of commonly used devices and the size of the number threshold, and transfer devices between the commonly used trusted device list and the verified device list, etc., which not only enriches the way to manage login devices and improves the diversity of login device management methods, but also facilitates the use of different management strategies to handle different types of devices in different business scenarios, thereby improving the convenience of login device management methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. 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 any creative work.

[0015] FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0016] FIG2 is a flowchart of a login device management method provided in an embodiment of the present application;

[0017] FIG3 is a schematic diagram of a login device management method provided in an embodiment of the present application;

[0018] FIG4 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0019] FIG5 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0020] FIG6 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0021] FIG7 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0022] FIG8 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0023] FIG9 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0024] FIG10 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0025] FIG11 is a schematic diagram of another login device management method provided in an embodiment of the present application;

[0026] FIG12 is a schematic diagram of a login device management apparatus 1200 provided in an embodiment of the present application;

[0027] FIG13 is a schematic block diagram of an electronic device 1300 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of this 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 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 variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0031] As mentioned above, the existing technology has the problem of a relatively simple management method for login devices.

[0032] In order to solve the above technical problems, the present application can divide login devices into two types: commonly used trusted device types and verified device types, and according to the number of commonly used devices and the size of the number threshold, add the target device to the commonly used trusted device list, transfer devices between the commonly used trusted device list and the verified device list, etc., thereby not only enriching the way to manage login devices and improving the diversity of login device management methods, but also facilitating the use of different management strategies to handle different types of devices in different business scenarios, thereby improving the convenience of login device management methods.

[0033] It should be understood that the technical solution of this application can be applied to the following scenarios, but is not limited to:

[0034] It should be noted that the solution provided in the embodiments of the present application can be executed by any electronic device with login device management capabilities, and the present application does not impose any specific restrictions on the electronic device. For example, the electronic device can be a server. The server can be a single server, a server cluster consisting of multiple servers, or a cloud platform control center, but is not limited thereto. Alternatively, the electronic device can be a terminal device. The terminal device can be a tablet computer, a laptop computer, or a desktop computer, etc. Alternatively, the electronic device can be implemented as a combination of a server and a terminal device, wherein the server and the terminal device can communicate wirelessly or wired.

[0035] In some implementations, as shown in FIG1 , the application scenario may include a terminal device 110 and a server 120 . The terminal device 110 may be connected to the server 120 via a wired network or a wireless network. The terminal device may be the aforementioned terminal device.

[0036] For example, an application client may be installed on the terminal device 110. The user may log in to the application client using a login account and password on the terminal device 110. The server 120 may verify the login account and password. If the verification is successful, it may be determined that the client has successfully logged in to the terminal device 110. The terminal device 110 may then display a list of commonly trusted devices and a list of verified devices. These lists and other content displayed on the terminal device 110 may all be sent by the server 120.

[0037] After introducing the application scenarios of the embodiments of the present application, the technical solutions of the present application will be described in detail below:

[0038] Figure 2 is a flow chart of a login device management method provided by an embodiment of the present application. The method can be executed by the electronic device in the above application scenario, but is not limited thereto. As shown in Figure 2, the method may include the following steps:

[0039] S210: Receive an account login event of a target account logging into an application client corresponding to a target device;

[0040] S220: In response to the account login event, obtain a list of commonly used trusted devices of the target account, and determine whether the number of commonly used devices in the list of commonly used trusted devices is less than a quantity threshold. If the number of commonly used devices is less than the quantity threshold, execute S230; if the number of commonly used devices is greater than or equal to the quantity threshold, execute S240;

[0041] S230: adding the target device information of the target device carried in the account login event to the commonly trusted device list, and the device type of the device in the commonly trusted device list is the commonly trusted device type;

[0042] S240: Move the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and add the target device information to the commonly used trusted device list; the first device is the device with the earliest login time in the commonly used trusted device list, and the device type of the device in the verified device list is the verified device type. Devices of the commonly used trusted device type and devices of the verified device type correspond to different management policies in different business scenarios.

[0043] It should be noted that, in the following embodiments, this application will introduce the technical solution of this application by taking the electronic device as a terminal device as an example. The terminal device may be the target device in the embodiments of this application. The terminal device runs an application client, and the terminal device can interact with the server through the application client to implement the corresponding method of the following embodiments; when the electronic device is other devices, the corresponding content is similar to that here, and this application will not elaborate on this.

[0044] It should be noted that the triggering operation, adjustment operation and other operations in this application can be single-click, double-click, press, drag to a specified area or floating touch gestures, etc. This application does not limit this.

[0045] It is understandable that the application client can be an application (Application, APP) or a web page.

[0046] In some implementations, before executing the above S210, the application client or server corresponding to the electronic device can classify the devices that log in to the application client based on the target account, determine multiple device types, and a list corresponding to each device type.

[0047] Exemplarily, the multiple device types may include: commonly used trusted device types, verified device types, and invalid device types. The corresponding lists of commonly used trusted device types, verified device types, and invalid device types are: commonly used trusted device list, verified device list, and invalid device list, respectively. That is, the device categories of the devices included in the commonly used trusted device list, verified device list, and invalid device list are commonly used trusted devices, verified devices, and invalid devices, respectively. In addition, the non-invalid devices in this application are commonly used trusted devices or verified devices, and devices with the commonly used trusted device type, verified device type, and invalid device type are respectively referred to as commonly used trusted devices, verified devices, and invalid devices.

[0048] Among them, devices of different device types correspond to different management policies in different business scenarios. For example, devices of different device types may correspond to different priorities. The priority of the device type can be: the priority of the commonly used trusted device type is greater than the priority of the verified device type, and the priority of the verified device type is greater than the priority of the invalid device type. Devices with different priorities may correspond to different management policies, and the management policies may include login policies, but are not limited to them. For another example, devices of different device types may correspond to different transaction permissions, such as the transaction permission of the commonly used trusted device type is direct transaction without verification, the transaction permission of the verified device type is to verify the account transaction password, and the transaction permission of the invalid device type is to verify the account transaction password and the account login password.

[0049] For commonly used trusted devices, it can refer to devices that have logged in more than 3 times and passed two-factor verification. Since commonly used trusted devices are the highest priority devices, they have high flexibility in many business scenarios. Therefore, the number of commonly used trusted devices, that is, the number of commonly used devices, can be limited, without limiting the number of verified devices and invalid devices. For example, the number of commonly used devices can be set to be less than the number threshold, which can be 3 or 10. When the number of commonly used devices needs to be increased, the electronic device can modify the number threshold of commonly used trusted devices through the corresponding application client. For verified devices, it can refer to devices that have passed two-factor verification. For invalid devices, it can refer to verified devices that have not logged in within 180 days.

[0050] When logging in on a terminal device, users must first authenticate via SMS with the device lock. After unlocking the device, authentication requires verification of both their phone number and password, hence the name two-factor authentication. Of course, other factors besides the phone number and password can also be used.

[0051] In the above process, the device types and the corresponding management methods of each type can be made simpler and clearer, which can solve some more complex management problems caused by unclear device types in different scenarios. For example, in the login process, different processing processes can be performed for devices of different types, thereby reducing unnecessary judgment logic and ensuring the simplicity and reliability of the login process.

[0052] This application will introduce the corresponding contents such as determining the device type, displaying and adjusting various device types in the following embodiments:

[0053] In some implementations, before receiving the account login event of the target account logging into the application client corresponding to the target device, the method further includes: receiving a login request from the target device for the target account to log into the application client; obtaining target device information from the login request, and obtaining the target device's historical login count based on the target device information; determining a target login verification method for the target device based on the historical login count, and performing login verification on the target device using the target login verification method. Accordingly, receiving the account login event of the target account logging into the application client corresponding to the target device includes: triggering the account login event when the target device's login verification is successful using the target login verification method.

[0054] For example, an application client is installed on the target device. A user can log in to the application client using a target account on the target device. The target device can then send a login request to the server. The login request includes target device information. The target device information can be used to uniquely identify the target device. For example, the target device information can be, but is not limited to, the target device identifier. The server can then, based on the target device information carried in the login request, obtain the target device's historical login count for the target device corresponding to the target device information. Based on this historical login count, the server can interact with the target device's application client to implement different login verification methods for the target account. The server corresponding to the application client can pre-store device information and a corresponding relationship between the target account's login counts on different devices. Whenever a target account logs in to the application client through a device, the server can record the target account's device information for that device and update the corresponding relationship between the device information and the login counts. Alternatively, the server can increment the historical login count by 1 each time it receives a login request from the target account to log in to the application client, and store the correspondingly increased historical login count and the target device's device information, thereby obtaining the target device's historical login count based on the target device information.

[0055] Exemplarily, the above-mentioned determination of the target login verification method for the target device based on the number of historical logins includes: if the number of historical logins is zero, determining that the target login method is the first login verification method; if the number of historical logins is non-zero, obtaining the initial verification information of the target device; when the initial verification information is valid, determining that the target login method is the second login verification method; when the initial verification information is invalid, determining that the target login method is the first login verification method; wherein, the number of verification factors corresponding to the first login verification method is greater than the number of verification factors corresponding to the second login verification method.

[0056] Exemplarily, the verification factors may include, but are not limited to, a login account, a login password, and a login gesture. The login account, login password, and login gesture may be, respectively, the account number, password, and gesture of the target account. The first login verification method may be two-factor authentication, and its corresponding verification factors may be the login account and login password. The second login verification method may be single-factor authentication, and its corresponding verification factor may be the login password. The login account may be, but is not limited to, a mobile phone number.

[0057] Exemplarily, the initial verification information may be historical login information when the target device logged in previously, and the historical login information may be ticket data, which may include: the version number of the logged-in client, the user identity identification (IDentification, ID) at the time of login, the type of logged-in client, device identification, password verification or SMS verification, and other login verification information, but is not limited to this.

[0058] For example, when verifying whether the initial verification information is valid, you can first determine the life cycle corresponding to the initial verification information. If the current moment does not belong to the life cycle, you can determine that the initial verification information is invalid; if the current moment belongs to the life cycle, you can determine that the initial verification information is valid. The target device can interact with the server through the application client to determine the life cycle corresponding to the initial verification information of the target device, such as 10 days. This application does not impose any restrictions on this.

[0059] When the initial verification information is ticket data, the target device can interact with the server through the application client to query the ticket expiration timestamp in the ticket data to determine whether the ticket data is invalid. If the ticket expiration timestamp has not been reached at the current moment, it can be determined that the data is valid; if the ticket expiration timestamp has been reached at the current moment, it can be determined that the data is invalid.

[0060] In some possible implementations, the above-mentioned moving the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and adding the target device information to the commonly used trusted device list, includes: obtaining the historical number of logins of the target device and the device type of the target device based on the target device information; if the historical number of logins is less than or equal to a preset login threshold or the device type of the target device is a verified device type, moving the first device information from the commonly used trusted device list to the verified device list, and adding the target device information to the commonly used trusted device list.

[0061] In addition, after obtaining the historical login times of the target device and the device type of the target device according to the target device information, the above method also includes: if the historical login times are greater than the preset login threshold and the device type of the target device is a verified device type, displaying the commonly used trusted device adding page; obtaining the first trigger operation for the add button in the commonly used trusted device adding page, the first trigger operation is used to indicate that the target device is added to the commonly used trusted device list; extracting the adding reason information from the operation information corresponding to the first trigger operation; if the adding reason information is extracted, adjusting the quantity threshold, and adding the target device information to the commonly used trusted device list; or, if the adding reason information cannot be extracted, moving the first device information from the commonly used trusted device list to the verified device list, and adding the target device information to the commonly used trusted device list; wherein the adding reason information is used to indicate the reason for adding the target device to the commonly used trusted device list.

[0062] Exemplarily, the first device may also be any device randomly selected from a list of commonly used trusted devices.

[0063] Exemplarily, the commonly used trusted device addition page may be a page that appears in a pop-up window, which is not a limitation in this application. As shown in FIG3(c), the commonly used trusted device addition page may be displayed in a preset area of ​​the display interface in a pop-up window format, and may specifically include an input box corresponding to the reason for adding the device; the user may use the input box to enter text information related to the reason for adding the device to the commonly used trusted devices, and after triggering the corresponding submit button, the electronic device may input the text information in the box as the reason for adding the device, and write it into the operation information corresponding to the first trigger operation, so that the first trigger operation carries the reason for adding the device, thereby instructing the application client to interact with the server to trigger the adjustment of the threshold value of the number of commonly used trusted devices based on the reason for adding the device.

[0064] Furthermore, considering that the management policies corresponding to commonly used information devices, such as login priority or transaction permissions, are often higher, in order to ensure the account security of the target account, after determining that the first trigger operation carries the addition reason information, it can also be determined whether to trigger the adjustment of the number threshold of commonly used trusted devices based on the addition reason information and the current login information of the target device. Specifically, after extracting the addition reason information from the operation information corresponding to the first trigger operation, the addition reason information and the current login information corresponding to the target device can be obtained, and the current login information includes but is not limited to information such as login time, login location, and login IP address; then, the addition reason information is converted into a corresponding target word vector, and the target word vector is matched with the word vector corresponding to the preset addition reason text to obtain a first matching degree. At the same time, the current login information is matched with the target login information of the target commonly used device in the commonly used trusted device list to obtain a second matching degree, wherein the target commonly used device refers to the device in the commonly used trusted device list whose login time is closest to the current time, and the target login information refers to the login information of the target commonly used device at the time of the most recent login; finally, based on the first matching degree and the second matching degree, it is determined whether to trigger the adjustment of the number threshold of commonly used trusted devices.

[0065] Taking the first matching degree as an example, the reason for adding information can be segmented and the target word vector of each segmentation can be obtained. Then, the target word vector corresponding to each segmentation is matched with the word vector corresponding to the preset reason for adding text, and the first matching degree is obtained by the following formula:

[0066] Among them, xi represents the matching result between the i-th (i=1, 2, ..., n) target word vector and the word vector corresponding to the preset reason for adding text, which is 1 if the match is successful and 0 if the match is unsuccessful; P1 represents the first matching degree.

[0067] Taking the second matching degree as an example, the second matching degree between the current login information and the target login information of the target commonly used device in the commonly used trusted device list can be obtained by the following formula (1):

[0068] Wherein, ai (i=1, 2, ..., n) represents the specific information sequence in the current login information, such as login time, login location, login IP address, etc.; b i (i=1, 2, ..., n) represents the specific information sequence in the target login information; P2 represents the second matching degree. It can be understood that when the second matching degree is closer to 1, it means that the login information of the target device, such as login time, login location, login IP address, etc., is similar to the login information of the target commonly used device in the commonly used trusted device list. The probability that the target device is logged in by the user corresponding to the target account is relatively high, which effectively improves the security of the account login settings.

[0069] After obtaining the first matching degree and the second matching degree, the target matching degree can be determined by the following formula (2):

[0070] Wherein, R represents the target matching degree, P1 represents the first matching degree, P2 represents the second matching degree, w1 represents the weight value of the first matching degree, and w2 represents the weight value of the second matching degree. When the target matching degree is greater than the preset matching degree threshold, it is determined that the adjustment of the number threshold of commonly used trusted devices is triggered; when the target matching degree is less than or equal to the preset matching degree threshold, it is determined that the adjustment of the number threshold of commonly used trusted devices is not triggered, and the steps of moving the first device information from the commonly used trusted device list to the verified device list and adding the target device information to the commonly used trusted device list are continued.

[0071] After the target device completes login, the commonly used trusted device adding page can be displayed directly, or the commonly used trusted device adding page can be displayed when the user triggers an operation on other pages or buttons. This application does not impose any restrictions on this.

[0072] For example, the electronic device can set a pop-up window condition. After the target device completes login, if it detects that the target device meets the pop-up window condition, it can display the frequently used trusted device addition page in a pop-up window. The pop-up window condition can be any of the following, but is not limited to: the target device's device type is not a frequently used trusted device, the target device's device type has become a frequently used trusted device and the number of frequently used devices exceeds a threshold, the target device's login duration is longer than a target duration, or the target device has not displayed the frequently used trusted device addition page before. The target duration can be 3 days.

[0073] For example, after the target device completes login, the frequently used trusted device adding page can also be displayed when the user triggers another page or button. As shown in FIG3 (a), when the user uses the target account and logs in to the application client based on the target device, the target device can first display the "self-selected page" shown in FIG3 (b), and a "My" button is displayed at the bottom of the "self-selected page". The target device can obtain the user's trigger operation on the "My" button and display the frequently used trusted device adding page shown in FIG3 (c). The frequently used trusted device adding page is displayed in the form of a pop-up window at the bottom of the "My Page" shown in FIG3 (c). The frequently used trusted device adding page may include an input box that can obtain the reason for adding input by the user.

[0074] In some implementable methods, in combination with the above-mentioned embodiment, as shown in FIG4 , after obtaining the login operation of the login application client, it is possible to first determine whether the login is a new device login, that is, to determine whether the target device is the first login device. The first login device can be understood as the device that logs into the application client for the first time. When the target device is the first login device, a two-factor login verification can be performed on the target device based on a two-factor verification method. When the verification passes, it can be determined whether the number of commonly used devices is less than the number threshold, that is, whether it exceeds the upper limit. When the number of commonly used devices is less than the number threshold, the target device is added to the list of commonly used trusted devices; when the number of commonly used devices is greater than or equal to the number threshold, the device with the earliest login time in the commonly used trusted device list is moved to the verified device list, and the target device is added to the list of commonly used trusted devices.

[0075] If it is determined that this is not the first time the target device has logged in, the device's ticket data can be determined to be expired. If the ticket data has not expired, the target device can be authenticated using single-factor authentication. If the ticket data has expired, the target device can be authenticated using two-factor authentication. Next, it can be determined whether the number of frequently used devices is less than a threshold. If the number of frequently used devices is less than the threshold, the target device is added to the frequently used trusted device list. If the number of frequently used devices is greater than or equal to the threshold, it can be determined whether the target device has logged in more than three times and whether the target device is on the verified device list. If the target device has logged in more than three times and is on the verified device list, a pop-up window can be displayed for adding frequently used trusted devices. After obtaining the user's trigger action for the Add button on the frequently used trusted device add page, if the reason for adding the device is obtained, the target device is added to the frequently used trusted device list without adjusting the threshold, i.e., the existing limit on the number of frequently used devices. If no reason for adding the device is obtained, the target device is added to the frequently used trusted device list and the threshold is increased by one. The commonly used trusted device list at this time may include information corresponding to existing commonly used trusted devices and information corresponding to the target device.

[0076] It should be noted that the commonly used devices in this application refer to commonly used trusted devices, and the commonly used device list refers to a commonly used trusted device list.

[0077] In the above embodiment, the first-time login device can be quickly and conveniently identified as a frequently used trusted device, thereby improving the efficiency and convenience of device management. In addition, for devices that have logged in frequently and have been pushed back to the verified device list (i.e., moved from the frequently used trusted device list to the verified device list), they can be added back to the frequently used trusted device list using the above-mentioned adding method, so that they can be managed as frequently used trusted devices.

[0078] In some implementations, the electronic device can display a login device management page, which includes a list of commonly trusted devices and a list of verified devices; obtain a second trigger operation for the second device in the login device management page; and display basic information and historical login information of the second device in response to the second trigger operation.

[0079] In addition, the electronic device may also obtain a category adjustment operation for the third device in the login device management page; and in response to the category adjustment operation, move the third device between the commonly used trusted device list and the verified device list.

[0080] Exemplarily, the above-mentioned category adjustment operation can be a drag operation of the third device displayed in the login device management page. For example, it can be dragging the third device displayed in the commonly used trusted device list to the display position corresponding to the verified device list; it can also be a click operation on the button corresponding to the third device displayed in the login device management page. This application does not impose any restrictions on this.

[0081] For example, the basic information may include at least one of the following, but is not limited to: device name, device type, and device version. The historical login information may include at least one of the following, but is not limited to: historical login time and historical login address.

[0082] Exemplarily, moving the third device between the commonly trusted device list and the verified device list may include: moving the third device from the commonly trusted device list to the verified device list, or moving the third device from the verified device list to the commonly trusted device list. In other words, adjusting the device type of the third device from a commonly trusted device to a verified device, or adjusting the device type of the third device from a verified device to a commonly trusted device.

[0083] In some implementations, the login device management page can be as shown in (a) of Figure 5, in which the electronic device can display the list of commonly used trusted devices and the list of verified devices separately, that is, the commonly used trusted devices and the verified devices can be displayed separately. After obtaining the user's trigger operation for any device, the device details page as shown in (b) of Figure 5 can be displayed, on which the basic information and historical login information of the device are displayed. After obtaining the user's trigger operation for "device name", the name modification page as shown in (c) of Figure 5 can be displayed, in which the device name entered by the user can be obtained, and the name can be determined as the new name of the device.

[0084] In some implementations, as shown in (a) of FIG6 , the login device management page may display a “+” or “-” button to the right of the position where each device is displayed, wherein the “+” button and the “-” button are respectively used to upgrade and downgrade the corresponding device, that is, respectively used to move the corresponding device from the verified device list to the commonly trusted device list and from the commonly trusted device list to the verified device list, that is, respectively used to adjust the corresponding device from the verified device to the commonly trusted device and from the commonly trusted device to the verified device. For example, after obtaining the trigger operation of the “+” button corresponding to device 3, the page shown in (b) of FIG6 may be displayed, and the corresponding content of the page may refer to the above-mentioned add commonly trusted device page. After obtaining the user's trigger operation for the submit button, the login device management page shown in (c) of FIG6 may be displayed. At this time, the newly added commonly trusted device, i.e., device 3, may be displayed at the display position corresponding to the commonly trusted device list.

[0085] During this process, electronic devices can use asynchronous processing to categorize and display different device types and lists. They can also aggregate basic device information and historical login information for easy viewing and modification. Furthermore, users can manually downgrade and upgrade device types, allowing them to manage their own device types.

[0086] This application will introduce the scenarios corresponding to the upgrade and downgrade of the login device, that is, the scenarios corresponding to the adjustment of the device type in the following embodiments:

[0087] It should be noted that device upgrades include: adjusting an invalid device to a commonly used trusted device, adjusting a verified device to a commonly used trusted device, and device downgrades include: adjusting a commonly used trusted device to a verified device, adjusting a verified device to an invalid device.

[0088] In some implementations, as shown in FIG7 , the upgrade of the login device includes the following two scenarios:

[0089] In scenario one, after the login device successfully logs in, it can be determined that the device is trustworthy. At this time, regardless of the device type, the device can be directly identified as a commonly used trusted device.

[0090] Scenario 2: Upgrading based on the device management interface, that is, upgrading based on the Add Common Trusted Devices page or Login Device Management page in the above embodiment.

[0091] In some implementations, as shown in FIG8 , the degradation of the login device includes the following three scenarios:

[0092] In the first scenario, after the login device successfully logs in, it is determined that the number of commonly used devices exceeds the limit of the number of commonly used trusted devices, that is, it is greater than or equal to the number threshold. Then, the commonly used trusted devices that exceed the limit, such as the commonly used trusted device with the earliest login time, will be downgraded to verified devices.

[0093] The second scenario is downgrading based on the device management interface, that is, downgrading based on the Add Commonly Trusted Device page or Login Device Management page in the above embodiment. The user downgrades the commonly trusted device in the device management interface, and the commonly trusted device is downgraded to a verified device.

[0094] The third scenario involves downgrading devices based on their login duration. This involves downgrading devices that haven't been logged in for a long time. For example, a commonly trusted device that hasn't been logged in for 30 days can be downgraded to a verified device, while a verified device that hasn't been logged in for 180 days can be downgraded to an invalid device. In this case, an invalid device is equivalent to a new device.

[0095] In addition, after the logged-in device is upgraded or downgraded, a reminder message may be pushed to the user based on instant messaging or real-time messaging (IM) to inform the user that the upgrade or downgrade operation is successful.

[0096] In the above process, the user may be provided with a login device management function for managing device types. The management of device types is mainly performed through upgrade and downgrade operations on the login device, thereby improving user operation convenience.

[0097] In some implementations, the electronic device may create multiple classes (i.e., interfaces) and call the created classes to execute the above embodiments or complete the methods corresponding to the above embodiments.

[0098] Specifically, in combination with Figure 9, electronic devices can create login service class, message middleware class, device compliance service class, login service class, device compliance service class, push service class, message sending service base class, email sending class, SMS sending class, reminder number sending class, device information service class, login history service class, and CRM platform class. Among them, the login service class is used to handle login events; the message middleware class is used to establish a subscription relationship between the login service class and the device compliance service class; the device compliance service class is used to asynchronously process login events, control the upgrade and downgrade of device types, and guide users to increase the number of commonly used trusted devices. The pop-up window push service class is used to push the pop-up window to increase the number of commonly used trusted devices to the client; the message sending service base class is used to notify messages. The message sending service base class includes: email sending class, SMS sending class, and reminder number sending class. These three sending classes are relatively similar, so a message sending service base class can be created so that these three sending classes inherit from the message sending service base class, and ensure that each sending class has its own notification method; the device information service class is used to maintain and store basic device information; the login history service class is used to maintain and store user login history. After the login device logs in successfully, this class can be called to store login records; the crm platform class is used to query related records of users increasing the number of commonly used trusted devices.

[0099] In some possible implementations, in combination with the above embodiments, as shown in FIG10 , the server may include a login service, a device information module, a device compliance module, a message middleware, and a push service. After the user performs a login operation based on the login device, the login service may determine the login event and send the login event to the message middleware. The message middleware may then consume the login event, causing the device compliance module to obtain device information from the device information module. The device compliance module may determine whether the device is a commonly used trusted device based on the device information, and update it to a commonly used trusted device if it is not a commonly used trusted device. If the number of commonly used devices is greater than or equal to the number threshold, the commonly used trusted device with the earliest login time is updated to a verified device. If the number of commonly used devices is greater than or equal to the number threshold, and the number of logins for the device is greater than 3 times, the number of commonly used devices may be modified through a pop-up window based on the push service.

[0100] In addition, since both the device compliance module and the device information module can maintain device types, the server can integrate and uniformly maintain the device compliance module and the device information template to achieve the single responsibility principle of service and reduce maintenance costs.

[0101] In some implementations, in combination with the above embodiment, as shown in FIG11 , the login device can be installed with a client, and the server can include a device compliance module and a device information module. The client can pull the device information of non-invalid devices sorted by login time from the device information module and display them according to device type. The device information module can also upgrade or downgrade the device type based on the user's upgrade, downgrade, or deletion operations. The device compliance module can push the above pop-up window to the client and interact with the device information module to adjust the number of commonly used devices and modify the device type.

[0102] It should be noted that all the above technical solutions can be combined in any way to form optional embodiments of the present application, and will not be described in detail here.

[0103] It should be noted that in the specific implementation of this application, relevant data such as login devices, accounts, passwords, etc. are involved. When the embodiments of this application are applied to specific products or technologies, user permission, consent or authorization must be obtained, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0104] Figure 12 is a schematic diagram of a login device management apparatus 1200 provided in an embodiment of the present application. As shown in Figure 12, login device management apparatus 1200 includes: a first receiving module 1201, an acquisition and determination module 1202, a first adding module 1203, an adding and moving module 1204, a second receiving module 1205, a first acquiring module 1206, a determination and verification module 1207, a first display module 1208, a second acquiring module 1209, an adjustment and moving module 1210, a second display module 1211, a third acquiring module 1212, a third display module 1213, a fourth acquiring module 1214, and a first moving module 1215.

[0105] In some possible implementations, the first receiving module 1201 is used to: receive an account login event of a target account logging into an application client corresponding to a target device; the obtaining and judging module 1202 is used to: in response to the account login event, obtain a list of commonly used trusted devices of the target account, and determine whether the number of commonly used devices in the commonly used trusted device list is less than a quantity threshold; the first adding module 1203 is used to: when the number of commonly used devices is less than the quantity threshold, add the target device information of the target device carried in the account login event to the commonly used trusted device list; the adding and moving module 1204 is used to: when the number of commonly used devices is greater than or equal to the quantity threshold, move the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and add the target device information to the commonly used trusted device list; the first device is the device with the earliest login time in the commonly used trusted device list; wherein, the device type of the device in the commonly used trusted device list is a commonly used trusted device type, and the device type of the device in the verified device list is a verified device type, and devices of the commonly used trusted device type and devices of the verified device type correspond to different management policies in different business scenarios.

[0106] In some possible implementations, the second receiving module 1205 is used to: receive a login request for a target account to log in to an application client sent by a target device; the first obtaining module 1206 is used to: obtain target device information from the login request, and obtain the historical login times of the target device based on the target device information; determine the verification module 1207, and use it to: determine the target login verification method for the target device based on the historical login times, and perform login verification on the target device through the target login verification method; the first receiving module 1201 is specifically used to: trigger an account login event when the login verification of the target device is passed through the target login verification method.

[0107] In some implementable methods, the verification module 1207 is determined to be specifically used to: if the number of historical logins is zero, determine that the target login method is the first login verification method; if the number of historical logins is non-zero, obtain the initial verification information of the target device; when the initial verification information is valid, determine that the target login method is the second login verification method; when the initial verification information is invalid, determine that the target login method is the first login verification method; wherein, the number of verification factors corresponding to the first login verification method is greater than the number of verification factors corresponding to the second login verification method.

[0108] In some possible implementations, a moving module 1204 is added, which is specifically used to: obtain the historical login times of the target device and the device type of the target device based on the target device information; if the historical login times are less than or equal to the preset login threshold or the device type of the target device is a verified device type, move the first device information from the commonly used trusted device list to the verified device list, and add the target device information to the commonly used trusted device list.

[0109] In some implementations, the first display module 1208 is used to: display the commonly used trusted device adding page if the number of historical login times is greater than a preset login threshold and the device type of the target device is a verified device type; the second acquisition module 1209 is used to: obtain a first trigger operation for the add button in the commonly used trusted device adding page, the first trigger operation being used to indicate that the target device is added to the commonly used trusted device list; the adjustment and movement module 1210 is used to: extract the adding reason information from the operation information corresponding to the first trigger operation in response to the first trigger operation; if the adding reason information is extracted, adjust the quantity threshold and add the target device information to the commonly used trusted device list; or, if the adding reason information cannot be extracted, move the first device information from the commonly used trusted device list to the verified device list, and add the target device information to the commonly used trusted device list; wherein the adding reason information is used to indicate the reason for adding the target device to the commonly used trusted device list.

[0110] In some implementations, the second display module 1211 is used to: display the login device management page, which includes a list of commonly trusted devices and a list of verified devices; the third acquisition module 1212 is used to: obtain a second trigger operation for the second device in the login device management page; the third display module 1213 is used to: display the basic information and historical login information of the second device in response to the second trigger operation.

[0111] In some implementations, the fourth acquisition module 1214 is used to: obtain a category adjustment operation for the third device in the login device management page; the first movement module 1215 is used to: move the third device between the commonly trusted device list and the verified device list in response to the category adjustment operation.

[0112] It should be understood that the device embodiments and method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. To avoid repetition, they will not be described in detail here. Specifically, the device 1200 shown in Figure 12 can perform the above-mentioned method embodiments, and the aforementioned and other operations and / or functions of each module in the device 1200 are respectively for implementing the corresponding processes in the above-mentioned methods. For the sake of brevity, they will not be described in detail here.

[0113] The above describes the device 1200 of the embodiment of the present application from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0114] FIG13 is a schematic block diagram of an electronic device 1300 provided in an embodiment of the present application.

[0115] As shown in FIG13 , the electronic device 1300 may include:

[0116] The memory 1310 and the processor 1320 are configured to store computer programs and transmit the program code to the processor 1320. In other words, the processor 1320 can call and execute the computer program from the memory 1310 to implement the method in the embodiment of the present application.

[0117] For example, the processor 1320 may be configured to execute the above method embodiments according to instructions in the computer program.

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

[0119] General-purpose processor, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

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

[0121] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0122] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 1310 and executed by the processor 1320 to implement the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of implementing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0123] As shown in FIG13 , the electronic device may further include:

[0124] The transceiver 1330 may be connected to the processor 1320 or the memory 1310 .

[0125] The processor 1320 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices. The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, which may be one or more.

[0126] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0127] The present application also provides a computer storage medium having a computer program stored thereon, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment. In other words, the present application also provides a computer program product containing instructions, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment.

[0128] When software is used to implement, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website, a computer, a server or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, a computer, a server or a data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center that includes one or more available media integrations. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (Digital Video Disc, DVD)) or a semiconductor medium (such as a solid-state drive (SSD)) etc.

[0129] Those skilled in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0130] In the several embodiments provided in this 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 merely schematic. For example, the division of the modules is merely a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0131] Modules described as separate components may or may not be physically separate, and components displayed as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the present embodiment. For example, the functional modules in the various embodiments of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module.

[0132] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A login device management method, characterized in that: include: Receive an account login event of the target account logging into the application client corresponding to the target device; In response to the account login event, obtaining a commonly used trusted device list of the target account, and determining whether the number of commonly used devices in the commonly used trusted device list is less than a number threshold; When the number of commonly used devices is less than the number threshold, adding the target device information of the target device carried in the account login event to the commonly used trusted device list; When the number of commonly used devices is greater than or equal to the number threshold, moving the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and adding the target device information to the commonly used trusted device list; the first device is the device with the earliest login time in the commonly used trusted device list; Among them, the device type of the devices in the commonly used trusted device list is the commonly used trusted device type, and the device type of the devices in the verified device list is the verified device type. The devices of the commonly used trusted device type and the devices of the verified device type correspond to different management policies in different business scenarios.

2. The method according to claim 1, characterized in that Before receiving an account login event of a target account logging into an application client corresponding to a target device, the method further includes: Receiving a login request sent by the target device for the target account to log in to the application client; Acquire the target device information from the login request, and acquire the historical login times of the target device according to the target device information; Determine a target login verification method for the target device according to the number of historical logins, and perform login verification on the target device using the target login verification method; The receiving an account login event of a target account logging into an application client corresponding to a target device includes: When the login verification of the target device is passed through the target login verification method, the account login event is triggered.

3. The method according to claim 2, characterized in that The determining of a target login verification method for the target device according to the number of historical login times includes: If the number of historical login times is zero, determining that the target login method is the first login verification method; If the number of historical logins is non-zero, obtaining initial verification information of the target device; When the initial verification information is valid, determining the target login method to be a second login verification method; When the initial verification information is invalid, determining the target login method to be the first login verification method; Among them, the number of verification factors corresponding to the first login verification method is greater than the number of verification factors corresponding to the second login verification method.

4. The method according to claim 1, characterized in that: The step of moving the first device information of the first device from the commonly used trusted device list to the verified device list of the target account, and adding the target device information to the commonly used trusted device list, includes: Acquire the historical login times of the target device and the device type of the target device according to the target device information; If the number of historical logins is less than or equal to a preset login threshold, or the device type of the target device is a verified device type, the first device information is moved from the commonly used trusted device list to the verified device list, and the target device information is added to the commonly used trusted device list.

5. The method according to claim 4, characterized in that After acquiring the historical login times of the target device and the device type of the target device according to the target device information, the method further includes: If the number of historical logins is greater than a preset login threshold and the device type of the target device is a verified device type, a commonly used trusted device adding page is displayed; Acquire a first trigger operation for an add button in the commonly used trusted device adding page, where the first trigger operation is used to instruct to add the target device to the commonly used trusted device list; In response to the first trigger operation, extracting adding reason information from the operation information corresponding to the first trigger operation; If the adding reason information is extracted, the quantity threshold is adjusted, and the target device information is added to the commonly used trusted device list; or, If the adding reason information cannot be extracted, moving the first device information from the commonly used trusted device list to the verified device list, and adding the target device information to the commonly used trusted device list; The adding reason information is used to indicate the reason for adding the target device to the commonly used trusted device list.

6. The method according to claim 5, characterized in that Before adjusting the quantity threshold, the method further includes: Obtain the current login information corresponding to the target device, the current login information including: login time, login location, login IP address; Segment the adding reason information to obtain target word vectors for each segmented word; Match the target word vector of each word segmentation with the word vector corresponding to the preset reason for adding text to obtain a first matching degree; match the current login information with the target login information of the target commonly used device in the commonly used trusted device list to obtain a second matching degree, wherein the target commonly used device refers to the device in the commonly used trusted device list whose login time is closest to the current time, and the target login information refers to the login information of the target commonly used device at the most recent login; Whether to trigger adjustment of the quantity threshold is determined according to the first matching degree and the second matching degree.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: Displaying a login device management page, the login device management page including the commonly used trusted device list and the verified device list; Obtaining a second trigger operation for a second device in the login device management page; In response to the second trigger operation, basic information and historical login information of the second device are displayed.

8. The method according to claim 7, characterized in that Also includes: Obtaining a category adjustment operation for a third device in the login device management page; In response to the category adjustment operation, the third device is moved between the commonly trusted device list and the authenticated device list.

9. A login device management device, characterized in that: include, A first receiving module is used to receive an account login event of a target account logging into an application client corresponding to a target device; an acquisition and determination module, configured to acquire a list of commonly used trusted devices of the target account in response to the account login event, and determine whether the number of commonly used devices in the list of commonly used trusted devices is less than a number threshold; A first adding module, configured to add target device information of the target device carried in the account login event to the commonly used trusted device list when the number of the commonly used devices is less than the number threshold; an adding and moving module, configured to move the first device information of the first device from the commonly used trusted device list to the verified device list of the target account when the number of the commonly used devices is greater than or equal to the number threshold, and add the target device information to the commonly used trusted device list; the first device is the device with the earliest login time in the commonly used trusted device list; Among them, the device type of the devices in the commonly used trusted device list is the commonly used trusted device type, and the device type of the devices in the verified device list is the verified device type. The devices of the commonly used trusted device type and the devices of the verified device type correspond to different management policies in different business scenarios.

10. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 8 by executing the executable instructions.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 8.

Images