CN111460411A - Method and system for keeping login state - Google Patents
Method and system for keeping login state Download PDFInfo
- Publication number
- CN111460411A CN111460411A CN202010302620.6A CN202010302620A CN111460411A CN 111460411 A CN111460411 A CN 111460411A CN 202010302620 A CN202010302620 A CN 202010302620A CN 111460411 A CN111460411 A CN 111460411A
- Authority
- CN
- China
- Prior art keywords
- time
- behavior
- login state
- determining
- login
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The embodiment of the specification discloses a method and a system for maintaining a login state, wherein the method comprises the following steps of: acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen; determining an extension time of the login state based on the characteristic data; adjusting the login state failure time based on the extension time; and keeping the login state valid before the login state failure moment.
Description
Technical Field
The embodiment of the specification relates to the technical field of communication, in particular to a method and a system for maintaining a login state.
Background
The login state (or login state) may refer to a state where a software system is logged in by a certain user, which may be used to prove the uniqueness and validity of the user identity, so that the current user can operate the software system. Typically, the logged-in state will have an expiration time, and the user will only remain logged-in until that time, with the right to operate the software system. Therefore, the application provides a method and a system for maintaining the login state, which can dynamically adjust the failure time of the login state.
Disclosure of Invention
One aspect of an embodiment of the present specification provides a method of maintaining a login state, comprising: acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen; determining an extension time of the login state based on the characteristic data; adjusting the login state failure time based on the extension time; and keeping the login state valid before the login state failure moment.
One aspect of an embodiment of the present specification provides a system for maintaining a login state, comprising: the method comprises the following steps: in the user login state: the device comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen; a determination module for determining the time extension of the login status based on the characteristic data; the adjusting module is used for adjusting the failure time of the login state based on the extension time; and the maintaining module is used for maintaining the login state to be effective before the login state failure moment.
An aspect of the embodiments of the present specification provides an apparatus for maintaining a login state, including a processor for executing the method for maintaining a login state as described above.
An aspect of embodiments of the present specification provides a computer-readable storage medium storing computer instructions, and when the computer reads the computer instructions in the storage medium, the computer performs the method of maintaining the login status as described above.
Drawings
The present description will be further described by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. These embodiments are not intended to be limiting, and in these embodiments like numerals are used to indicate like structures, wherein:
FIG. 1 is a schematic diagram of an application scenario of a system for maintaining a logged-on state, according to some embodiments of the present description;
FIG. 2 is a flow diagram of a method of maintaining a login state in accordance with some embodiments of the present description;
FIG. 3 is a flow diagram illustrating a method of determining an extension time in accordance with some embodiments of the present description;
FIG. 4 is another flow diagram of a method of determining an extension time in accordance with some embodiments of the present description;
FIG. 5 is another flow diagram of a method of determining an extension time in accordance with some embodiments of the present description;
FIG. 6 is another flow diagram of a method of determining an extension time in accordance with some embodiments of the present description;
FIG. 7 is a block diagram illustrating a system to maintain a logged on state in accordance with some embodiments of the present description.
Detailed Description
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the present description, and that for a person skilled in the art, the present description can also be applied to other similar scenarios on the basis of these drawings without inventive effort. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.
It should be understood that "system", "device", "unit" and/or "module" as used in this specification is a method for distinguishing different components, elements, parts or assemblies at different levels. However, other words may be substituted by other expressions if they accomplish the same purpose.
As used in this specification and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.
Flow charts are used in this description to illustrate operations performed by a system according to embodiments of the present description. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, the various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or several steps of operations may be removed from the processes.
FIG. 1 is a schematic diagram of an application scenario of a system for maintaining a logged-on state, according to some embodiments of the present description.
As shown in FIG. 1, a keep-logged-state system 100 may include a terminal device 110, a network 120, and a server 130.
In some embodiments, the terminal device 110 may be a common device that provides query services and/or data processing services to the public, such as an internet of things device (IoT device) 110-1. an exemplary IoT device 110-1 may include, but is not limited to, a face vending machine, a self-service cash register, a bank personal business terminal, and the like, or any combination thereof after a user completes a login on the terminal device 110, the data services provided by the device may be used.
In some embodiments, the terminal device 110 may also be a portable device with data acquisition, storage, and/or transmission capabilities, such as a tablet computer 110-2, a laptop computer 110-3, a smartphone 110-4, and the like, or any combination thereof. In some embodiments, the terminal device 110 may perform data interaction with the server 130 through the network, and after a user logs in on the terminal device 110, the data service of the server 130 may be used through the terminal device 110. At this time, the terminal device 110 may place a part of the information and/or data associated with the login-holding state on the server 130 for processing, and implement the related function of the login-holding state. For example, terminal device 110 may transmit the acquired data to server 130. In some embodiments, the data acquired by the terminal device 110 may be feature data generated by the user on the device screen that reflects the trigger behavior. It is understood that the terminal device 110 may implement the function of maintaining the user login status locally, or may implement the function in conjunction with the server 130.
In some embodiments, one or more components of the keep-alive system 100 (e.g., terminal device 110, server 130) may communicate information to other components of the keep-alive system 100 via network 120. for example, terminal device 110 may obtain data provided by server 130 via network 120 to perform user-oriented data service functions (e.g., data queries or data changes, etc.).
The technical scheme disclosed by the embodiment of the specification can be applied to a scene that a user interacts with the server through the terminal equipment and uses the online service provided by the server. For example, the user uses an online payment service provided by mobile payment software through a mobile phone. As another example, a user, through an IoT device: the vending machine uses the online shopping service provided by its system. It can be understood that the technical solution disclosed in the embodiments of the present disclosure may also be applied to a situation where a user directly interacts with a terminal device, and the terminal device may locally integrate all functions of a server without remotely connecting to a background server through a network.
As an example, when a user uses an IoT device, the user needs to log in (e.g., swipe face login, scan code login, account password login, etc.) on a software system of the device to perform authentication to obtain a login status, so as to be able to operate the non-shared information of the IoT device. Generally, an IoT device is a public device, provides data services for the public, and sets a login effective time in a login state in order to prevent a previous user from logging out of the IoT device in time after using the IoT device, and further information security accidents such as leakage of private data are caused. As can be appreciated, after this time, the user's login status fails and is unable to manipulate the corresponding non-common information of the IoT device. In some embodiments, the validity time of the logged state is fixed. This approach may have the following features: the effective time is set to be too long, so that the risk that the login state of the current user is effective but the operation equipment is not the current user exists, the personal information of the user is leaked, and potential safety hazards exist; the effective time is set to be too short, so that the user can log in for multiple times in the operation process, and the use experience of the user is reduced.
Therefore, the embodiment of the specification discloses a method for maintaining a login state, which dynamically adjusts the failure time of the login state by correspondingly processing the characteristic data generated on the screen of the device. The technical solution disclosed in the present specification is explained in detail below with reference to the accompanying drawings.
Fig. 2 is a flow diagram illustrating a method of maintaining a login state according to some embodiments of the present description.
In particular, this step may be performed by the obtaining module 710.
In some embodiments, the user login status may refer to a status generated after the user successfully logs in the software system of the device, or referred to as a login status. In some embodiments, the device may be a terminal that provides online services for the user. Such as a self-service cash register, a face vending machine, or a smart phone. It can be understood that, in the user login state, the user and the device may perform an interactive operation, thereby using the online service provided by the device. For example, self-service payment services provided using a self-service cash register.
In some embodiments, the feature data reflecting the trigger behavior may refer to any data generated by the device screen being triggered. In some embodiments, the feature data reflecting the triggering behavior may include feature data of at least one focus point generated as a result of the device screen being triggered. The focus may refer to a portion of the screen of the device triggered by the user, which may be an area or a point.
In some embodiments, the focus may be represented using a certain one or a certain set of coordinate points in a focus coordinate range determined based on the resolution of the device screen. In general, the origin (0, 0) may be the vertex in the upper left corner of the screen device. For example, if the resolution of the device screen is a × b, the coordinate range may be a rectangular region surrounded by an upper left vertex (0, 0), an upper right vertex (b, 0), a lower left vertex (0, a), and a lower right vertex (b, a). When the equipment screen is triggered, a user can directly contact with the equipment screen, the abscissa of the focus is in a numerical range [0, b ] at the moment, and the ordinate of the focus is in the numerical range [0, a ].
In some embodiments, the characteristic data of the focus may include focus coordinate values, or include focus coordinate values and their corresponding time information. In some embodiments, the time information corresponding to the focus coordinate value may refer to a time at which the focus coordinate value is generated. In some embodiments, the feature data of the focus may be directly obtained through a system underlying interface of the terminal device.
In some embodiments, some operating systems may further process the focus data, for example, determine a corresponding operation behavior based on a track of the focus data, and package a result obtained by the processing into a form more oriented to an application layer for a developer to directly call, so as to save program development resources. Thus, in some embodiments, the characteristic data reflecting the trigger behavior may include behavior events of the system package. In some embodiments, the system may refer to an operating system included in the device. Such as an android system or an IOS system. In some embodiments, a behavior event may refer to an event packaged by the system to characterize a category of behavior that a user operates on a screen of the device. For example, a click behavior event characterizing a user click operation. As another example, a press behavior event that characterizes a user press operation.
In some embodiments, the obtaining module 710 may obtain the feature data within a preset time period before the current login status failure time. In some embodiments, the preset duration may be specifically set according to actual requirements. E.g., 10s or 30s, etc.
In some embodiments, the current login state expiration time may be the login state expiration time before the next update. For example, the initial login state invalidation time may be the sum of the generation time of the login state and the preset validity time of the login state. In some embodiments, the preset valid time may be specifically set according to actual requirements. For example, 3min, 5min, or 10min, etc. It will be appreciated that the initial login state expiration time is the time at which the login state is not delayed. For example, if the user logs in to loT the device at 10 hours and the preset valid time of the login state is 3min, the current login state failure time is as follows: and the time is 10 hours and 03 minutes.
In some embodiments, the current login failure time may be a login status failure time adjusted based on the extended time. It is understood that the current login failure time is the time when the login status is delayed. For the adjusted login status failure time, reference may be made to step 206 and the related description thereof, which are not described herein again.
In some embodiments, the acquisition module 710 may acquire the feature data from the user terminal 130. In some embodiments, the obtaining module 710 may also obtain the characteristic data by reading stored data, invoking an associated interface, or otherwise.
In particular, this step may be performed by the determination module 720.
In some embodiments, the determination module 720 may determine the extension time of the login status in different ways based on different characteristic data. For example, based on the focus coordinate value, or the focus coordinate value and its corresponding time information, a delay prediction model or a behavior prediction model may be used to determine the time for the login status. Specific details regarding the determination of the extension time can be seen in fig. 3 and 4, which are not described herein. For another example, based on the focus coordinate value and the corresponding time information thereof, a preset behavior determination rule may be employed to determine the extended time of the login state. For specific details of determining the extension time, reference may be made to fig. 5, which is not described herein.
And step 206, adjusting the login state failure time based on the extension time.
In particular, this step 206 may be performed by the adjustment module 730.
In some embodiments, the login status expiration time may be the expiration time of the user's login status. It will be appreciated that after the time of failure of the login status, the login status of the user is disabled and the user is unable to operate the software system of the device. For example, non-common information in IoT devices cannot be manipulated.
In some embodiments, the adjustment module 730 may determine the login status failure time based on the current login status failure time and the extended time. For example, the current registration state failure time is 03 minutes when 10 hours, and if the extension time is 1min, the registration state failure time is 04 minutes when 10 hours.
In some embodiments, the adjustment module 730 may obtain the current time; and determining the login state failure time based on the current time and the extension time. In some embodiments, the current time may refer to the time when the device screen is triggered to generate feature data reflecting the triggering behavior. In some embodiments, the current time may be a time corresponding to a preset time period before the current login state failure time. Still by way of example, taking the current login state failure time as 10 hours 03 minutes and the extension time as 1min as an example, if the preset time duration is 30s, the current time may be 10 hours 02 minutes 30 seconds, and at this time, the login state failure time is 10 hours 03 minutes 30 seconds.
And step 208, keeping the login state valid before the login state failure time.
In particular, this step 208 may be performed by the retention module 740.
In some embodiments, the retention module 740 may retain the login state valid until the time the login state fails. For example, still when the login status failure time is 10 hours 04 minutes, the keeping module 740 may keep the login status of the user valid for 10 hours and 10 hours 04 minutes.
As can be seen from the above description, the extended time is determined by the feature data in the embodiments of the present specification, so that the login failure time can be dynamically adjusted according to different behaviors of the user. The operation safety of the user in the process of interacting with the equipment screen is ensured, meanwhile, the user is prevented from carrying out identity authentication for many times, and the satisfaction degree of the user is improved.
Fig. 3 is a flow diagram illustrating a method of determining an extension time in accordance with some embodiments of the present description.
As shown in fig. 3, the embodiment of the present disclosure may input the feature data of the at least one focus point into a pre-trained delay prediction model to determine the extension time. In some embodiments, the characteristic data input to the at least one focus of the delay prediction model may include a focus coordinate value, or a focus coordinate value and its corresponding time information.
In some embodiments, the delay prediction model may be a pre-trained machine learning model. The trained delay prediction model can reflect the mapping relation between the characteristic data of the focus and the extension time.
In some embodiments, the time-delay prediction model may be trained based on a plurality of labeled sample feature data. In some embodiments, the tag may be a label for an extended time. For example, 10s, 30s or 1 min. Specifically, the parameters of the initial delay prediction model may be iteratively updated based on a plurality of sample feature data, so that the loss function of the model satisfies a predetermined condition, for example, the loss function converges, or the loss function value is smaller than a predetermined value. And finishing model training when the loss function meets the preset condition to obtain a trained delay prediction model.
Fig. 4 is another flow diagram illustrating a method of determining an extension time in accordance with some embodiments of the present description.
And 402, inputting the characteristic data of the at least one focus into a pre-trained behavior prediction model to obtain a behavior category.
In particular, this step 402 may be performed by the determination module 720.
In some embodiments, the feature data input to the at least one focus of the behavior prediction model may include focus coordinate values, or focus coordinate values and their corresponding time information. In some embodiments, the behavior prediction model may be a pre-trained machine learning model. The trained behavior prediction model may reflect a mapping between the feature data of the at least one focus and the behavior class. In some embodiments, the behavior categories may refer to operational behavior categories of the user on the screen of the device. Such as clicking, pressing, sliding, etc.
In some embodiments, the behavior prediction model may be trained based on a plurality of labeled sample feature data. In some embodiments, the tags may be labels for the behavior categories. Such as clicking, pressing, sliding, etc. Specifically, the parameters of the initial behavior prediction model may be iteratively updated based on a plurality of sample feature data, so that the loss function of the model satisfies a preset condition, for example, the loss function converges, or the loss function value is smaller than a preset value. And finishing model training when the loss function meets the preset condition to obtain a trained behavior prediction model.
In particular, this step 404 may be performed by the determination module 720.
In some embodiments, the duration mapping rule may refer to a mapping rule of a behavior category or a behavior event with an extended time. In some embodiments, the duration mapping rule may be set according to actual requirements. For example, click behavior is mapped to a 5s extension time. For another example, the sliding behavior may be considered to mean that the user is reading, and may have a mapping relationship with an extended time of 30 s.
Fig. 5 is another flow diagram illustrating a method of determining an extension time in accordance with some embodiments of the present description.
In particular, this step 402 may be performed by the determination module 720.
In some embodiments, the determining module 720 may obtain the behavior category through a preset behavior determination rule based on the feature data of the at least one focus. In some embodiments, the characteristic data of the at least one focus point includes a focus point coordinate value and its corresponding time information.
In some embodiments, the behavior determination rule may be set according to actual conditions. In some embodiments, the behavior determination rule may reflect a mapping of the feature data of the at least one focus point to the behavior category. That is, the mapping relationship between the change in at least one focus coordinate value and time and the behavior category may be reflected. For example, the feature data of at least one focus includes 5 focus coordinate values, the 5 focus coordinate values are concentrated in one coordinate region, and the 5 focus coordinate values correspond to the same time, then the behavior category mapped by the feature data is click. Similarly, if the 5 focus coordinate values are generated continuously for a continuous period of time, and the 5 focus coordinate values are close to each other, the behavior type mapped by the feature data is pressing. For another example, if the feature data of at least one focus includes 10 focus coordinate values, and the 10 focus coordinate values are different and the corresponding time information is also different, the behavior category corresponding to the feature data may be a sliding behavior.
In particular, this step 402 may be performed by the determination module 720.
For details of step 504, reference may be made to step 404 and its related description, which are not repeated herein.
FIG. 6 is another flow diagram of a method of determining an extension time in accordance with some embodiments of the present disclosure.
As described in fig. 6, embodiments of the present specification may also determine the extension time based on the behavioral event. Specifically, the extension time may be determined by a preset time length mapping rule based on the behavior event. In some embodiments, the duration mapping rule may refer to a mapping rule of a behavior category or a behavior event with an extended time. In some embodiments, the duration mapping rule may be set according to actual requirements. For example, a click event has a mapping relationship with an extended time of 5 s. For another example, the slip event is mapped to an extended time of 30 s. For specific details of the behavior event, reference may be made to step 202 and its related description, which are not described herein again.
FIG. 7 is a block diagram illustrating a system to maintain a logged on state in accordance with some embodiments of the present description. In some embodiments, the stay-logged-state system may be implemented by the processing device 110. As shown in FIG. 7, the stay logged on state system 700 may include an acquisition module 710, a determination module 720, an adjustment module 730, and a retention module 740.
The obtaining module 710 may be configured to obtain feature data reflecting a trigger behavior generated by the device screen being triggered. In some embodiments, the feature data reflecting the trigger behavior comprises feature data of at least one focus point generated as a result of the device screen being triggered; the characteristic data of the focus comprises a focus coordinate value or comprises the focus coordinate value and time information corresponding to the focus coordinate value. In some embodiments, the characterizing data reflecting the triggering behavior includes behavior events of a system package.
In some embodiments, the obtaining module 710 is further configured to obtain the feature data within a preset time period before the current login status failure time.
The determination module 720 may be configured to determine the time extension of the login status based on the characteristic data.
In some embodiments, the determining module 720 may be further configured to input the feature data of the at least one focus point into a pre-trained delay prediction model to determine the extension time.
In some embodiments, the determining module 720 may be further configured to input the feature data of the at least one focus point into a pre-trained behavior prediction model to obtain a behavior category; and determining the extension time through a preset time length mapping rule based on the behavior category.
In some embodiments, the determining module 720 may be further configured to obtain a behavior category according to a preset behavior determination rule based on the feature data of the at least one focus point; and determining the extension time through a preset time length mapping rule based on the behavior category.
In some embodiments, the determining module 720 may be further configured to determine the extended time according to a preset time mapping rule based on the behavior event.
The adjusting module 730 may be configured to adjust the login status failure time based on the extended time.
In some embodiments, the adjustment module 730 may be further configured to determine the login status failure time based on the current login status failure time and the extended time.
In some embodiments, the adjusting module 730 may be further configured to obtain a current time; determining the login state failure time based on the current time and the extension time; or acquiring the moment of the characteristic data which is generated by triggering the equipment screen and reflects the triggering behavior; determining the login state failure time based on the time and the extension time.
The maintaining module 740 may be configured to maintain the login status valid before the time when the login status fails.
It should be understood that the system and its modules shown in FIG. 7 may be implemented in a variety of ways. For example, in some embodiments, the system and its modules may be implemented in hardware, software, or a combination of software and hardware. Wherein the hardware portion may be implemented using dedicated logic; the software portions may be stored in a memory for execution by a suitable instruction execution system, such as a microprocessor or specially designed hardware. Those skilled in the art will appreciate that the methods and systems described above may be implemented using computer executable instructions and/or embodied in processor control code, such code being provided, for example, on a carrier medium such as a diskette, CD-or DVD-ROM, a programmable memory such as read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The system and its modules in this specification may be implemented not only by hardware circuits such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., but also by software executed by various types of processors, for example, or by a combination of the above hardware circuits and software (e.g., firmware).
It should be noted that the above description of the keep-alive system 700 and its modules is for convenience of description only and should not limit the scope of the present disclosure to the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. For example, the obtaining module 710, the determining module 720, the adjusting module 730, and the maintaining module 740 disclosed in fig. 7 may be different modules in one system, or may be a module that implements the functions of the two modules. For another example, the modules in the login-holding system 700 may share one storage module, and each module may have a storage module. Such variations are within the scope of the present disclosure.
The embodiment of the specification also provides a device for maintaining the login state, which comprises a processor. The processor is used in the aforementioned method of maintaining a login status. The method may include: in the user login state: acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen; determining an extension time of the login state based on the characteristic data; adjusting the login state failure time based on the extension time; and keeping the login state valid before the login state failure moment.
The embodiment of the specification also provides a computer readable storage medium. The storage medium stores computer instructions, and after the computer reads the computer instructions in the storage medium, the computer realizes the method for keeping the login state. The method may include: in the user login state: acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen; determining an extension time of the login state based on the characteristic data; adjusting the login state failure time based on the extension time; and keeping the login state valid before the login state failure moment.
The beneficial effects that may be brought by the embodiments of the present description include, but are not limited to: the extension time is determined through the characteristic data, so that the failure time of the login state can be dynamically adjusted according to different behaviors of the user. The operation safety of the user in the process of interacting with the equipment screen is ensured, meanwhile, the user is prevented from carrying out identity authentication for many times, and the satisfaction degree of the user is improved. It is to be noted that different embodiments may produce different advantages, and in different embodiments, any one or combination of the above advantages may be produced, or any other advantages may be obtained.
Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing detailed disclosure is to be regarded as illustrative only and not as limiting the present specification. Various modifications, improvements and adaptations to the present description may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present specification and thus fall within the spirit and scope of the exemplary embodiments of the present specification.
Also, the description uses specific words to describe embodiments of the description. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the specification is included. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the specification may be combined as appropriate.
Moreover, those skilled in the art will appreciate that aspects of the present description may be illustrated and described in terms of several patentable species or situations, including any new and useful combination of processes, machines, manufacture, or materials, or any new and useful improvement thereof. Accordingly, aspects of this description may be performed entirely by hardware, entirely by software (including firmware, resident software, micro-code, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the present description may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media.
The computer storage medium may comprise a propagated data signal with the computer program code embodied therewith, for example, on baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, etc., or any suitable combination. A computer storage medium may be any computer-readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code located on a computer storage medium may be propagated over any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or any combination of the preceding.
Computer program code required for operation of portions of the present description may be written in any one or more programming languages, including AN object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB.NET, Python, and the like, a conventional procedural programming language such as C, Visual Basic, Fortran2003, Perl, COBO L, PHP, ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages, and the like.
Additionally, the order in which the elements and sequences of the process are recited in the specification, the use of alphanumeric characters, or other designations, is not intended to limit the order in which the processes and methods of the specification occur, unless otherwise specified in the claims. While various presently contemplated embodiments of the invention have been discussed in the foregoing disclosure by way of example, it is to be understood that such detail is solely for that purpose and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements that are within the spirit and scope of the embodiments herein. For example, although the system components described above may be implemented by hardware devices, they may also be implemented by software-only solutions, such as installing the described system on an existing processing device or mobile device.
Similarly, it should be noted that in the preceding description of embodiments of the present specification, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to imply that more features than are expressly recited in a claim. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.
Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.
For each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., cited in this specification, the entire contents of each are hereby incorporated by reference into this specification. Except where the application history document does not conform to or conflict with the contents of the present specification, it is to be understood that the application history document, as used herein in the present specification or appended claims, is intended to define the broadest scope of the present specification (whether presently or later in the specification) rather than the broadest scope of the present specification. It is to be understood that the descriptions, definitions and/or uses of terms in the accompanying materials of this specification shall control if they are inconsistent or contrary to the descriptions and/or uses of terms in this specification.
Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present disclosure. Other variations are also possible within the scope of the present description. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the specification can be considered consistent with the teachings of the specification. Accordingly, the embodiments of the present description are not limited to only those embodiments explicitly described and depicted herein.
Claims (21)
1. A method of maintaining a login state, comprising, in a user login state:
acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen;
determining an extension time of the login state based on the characteristic data;
adjusting the login state failure time based on the extension time;
and keeping the login state valid before the login state failure moment.
2. The method of claim 1, wherein the obtaining of feature data reflecting triggering behavior generated as a result of a device screen being triggered comprises:
and acquiring the characteristic data within a preset time before the failure moment of the current login state.
3. The method of claim 1, wherein the feature data reflecting triggering behavior comprises feature data of at least one focus point generated as a result of a device screen being triggered; the characteristic data of the focus comprises a focus coordinate value or comprises the focus coordinate value and time information corresponding to the focus coordinate value.
4. The method of claim 3, said determining the extension time of the login status based on the characteristic data comprising:
and inputting the characteristic data of the at least one focus into a pre-trained delay prediction model, and determining the extension time.
5. The method of claim 3, said determining the extension time of the login status based on the characteristic data comprising:
inputting the characteristic data of the at least one focus into a pre-trained behavior prediction model to obtain a behavior category;
and determining the extension time through a preset time length mapping rule based on the behavior category.
6. The method of claim 3, said determining the extension time of the login status based on the characteristic data comprising:
obtaining a behavior category through a preset behavior determination rule based on the feature data of the at least one focus;
and determining the extension time through a preset time length mapping rule based on the behavior category.
7. The method of claim 1, wherein the characterization data reflecting triggering behavior comprises behavior events of a system package.
8. The method of claim 7, said determining the extension time of the login status based on the characteristic data comprising:
and determining the extension time through a preset time length mapping rule based on the behavior event.
9. The method of claim 1, wherein adjusting the login status failure time based on the extended time comprises:
and determining the login state failure time based on the current login state failure time and the extension time.
10. The method of claim 1, wherein adjusting the login status failure time based on the extended time comprises:
acquiring the current moment;
determining the login state failure time based on the current time and the extension time;
alternatively, the first and second electrodes may be,
acquiring the moment of generating characteristic data reflecting triggering behaviors when the device screen is triggered;
determining the login state failure time based on the time and the extension time.
11. A system for maintaining a login status, comprising: in the user login state:
the device comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring characteristic data which reflects triggering behaviors and is generated by triggering a device screen;
a determination module for determining the time extension of the login status based on the characteristic data;
the adjusting module is used for adjusting the failure time of the login state based on the extension time;
and the maintaining module is used for maintaining the login state to be effective before the login state failure moment.
12. The system of claim 11, the acquisition module further to:
and acquiring the characteristic data within a preset time before the failure moment of the current login state.
13. The system of claim 11, the feature data reflecting triggering behavior comprising feature data of at least one focus point resulting from a device screen being triggered; the characteristic data of the focus comprises a focus coordinate value or comprises the focus coordinate value and time information corresponding to the focus coordinate value.
14. The system of claim 13, the determination module further to:
and inputting the characteristic data of the at least one focus into a pre-trained delay prediction model, and determining the extension time.
15. The system of claim 13, the determination module further to:
inputting the characteristic data of the at least one focus into a pre-trained behavior prediction model to obtain a behavior category;
and determining the extension time through a preset time length mapping rule based on the behavior category.
16. The system of claim 13, the determination module further to:
obtaining a behavior category through a preset behavior determination rule based on the feature data of the at least one focus;
and determining the extension time through a preset time length mapping rule based on the behavior category.
17. The system of claim 11, wherein the characterization data reflecting triggering behavior comprises behavior events of a system package.
18. The system of claim 17, the determination module further to:
and determining the extension time through a preset time length mapping rule based on the behavior event.
19. The system of claim 11, the adjustment module further to:
and determining the login state failure time based on the current login state failure time and the extension time.
20. The system of claim 11, the adjustment module further to:
acquiring the current moment;
determining the login state failure time based on the current time and the extension time;
alternatively, the first and second electrodes may be,
acquiring the moment of generating characteristic data reflecting triggering behaviors when the device screen is triggered;
determining the login state failure time based on the time and the extension time.
21. An apparatus for maintaining a login status, comprising a processor configured to perform the method of any one of claims 1 to 10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310879833.9A CN116680676A (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
| CN202010302620.6A CN111460411B (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010302620.6A CN111460411B (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310879833.9A Division CN116680676A (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111460411A true CN111460411A (en) | 2020-07-28 |
| CN111460411B CN111460411B (en) | 2023-08-04 |
Family
ID=71684549
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010302620.6A Active CN111460411B (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
| CN202310879833.9A Pending CN116680676A (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310879833.9A Pending CN116680676A (en) | 2020-04-17 | 2020-04-17 | Method and system for keeping login state |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN111460411B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593594A (en) * | 2012-01-09 | 2014-02-19 | 明智视觉有限公司 | System and method for providing secure access to an electronic device using facial biometric identification and screen gesture |
| CN108604265A (en) * | 2016-09-24 | 2018-09-28 | 华为技术有限公司 | The method and terminal device of outline management application program usage time |
| CN108632301A (en) * | 2017-03-15 | 2018-10-09 | 腾讯科技（深圳）有限公司 | A kind of log in renews processing method and terminal after state fails |
| CN108900559A (en) * | 2018-09-26 | 2018-11-27 | 平安普惠企业管理有限公司 | Management method, device, computer equipment and the storage medium of logging on authentication |
| CN109802941A (en) * | 2018-12-14 | 2019-05-24 | 平安科技（深圳）有限公司 | A kind of login validation method, device, storage medium and server |
| CN109952753A (en) * | 2016-10-25 | 2019-06-28 | 苹果公司 | For managing the user interface of the access to the voucher used in operation |
| CN109995755A (en) * | 2019-02-20 | 2019-07-09 | 深圳点猫科技有限公司 | A kind of control method and device of the logging state based on small routine framework |
| CN110166529A (en) * | 2019-04-16 | 2019-08-23 | 平安普惠企业管理有限公司 | It keeps logging in state method, apparatus, equipment and storage medium |
| CN110381078A (en) * | 2019-07-29 | 2019-10-25 | 迈普通信技术股份有限公司 | Determination method, apparatus, electronic equipment and the storage medium that token renews |
| CN110417719A (en) * | 2019-02-26 | 2019-11-05 | 腾讯科技（深圳）有限公司 | It logs in state and renews method, login method, device, server and terminal |
-
2020
- 2020-04-17 CN CN202010302620.6A patent/CN111460411B/en active Active
- 2020-04-17 CN CN202310879833.9A patent/CN116680676A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593594A (en) * | 2012-01-09 | 2014-02-19 | 明智视觉有限公司 | System and method for providing secure access to an electronic device using facial biometric identification and screen gesture |
| CN108604265A (en) * | 2016-09-24 | 2018-09-28 | 华为技术有限公司 | The method and terminal device of outline management application program usage time |
| CN109952753A (en) * | 2016-10-25 | 2019-06-28 | 苹果公司 | For managing the user interface of the access to the voucher used in operation |
| CN108632301A (en) * | 2017-03-15 | 2018-10-09 | 腾讯科技（深圳）有限公司 | A kind of log in renews processing method and terminal after state fails |
| CN108900559A (en) * | 2018-09-26 | 2018-11-27 | 平安普惠企业管理有限公司 | Management method, device, computer equipment and the storage medium of logging on authentication |
| CN109802941A (en) * | 2018-12-14 | 2019-05-24 | 平安科技（深圳）有限公司 | A kind of login validation method, device, storage medium and server |
| CN109995755A (en) * | 2019-02-20 | 2019-07-09 | 深圳点猫科技有限公司 | A kind of control method and device of the logging state based on small routine framework |
| CN110417719A (en) * | 2019-02-26 | 2019-11-05 | 腾讯科技（深圳）有限公司 | It logs in state and renews method, login method, device, server and terminal |
| CN110166529A (en) * | 2019-04-16 | 2019-08-23 | 平安普惠企业管理有限公司 | It keeps logging in state method, apparatus, equipment and storage medium |
| CN110381078A (en) * | 2019-07-29 | 2019-10-25 | 迈普通信技术股份有限公司 | Determination method, apparatus, electronic equipment and the storage medium that token renews |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111460411B (en) | 2023-08-04 |
| CN116680676A (en) | 2023-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10417396B2 (en) | System and methods for provisioning and monitoring licensing of applications or extensions to applications on a multi-tenant platform | |
| EP3190765A1 (en) | Sensitive information processing method, device, server and security determination system | |
| US20180196875A1 (en) | Determining repeat website users via browser uniqueness tracking | |
| US11777921B2 (en) | Systems and methods for controlling personal information on online services | |
| CN113079164B (en) | Remote control method and device for bastion machine resources, storage medium and terminal equipment | |
| US11488149B2 (en) | Management of credentials and authorizations for transactions | |
| CA3066451C (en) | Systems and methods for authenticating user information | |
| US20220284072A1 (en) | Methods and systems for providing authenticated one-click access to a customized user interaction-specific web page | |
| US20240020459A1 (en) | Using machine learning to predict performance of secure documents | |
| CN111460411A (en) | Method and system for keeping login state | |
| US20220358250A1 (en) | Data processing systems and methods for detecting tools for the automatic blocking of consent requests | |
| CN111385313B (en) | Method and system for verifying object request validity | |
| US9824235B2 (en) | Web session security techniques | |
| US20220269747A1 (en) | Qr code access restriction without geolocation knowledge | |
| US20240015158A1 (en) | Systems and methods for granting account access to a guest contact | |
| CN112149106B (en) | Login method, device, equipment and medium of enterprise private applet | |
| US20230067897A1 (en) | Automatic detection of proxy-based phishing sites | |
| CN117728987A (en) | Control method, device and system based on browser and fort equipment | |
| CN113706155A (en) | Network financial anti-fraud method, apparatus, device, medium, and program product | |
| CN115604041A (en) | Security agent method, system, device, computer equipment and storage medium | |
| CN114386017A (en) | Authentication mode configuration method, device, equipment and medium | |
| CN114490747A (en) | Service processing request control method and device, electronic equipment and storage medium | |
| CN117853246A (en) | Policy processing method, policy processing device, computer equipment and storage medium | |
| CN117876087A (en) | Data processing method, device, equipment and storage medium | |
| CN118093958A (en) | Control method, device, equipment, storage medium and program product for data query |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |