CN117376018A - Login equipment management method, device and equipment - Google Patents

Login equipment management method, device and equipment Download PDF

Info

Publication number
CN117376018A
CN117376018A CN202311560670.4A CN202311560670A CN117376018A CN 117376018 A CN117376018 A CN 117376018A CN 202311560670 A CN202311560670 A CN 202311560670A CN 117376018 A CN117376018 A CN 117376018A
Authority
CN
China
Prior art keywords
login
target
equipment
list
common
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311560670.4A
Other languages
Chinese (zh)
Inventor
韩炳豪
吕科
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Futu Network Technology Co Ltd
Original Assignee
Shenzhen Futu Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Futu Network Technology Co Ltd filed Critical Shenzhen Futu Network Technology Co Ltd
Priority to CN202311560670.4A priority Critical patent/CN117376018A/en
Publication of CN117376018A publication Critical patent/CN117376018A/en
Priority to PCT/CN2024/132738 priority patent/WO2025108238A1/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application provides a login device management method, a login device management device and login device, comprising the following steps: receiving an account login event of an application client corresponding to target account login target equipment; acquiring a common trust device list, and adding target device information of target devices carried in account login events to the common trust device list when the number of the common devices is smaller than a number threshold; when the number of the common equipment is greater than or equal to a number threshold value, moving first equipment information of first equipment with earliest login time in a common trust equipment list from the common trust equipment list to a verified equipment list, and adding target equipment information to the common trust equipment list; the device types of the devices in the common trust device list and the verified device list are respectively the common trust device type and the verified device type, and the common trust device and the verified device correspond to different management strategies under different service scenes so as to improve the diversity and convenience of management modes aiming at login devices.

Description

Login equipment management method, device and equipment
Technical Field
The embodiment of the application relates to the technical field of equipment management, in particular to a login equipment management method, a login equipment management device and login equipment.
Background
With the development of equipment management technology, a user can log in the same client by using the same account based on a plurality of login equipment, wherein the login equipment can be terminal equipment such as a mobile phone, a computer and the like.
At present, when a user logs in the same client based on a plurality of login devices by using the same account, the client can display the plurality of login devices, but the management mode of the login devices is single in the prior art.
Disclosure of Invention
The application provides a login device management method, a login device management device and login device, so that diversity and convenience of login device management modes are improved.
In a first aspect, the present application provides a login device management method, including: receiving an account login event of an application client corresponding to target account login target equipment; responding to an account login event, acquiring a common trust device list of a target account, and judging whether the number of common devices in the common trust device list is smaller than a number threshold; when the number of the common devices is smaller than the number threshold, adding target device information of target devices carried in the account login event into a common trust device list; when the number of the common devices is greater than or equal to a number threshold, moving first device information of the first device from a common trust device list to a verified device list of a target account, and adding target device information to the common trust device list; the first device is the device with the earliest login time in the common trust device list; the device types of the devices in the common trust device list are common trust device types, the device types of the devices in the verified device list are verified device types, and the devices of the common trust device types and the devices of the verified device types correspond to different management strategies under different service scenes.
In a second aspect, the present application provides a login device management apparatus, including a first receiving module, configured to receive an account login event of a target account login target device corresponding to an application client; the acquisition judging module is used for responding to the account login event, acquiring a common trust equipment list of the target account and judging whether the number of the common equipment in the common trust equipment list is smaller than a number threshold value; the first adding module is used for adding the target equipment information of the target equipment carried in the account login event to the common trust equipment list when the number of the common equipment is smaller than the number threshold value; the mobile module is used for moving the first device information of the first device from the common trust device list to the verified device list of the target account when the number of the common devices is greater than or equal to the number threshold value, and adding the target device information to the common trust device list; the first device is the device with the earliest login time in the common trust device list; the device types of the devices in the common trust device list are common trust device types, the device types of the devices in the verified device list are verified device types, and the devices of the common trust device types and the devices of the verified device types correspond to different management strategies under different service scenes.
In a third aspect, the present application provides an electronic device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory for performing the method as in the first aspect or in various implementations thereof.
In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program for causing a computer to perform a method as in the first aspect or implementations thereof.
In a fifth aspect, the present application provides a computer program product comprising computer program instructions for causing a computer to perform the method as in the first aspect or in various implementations thereof.
In a sixth aspect, the present application provides a computer program for causing a computer to perform the method as in the first aspect or in various implementations thereof.
According to the technical scheme, the electronic equipment can receive the account login event of the application client corresponding to the target account login target equipment, can acquire the common trust equipment list of the target account in response to the account login event, and judges whether the number of the common equipment in the common trust equipment list is smaller than a number threshold value: when the number of the common devices is smaller than the number threshold, the electronic device can increase target device information of target devices carried in the account login event into a common trust device list; when the number of the common devices is greater than or equal to the number threshold, the electronic device may move the first device information of the first device from the common trusted device list to the verified device list of the target account, and increase the target device information to the common trusted device list, where the first device is a device with the earliest login time in the common trusted device list, a device type of the device in the common trusted device list is a common trusted device type, a device type of the device in the verified device list is a verified device type, and the device of the common trusted device type and the device of the verified device type correspond to different management policies under different service scenarios. In the above process, the electronic device may divide the login device into two types of common trusted devices and verified devices, and increase the target device to the common trusted device list according to the number of the common devices and the size of the number threshold, and perform device transfer between the common trusted device list and the verified device list, so as to not only enrich the management manner of the login device, improve the diversity of the management manner of the login device, but also facilitate the use of different management policies to process different types of devices in different service scenarios, and improve the convenience of the management manner of the login device.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 2 is a flowchart of a login device management method provided in an embodiment of the present application;
fig. 3 is a schematic diagram of a login device management method according to an embodiment of the present application;
fig. 4 is a schematic diagram of another login device management method according to an embodiment of the present application;
FIG. 5 is a schematic diagram of another login device management method according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of another login device management method according to an embodiment of the present disclosure;
fig. 7 is a schematic diagram of another login device management method according to an embodiment of the present application;
FIG. 8 is a schematic diagram of another login device management method according to an embodiment of the present disclosure;
FIG. 9 is a schematic diagram of another login device management method according to an embodiment of the present application;
FIG. 10 is a schematic diagram of another login device management method according to an embodiment of the present disclosure;
FIG. 11 is a schematic diagram of another login device management method according to an embodiment of the present disclosure;
fig. 12 is a schematic diagram of a login device management apparatus 1200 according to an embodiment of the present application;
fig. 13 is a schematic block diagram of an electronic device 1300 according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present application based on the embodiments herein.
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present application based on the embodiments herein.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
As described above, the prior art has a problem that the management method for the login device is relatively single.
In order to solve the technical problem, the login device can be divided into two types of common trust device types and verified device types, and the target device is added into a common trust device list according to the number of the common devices and the size of a quantity threshold value, device transfer is carried out between the common trust device list and the verified device list, and the like, so that the login device management mode can be enriched, the diversity of the login device management mode is improved, the login device management mode is convenient to use different management strategies to process different types of devices in different service scenes, and the convenience of the login device management mode is improved.
It should be understood that the technical solution of the present application may be applied to the following scenarios, but is not limited to:
it should be noted that, the solution provided in the embodiment of the present application may be executed by any electronic device having login device management capability, and the present application does not specifically limit the electronic device. For example, the electronic device may be a server. The server may be a server, a server cluster composed of a plurality of servers, or a cloud platform control center, but is not limited thereto. Alternatively, the electronic device may be a terminal device. The terminal device can be a tablet computer, a notebook computer, a desktop computer or the like. Alternatively, the electronic device may be implemented as a combination of a server and a terminal device, wherein the server and the terminal device may communicate in a wireless or wired manner.
In some implementations, as shown in fig. 1, the application scenario may include a terminal device 110 and a server 120, where the terminal device 110 may be connected to the server 120 through a wired network or a wireless network, and the terminal device may be the terminal device described above.
For example, an application client may be installed on the terminal device 110, a user may log in to the application client based on the terminal device 110 using a login account and a login password, and the server 120 may verify the login account and the login password, and when the verification passes, may determine that the client is successfully logged in based on the terminal device 110. Thereafter, terminal device 110 may display a list of commonly used trusted devices with a list of verified devices, which may be sent by server 120, along with other content displayed in terminal device 110.
After the application scenario of the embodiment of the present application is introduced, the following details of the technical solution of the present application will be described:
fig. 2 is a flowchart of a login device management method according to an embodiment of the present application, where the method may be executed by an electronic device in the application scenario, but is not limited thereto. As shown in fig. 2, the method may include the steps of:
s210: receiving an account login event of an application client corresponding to target account login target equipment;
s220: responding to an account login event, acquiring a common trust device list of a target account, judging whether the number of common devices in the common trust device list is smaller than a number threshold, executing S230 when the number of the common devices is smaller than the number threshold, and executing S240 when the number of the common devices is larger than or equal to the number threshold;
s230: adding target equipment information of target equipment carried in an account login event into a common trust equipment list, wherein equipment types of equipment in the common trust equipment list are common trust equipment types;
s240: moving first device information of the first device from the common trusted device list to a verified device list of the target account, and adding target device information to the common trusted device list; the first device is the device with the earliest login time in the common trust device list, the device type of the device in the verified device list is the verified device type, and the common trust device type device and the verified device type device correspond to different management strategies under different service scenes.
It should be noted that, in the following embodiments, the technical solution of the present application will be described by taking an example that an electronic device is a terminal device, where the terminal device may be a target device in the embodiments of the present application, and the terminal device runs an application client, through which the terminal device may perform data interaction with a server, so as to implement a method corresponding to the following embodiments; when the electronic device is other device, the corresponding content is similar to that of the electronic device, and the description of the content is omitted herein.
It should be noted that the triggering operation, the adjusting operation, and the like in the present application may specifically be a single click, a double click, a press, a drag to a designated area, or a hover touch gesture, which is not limited in the present application
It will be appreciated that the Application client may be an Application (APP) or a web page.
In some implementations, before executing S210 above, the application client or the server corresponding to the electronic device may classify devices logged into the application client based on the target account, determine multiple device types, and a list corresponding to each device type.
By way of example, the plurality of device types may include: the list corresponding to the common trust device type, the verified device type and the invalid device type is as follows: the device categories of the devices respectively contained in the common trust device list, the verified device list and the invalid device list are the common trust device, the verified device and the invalid device. In addition, the non-invalid device in the application is a common trusted device or an authenticated device, and devices with device types of common trusted device type, authenticated device type and invalid device type are respectively called a common trusted device, an authenticated device and an invalid device.
The devices of different device types correspond to different management strategies under different service scenes. For example, devices of different device types may correspond to different priorities. The priority size of the device type may be: the priority of the commonly trusted device type is greater than the priority of the verified device type, which is greater than the priority of the failed device type. Devices of different priorities may correspond to different management policies, which may include, but are not limited to, login policies. For another example, devices of different device types may correspond to different transaction authorities, e.g., a transaction authority of a common trusted device type is a direct transaction without verification, a transaction authority of a verified device type is a verification account transaction password, and a transaction authority of a deactivated device type is a verification account transaction password and an account login password.
For the common trust device, the device which logs in for more than 3 times and passes the two-factor verification can be referred to, and because the common trust device is the highest priority device and has higher flexible processing in many business scenes, the number of the common trust devices, namely the number of the common devices, can be limited, and the number of the verified devices and the failed devices can not be limited. For example, the number of common devices may be set to be less than a number threshold, which may be 3 or 10. When the number of common devices needs to be increased, the electronic device can modify the number threshold of common trusted devices through the corresponding application client. For authenticated devices, it may be referred to as devices that pass two-factor authentication. For a failed device, it may refer to a verified device that has not logged in within 180 days.
When a user logs in on a terminal device, the user needs to perform device lock short message authentication, and after the device lock is opened, the user needs to verify two factors, namely a mobile phone number and a password, during authentication, so that the authentication is called double-factor authentication. Of course, two factors other than the mobile phone number and password are also possible.
In the above process, the device types and the management methods corresponding to the device types can be made simpler and clearer, and the problem that management is complicated due to the fact that the device types are ambiguous under different scenes can be solved, for example, in the login process, different processing processes can be performed for the devices of different device types, so that unnecessary judgment logic is reduced, and the simplicity and reliability of the login process are ensured.
The present application will be described in the following embodiments with respect to determining a device type, displaying and adjusting various device types, and the like:
in some implementations, before the receiving the account login event of the application client corresponding to the target account login target device, the method further includes: receiving a login request sent by target equipment for logging in an application client of a target account; acquiring target equipment information from a login request, and acquiring historical login times of target equipment according to the target equipment information; and determining a target login verification mode of the target equipment according to the historical login times, and carrying out login verification on the target equipment through the target login verification mode. Correspondingly, the receiving the account login event of the application client corresponding to the target account login target device includes: and triggering an account login event when the login verification of the target device is passed through a target login verification mode.
Illustratively, the target device has an application client installed thereon, and the user may log in to the application client using the target account number based on the target device, so that the target device may send a login request to the server, where the login request includes target device information, and the target device information may be used to uniquely identify the target device, for example, the target device information may be an identification of the target device, but is not limited thereto. Then, the server can acquire the historical login times of the target device corresponding to the target device information based on the target device information carried in the login request, and interact with the application client of the target device based on the historical login times to realize login verification of different modes on the target account. The server corresponding to the application client may store in advance the device information of the target account logged in to different devices and the corresponding relationship of the login times logged in to different devices, and each time the target account logs in to the application client through the device, the server may record the device information of the target account logged in to the device and the corresponding relationship of the device information and the login times correspondingly updated. Or, the server may add 1 to the historical login frequency when obtaining the login request for logging in the application client based on the target account number each time, and store the historical login frequency after the corresponding record frequency is increased and the device information of the target device, so that the historical login frequency of the target device may be obtained according to the target device information.
The determining a target login verification manner for the target device according to the historical login times includes: if the historical login times are zero, determining that the target login mode is a first login verification mode; if the historical login times are non-zero values, initial verification information of the target equipment is obtained; when the initial verification information is valid, determining that the target login mode is a second login verification mode; when the initial verification information is invalid, determining that the target login mode is a first login verification mode; the number of verification factors corresponding to the first login verification mode is larger than that of verification factors corresponding to the second login verification mode.
Illustratively, the verification factor may include, but is not limited to, a login account number, a login password, a login gesture. The login account number, the login password and the login gesture can be an account number, a password and a gesture under a target account respectively. The first login verification mode can be two-factor verification, and the corresponding verification factors can be a login account number and a login password; the second login verification mode may be single factor verification, and the corresponding verification factor may be a login password, where the login account may be a mobile phone number, but is not limited thereto.
For example, the initial authentication information may be historical login information when the target device was previously logged in, the historical login information may be ticket data, and the ticket data may include: the version number of the logged-in client, the user identification (IDentification, ID) at the time of login, the type of the logged-in client, the device identification, the password authentication, the short message authentication, or the like, but is not limited thereto.
For example, when verifying whether the initial verification information is valid, the lifecycle corresponding to the initial verification information may be determined first, and if the current time does not belong to the lifecycle, it may be determined that the initial verification information is invalid; if the current time belongs to the life cycle, the initial verification information can be determined to be valid, wherein the target device can interact with the server through the application client to determine the life cycle corresponding to the initial verification information corresponding to the target device, for example, 10 days, and the application is not limited to the life cycle.
When the initial verification information is bill data, the target equipment can interact with the server through the application client to inquire a bill failure time stamp in the bill data so as to judge whether the bill data is failed, and if the current time does not reach the bill failure time stamp, the target equipment can determine that the data is valid; if the current time reaches the ticket failure time stamp, the data can be determined to be invalid.
In some implementations, the moving the first device information of the first device from the common trusted device list to the verified device list of the target account, and adding the target device information to the common trusted device list includes: acquiring historical login times of target equipment according to the target equipment information and equipment types of the target equipment; if the historical login times are smaller than or equal to a preset login threshold value or the device type of the target device is the verified device type, the first device information is moved from the common trust device list to the verified device list, and the target device information is added to the common trust device list.
In addition, after the historical login times of the target device and the device type of the target device are obtained according to the target device information, the method further includes: if the historical login times are larger than a preset login threshold value and the equipment type of the target equipment is the verified equipment type, displaying a common trust equipment adding page; acquiring a first trigger operation aiming at an adding button in a common trust device adding page, wherein the first trigger operation is used for indicating to add a target device to a common trust device list; extracting addition reason information from operation information corresponding to the first triggering operation; if the adding reason information is extracted, adjusting the quantity threshold value, and adding the target equipment information into a common trust equipment list; or if the adding reason information cannot be extracted, moving the first equipment information from the common trust equipment list to the verified equipment list, and adding the target equipment information to the common trust equipment list; wherein the addition reason information is used to represent the reason for adding the target device to the list of commonly used trusted devices.
The first device may also be any device selected randomly from a list of commonly used trusted devices, for example.
By way of example, the common trust device add page may be a popup page, which is not limited in this application. As shown in fig. 3 (c), the common trust device adding page may be displayed in a pop-up window form in a preset area in the display interface, and may specifically include an input box corresponding to the addition reason information; after the user inputs the relevant text information of the reason added to the common trust device through the input box and triggers the corresponding submit button, the electronic device can input the text information in the box as the added reason information and write the added reason information into the operation information corresponding to the first trigger operation, so that the first trigger operation carries the added reason information to instruct the application client to interact with the server to trigger and adjust the quantity threshold of the common trust device based on the added reason information.
Further, in consideration of a management policy corresponding to the common information device, such as a login priority or a transaction authority is often higher, in order to ensure account security of the target account, after determining that the first triggering operation carries the addition reason information, whether to trigger adjustment of the number threshold of the common trust device can be determined based on the addition reason information and the current login information of the target device. Specifically, after adding reason information is extracted from operation information corresponding to the first triggering operation, adding reason information and current login information corresponding to the target equipment can be obtained, wherein the current login information comprises but is not limited to login time, login position, login ip address and the like; further, converting the addition reason information into a corresponding target word vector, matching the target word vector with a word vector corresponding to a preset addition reason text to obtain a first matching degree, and simultaneously matching current login information with target login information of target common equipment in a common trust equipment list to obtain a second matching degree, wherein the target common equipment refers to equipment with login time closest to the current time in the common trust equipment list, and the target login information refers to login information of the target common equipment in the last login; and finally, determining whether to trigger the adjustment of the quantity threshold value of the commonly used trust equipment according to the first matching degree and the second matching degree.
Taking the first matching degree as an example, the added cause information can be segmented, target word vectors of all segmented words are obtained, then the target word vectors corresponding to all segmented words are respectively matched with word vectors corresponding to preset added cause texts, and the first matching degree is obtained through the following formula:
wherein x is i Representing a matching result of the i (i=1, 2, …, n) th target word vector and a word vector corresponding to a preset addition reason text, if the matching is successful, the matching is 1, and if the matching is unsuccessful, the matching is 0; p (P) 1 A second degree of matching is indicated and,
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 common device in the common trust device list can be obtained through the following formula (1):
wherein LogA represents current login information of target equipment, a i (i=1, 2, …, n) represents a specific information sequence in the current login information, such as loginRecording time, login position, login ip address and the like; logB represents target login information of target common equipment, b i (i=1, 2, …, n) represents a specific information sequence in the target login information; p (P) 2 And the second matching degree is represented, and it can be understood that when the second matching degree is closer to 1, the logging time, the logging position, the logging ip address and other logging information of the target equipment are similar to the logging information of the target common equipment in the common trust equipment list, the probability that the target equipment carries out logging operation for the user corresponding to the target account is higher, and the safety of account logging setting is effectively improved.
After the first matching degree and the second matching degree are obtained, the target matching degree can be determined by the following formula (2):
wherein R represents the target matching degree, P 1 Represents the first degree of matching, P 2 Represents the second degree of matching, w 1 Weight value, w, representing first degree of matching 2 And a weight value representing the second degree of matching. And when the target matching degree is smaller than or equal to the preset matching degree threshold, determining not to trigger the adjustment of the quantity threshold of the commonly used trust equipment, and continuing to execute the steps of moving the first equipment information from the commonly used trust equipment list to the verified equipment list and adding the target equipment information to the commonly used trust equipment list.
After the target device finishes logging in, the common trust device adding page can be directly displayed, or the common trust device adding page can be displayed when the trigger operation of the user for other pages or buttons is acquired.
For example, the electronic device may set a popup window condition, and when the target device is detected to meet the popup window condition after the target device completes logging in, a common trust device adding page may be displayed in a popup window manner. The popup condition may be any of the following, but is not limited thereto: the device type of the target device is not a common trust device, the device type of the target device is changed into a common trust device, the number of the common devices exceeds a number threshold, the login time of the target device is longer than the target time, the target device does not display a page for adding the common trust device, and the target time can be 3 days.
For example, after the target device completes login, a common trust device adding page can be displayed when trigger operation of a user for other pages or buttons is acquired; as shown in fig. 3 (a), when the user uses the target account, after logging in the application client based on the target device, the target device may display a "self-selected page" as shown in fig. 3 (b), and the bottom of the "self-selected page" is displayed with a "my" button, and the target device may acquire a trigger operation of the user on the "my" button, and display a common trust device addition page as shown in fig. 3 (c), where the bottom of the "my page" is displayed in a popup window form as shown in fig. 3 (c). The common trust device add page may include an input box that may obtain the user entered add cause information.
In some implementations, in conjunction with the foregoing embodiments, as shown in fig. 4, after the login operation of the login application client is acquired, it may be determined whether the login is a new device, that is, whether the target device is a first-time login device, where the first-time login device may be understood as a device of the first-time login application client. When the target device is the first login device, the target device can be subjected to double-factor login verification based on a double-factor verification mode, and when verification passes, whether the number of the common devices is smaller than a number threshold or not, namely whether the number exceeds an upper limit can be judged. When the number of the common devices is smaller than the number threshold, adding the target device to a common trust device list; when the number of the common devices is greater than or equal to the number threshold, the device with the earliest login time in the common trust device list is moved to the verified device list, and the target device is added to the common trust device list.
When the target device is judged not to be the first login device, whether bill data of the target device is out of date or not can be judged. When the bill data is not expired, single-factor login verification can be carried out on the target equipment based on a single-factor verification mode; and when the bill data is out of date, performing double-factor login verification on the target equipment based on a double-factor verification mode. Next, it may be determined whether the number of commonly used devices is less than a number threshold. When the number of the common devices is smaller than the number threshold, adding the target device to a common trust device list; when the number of the common devices is greater than or equal to the number threshold, it may be determined whether the login number of the target device is greater than 3 and whether the target device belongs to the verified device list. When the login times of the target equipment are more than 3 and the target equipment belongs to the verified equipment list, a common trust equipment adding page can be displayed in a popup window mode, after the trigger operation of an adding button in the common trust equipment adding page by a user is obtained, if the adding reason information, namely the application reason information, is obtained, the target equipment is added into the common trust equipment list, and the existing limit on the number of the common equipment is not adjusted without adjusting the number threshold; if the adding reason information is not acquired, the target device is added to the common trust device list, and the number threshold is adjusted to be increased by 1. The list of commonly used trusted devices at this time may include information corresponding to existing commonly used trusted devices and information corresponding to the target device.
It should be noted that, in the present application, a common device refers to a common trusted device, and a common device list refers to a common trusted device list.
In the embodiment, the first login device can be quickly and conveniently determined to be the common trust device, so that the efficiency and convenience of device management are improved. In addition, for the device which has more login times and is extruded to the verified device list (i.e. moves from the common trusted device list to the verified device list), the device can be re-added to the common trusted device list by the adding manner so as to perform corresponding management on the common trusted device.
In some implementations, the electronic device can display a login device management page that includes a list of commonly used trusted devices and a list of verified devices; acquiring a second triggering operation aiming at a second device in the login device management page; and responding to the second triggering operation, and displaying basic information and historical login information of the second equipment.
In addition, the electronic device can also acquire a category adjustment operation for the third device in the login device management page; in response to the category adjustment operation, the third device is moved between the list of commonly used trusted devices and the list of verified devices.
For example, the above-mentioned category adjustment operation may be a drag operation of the third device displayed in the login device management page, for example, may be dragging the third device displayed in the commonly used trusted device list to a display position corresponding to the verified device list; the clicking operation may be performed on a button corresponding to the third device displayed on the login device management page, which is not limited in this application.
By way of example, the above-described basic information may include at least one of, but is not limited to: device name, device type, device version. The history log-in information may include at least one of, but is not limited to: historical login time, historical login address.
For example, moving the third device between the list of commonly trusted devices and the list of verified devices may include: moving the third device from the list of commonly used trusted devices into the list of verified devices, and moving the third device from the list of verified devices into the list of commonly used trusted devices. That is, the device type of the third device is adjusted from the common trusted device to the verified device or the device type of the third device is adjusted from the verified device to the common trusted device.
In some implementations, the login device management page may be as shown in fig. 5 (a), in which the electronic device may display the common trusted device list and the verified device list separately, i.e., the common trusted device and the verified device may be displayed separately. After acquiring a trigger operation by the user for any one of the devices, a device detail page as shown in (b) in fig. 5 may be displayed, on which basic information, history login information, and the like of the device are displayed. When the trigger operation of the user for the "device name" is acquired, a modified name page as shown in (c) of fig. 5 may be displayed, the device name input by the user may be acquired in the page, and the name may be determined as a new name of the device.
In some implementations, as shown in (a) of fig. 6, the login device management page may display a "+" or a "-" button on the right of the location where each device is displayed, where the "+" button and the "-" button are used to perform an upgrade operation and a downgrade operation, respectively, for moving the corresponding device from the verified device list to the common trusted device list, from the common trusted device list to the verified device list, respectively, for adjusting the corresponding device from the verified device to the common trusted device, and from the common trusted device to the verified device, respectively. For example, after the trigger operation of the "+" button corresponding to the device 3 is acquired, a page as shown in (b) in fig. 6 may be displayed, the content corresponding to the page may refer to the above-described adding commonly used trusted device page, and after the trigger operation of the user for the submit button is acquired, a login device management page as shown in (c) in fig. 6 may be displayed, at which time a newly added commonly used trusted device, i.e., the device 3, may be displayed at a display position corresponding to the commonly used trusted device list.
In the process, the electronic equipment can display different equipment types and equipment lists in a classified manner through an asynchronous processing method, and can also gather and display basic information of the equipment according to historical login information, so that the electronic equipment is convenient for a user to check and modify. In addition, the degradation and the upgrading of the equipment type based on the manual operation mode are provided for the user, so that the user can manage the equipment type by himself.
In the following embodiments, the present application will be described with respect to a scenario corresponding to upgrading and downgrading of a login device, that is, a scenario corresponding to an adjustment device type:
it should be noted that, the upgrading of the device includes: adjusting the failed device to be a common trusted device, adjusting the verified device to be a common trusted device, the downgrading of the device includes: the common trusted device is tuned to be a verified device and the verified device is tuned to be a failed device.
In some implementations, as shown in fig. 7, the upgrade of the login device includes the following two scenarios:
in a first scenario, after the login device is successfully logged in, the device can be determined to be trusted, and then the device can be directly determined to be a commonly trusted device no matter what type of device the device is.
And in a second scenario, upgrading is performed based on the device management interface, namely upgrading based on adding a common trusted device page or logging device management page in the embodiment.
In some implementations, as shown in fig. 8, the demotion of the login device includes the following three scenarios:
in the first scenario, after the login of the login device is successful, if the number of the common devices exceeds the limit of the number of the common trust devices, that is, is greater than or equal to the number threshold, the common trust device exceeding the limit, such as the common trust device with the earliest login time, is demoted to the verified device.
The second scenario is based on device management interface degradation, i.e. on adding a common trusted device page or logging on a device management page degradation in the above embodiments. The user downgrades the common trusted device at the device management interface, where the common trusted device is downgraded to a verified device.
And in a third scenario, degrading based on the login duration of the device, and degrading the device which is not logged in for a long time. For example, a common trusted device that is not logged in for 30 days is downgraded to a verified device, and a verified device that is not logged in for 180 days is downgraded to a failed device. Wherein the failed device is equivalent to the new device.
In addition, after the login device is upgraded or downgraded, the user can be informed of successful upgrading or downgrading operation based on instant messaging or real-time messaging (Instant Messaging, IM) to push (push) reminding information to the user.
In the process, the login device management function for managing the device type can be provided for the user, and the management for the device type is mainly performed through upgrading and degrading operations for the login device, so that the operation convenience of the user is improved.
In some implementations, the electronic device may create multiple classes (with respect to interfaces) and invoke the created classes to perform the above embodiments or to perform methods corresponding to the above embodiments.
Specifically, in connection with fig. 9, the electronic device may create a login service class, a message middleware class, a device compliance service class, a login service class, a device compliance service class, a push service class, a message sending service base class, a mail sending class, a short message sending class, a reminder sending class, a device information service class, a login history service class, and a crm platform class. The login service class is used for processing login events; the message middleware class is used for establishing a subscription relationship between the login service class and the equipment compliance service class; the device compliance service class is used for asynchronously processing login events, controlling upgrading and degrading of device types and guiding a user to increase the number popup window of the common trust devices; the pushing service class is used for pushing the popup windows for increasing the number of the common trust devices to the client; the messaging service base class is used for notifying the message, and comprises: the mail sending class, the short message sending class, the reminding number sending class and the three sending classes are similar, so that a message sending service base class can be established, the three sending classes are inherited to the message sending service base class, and each sending class is ensured to have a notification mode; the equipment information service class is used for maintaining and storing the basic information of the equipment; the login history service class is used for maintaining and storing the login history of the user, and can be called for login record storage after login of login equipment is successful; the crm platform class is used for querying the user to increase the number of related records of commonly used trusted devices.
In some implementations, in combination with the foregoing embodiments, as shown in fig. 10, the server may include a login service, a device information module, a device compliance module, a message middleware, and a push service, where when a user performs a login operation based on a login device, the login service may determine a login event and send the login event to the message middleware, and then the message middleware may consume the login event, so that the device compliance module obtains device information from the device information module, and the device compliance module may determine whether the device is a common trust device according to the device information and update the device to the common trust device when the device is not the common trust device. And if the number of the common devices is greater than or equal to the number threshold, updating the common trust device with the earliest login time into the verified device. If the number of common devices is greater than or equal to the number threshold and the number of logins of the device is greater than 3, the number of common devices may be modified by popup based on the push service.
In addition, the equipment type can be maintained by the equipment compliance module and the equipment information module, so that the server can integrate and uniformly maintain the equipment compliance module and the equipment information template so as to achieve the single responsibility principle of service and reduce the maintenance cost.
In some implementations, in combination with the above embodiments, as shown in fig. 11, the login device may install a client, and the server may include a device aggregate block and a device information module. The client can pull the device information of the non-invalid devices ordered according to the login time from the device information module and display the device information according to the device type. The device information module can upgrade and downgrade the device type based on upgrade operation, downgrade operation and delete operation of the user. The equipment compliance module can push the popup window to the client and interact with the equipment information module to finish the adjustment of the number of common equipment and the modification of equipment types.
It should be noted that, in all the above technical solutions, any combination may be adopted to form an optional embodiment of the present application, which is not described herein in detail.
It should be noted that, in the specific embodiments of the present application, related data such as login devices, account numbers, passwords, etc. are related, when the embodiments of the present application are applied to specific products or technologies, user permission, consent or authorization needs to be obtained, and collection, use and processing of related data need to comply with related laws and regulations and standards of related countries and regions.
Fig. 12 is a schematic diagram of a login device management apparatus 1200 according to an embodiment of the present application. As shown in fig. 12, the login device management apparatus 1200 includes: the first receiving module 1201, the acquisition judging module 1202, the first adding module 1203, the adding moving module 1204, the second receiving module 1205, the first acquiring module 1206, the determination verifying module 1207, the first display module 1208, the second acquiring module 1209, the adjusting moving module 1210, the second display module 1211, the third acquiring module 1212, the third display module 1213, the fourth acquiring module 1214, and the first moving module 1215.
In some implementations, the first receiving module 1201 is configured to: receiving an account login event of an application client corresponding to target account login target equipment; an acquisition judgment module 1202 for: responding to an account login event, acquiring a common trust device list of a target account, and judging whether the number of common devices in the common trust device list is smaller than a number threshold; a first adding module 1203 configured to: when the number of the common devices is smaller than the number threshold, adding target device information of target devices carried in the account login event into a common trust device list; the adding mobile module 1204 is configured to: when the number of the common devices is greater than or equal to a number threshold, moving first device information of the first device from a common trust device list to a verified device list of a target account, and adding target device information to the common trust device list; the first device is the device with the earliest login time in the common trust device list; the device types of the devices in the common trust device list are common trust device types, the device types of the devices in the verified device list are verified device types, and the devices of the common trust device types and the devices of the verified device types correspond to different management strategies under different service scenes.
In some implementations, the second receiving module 1205 is configured to: receiving a login request sent by target equipment for logging in an application client of a target account; a first obtaining module 1206, configured to: acquiring target equipment information from a login request, and acquiring historical login times of target equipment according to the target equipment information; a determination verification module 1207 for: determining a target login verification mode of target equipment according to the historical login times, and carrying out login verification on the target equipment through the target login verification mode; the first receiving module 1201 is specifically configured to: and triggering an account login event when the login verification of the target device is passed through a target login verification mode.
In some implementations, the validation module 1207 is determined, specifically to: if the historical login times are zero, determining that the target login mode is a first login verification mode; if the historical login times are non-zero values, initial verification information of the target equipment is obtained; when the initial verification information is valid, determining that the target login mode is a second login verification mode; when the initial verification information is invalid, determining that the target login mode is a first login verification mode; the number of verification factors corresponding to the first login verification mode is larger than that of verification factors corresponding to the second login verification mode.
In some implementations, the mobile module 1204 is added, specifically for: acquiring historical login times of target equipment according to the target equipment information and equipment types of the target equipment; if the historical login times are smaller than or equal to a preset login threshold value or the device type of the target device is the verified device type, the first device information is moved from the common trust device list to the verified device list, and the target device information is added to the common trust device list.
In some implementations, a first display module 1208 to: if the historical login times are larger than a preset login threshold value and the equipment type of the target equipment is the verified equipment type, displaying a common trust equipment adding page; a second acquisition module 1209 for: acquiring a first trigger operation aiming at an adding button in a common trust device adding page, wherein the first trigger operation is used for indicating to add a target device to a common trust device list; an adjustment movement module 1210 for: responding to a first trigger operation, and responding to the first trigger operation, and extracting addition reason information from operation information corresponding to the first trigger operation; if the adding reason information is extracted, adjusting the quantity threshold value, and adding the target equipment information into a common trust equipment list; or if the adding reason information cannot be extracted, moving the first equipment information from the common trust equipment list to the verified equipment list, and adding the target equipment information to the common trust equipment list; wherein the addition reason information is used to represent the reason for adding the target device to the list of commonly used trusted devices.
In some implementations, the second display module 1211 is to: displaying a login device management page, wherein the login device management page comprises a common trust device list and a verified device list; a third acquisition module 1212 for: acquiring a second triggering operation aiming at a second device in the login device management page; a third display module 1213 for: and responding to the second triggering operation, and displaying basic information and historical login information of the second equipment.
In some implementations, a fourth acquisition module 1214 for: acquiring a category adjustment operation for a third device in the login device management page; a first movement module 1215 for: in response to the category adjustment operation, the third device is moved between the list of commonly used trusted devices and the list of verified devices.
It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus 1200 shown in fig. 12 may perform the above method embodiments, and the foregoing and other operations and/or functions of each module in the apparatus 1200 are respectively for implementing the corresponding flows in each method, which are not described herein for brevity.
The apparatus 1200 of the embodiments of the present application is described above in terms of functional modules in connection with the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiments in the embodiments of the present application may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in software form, and the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented as a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.
Fig. 13 is a schematic block diagram of an electronic device 1300 according to an embodiment of the present application.
As shown in fig. 13, the electronic device 1300 may include:
A memory 1310 and a processor 1320, the memory 1310 for storing a computer program and transmitting the program code to the processor 1320. In other words, the processor 1320 may call and run a computer program from the memory 1310 to implement the methods in embodiments of the present application.
For example, the processor 1320 may be configured to perform the method embodiments described above in accordance with instructions in the computer program.
In some embodiments of the present application, the processor 1320 may include, but is not limited to:
a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.
In some embodiments of the present application, the memory 1310 includes, but is not limited to:
volatile memory and/or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM).
In some embodiments of the present application, the computer program may be partitioned into one or more modules that are stored in the memory 1310 and executed by the processor 1320 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing the specified functions, which are used to describe the execution of the computer program in the electronic device.
As shown in fig. 13, the electronic device may further include:
a transceiver 1330, the transceiver 1330 being connectable to the processor 1320 or the memory 1310.
Wherein the processor 1320 may control the transceiver 1330 to communicate with other devices, in particular, 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 antennas, the number of which may be one or more.
It will be appreciated that the various components in the electronic device are connected by a bus system that includes, in addition to a data bus, a power bus, a control bus, and a status signal bus.
The present application also provides a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the method embodiments described above.
When implemented in software, may 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 loaded and executed on a computer, produces, in whole or in part, a flow or function consistent with embodiments of the present application. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.
The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes or substitutions are covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A login device management method, comprising:
receiving an account login event of an application client corresponding to target account login target equipment;
responding to the account login event, acquiring a common trust equipment list of the target account, and judging whether the number of common equipment in the common trust equipment list is smaller than a number threshold;
When the number of the common devices is smaller than the number threshold, adding target device information of target devices carried in the account login event to the common trust device list;
when the number of the common devices is greater than or equal to the number threshold, moving first device information of a first device from the common trust device list to a verified device list of the target account, and adding the target device information to the common trust device list; the first device is the device with the earliest login time in the common trust device list;
the device types of the devices in the common trust device list are common trust device types, the device types of the devices in the verified device list are verified device types, and the devices of the common trust device types and the devices of the verified device types correspond to different management strategies under different service scenes.
2. The method of claim 1, wherein prior to receiving the account login event for the application client for the target account login target device, further comprising:
receiving a login request for logging in the application client by the target account, which is sent by the target equipment;
Acquiring the target equipment information from the login request, and acquiring the historical login times of the target equipment according to the target equipment information;
determining a target login verification mode of the target equipment according to the historical login times, and carrying out login verification on the target equipment through the target login verification mode;
the receiving the account login event of the application client corresponding to the target account login target device comprises the following steps:
and triggering the account login event when the login verification of the target equipment is passed through the target login verification mode.
3. The method of claim 2, wherein determining a target login authentication method for the target device based on the historical login times comprises:
if the historical login times are zero, determining that the target login mode is a first login verification mode;
if the historical login times are non-zero values, initial verification information of the target equipment is obtained;
when the initial verification information is valid, determining that the target login mode is a second login verification mode;
when the initial verification information is invalid, determining that the target login mode is the first login verification mode;
The number of verification factors corresponding to the first login verification mode is larger than the number of verification factors corresponding to the second login verification mode.
4. The method of claim 1, wherein the moving the first device information of the first device from the common trusted device list to the verified device list of the target account and adding the target device information to the common trusted device list comprises:
acquiring historical login times of the target equipment and equipment types of the target equipment according to the target equipment information;
and if the historical login times are smaller than or equal to a preset login threshold value or the equipment type of the target equipment is the verified equipment type, moving the first equipment information from the common trust equipment list to the verified equipment list, and adding the target equipment information to the common trust equipment list.
5. The method of claim 4, wherein after the obtaining the historical login times of the target device and the device type of the target device according to the target device information, further comprises:
If the historical login times are larger than a preset login threshold value and the equipment type of the target equipment is the verified equipment type, displaying a common trust equipment adding page;
acquiring a first trigger operation aiming at an add button in the common trust equipment adding page, wherein the first trigger operation is used for indicating to add the target equipment to the common trust equipment list;
responding to the first trigger operation, and extracting addition reason information from operation information corresponding to the first trigger operation;
if the adding reason information is extracted, adjusting the quantity threshold value, and adding the target equipment information into the common trust equipment list; or,
if the adding reason information cannot be extracted, moving the first equipment information from the common trust equipment list to the verified equipment list, and adding the target equipment information to the common trust equipment list;
wherein the addition reason information is used for indicating the reason for adding the target device to the common trust device list.
6. The method of any one of claims 1-4, further comprising:
Displaying a login device management page, wherein the login device management page comprises the common trust device list and the verified device list;
acquiring a second triggering operation aiming at a second device in the login device management page;
and responding to the second triggering operation, and displaying basic information and historical login information of the second equipment.
7. The method as recited in claim 6, further comprising:
acquiring 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 list of commonly used trusted devices and the list of verified devices.
8. A login device management apparatus, comprising,
the first receiving module is used for receiving an account login event of the application client corresponding to the target account login target device;
the acquisition judging module is used for responding to the account login event, acquiring a common trust equipment list of the target account and judging whether the number of the common equipment in the common trust equipment list is smaller than a number threshold value or not;
the first adding module is used for adding the target equipment information of the target equipment carried in the account login event to the common trust equipment list when the number of the common equipment is smaller than the number threshold;
An adding mobile module, configured to, when the number of the common devices is greater than or equal to the number threshold, move first device information of a first device from the common trusted device list to a verified device list of the target account, and add the target device information to the common trusted device list; the first device is the device with the earliest login time in the common trust device list;
the device types of the devices in the common trust device list are common trust device types, the device types of the devices in the verified device list are verified device types, and the devices of the common trust device types and the devices of the verified device types correspond to different management strategies under different service scenes.
9. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the method of any of claims 1-7 via execution of the executable instructions.
10. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1-7.
CN202311560670.4A 2023-11-21 2023-11-21 Login equipment management method, device and equipment Pending CN117376018A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202311560670.4A CN117376018A (en) 2023-11-21 2023-11-21 Login equipment management method, device and equipment
PCT/CN2024/132738 WO2025108238A1 (en) 2023-11-21 2024-11-18 Login device management method and apparatus, and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311560670.4A CN117376018A (en) 2023-11-21 2023-11-21 Login equipment management method, device and equipment

Publications (1)

Publication Number Publication Date
CN117376018A true CN117376018A (en) 2024-01-09

Family

ID=89407837

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311560670.4A Pending CN117376018A (en) 2023-11-21 2023-11-21 Login equipment management method, device and equipment

Country Status (2)

Country Link
CN (1) CN117376018A (en)
WO (1) WO2025108238A1 (en)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125062B (en) * 2013-04-26 2016-04-27 腾讯科技（深圳）有限公司 Login method and device, login authentication device, server, terminal and system
US9887991B2 (en) * 2015-03-27 2018-02-06 Yahoo Holdings, Inc. Facilitation of service login
CN107483698A (en) * 2017-09-05 2017-12-15 北京珠穆朗玛移动通信有限公司 A kind of contact management method, mobile terminal and storage medium
CN108848113B (en) * 2018-08-15 2021-03-26 广州视源电子科技股份有限公司 Client device login control method and device, storage medium and server
CN114157438A (en) * 2020-08-18 2022-03-08 深圳富桂精密工业有限公司 Network equipment management method and device and computer readable storage medium
CN115604708A (en) * 2022-10-19 2023-01-13 北京自如信息科技有限公司（Cn） User account protection method, device, electronic device and readable storage medium

Also Published As

Publication number Publication date
WO2025108238A1 (en) 2025-05-30

Similar Documents

Publication Publication Date Title
US12204650B2 (en) High granularity application and data security in cloud environments
US11265329B2 (en) Mechanisms for anomaly detection and access management
US11595392B2 (en) Gateway enrollment for internet of things device management
US11258827B2 (en) Autonomous monitoring of applications in a cloud environment
US11165800B2 (en) Cloud based security monitoring using unsupervised pattern recognition and deep learning
CN109792439B (en) Dynamic policy injection and access visualization for threat detection
US9596232B2 (en) Managing sharing of wireless network login passwords
US11336599B2 (en) Architecture for performing action in a third-party service by an email client
US9264449B1 (en) Automatic privilege determination
US10225283B2 (en) Protection against end user account locking denial of service (DOS)
US20130080522A1 (en) Broker-based management of mobile devices
US10965680B2 (en) Authority management method and device in distributed environment, and server
US10582005B2 (en) Architecture for performing actions in a third-party service by an email client
US11930003B2 (en) Workflow service back end integration
US11722476B2 (en) Workflow service back end integration
CN113767613A (en) Managing data and data usage in an IOT network
CN117376018A (en) Login equipment management method, device and equipment
US12028329B2 (en) Workflow service back end integration
CN117278201A (en) Information processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination