CN111460411B

CN111460411B - Method and system for keeping login state

Info

Publication number: CN111460411B
Application number: CN202010302620.6A
Authority: CN
Inventors: 赵鹏飞
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-04-17
Filing date: 2020-04-17
Publication date: 2023-08-04
Anticipated expiration: 2040-04-17
Also published as: CN116680676A; CN111460411A

Abstract

The embodiment of the specification discloses a method and a system for keeping a login state, wherein the method comprises the following steps of: acquiring feature data reflecting trigger behaviors generated due to the triggering of a device screen; determining an extended time of the login state based on the feature data; adjusting the login state failure moment based on the extension time; and keeping the login state valid before the login state failure moment.

Description

Method and system for keeping login state

Technical Field

Embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method and a system for maintaining a login state.

Background

A login state (or log-in state) may refer to a state in which a software system is logged in by a user, which may be used to prove the identity of the user as to its uniqueness and legitimacy, thereby enabling the current user to operate the software system. Typically, the login state will have a dead time, and the user will only be able to maintain the login state until that time, with the right to operate the software system. Therefore, the application provides a method and a system for keeping a login state, which can dynamically adjust the failure time of the login state.

Disclosure of Invention

One aspect of the embodiments of the present disclosure provides a method for maintaining a login state, including: acquiring feature data reflecting trigger behaviors generated due to the triggering of a device screen; determining an extended time of the login state based on the feature data; adjusting the login state failure moment based on the extension time; and keeping the login state valid before the login state failure moment.

One aspect of the embodiments of the present specification provides a system for maintaining a login state, comprising: comprising the following steps: in the user login state: the acquisition module is used for acquiring characteristic data reflecting the triggering behavior generated by triggering the device screen; a determining module, configured to determine an extension time of the login state based on the feature data; the adjustment module is used for adjusting the invalid moment 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 embodiments of the present disclosure provides an apparatus for maintaining a login state, including a processor for performing the method for maintaining a login state as described above.

An aspect of the embodiments of the present specification provides a computer-readable storage medium storing computer instructions that, when read by a computer, perform a method of maintaining a login state as described above.

Drawings

The present specification will be further described by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:

FIG. 1 is a schematic illustration of an application scenario of a keep-in-state system according to some embodiments of the present description;

FIG. 2 is a flow chart of a method of maintaining a login state, shown in accordance with some embodiments of the present description;

FIG. 3 is a flow chart of a method of determining an extended time, shown in accordance with some embodiments of the present description;

FIG. 4 is another flow chart of a method of determining an extended time according to some embodiments of the present description;

FIG. 5 is another flow chart of a method of determining an extended time according to some embodiments of the present description;

FIG. 6 is another flow chart of a method of determining an extended time according to some embodiments of the present description;

FIG. 7 is a block diagram of a keep-in-state system according to some embodiments of the present description.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings that are required to be used in the description of the embodiments will be briefly described below. It is apparent that the drawings in the following description are only some examples or embodiments of the present specification, and it is possible for those of ordinary skill in the art to apply the present specification to other similar situations according to the drawings without inventive effort. Unless otherwise apparent from the context of the language or otherwise specified, like reference numerals in the figures refer to like structures or operations.

It should be appreciated that "system," "apparatus," "unit," and/or "module" as used in this specification is a method for distinguishing between different components, elements, parts, portions, or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

As used in this specification and the claims, the terms "a," "an," "the," and/or "the" are not specific to a singular, but may include a plurality, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus.

A flowchart is used in this specification to describe the operations performed by the system according to embodiments of the present specification. It should be appreciated that the preceding or following operations are not necessarily performed in order precisely. Rather, the steps may be processed in reverse order or simultaneously. Also, other operations may be added to or removed from these processes.

Fig. 1 is a schematic view of an application scenario of a keep-in-state system according to some embodiments of the present description.

As shown in fig. 1, the stay logged in state system 100 may include a terminal device 110, a network 120, and a server 130.

Terminal device 110 can be configured to process information and/or data associated with maintaining a logged-on state to perform one or more of the functions disclosed in this specification. In some embodiments, the terminal device 110 may be a public device that provides query services and/or data processing services to the public, such as an internet of things device (IoT device) 110-1. Exemplary IoT devices 110-1 may include, but are not limited to, face vending machines, self-service cash registers, banking personal business terminals, and the like, or any combination thereof. After the user has completed logging on to the terminal device 110, the data services provided by the device can be used. In some embodiments, the terminal device 110 may be configured to obtain feature data reflecting the trigger behavior due to the device screen being triggered. In some embodiments, terminal device 110 may determine the extended time of the login state based on the feature data. In some embodiments, terminal device 110 may adjust the login status expiration time based on the extended time. In some embodiments, terminal device 110 may remain in the logged-on state valid until the time of the logged-on state failure. In some embodiments, terminal device 110 may include one or more processing engines (e.g., single core processing engines or multi-core processors). By way of example only, the processing device 110 may include one or more combinations of a central processing unit (cpu), an Application Specific Integrated Circuit (ASIC), an application specific instruction set processor (ASIP), an image processor (GPU), a physical arithmetic processing unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller unit, a Reduced Instruction Set Computer (RISC), a microprocessor, and the like.

In some embodiments, terminal device 110 may also be a portable device with data acquisition, storage, and/or transmission capabilities, such as tablet 110-2, notebook 110-3, smart phone 110-4, etc., or any combination thereof. In some embodiments, the terminal device 110 may interact with the server 130 via a network, and after a user logs in on to the terminal device 110, the data service of the server 130 may be used by the terminal device 110. At this time, the terminal device 110 may place a part of the information and/or data associated with maintaining the login state on the server 130 to process, thereby implementing the related function of maintaining the login state. For example, the terminal device 110 may transmit the acquired data to the 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 reflecting the trigger behavior. It will be appreciated that the terminal device 110 may implement the function of maintaining the user login state locally, or may implement the function in conjunction with the server 130.

The network 120 may facilitate the exchange of information and/or data. In some embodiments, one or more components of the keep-alive system 100 (e.g., terminal device 110, server 130) may communicate information over the network 120 to other components of the keep-alive system 100. For example, the terminal device 110 may obtain data provided by the server 130 through the network 120 to perform a data service function (such as data query or data change) for a user. For another example, the terminal device 110 may send, to the server 130, feature data reflecting the trigger behavior generated by the user on the screen of the terminal device 100 through the network 120, and receive, through the network 120, an extended time or a login status failure time returned by the server 130. In some embodiments, network 120 may be any form of wired or wireless network, or any combination thereof. By way of example only, the network 120 may be one or more combinations of a wired network, a fiber optic network, a telecommunications network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth network, and the like.

Server 130 may be used to process information and/or data related to data service requests and/or maintaining a logged on state. For example, the server 130 may provide corresponding data in response to a data service request from the terminal device 110, and return the corresponding data to the terminal device 110. For another example, the server 130 may receive the feature data reflecting the trigger behavior, calculate the extension time or the login state failure time, and return to the terminal device 110, so that the terminal device 110 may maintain the login state before the login state failure time. In some embodiments, server 130 may be local or remote. For example, server 130 may connect terminal device 110 locally at terminal device 110 to obtain information and/or data it sends. For another example, server 130 may receive information and/or data transmitted by terminal device 110 remotely via network 120. In some embodiments, server 130 may be implemented on a cloud platform. For example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-layer cloud, or the like, or any combination thereof.

The technical scheme disclosed by the embodiment of the specification can be applied to a scene that a user interacts with a server through terminal equipment and uses online services provided by the server. For example, a user uses an online payment service provided by mobile payment software through a mobile phone. For another example, the user, through the IoT device: the vending machine uses online shopping services 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 case where a user directly interacts with a terminal device, where the terminal device may integrate all functions of a server locally, without remotely connecting a background server through a network.

As an example, when a user uses an IoT device, the user needs to log on to the device's software system (e.g., swipe face login, swipe code login, account login, etc.) to perform authentication to obtain a logged-on state, thereby being able to operate the non-shared information of the IoT device. Generally, ioT devices are public devices, provide data services for the public, and in order to prevent a previous user from logging out in time after using the devices, and further cause information security incidents such as privacy data disclosure, the login state needs to set login valid time. It can be appreciated that after this time, the user's login status fails and is unable to operate the IoT device's corresponding non-common information. In some embodiments, the validity time of the login state is fixed. This approach may have the following characteristics: the effective time is set too long, the risk that the login state of the current user is effective but the operation equipment is not the current user exists, personal information of the user is leaked, and potential safety hazards exist; the effective time is set too short, so that the user logs 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 moment of the login state by performing corresponding processing on feature data generated on a device screen. The technical scheme disclosed in the specification is explained in detail below with reference to the attached drawings.

Fig. 2 is a flow chart of a method of maintaining a login state, shown in accordance with some embodiments of the present description.

Step 202, feature data reflecting trigger behavior generated due to the device screen being triggered is acquired.

Specifically, this step may be performed by the acquisition module 710.

In some embodiments, the user login state may refer to a state that results after a user has successfully logged on to the software system of the device, or referred to as a login state. In some embodiments, the device may be a terminal that provides online services to the user. For example, a self-service cash register, a face vending machine, a smart phone, or the like. It will be appreciated that in the user login state, the user may interact with the device to use the online service provided by the device. For example, a self-service payment service provided by a self-service cash register is used.

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 resulting from the device screen being triggered. The focus may be a location on the screen of the device that is triggered by the user, and 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 of 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 area 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 device screen is triggered, the user is in direct contact with the device screen, and the abscissa of the focus is within the numerical range [0, b ], and the ordinate is within the numerical range [0, a ].

In some embodiments, the characteristic data of the focus may include a focus coordinate value, or include a focus coordinate value and its corresponding time information. In some embodiments, the time information corresponding to the focus coordinate value may refer to a time when the focus coordinate value is generated. In some embodiments, the feature data of the focus may be directly acquired through a system bottom layer interface of the terminal device.

In some embodiments, some operating systems may further process the focus data, for example, determine the corresponding operation behavior based on the track of the focus data, and package the result obtained by the processing into a form more oriented to an application layer, so that the developer can directly call the result, and program development resources are saved. Thus, in some embodiments, the feature 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, behavior events may refer to system-encapsulated events that characterize a class of behavior that a user operates on a device screen. For example, a click behavior event that characterizes a user click operation. For another example, a press behavior event characterizing a user press operation.

In some embodiments, the obtaining module 710 may obtain the feature data during a pre-set time period before the current login state failure time. In some embodiments, the preset duration may be specifically set according to actual requirements. For example, 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 expiration time may be the sum of the login state generation time and the login state preset valid time. In some embodiments, the preset valid time may be specifically set according to actual requirements. For example, 3min, 5min, 10min, etc. It will be appreciated that the initial login state failure time is the time when the login state is not delayed. For example, if the user logs in the loT device entirely at 10 hours, the preset valid time of the login state is 3min, and the failure time of the current login state is: and at 10 hours 03 minutes.

In some embodiments, the current login failure time may be a login state failure time adjusted based on the extended time. It can be appreciated that the current login failure time is a time when the login state is delayed. For the adjusted login status invalidation time, refer to step 206 and the related description thereof, which are not described herein.

In some embodiments, the acquisition module 710 may acquire the feature data from the user terminal 130. In some embodiments, the acquisition module 710 may also acquire the feature data by reading the stored data, invoking a related interface, or otherwise.

Step 204, determining an extension time of the login state based on the characteristic data.

Specifically, this step may be performed by the determination module 720.

In some embodiments, the determination module 720 may determine the extended time of the login state in different ways based on different characteristic data. For example, a delay predictive model or a behavior predictive model may be employed to determine an extended time of the login state based on the focus coordinate values, or the focus coordinate values and their corresponding time information. Specific details regarding the determination of the extension time may be found in fig. 3 and 4, and are not described here. For another example, based on the focus coordinate values and their corresponding time information, a preset behavior determination rule may be used to determine the extended time of the login state. Specific details regarding the determination of the extension time may be found in fig. 5 and are not described in detail herein.

And step 206, adjusting the login state failure moment based on the extension time.

Specifically, this step 206 may be performed by the adjustment module 730.

In some embodiments, the login state expiration time may be an expiration time of the user's login state. It will be appreciated that after this login state expiration time, the user's login state expires and the user is unable to operate the software system of the device. For example, non-shared information in IoT devices cannot be manipulated.

In some embodiments, the adjustment module 730 may determine the login state expiration time based on the current login state expiration time and the extension time. For example, still taking the above-mentioned case that the current login state invalidation time is 10 hours 03 as an example, if the extension time is 1min, the login state invalidation time is 10 hours 04 as an example.

In some embodiments, the adjustment module 730 may obtain the current time; determining the login state failure moment based on the current moment and the extension time. In some embodiments, the current time may refer to the time of day that the device screen is triggered to generate feature data reflecting the triggering behavior. In some embodiments, the current time may refer to a time corresponding to a pre-set time length of the current login state failure time. For example, still taking the above-mentioned current login state failure time as 10 hours 03 minutes and the extension time as 1 minute as an example, if the preset time length 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.

Step 208, keeping the login state valid until the login state failure time.

Specifically, this step 208 may be performed by the retention module 740.

In some embodiments, the retention module 740 may keep the login state valid until the login state failure time. For example, still with the login status expiration time of 10 hours 04 points, the holding module 740 may keep the login status of the user valid between 10 hours and 10 hours 04 points.

As can be seen from the above description, the embodiment of the present specification determines the extension time through the feature data, so that the login state failure time can be dynamically adjusted for different behaviors of the user. The operation safety of the user in the interaction process with the equipment screen is ensured, the user is prevented from carrying out identity verification for many times, and the satisfaction degree of the user is improved.

FIG. 3 is a flow chart of a method of determining an extended time, shown 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 into a pre-trained delay prediction model to determine the extended time. In some embodiments, the feature data of at least one focus input to 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 delay prediction model may be trained based on a plurality of tagged sample feature data. In some embodiments, the tag may be an extended time annotation. For example 10s, 30s or 1min. Specifically, the parameters of the initial delay prediction model may be iteratively updated based on the plurality of sample feature data so that the loss function of the model satisfies a preset condition, e.g., the loss function converges, or the loss function value is less than a preset value. And when the loss function meets the preset condition, model training is completed, and a trained delay prediction model is obtained.

FIG. 4 is another flow chart of a method of determining an extended time, shown in accordance with some embodiments of the present description.

And step 402, inputting the characteristic data of the at least one focus to a pre-trained behavior prediction model to obtain a behavior class.

Specifically, this step 402 may be performed by the determination module 720.

In some embodiments, the feature data of at least one focus input to the behavior prediction model may include a focus coordinate value, or a focus coordinate value and its 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 relationship between the feature data of the at least one focus and the behavior class. In some embodiments, the behavior categories may refer to the operational behavior categories of the user on the device screen. For example, clicking, pressing or sliding, etc.

In some embodiments, the behavior prediction model may be trained based on a plurality of tagged sample feature data. In some embodiments, the tag may be an annotation of a category of behavior. For example, clicking, pressing or sliding, etc. Specifically, the parameters of the initial behavior prediction model may be iteratively updated based on the 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 when the loss function meets the preset condition, model training is completed, and a trained behavior prediction model is obtained.

Step 404, determining the extension time through a preset duration mapping rule based on the behavior category.

Specifically, this step 404 may be performed by the determination module 720.

In some embodiments, the duration mapping rules may refer to mapping rules of behavior categories or behavior events to extended times. In some embodiments, the duration mapping rules may be set according to actual requirements. For example, the click behavior has a mapping relationship with an extended time of 5 s. For another example, it can be considered that the sliding behavior means that the user is reading, and can have a mapping relationship with an extended time of 30 s.

FIG. 5 is another flow chart of a method of determining an extended time, shown in accordance with some embodiments of the present description.

Step 502, obtaining a behavior category through a preset behavior determination rule based on the characteristic data of the at least one focus.

Specifically, 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 includes a focus coordinate value and corresponding time information thereof.

In some embodiments, the behavior determination rules may be set according to actual conditions. In some embodiments, the behavior determination rule may reflect a mapping of feature data of at least one focus to behavior categories. That is, a 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 a coordinate area, and the 5 focus coordinate values correspond to the same moment, and the behavior category mapped by the feature data is clicking. Similarly, if the 5 focus coordinate values are generated continuously over a continuous period of time and the 5 focus coordinate values are very close, the behavior class of the feature data map is press. For another example, 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, and the behavior category corresponding to the feature data may be a sliding.

Step 504, determining the extension time through a preset duration mapping rule based on the behavior category.

Specifically, this step 402 may be performed by the determination module 720.

For specific details regarding step 504, reference may be made to step 404 and the description thereof, which are not repeated herein.

FIG. 6 is another flow chart of a method of determining an extended time according to some embodiments of the present description.

As illustrated in FIG. 6, embodiments of the present description may also determine an extension time based on the behavioral event. Specifically, the extension time may be determined based on the behavior event through a preset duration mapping rule. In some embodiments, the duration mapping rules may refer to mapping rules of behavior categories or behavior events to extended times. In some embodiments, the duration mapping rules 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 sliding event has a mapping relationship with an extended time of 30 s. Specific details regarding the behavior event can be found in step 202 and the related description thereof, and are not repeated here.

FIG. 7 is a block diagram of a keep-in-state system according to some embodiments of the present description. In some embodiments, the keep-in-state system may be implemented by the processing device 110. As shown in fig. 7, the keep-logged-on status system 700 may include an acquisition module 710, a determination module 720, an adjustment module 730, and a retention module 740.

The acquisition module 710 may be configured to acquire feature data reflecting the trigger behavior due to the device screen being triggered. In some embodiments, the feature data reflecting the triggering behavior includes feature data of at least one focus resulting from the device screen being triggered; the characteristic data of the focus comprises a focus coordinate value or comprises the focus coordinate value and corresponding time information. In some embodiments, the characteristic data reflecting the triggering behavior comprises behavior events of a system package.

In some embodiments, the obtaining module 710 is further configured to obtain the feature data during a pre-preset time period before a failure time of the current login status.

The determining module 720 may be configured to determine an extended time of the login status based on the feature data.

In some embodiments, the determining module 720 may be further configured to input the characteristic data of the at least one focus to a pre-trained delay prediction model to determine the extended time.

In some embodiments, the determining module 720 may be further configured to input the feature data of the at least one focus to a pre-trained behavior prediction model to obtain a behavior class; and determining the extension time through a preset duration mapping rule based on the behavior category.

In some embodiments, the determining module 720 may be further configured to obtain a behavior category through a preset behavior determining rule based on the feature data of the at least one focus; and determining the extension time through a preset duration mapping rule based on the behavior category.

In some embodiments, the determining module 720 may be further configured to determine the extended time based on the behavior event through a preset duration mapping rule.

The adjustment module 730 may be configured to adjust the login status expiration time based on the extended time.

In some embodiments, the adjustment module 730 may be further configured to determine the login status expiration time based on the current login status expiration time and the extended time.

In some embodiments, the adjustment module 730 may be further configured to obtain the current time; determining the login state failure moment based on the current moment and the extension time; or, acquiring the moment of feature data reflecting the triggering behavior generated by triggering the device screen; and determining the login state failure moment based on the moment and the extension time.

The holding module 740 may be configured to hold the login state valid until the login state failure time.

It should be appreciated that the system shown in fig. 7 and its modules 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 then be stored in a memory and executed by a suitable instruction execution system, such as a microprocessor or special purpose design 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 as provided on a carrier medium such as a magnetic disk, 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 of the present specification and its modules may be implemented not only with hardware circuits such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., but also with software executed by various types of processors, for example, and with a combination of the above hardware circuits and software (e.g., firmware).

It should be noted that the description of the keep-alive system 700 and its modules is for convenience only and is not intended to limit the present disclosure to the scope of the illustrated embodiments. It will be appreciated by those skilled in the art that, given the principles of the system, various modules may be combined arbitrarily or a subsystem may be constructed in connection with other modules without departing from such principles. For example, the acquisition module 710, the determination module 720, the adjustment module 730, and the holding module 740 disclosed in fig. 7 may be different modules in one system, or may be one module to implement the functions of the two modules. For another example, each module in the keep-alive system 700 may share one storage module, or each module may have a respective storage module. Such variations are within the scope of the present description.

The embodiment of the specification also provides a device for keeping the login state, which comprises a processor. The processor is used for the method for keeping the login state. The method may include: in the user login state: acquiring feature data reflecting trigger behaviors generated due to the triggering of a device screen; determining an extended time of the login state based on the feature data; adjusting the login state failure moment based on the extension time; and keeping the login state valid before the login state failure moment.

The present description also provides a computer-readable storage medium. The storage medium stores computer instructions, and when 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 feature data reflecting trigger behaviors generated due to the triggering of a device screen; determining an extended time of the login state based on the feature data; adjusting the login state failure moment based on the extension time; and keeping the login state valid before the login state failure moment.

Possible benefits of embodiments of the present description include, but are not limited to: the extension time is determined through the feature data, so that the login state failure moment can be dynamically adjusted according to different behaviors of the user. The operation safety of the user in the interaction process with the equipment screen is ensured, the user is prevented from carrying out identity verification for many times, and the satisfaction degree of the user is improved. It should be noted that, the advantages that may be generated by different embodiments may be different, and in different embodiments, the advantages that may be generated may be any one or a combination of several of the above, or any other possible advantages that may be obtained.

While the basic concepts have been described above, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations to the present disclosure may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this specification, and therefore, such modifications, improvements, and modifications are intended to be included within the spirit and scope of the exemplary embodiments of the present invention.

Meanwhile, the specification uses specific words to describe the embodiments of the specification. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present description. Thus, it should be emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this specification are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present description may be combined as suitable.

Furthermore, those skilled in the art will appreciate that the various aspects of the specification can be illustrated and described in terms of several patentable categories or circumstances, including any novel and useful procedures, machines, products, or materials, or any novel and useful modifications thereof. Accordingly, aspects of the present 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 a "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the specification may take the form of a computer product, comprising computer-readable program code, embodied in one or more computer-readable media.

The computer storage medium may contain a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take on a variety of forms, including electro-magnetic, optical, etc., or any suitable combination thereof. 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 through any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or a combination of any of the foregoing.

The computer program code necessary 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 programming language such as C language, visual Basic, fortran2003, perl, COBOL2002, PHP, ABAP, a dynamic programming language such as Python, ruby and Groovy, or other programming languages and the like. The program code may execute entirely on the user's computer or as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or processing device. In the latter scenario, the remote computer may be connected to the user's computer through any form of network, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or the use of services such as software as a service (SaaS) in a cloud computing environment.

Furthermore, the order in which the elements and sequences are processed, the use of numerical letters, or other designations in the description are not intended to limit the order in which the processes and methods of the description are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative 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 included within the spirit and scope of the embodiments of the present disclosure. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing processing device or mobile device.

Likewise, it should be noted that in order to simplify the presentation disclosed in this specification and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure, however, is not intended to imply that more features than are presented in the claims are required for the present description. Indeed, less than all of the features of a single embodiment disclosed above.

In some embodiments, numbers describing the components, number of attributes are used, it being understood that such numbers being used in the description of embodiments are modified in some examples by the modifier "about," approximately, "or" substantially. Unless otherwise indicated, "about," "approximately," or "substantially" indicate that the number allows for a 20% variation. Accordingly, in some embodiments, numerical parameters set forth in the specification and claims are approximations that may vary depending upon the desired properties sought to be obtained by the individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and employ a method for preserving the general number of digits. Although the numerical ranges and parameters set forth herein are approximations that may be employed in some embodiments to confirm the breadth of the range, in particular embodiments, the setting of such numerical values is as precise as possible.

Each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., referred to in this specification is incorporated herein by reference in its entirety. Except for application history documents that are inconsistent or conflicting with the content of this specification, documents that are currently or later attached to this specification in which the broadest scope of the claims to this specification is limited are also. It is noted that, if the description, definition, and/or use of a term in an attached material in this specification does not conform to or conflict with what is described in this specification, the description, definition, and/or use of the term in this specification controls.

Finally, it should be understood that the embodiments described in this specification are merely illustrative of the principles of the embodiments of this specification. Other variations are possible within the scope of this description. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present specification may be considered as consistent with the teachings of the present specification. Accordingly, the embodiments of the present specification are not limited to only the embodiments explicitly described and depicted in the present specification.

Claims

1. A method of maintaining a login state, comprising, in a user login state:

acquiring feature data reflecting trigger behaviors generated due to the triggering of a device screen; the feature data reflecting the triggering behavior comprises feature data of at least one focus generated as a result of the device screen being triggered;

determining an extended time of the login state based on the feature data, comprising:

inputting the characteristic data of the at least one focus to a pre-trained behavior prediction model to obtain a behavior category;

determining the extension time through a preset duration mapping rule based on the behavior category;

adjusting the login state failure moment based on the extension time;

and keeping the login state valid before the login state failure moment.

2. The method of claim 1, the acquiring feature data reflecting the triggering behavior due to the device screen being triggered, comprising:

and acquiring the characteristic data in the preset time before the failure moment of the current login state.

3. The method of claim 1, wherein the characteristic data of the focus includes a focus coordinate value or includes a focus coordinate value and corresponding time information thereof.

4. The method of claim 1, the determining the extended time of the login state based on the characteristic data comprising:

and inputting the characteristic data of the at least one focus to a pre-trained delay prediction model, and determining the extension time.

5. The method of claim 1, the determining the extended time of the login state based on the characteristic data comprising:

obtaining a behavior category through a preset behavior determination rule based on the characteristic data of the at least one focus;

and determining the extension time through a preset duration mapping rule based on the behavior category.

6. The method of claim 1, wherein the characteristic data reflecting trigger behavior comprises system-in-package behavior events.

7. The method of claim 6, the determining the extended time of the login state based on the characteristic data comprising:

and determining the extension time through a preset duration mapping rule based on the behavior event.

8. The method of claim 1, the adjusting the login status invalidation time based on the extension time comprising:

and determining the login state failure moment based on the current login state failure moment and the extension time.

9. The method of claim 1, the adjusting the login status invalidation time based on the extension time comprising:

acquiring the current moment;

determining the login state failure moment based on the current moment and the extension time;

or alternatively, the process may be performed,

acquiring the moment of feature data reflecting the triggering behavior generated by triggering the equipment screen;

and determining the login state failure moment based on the moment and the extension time.

10. A system for maintaining a login state, comprising: in the user login state:

the acquisition module is used for acquiring characteristic data reflecting the triggering behavior generated by triggering the device screen; the feature data reflecting the triggering behavior comprises feature data of at least one focus generated as a result of the device screen being triggered;

A determining module, configured to determine an extension time of the login state based on the feature data; the determination module is further to:

the adjustment module is used for adjusting the invalid moment 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.

11. The system of claim 10, the acquisition module further to:

12. The system of claim 10, wherein the characteristic data of the focus includes a focus coordinate value or includes a focus coordinate value and corresponding time information thereof.

13. The system of claim 10, the determination module further to:

14. The system of claim 10, the determination module further to:

15. The system of claim 10, wherein the characteristic data reflecting trigger behavior comprises system-in-package behavior events.

16. The system of claim 15, the determination module further to:

17. The system of claim 10, the adjustment module further to:

18. The system of claim 10, the adjustment module further to:

acquiring the current moment;

or alternatively, the process may be performed,

19. An apparatus for maintaining a login state, comprising a processor for performing the method of any one of claims 1-9.