Login verification method and system

Abstract

The embodiment of the present application relates to a login verification method and system, wherein the login verification method applied to a first device comprises: obtaining a coding result, wherein the coding result is obtained by encoding the verification information of the first device logging into the target application via a second device; decoding the coding result to obtain the verification information; determining whether the login time of the first device matches the verification information to obtain first discrimination information; and performing login verification on the first device based on the first discrimination information. Thus, the login verification of the first device can be achieved by determining that the login time of the first device matches the verification information, so that the user can achieve login verification without having to remember the login password, thereby reducing the complexity of the user login verification.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a login verification method and system. Background Art

[0002] Currently, many client applications use a traditional login method, that is, the user enters a user name and password on a login page for login verification.

[0003] However, the user experience of the above method is limited: the above login verification scheme usually requires users to enter sensitive information such as username and password, which may be difficult to remember. At the same time, users need to change passwords regularly to increase security, but frequent password changes may reduce user experience. As a result, the user login verification is more complicated. Summary of the invention

[0004] In view of this, in order to solve some or all of the above-mentioned technical problems, an embodiment of the present application provides a login verification method and system.

[0005] In a first aspect, an embodiment of the present application provides a login verification method, which is applied to a first device and includes:

[0006] Obtaining an encoding result, wherein the encoding result is obtained by encoding verification information of the first device logging into the target application via the second device;

[0007] Decoding the encoding result to obtain the verification information;

[0008] Determine whether the login time of the first device matches the verification information to obtain first identification information;

[0009] Based on the first identification information, a login verification is performed on the first device.

[0010] In one possible implementation, the first device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

[0011] In a possible implementation manner, the verification information includes a login deadline; and

[0012] The performing login verification on the first device based on the first identification information includes:

[0013] If the first identification information indicates that the login time of the first device is earlier than the login deadline, determining that the first device passes the login verification;

[0014] When the first identification information indicates that the login time of the first device is later than the login deadline, it is determined that the first device has failed the login verification.

[0015] In a possible implementation manner, after performing login verification on the first device based on the first identification information, the method further includes:

[0016] If the first device passes the login verification, determining a target upgrade package;

[0017] The target application is upgraded based on the target upgrade package.

[0018] In a possible implementation manner, the encoding result is obtained by encoding, by the second device, verification information and identification information of the first device logging into the target application; and

[0019] The decoding of the encoding result to obtain the verification information includes:

[0020] Decoding the encoding result to obtain the verification information and the identification information; and

[0021] The performing login verification on the first device based on the first identification information includes:

[0022] Determine whether the identification information indicates the identification of the first device, and obtain second identification information;

[0023] Based on the first identification information and the second identification information, a login verification is performed on the first device.

[0024] In a possible implementation manner, after performing login verification on the first device based on the first identification information, the method further includes:

[0025] In the case where the first device passes the login verification, determining whether the current moment matches the verification information;

[0026] When the current moment does not match the verification information and the first device is in a logged-in state, the login verification method is executed again.

[0027] In a second aspect, an embodiment of the present application provides a login verification method, which is applied to a second device, and the method includes:

[0028] Determining verification information for logging into a target application on the first device;

[0029] The verification information is encoded to obtain an encoding result, wherein the encoding result is used for the first device to perform login verification.

[0030] In a possible implementation, determining verification information for logging into a target application by the first device includes:

[0031] Determine verification information of multiple first device login target applications respectively, and obtain verification information of each first device login target application; and

[0032] The step of encoding the verification information to obtain an encoding result includes:

[0033] For each first device among the plurality of first devices, the identification information of the first device and the verification information of the first device logging into the target application are encoded to obtain an encoding result.

[0034] In one possible implementation, the second device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

[0035] In a possible implementation manner, after encoding the verification information to obtain an encoding result, the method further includes:

[0036] receiving a login request from the first device;

[0037] Determining a login time and verification information of the first device carried in the login request;

[0038] Determine whether the login time matches the verification information to obtain first discrimination information;

[0039] Based on the first identification information, a login verification is performed on the first device.

[0040] In a third aspect, an embodiment of the present application provides a login verification system, the login verification system comprising a second device and a first device; wherein:

[0041] The second device is configured to: determine verification information of the first device logging into the target application; encode the verification information to obtain an encoding result;

[0042] The first device is configured to: obtain the encoding result; decode the encoding result to obtain the verification information; determine whether the login time of the first device matches the verification information to obtain first discrimination information; and perform login verification on the first device based on the first discrimination information.

[0043] In a possible implementation, the second device is configured to: respectively determine verification information of a plurality of first devices logging into a target application, and obtain verification information of each first device logging into the target application; for each first device among the plurality of first devices, encode the identification information of the first device and the verification information of the first device logging into the target application, and obtain an encoding result; and

[0044] The first device is configured to: decode the encoding result to obtain the verification information and the identification information; determine whether the identification information represents the identification of the first device to obtain second discrimination information; and perform login verification on the first device based on the first discrimination information and the second discrimination information.

[0045] The login verification method applied to the first device provided in the embodiment of the present application can obtain a coding result, wherein the coding result is obtained by encoding the verification information of the first device logging into the target application via the second device, and then decoding the coding result to obtain the verification information, and then determining whether the login time of the first device matches the verification information to obtain the first discrimination information, and then performing login verification on the first device based on the first discrimination information. Thus, the login verification of the first device can be achieved by determining whether the login time of the first device matches the verification information, so that the user can achieve login verification without remembering the login password, thereby reducing the complexity of the user login verification.

[0046] The login verification method applied to the second device provided in the embodiment of the present application can determine the verification information of the first device logging into the target application, and then encode the verification information to obtain the encoding result, wherein the encoding result is used for the first device to perform login verification. Thus, the login verification of the first device can be implemented through the verification information, so that the user can implement the login verification without remembering the login password, thereby reducing the complexity of the user login verification.

[0047] The login verification system provided by the embodiment of the present application includes a second device and a first device; wherein: the second device is configured to: determine the verification information of the first device logging into the target application; encode the verification information to obtain the encoding result; the first device is configured to: obtain the encoding result; decode the encoding result to obtain the verification information; determine whether the login time of the first device matches the verification information to obtain the first discrimination information; and perform login verification on the first device based on the first discrimination information. Thus, the login verification of the first device can be achieved by determining whether the login time of the first device matches the verification information. In this way, the user can achieve login verification without remembering the login password, thereby reducing the complexity of the user login verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

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

[0050] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0051] Figure 1 A flowchart of a login verification method provided in an embodiment of the present application;

[0052] Figure 2 A flowchart of another login verification method provided in an embodiment of the present application;

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

[0054] Figure 3B A schematic diagram of a login interface of a login target application of a login verification method provided in an embodiment of the present application;

[0055] Figure 3C A schematic diagram of a display interface of a target application of a login verification method provided in an embodiment of the present application;

[0056] Figure 3D A flowchart of another login verification method provided in an embodiment of the present application;

[0057] Figure 4 A schematic diagram of the structure of a login verification system provided in an embodiment of the present application;

[0058] Figure 5 A schematic diagram of the structure of a login verification device provided in an embodiment of the present application;

[0059] Figure 6 A schematic diagram of the structure of another login verification device provided in an embodiment of the present application;

[0060] Figure 7A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the numerical expressions and the numerical values ​​described in these embodiments do not limit the scope of the present application.

[0062] Those skilled in the art will understand that the terms "first" and "second" in the embodiments of the present application are only used to distinguish between different steps, devices, modules and other objects, and do not represent any specific technical meanings, nor do they indicate the logical order between them.

[0063] It should also be understood that in this embodiment, “plurality” may refer to two or more than two, and “at least one” may refer to one, two or more than two.

[0064] It should also be understood that any component, data or structure mentioned in the embodiments of the present application can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0065] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0066] It should also be understood that the description of the various embodiments in this application focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0067] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

[0068] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the above-mentioned technologies, methods, and equipment should be considered as part of the specification.

[0069] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0070] It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. To facilitate the understanding of the embodiments of the present application, the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0071] In addition, it should be noted that the users (including administrators) described in this application can be distinguished by user identification. For example, the user identification can be a login account. In this scenario, if different persons use the same account to log in, the above-mentioned different persons can be considered to be the same user; if the same person uses different accounts to log in respectively, the same person who logs in to different accounts can be considered to be different users. For another example, when the device is not logged in, the user identification can also be assigned based on the device identification of the device. In this scenario, if different persons use devices with the same device identification to operate, the above-mentioned different persons can be considered to be the same user; if the same person uses devices with different device identifications to operate, the above-mentioned same person can be considered to be different users.

[0072] In order to solve the technical problem of high complexity of user login verification in the prior art, the present application provides a login verification method, which can reduce the complexity of user login verification.

[0073] Figure 1 A flowchart of a login verification method provided for an embodiment of the present application. The method can be applied to one or more electronic devices (i.e., the first device) such as a smart phone, a laptop computer, a desktop computer, a portable computer, etc. In addition, the execution subject of the method can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute the method, or multiple electronic devices can cooperate with each other to execute the method.

[0074] like Figure 1 As shown, the method specifically includes:

[0075] Step 101, obtaining an encoding result, wherein the encoding result is obtained by encoding verification information of the first device logging into a target application via the second device.

[0076] In this embodiment, the second device may be another electronic device different from the first device. As an example, the first device may be an electronic device to be logged in for verification, and the second device may be an electronic device for encoding verification information of the first device logging into the target application, thereby generating an encoding result. In addition, the first device and the second device may also be used to implement other functions, which will be described later and will not be described here.

[0077] The verification information can be used to perform a login verification on the first device.

[0078] In some cases, the first device may be an electronic device used by a user, and the second device may be an electronic device used by an administrator.

[0079] Here, each second device can encode verification information of one or more first devices logging into the target application. The verification information can be set by an administrator account or determined according to a preset rule. For example, verification information matching the permission of each first device can be determined.

[0080] Among them, the verification information may include a first moment A (indicating the moment when the second device encodes the verification information of the first device logging into the target application) and a valid login period. Thus, when the login moment of the first device is after the first moment A, and the duration between the login moment and the first moment A is less than or equal to the above-mentioned valid login period, the first device can pass the login verification and thus log in successfully.

[0081] Here, the valid login duration may represent a fixed duration or a non-fixed duration. For example, the second device may determine multiple valid login durations of different durations for the same first device at different times.

[0082] Here, the encoding result may be input into the first device by means of email, telephone, work order, oral notification, etc., so that the first device obtains the encoding result.

[0083] In some optional implementations of the embodiment, the verification information includes a login deadline.

[0084] On this basis, the following method may be used to perform login verification on the first device based on the first identification information:

[0085] When the first judgment information indicates that the login time of the first device is earlier than the login deadline, it is determined that the first device has passed the login verification; when the first judgment information indicates that the login time of the first device is later than the login deadline, it is determined that the first device has not passed the login verification.

[0086] It can be understood that in the above optional implementation, whether the first device passes the login verification can be determined by comparing the time sequence between the login time and the login deadline of the first device, thereby improving the efficiency of the login verification.

[0087] In addition, the second device may encode the verification information of the first device logging into the target application in a variety of ways, for example, a Base64 encoding algorithm, an MD5 (Message-Digest Algorithm) encryption algorithm, etc. may be used.

[0088] Among them, Base64 is a binary to text encoding method, which can be considered as a method of encoding a byte array into a string, and the encoded string only contains ASCII (a set of character encodings based on the Latin alphabet) basic characters.

[0089] Here, by using the Base64 algorithm to obtain the encoding result, the encoding efficiency can be improved.

[0090] Step 102: decode the encoding result to obtain the verification information.

[0091] In this embodiment, after the first device obtains the encoding result, it can use a decoding algorithm that matches the encoding algorithm used by the second device to decode the encoding result, thereby obtaining verification information.

[0092] Step 103: determine whether the login time of the first device matches the verification information to obtain first identification information.

[0093] In this embodiment, the first identification information may indicate whether the login time of the first device matches the verification information.

[0094] As an example, in the case where the verification information includes a first moment A (indicating the moment when the second device encodes the verification information of the first device logging into the target application) and a valid login period, if the login moment of the first device is after the first moment A, and the duration between the login moment and the first moment A is less than or equal to the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device matches the verification information; if the login moment of the first device is before the first moment A, or the duration between the login moment and the first moment A is greater than the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device does not match the verification information.

[0095] Step 104: Perform a login verification on the first device based on the first identification information.

[0096] In this embodiment, when the first judgment information indicates that the login time of the first device belongs to the verification information, it can be determined that the first device has passed the login verification; when the first judgment information indicates that the login time of the first device does not belong to the verification information, it can be determined that the first device has not passed the login verification.

[0097] Through this application, when a user wants to log in to the target application through the first device, there is no need for a username and login password. The target application can be accessed by simply passing the login verification. The conventional three-step login (user name, password, confirm) is optimized to a one-step login, saving operation steps. The login steps are simplified, thereby reducing the complexity of user login verification. In addition, this application only uses the terminal device to perform login verification, without the need for a server, simplifying the communication equipment and communication steps.

[0098] In some optional implementations of this embodiment, the first device is in a state where it can be disconnected from the network during the target period.

[0099] The start time of the target time period is the time when the first device obtains the encoding result. The end time of the target time period is the time when the first device obtains the verification result of the login verification.

[0100] The disconnectable state is a state in which the connection between the first device and the network can be disconnected. That is, in this state, as long as the first device obtains the coding result, the first device can complete the login verification without relying on the network or other electronic devices except the first device.

[0101] However, it should be noted that the disconnectable state does not require the first device to be disconnected from the network, nor does it require the first device to be prohibited from communicating with other electronic devices. The first device is in a disconnectable state during the target period, which means that after the first device obtains the coding result, it can implement login verification without relying on the network and other electronic devices.

[0102] It can be understood that in the related art, after the device obtains the login account, password and other information, the device usually sends the above information to other devices (such as servers) for verification, that is, in the above technology, after the device obtains the above information, it must rely on the network and other electronic devices to realize login verification. In the present application, after the first device obtains the coding result, the login verification can be realized without other electronic devices, so that the dependence on other electronic devices (such as the second electronic device, the server) other than the first device can be reduced, and there is no need to consider the risk of other electronic devices being breached and causing the account information of the first device to be leaked, which improves the security of login verification. In addition, in terms of network connectivity, the related technology usually requires the first device to communicate with other electronic devices such as servers, so the user must have a stable network connection. If the network connection is unstable or interrupted, the user will not be able to log in normally, and the system availability is limited. In the scheme described in the above optional implementation method, after the first device obtains the coding result, it is in a disconnectable state, which can reduce the dependence on the network.

[0103] In some optional implementations of this embodiment, after performing login verification on the first device based on the first discrimination information, if the first device passes the login verification, a target upgrade package may be determined, and a target application may be upgraded based on the target upgrade package.

[0104] The target upgrade package is used for the first device to log in to the target application and upgrade the specified function in the target application. The target application is used to support the operation of the interface interconnection system, and the interface interconnection system is used to obtain interface information from multiple signal sources and display the interface information of the multiple signal sources in the interface interconnection system.

[0105] Here, the target upgrade package may be uploaded to the first device by a user of the first device.

[0106] The target application may be an application to be upgraded by a target upgrade package.

[0107] It can be understood that in the above optional implementation, when the first device login verification passes, the target application of the first device can be upgraded through the target upgrade package, thereby reducing the complexity of login verification in the user upgrade application scenario.

[0108] In some optional implementations of this embodiment, the second device may determine the verification information of the first device logging into the target application in the following manner; encode the verification information to obtain an encoding result, wherein the encoding result is used for the first device to perform login verification.

[0109] Upon receiving a login request from the first device, the second device determines verification information for logging into a target application of the first device.

[0110] It can be understood that in the above optional implementation, the second device receiving the login request of the first device can be used as a trigger condition for the second device to determine the verification information of the first device logging into the target application.

[0111] In some optional implementations of this embodiment, when there are multiple first devices and multiple first devices request to log in to the target application, the second device may determine the verification information of the first device logging in to the target application in the following manner:

[0112] Verification information of multiple first device login target applications is determined respectively, and verification information of each first device login target application is obtained.

[0113] Here, each first device may correspond to a verification information, and each verification information may be different.

[0114] On this basis, the second device may encode the verification information in the following manner to obtain an encoding result:

[0115] For each first device among the plurality of first devices, the identification information of the first device and the verification information of the first device logging into the target application are encoded to obtain an encoding result.

[0116] The identification information of the first device may include at least one of the following: a login account of the first device, a device address of the first device, etc.

[0117] Furthermore, the first device can decode the encoding result to obtain the verification information and the identification information, then determine whether the identification information represents the identification of the first device to obtain second discrimination information, and finally, perform login verification on the first device based on the first discrimination information and the second discrimination information.

[0118] The second discrimination information indicates whether the identification information indicates the identification of the first device.

[0119] It can be understood that in the above-mentioned optional implementation method, each second device can be used to encode the verification information of multiple first devices logging into the target application, and perform login verification on multiple first devices through the encoding results of the identification information and the verification information. Thereby, the accuracy of the login verification can be ensured in the login verification scenario of multiple first devices.

[0120] In some optional implementations of this embodiment, the second device may further perform the following steps:

[0121] The first step is to generate a random string.

[0122] The second step is to encode the verification information and the random character string to obtain an encoding result.

[0123] It can be understood that in the above optional implementation, by encoding the verification information and the random character string, and using the obtained encoding result to perform login verification on the first device, the security of the login verification can be improved.

[0124] In some optional implementations of this embodiment, the encoding result is obtained by encoding, by the second device, verification information and identification information of the target application logged in by the first device.

[0125] For example, the second device may encode the verification information in the following manner to obtain an encoding result:

[0126] For each first device among the plurality of first devices, the identification information of the first device and the verification information of the first device logging into the target application are encoded to obtain an encoding result.

[0127] The identification information of the first device may include at least one of the following: a login account of the first device, a device address of the first device, etc.

[0128] On this basis, the encoding result is decoded to obtain the verification information and the identification information.

[0129] Furthermore, the following method may be used to perform login verification on the first device based on the first identification information:

[0130] The first step is to determine whether the identification information represents the identification of the first device currently being compared, and obtain second discrimination information.

[0131] The second step is to perform a login verification on the first device based on the first identification information and the second identification information.

[0132] Here, in the scenario of multiple first devices, the second device can encode the identification information of each first device and the verification information of the first device logging into the target application to obtain the encoding result. Therefore, in the login verification stage, the first device can perform login verification by determining whether the identification information obtained after decoding the encoding result obtained is the same as the identification carried by the first device itself, and determining whether the login time of the first device matches the verification information obtained after decoding the encoding result obtained.

[0133] If the identification information is the same as the identification of the first device itself, and the login time of the first device matches the verification information obtained by the first device, it can be determined that the first device has passed the login verification. If the identification information does not represent the identification of the first device itself (is different from the identification of the first device itself), or the login time does not match the verification information obtained by the first device, it can be determined that the first device has passed the login verification.

[0134] It can be understood that in the above optional implementation method, each second device can be used to encode the verification information of multiple first devices logging into the target application, and perform login verification of the first device through the encoding results of the identification information and the verification information, thereby ensuring the accuracy of login verification in the scenario of multiple first device login verification.

[0135] In some optional implementations of this embodiment, after performing login verification on the first device based on the first identification information, the following steps may also be performed:

[0136] The first step is to determine whether the current time (which may be the time collected in real time by the first device) matches the verification information when the first device passes the login verification.

[0137] As an example, in the case where the verification information includes a first moment A (indicating the moment when the second device encodes the verification information of the first device logging into the target application) and the login validity period, if the current moment (indicating the moment when the first device last acquired the data) is after the first moment A, and the duration between the current moment and the first moment A is less than or equal to the above login validity period, then it can be determined that the first discrimination information indicates that the current moment of the first device matches the verification information; if the current moment of the first device is before the first moment A, or the duration between the current moment and the first moment A is greater than the above login validity period, then it can be determined that the first discrimination information indicates that the current moment of the first device does not match the verification information. In this way, the first device can be controlled to log into the target application only within the valid time.

[0138] Here, after logging into the target application, as time passes, the current time and the verification information will change from matching each other to not matching each other.

[0139] In the second step, when the current moment does not match the verification information and the first device is in a logged-in state, the login verification method is executed again.

[0140] It is understandable that after passing the login verification, if the login time is too long or too late, the authorized login period will expire. In this case, you can apply again to obtain the coding result and extend the usage period.

[0141] The login verification method applied to the first device provided in the embodiment of the present application can obtain a coding result, wherein the coding result is obtained by encoding the verification information of the first device logging into the target application via the second device, and then decoding the coding result to obtain the verification information, and then determining whether the login time of the first device matches the verification information to obtain the first discrimination information, and then performing login verification on the first device based on the first discrimination information. Thus, the login verification of the first device can be achieved by determining whether the login time of the first device matches the verification information, so that the user can achieve login verification without remembering the login password, thereby reducing the complexity of the user login verification.

[0142] Figure 2 A flow chart of another login verification method provided for an embodiment of the present application. The method can be applied to one or more electronic devices (i.e., second devices) such as a smart phone, a laptop computer, a desktop computer, a portable computer, etc. In addition, the execution subject of the method can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute the method, or multiple electronic devices can cooperate with each other to execute the method.

[0143] like Figure 2 As shown, the method specifically includes:

[0144] Step 201, determine verification information for a first device to log into a target application.

[0145] In this embodiment, the second device may be another electronic device different from the first device. As an example, the first device may be an electronic device to be logged in for verification, and the second device may be an electronic device for encoding verification information of the first device logging into the target application, thereby generating an encoding result. In addition, the first device and the second device may also be used to implement other functions, which will be described later and will not be described here.

[0146] In some cases, the first device may be an electronic device used by a user, and the second device may be an electronic device used by an administrator. The first device and the second device may be connected using an HDMI cable, or may communicate using radio waves.

[0147] Here, each second device can encode verification information of one or more first devices logging into the target application. The verification information can be set by an administrator account or determined according to a preset rule. For example, verification information matching the permission of each first device can be determined.

[0148] Among them, the verification information may include a first moment A (indicating the moment when the second device encodes the verification information of the first device logging into the target application) and a valid login period. Thus, when the login moment of the first device is after the first moment A, and the duration between the login moment and the first moment A is less than or equal to the above-mentioned valid login period, the first device can pass the login verification and thus log in successfully.

[0149] Step 202: Encode the verification information to obtain an encoding result.

[0150] In this embodiment, after the second device obtains the coding result, the first device can use the coding result to perform login verification. Specifically, the first device can obtain the coding result; decode the coding result to obtain the verification information; determine whether the login time of the first device matches the verification information to obtain first identification information; and perform login verification on the first device based on the first identification information.

[0151] In addition, the second device may encode the verification information of the first device logging into the target application in a variety of ways, for example, a Base64 encoding algorithm, an MD5 (Message-Digest Algorithm) encryption algorithm, etc. may be used.

[0152] Here, the second device can generate different encoding results for the same first device. For example, the second device can use different encoding algorithms to generate multiple different encoding results for the same first device. The second device can also generate different encoding results for different first devices. For example, the second device can use the same or different encoding algorithms to encode the identification information of different first devices, thereby obtaining multiple different encoding results. Exemplarily, the encoding result can be automatically input into the first device, and the first device performs the decoding operation, and this process is invisible to the user's naked eye. It can also be input into the user's mobile phone, mailbox, etc., and the user manually copies the encoding result and inputs it into the first device, and the first device performs the decoding operation, and this process is visible to the user's naked eye.

[0153] Among them, Base64 is a binary to text encoding method, which can be considered as a method of encoding a byte array into a string, and the encoded string only contains ASCII (a set of character encodings based on the Latin alphabet) basic characters.

[0154] After the first device obtains the encoding result, it can use a decoding algorithm that matches the encoding algorithm used by the second device to decode the encoding result, thereby obtaining verification information.

[0155] The first determination information may indicate whether the login time of the first device matches the verification information.

[0156] As an example, in the case where the verification information includes a first moment A (indicating the moment when the second device encodes the verification information of the target application for logging into the first device) and a valid login period, if the login moment of the first device is after the first moment A, and the duration between the login moment and the first moment A is less than or equal to the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device belongs to the verification information; if the login moment of the first device is before the first moment A, or the duration between the login moment and the first moment A is greater than the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device does not belong to the verification information.

[0157] When the first judgment information indicates that the login time of the first device belongs to the verification information, it can be determined that the first device has passed the login verification; when the first judgment information indicates that the login time of the first device does not belong to the verification information, it can be determined that the first device has not passed the login verification.

[0158] In some optional implementations of this embodiment, the following method may be used to determine the verification information of the first device logging into the target application:

[0159] Verification information of multiple first device login target applications is determined respectively, and verification information of each first device login target application is obtained.

[0160] Here, each first device may correspond to one verification information.

[0161] On this basis, the verification information can be encoded in the following manner to obtain an encoding result:

[0162] For each first device among the plurality of first devices, the identification information of the first device and the verification information of the first device logging into the target application are encoded to obtain an encoding result.

[0163] The identification information of the first device may include at least one of the following: a login account of the first device, a device address of the first device, etc.

[0164] Furthermore, the first device can decode the encoding result to obtain the verification information and the identification information, then determine whether the identification information represents the identification of the first device to obtain second discrimination information, and finally, perform login verification on the first device based on the first discrimination information and the second discrimination information.

[0165] The second discrimination information indicates whether the identification information indicates the identification of the first device.

[0166] It can be understood that in the above optional implementation method, each second device can be used to encode the verification information of multiple first devices logging into the target application, and perform login verification of the first device through the encoding results of the identification information and the verification information, thereby ensuring the accuracy of login verification in the scenario of multiple first device login verification.

[0167] In some optional implementations of this embodiment, the second device is in a disconnectable state during the target period.

[0168] The starting time of the target time period is the time when the first device obtains the encoding result, and the ending time of the target time period is the time when the first device obtains the verification result of the login verification.

[0169] In some optional implementations of this embodiment, the following method may be used to determine the verification information of the first device logging into the target application:

[0170] In case of receiving a login request from a first device, verification information for logging into a target application by the first device is determined.

[0171] It can be understood that in the above optional implementation, the second device receiving the login request of the first device can be used as a trigger condition for the second device to determine the verification information of the first device logging into the target application.

[0172] In some optional implementations of this embodiment, the second device may further perform the following steps:

[0173] The first step is to generate a random string.

[0174] The second step is to encode the verification information and the random character string to obtain an encoding result.

[0175] It can be understood that in the above optional implementation, by performing login verification of the first device using the encoding result obtained by encoding the verification information and the random character string, the security of the login verification can be improved.

[0176] In some optional implementations of this embodiment, after encoding the verification information to obtain the encoding result, the following steps may also be performed:

[0177] First, a login request from the first device is received.

[0178] The login request may carry the login time and verification information of the first device.

[0179] Afterwards, the login time and verification information of the first device carried in the login request are determined.

[0180] Then, it is determined whether the login time matches the verification information to obtain first determination information.

[0181] The first discrimination information indicates whether the login time matches the verification information.

[0182] Finally, based on the first identification information, a login verification is performed on the first device.

[0183] As an example, in the case where the verification information includes a first moment A (indicating the moment when the second device encodes the verification information of the first device logging into the target application) and a valid login period, if the login moment of the first device is after the first moment A, and the duration between the login moment and the first moment A is less than or equal to the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device matches the verification information, and thus it is determined that the login verification has passed; if the login moment of the first device is before the first moment A, or the duration between the login moment and the first moment A is greater than the above-mentioned valid login period, then it can be determined that the first judgment information indicates that the login moment of the first device does not match the verification information, and thus it is determined that the login verification has not passed.

[0184] It can be understood that in the above optional implementation, the second device can receive the login request of the first device and perform login verification through the login request.

[0185] It should be noted that, in addition to the above contents, this embodiment may also include Figure 1 The corresponding technical features described in the corresponding embodiments are realized Figure 1 For details on the technical effects of the login verification method shown, please refer to Figure 1 For the sake of brevity, the relevant description is not repeated here.

[0186] The login verification method applied to the second device provided in the embodiment of the present application can determine the verification information of the first device logging into the target application, and then encode the verification information to obtain the encoding result, wherein the encoding result is used for the first device to perform login verification. Therefore, the login verification of the first device can be implemented by determining the verification information, so that the user can implement the login verification without remembering the login password, thereby reducing the complexity of the user login verification.

[0187] The following is an illustrative description of the embodiments of the present application, but it should be noted that the embodiments of the present application may have the features described below, but the following description does not constitute a limitation on the scope of protection of the embodiments of the present application.

[0188] Currently, many client applications use the traditional login method, that is, users enter their username and password on the login page for identity authentication. However, this method has some shortcomings, such as strong dependence on the server, high network connectivity requirements, the risk of password leakage and cracking, and limited user experience.

[0189] Strong server dependence: Traditional login solutions usually rely on central servers for user authentication and password verification. This dependence makes the server a target for attackers. If the server is compromised, the security of the entire system will be seriously threatened.

[0190] High network connectivity requirements: Traditional login solutions require users to communicate with the server over the network, so users must have a stable network connection. If the network connection is unstable or interrupted, users will not be able to log in normally, and system availability will be limited.

[0191] There is a risk of password leakage: In traditional login solutions, user passwords are usually stored in plain text on the server or during transmission, which may be intercepted or stolen. Once the password is leaked, anyone can impersonate the user to log in illegally, threatening system security.

[0192] Limited user experience: Traditional login solutions usually require users to enter sensitive information such as usernames and passwords, which may be difficult to remember and easy to enter incorrectly. At the same time, users need to change passwords regularly to increase security, but frequent password changes may reduce user experience.

[0193] The specific application scenario of this solution is that the user of the first device (the party accessing the target application) belongs to the client unit. Once the server is handed over to the other party, they cannot access the server. If they want to use the server to upgrade, it is simply impossible; they cannot use the server to provide technical support for the target application login; but they cannot directly hand over the password of the target application to the other party, otherwise the password will become public and cannot be controlled later.

[0194] In order to solve the above technical problems, this method adopts time coding technology, which can improve the security and availability of verification without connecting to the server. Among them, the application in the above client is the client target application (that is, the above target application), which is used for users to upgrade and maintain the background system, and the background system is used to support the operation of interface interconnection products (assistants, cloud terminal systems). After the user logs in to the client target application, he can access the background system and perform operations such as upgrading and maintaining the background system.

[0195] This solution can (but not necessarily) provide a simple client target application login method that does not require a server or a persistent network connection. The user obtains the encoded result from the administrator and enters the password (i.e. the encoded result) to determine whether the current time is within the validity period (i.e. the verification information). If it is within the validity period, the login will succeed; otherwise, the login will fail.

[0196] For example: a time verification function is set in the administrator terminal (that is, the second device mentioned above), and the terminal where the target application is located (that is, the first device mentioned above) sends a login request to the administrator terminal. The administrator terminal converts the deadline for logging into the target application (that is, the above login deadline) into a letter identifier (that is, the above encoding result, equivalent to a secret key) based on the coding rules, and sends the letter identifier to the terminal where the target application is located. The terminal enters the letter identifier into the login page, and converts the letter identifier into the corresponding deadline, and compares the deadline date with the current login date of the terminal. If the login date is earlier than the deadline, the terminal is allowed to log in; if the login date is later than the deadline, the terminal is not allowed to log in. This solution is simple and efficient; it does not require a server; and it can be used in a closed (non-networked) environment. Without networking, multiple terminal devices can use HDMI cables, Bluetooth, radio waves, etc. to exchange information.

[0197] This solution can transmit and use login codes (i.e. secret keys) across networks and without servers. The administrator terminal can send the login code (i.e. secret key) to the terminal where the target application is located by email, phone call, work order, etc. There is no restriction on the specific sending method.

[0198] like Figure 3A As shown, Figure 3A A flowchart of another login verification method provided in an embodiment of the present application.

[0199] When multiple user terminals send login requests to the administrator terminal, the administrator terminal can generate a "secret key (i.e. the verification information) + the account information of the corresponding terminal (i.e. the identification information)", and send the "secret key + the account information of the corresponding terminal" to the corresponding user terminal. Only user terminals with correct correspondence and valid time can successfully log in to the target application.

[0200] Specifically, during the encoding process, when the administrator client generates a key, you can choose to encrypt the key based on the target application using the login deadline, which can ensure that each key can only be used within the specified time, improving the security of the software system. When generating an encrypted key, the administrator can use the Base64 encoding algorithm to encode the string of the login deadline to generate a key.

[0201] During the login process, when the user uses the target application, he only needs to log in to the login interface (see Figure 3B ) to complete the login operation of the target application. The user does not need to provide other information. The key will be transmitted to the client, which will decrypt and verify it. After the user successfully logs in, the client target application login interface (such as Figure 3C As shown in the figure, the user uploads the file package to be upgraded (that is, the target upgrade package) to the file upload area of ​​the page, and the server performs the upgrade of the company's interface interconnection products (assistant, cloud terminal system) corresponding to the file package to be upgraded. It should be noted that after the first device successfully logs in to the target application, operations such as upgrading the target application can be performed by the server placed in the above-mentioned customer unit, so as to achieve the technical purpose of upgrading the target application in the customer unit without going to the customer site.

[0202] During the decoding process, the target application can transmit the key to the local client for decoding after the user enters the key. The client can use the same algorithm as the administrator client to decrypt the key to obtain the login deadline of the target application.

[0203] During the judgment process, the target application can locally call a time verification function, which is a function pre-written into the target application, and use the time verification function to compare the time sequence between the current login date and the deadline. If the current login date (that is, the login time mentioned above) is earlier than the login deadline, you can continue to log in to the target application. If the current login date is later than the deadline, the target application will prevent the user from continuing to use the program to ensure software security.

[0204] During maintenance processing, after the user successfully logs in to the target application, the user can continue to use other functions within the target application to perform operations, such as maintenance operations of the assistant, interface cloud terminal system, etc.

[0205] Among them, in this scheme, if Figure 3D As shown, the Base64 encoding algorithm can be used to generate the encoding result (secret key) and limit it to the login time range. The application of the Base64 encoding algorithm in this solution and the encoding and decoding process are described in detail below.

[0206] a. Implementation of Base64 encoding:

[0207] On the management side (i.e., the second device), the administrator can generate a random password that includes the effective login deadline for the target application and a random string. The administrator enters the random password into the Base64 algorithm for encoding, generating an encoding result with a character mapping. For example, the original password is "231109", and the encoding result is "A8Hj".

[0208] In addition, the MD5 encryption algorithm can also be used for encryption.

[0209] During the login process, the user can obtain the encoded result from the management end, then enter the encoded result in the target application login interface and click the login button. The target application decrypts the password through the Base64 decoding algorithm to obtain the original password "231109".

[0210] During the decryption process, the target application uses the Base64 decoding algorithm to decode the encoding result to obtain the original encrypted password. The advantage of using the Base64 algorithm in this solution is that the encoding result is short in length, has a fast reading and writing speed, and is simple and easy to understand.

[0211] During the verification process, the target application will compare the current time with the decoded login deadline to determine whether the user's login time is within the validity period. If the user's login time is within the validity period, the login will succeed; otherwise, the login will fail.

[0212] This solution uses the Base64 encoding algorithm to generate the encoding result and use it as the input password. It is simple and easy to understand, fast, and does not involve complex algorithms or protocols. Using a time-based verification method can ensure that users can only access the target application within the validity period.

[0213] This solution eliminates the hassle of using a complex registration process or remembering complex passwords, and provides good security controls to prevent unauthorized users from accessing and using the target application. This solution mainly uses time verification to ensure software security and avoid the risk of information leakage.

[0214] By adopting time encryption cryptography technology, this solution can ensure the security and accuracy of user identity authentication, while avoiding the problem of relying on servers and network connections in traditional login methods, improving the system's usability and user experience. In addition, the login method of the present invention can also effectively prevent the risk of password leakage and cracking, and protect the privacy and security of users.

[0215] In summary, this solution can provide a more secure, convenient, and network-free client target application login method to address the shortcomings and deficiencies of the prior art.

[0216] It should be noted that, in addition to the contents recorded above, this embodiment may also include the technical features described in the above embodiments, so as to achieve the technical effects of the login verification method shown above. Please refer to the above description for details. For the sake of brevity, it will not be repeated here.

[0217] The login verification scheme provided in the embodiment of the present application adopts time coding technology to ensure the security and accuracy of user identity authentication. No continuous network connection is required. The user only needs to enter the encrypted password (i.e., the encoding result) provided by the administrator to perform identity authentication and login operations, which improves the availability and user experience of the system. The verification information is processed by the encoding algorithm to ensure the security of the password and reduce the risk of password leakage. The user operation process is simplified. The user only needs to enter the password (i.e., the encoding result) once to complete the identity authentication and login operations, without entering other sensitive information, reducing the user's operation difficulty and improving the user experience. At the same time, since all authentication processes are carried out on the client, the burden on the server is greatly reduced and the operating efficiency of the system is improved. Moreover, the user can log in without networking, which makes it possible to log in to the target application in an environment without a network. By adopting the Base64 encryption algorithm, it is ensured that the generated password has a certain security and is not easy to be destroyed. The limited login time range can effectively control the window period of user login. In addition, since the issuance and management of the password are all carried out by the administrator, the password will not be transmitted in the network, which greatly improves the security of the system and prevents the password from being intercepted or cracked during the network transmission process. If the password expires or is leaked, the administrator can update the password at any time to ensure the security of the system. At the same time, if the user forgets the password, he can also ask the administrator for help, and will not be unable to log in because of forgetting the password. In short, this solution has the advantages of simplicity, efficiency, and security, and is an excellent login verification solution.

[0218] Figure 4 This is a schematic diagram of the structure of a login verification system provided in an embodiment of the present application. Figure 4 As shown, the login verification system 300 includes a second device 302 and a first device 301; wherein:

[0219] The second device 302 is configured to: determine verification information of the first device 301 logging into the target application; encode the verification information to obtain an encoding result;

[0220] The first device 301 is configured to: obtain the encoding result; decode the encoding result to obtain the verification information; determine whether the login time of the first device matches the verification information to obtain first discrimination information; and perform login verification on the first device 301 based on the first discrimination information.

[0221] In some optional implementations of this embodiment,

[0222] The second device 302 is configured to: respectively determine verification information of the target application logged by the plurality of first devices 301, and obtain verification information of each of the first devices 301 logged in to the target application; for each of the plurality of first devices 301, encode the identification information of the first device 301 and the verification information of the target application logged in by the first device 301, and obtain an encoding result; and

[0223] The first device 301 is configured to: decode the encoding result to obtain the verification information and the identification information; determine whether the identification information represents the identification of the first device to obtain second discrimination information; and perform login verification on the first device 301 based on the first discrimination information and the second discrimination information.

[0224] In some optional implementations of this embodiment, the first device 301 is in a disconnectable state during a target time period, wherein the start time of the target time period is the time when the first device 301 obtains the encoding result, and the end time of the target time period is the time when the first device 301 obtains the verification result of the login verification.

[0225] In some optional implementations of this embodiment, the second device 302 is configured to:

[0226] When a login request from the first device 301 is received, verification information of the first device 301 is determined.

[0227] In some optional implementations of this embodiment, the verification information includes a login deadline; and

[0228] The first device 301 is configured to: when the login time of the first device 301 is earlier than the login deadline, determine that the first device 301 has passed the login verification; when the login time of the first device 301 is later than the login deadline, determine that the first device 301 has not passed the login verification.

[0229] In some optional implementations of this embodiment, the second device 302 is configured to:

[0230] Generate a random string;

[0231] The verification information and the random character string are encoded to obtain an encoding result.

[0232] In some optional implementations of this embodiment,

[0233] The second device 302 is configured to: use a Base64 encoding algorithm to encode the verification information to obtain an encoding result;

[0234] The first device 301 is configured to: use a Base64 decoding algorithm to decode the encoding result to obtain the verification information.

[0235] In some optional implementations of this embodiment, the first device 301 is further configured to:

[0236] When the first device 301 passes the login verification, a target upgrade package is determined, wherein the target upgrade package is used for upgrading a target application of the first device 301 .

[0237] It should be noted that, in addition to the above contents, this embodiment may also include Figure 1 , Figure 2 The corresponding technical features described in the corresponding embodiments are realized Figure 1 , Figure 2 For example, the first device 301 in the login verification system provided in the embodiment of the present application can be used to implement Figure 1 The steps shown; the second device 301 in the login verification system provided in the embodiment of the present application can be used to implement Figure 2 For details, please refer to Figure 1 , Figure 2 For the sake of brevity, the relevant description is not repeated here.

[0238] Similarly, except Figure 1 , Figure 2 In addition to the recorded content, Figure 1 , Figure 2 The illustrated embodiment may also include the corresponding technical features described in the login verification system provided in the embodiment of the present application, thereby realizing the technical effects of the login verification system provided in the embodiment of the present application. For the sake of concise description, they are not elaborated here.

[0239] The login verification system provided by the embodiment of the present application includes a second device 302 and a first device 301; wherein: the second device 302 is configured to: determine the verification information of the first device 301; encode the verification information to obtain the encoding result; the first device 301 is configured to: obtain the encoding result; decode the encoding result to obtain the verification information; and perform login verification on the first device 301 based on the first discrimination information. Thus, the login verification of the first device 301 can be achieved by determining whether the login time of the first device 301 matches the verification information. In this way, the user can achieve login verification without remembering the login password, thereby reducing the complexity of the user login verification.

[0240] Figure 5 A schematic diagram of the structure of a login verification device provided in an embodiment of the present application. Specifically comprising:

[0241] An acquiring unit 401 is configured to acquire an encoding result, wherein the encoding result is obtained by encoding verification information of the first device logging into a target application via the second device;

[0242] A decoding unit 402, configured to decode the encoding result to obtain the verification information;

[0243] A second determination unit 403 is used to determine whether the login time of the first device matches the verification information to obtain first identification information;

[0244] The verification unit 404 is configured to perform a login verification on the first device based on the first identification information.

[0245] In one possible implementation, the first device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

[0246] In a possible implementation manner, the verification information includes a login deadline; and

[0247] The performing login verification on the first device based on the first identification information includes:

[0248] If the first identification information indicates that the login time of the first device is earlier than the login deadline, determining that the first device passes the login verification;

[0249] When the first identification information indicates that the login time of the first device is later than the login deadline, it is determined that the first device has failed the login verification.

[0250] In a possible implementation manner, after performing login verification on the first device based on the first identification information, the apparatus further includes:

[0251] If the first device passes the login verification, determining a target upgrade package;

[0252] The target application is upgraded based on the target upgrade package.

[0253] In a possible implementation manner, the encoding result is obtained by encoding, by the second device, verification information and identification information of the first device logging into the target application; and

[0254] The decoding of the encoding result to obtain the verification information includes:

[0255] Decoding the encoding result to obtain the verification information and the identification information; and

[0256] The performing login verification on the first device based on the first identification information includes:

[0257] Determine whether the identification information indicates the identification of the first device, and obtain second identification information;

[0258] Based on the first identification information and the second identification information, a login verification is performed on the first device.

[0259] In a possible implementation manner, after performing login verification on the first device based on the first identification information, the apparatus further includes:

[0260] A third determination unit (not shown in the figure), configured to determine whether the current moment matches the verification information when the first device passes the login verification;

[0261] An execution unit (not shown in the figure) is used to execute the login verification method again when the current moment does not match the verification information and the first device is in a logged-in state.

[0262] The login verification device provided in this embodiment can be as follows Figure 6 The login verification device shown in can execute all the steps of the login verification methods described above, thereby achieving the technical effects of the login verification methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0263] Figure 6 A schematic diagram of the structure of another login verification device provided in an embodiment of the present application. Specifically comprising:

[0264] A first determining unit 411 is used to determine verification information for logging into a target application by a first device;

[0265] The encoding unit 412 is used to encode the verification information to obtain an encoding result, wherein the encoding result is used for the first device to perform login verification.

[0266] In a possible implementation, determining verification information for logging into a target application by the first device includes:

[0267] Determine verification information of multiple first device login target applications respectively, and obtain verification information of each first device login target application; and

[0268] The step of encoding the verification information to obtain an encoding result includes:

[0269] For each first device among the plurality of first devices, encoding the identification information of the first device and the verification information of the first device logging into the target application to obtain an encoding result;

[0270] Among them, the first device is configured to: decode the encoding result to obtain the verification information and the identification information; determine whether the identification information represents the identification of the first device to obtain second discrimination information; and perform login verification on the first device based on the first discrimination information and the second discrimination information.

[0271] In one possible implementation, the second device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

[0272] In a possible implementation, determining verification information for logging into a target application by the first device includes:

[0273] In case of receiving a login request from a first device, verification information for logging into a target application by the first device is determined.

[0274] In a possible implementation manner, after encoding the verification information to obtain an encoding result, the method further includes:

[0275] A receiving unit (not shown in the figure), configured to receive a login request from the first device;

[0276] a fourth determining unit (not shown in the figure), configured to determine a login time and verification information of the first device carried in the login request;

[0277] A fifth determination unit (not shown in the figure), used to determine whether the login time matches the verification information, and obtain first discrimination information;

[0278] A processing unit (not shown in the figure) is used to perform a login verification on the first device based on the first identification information.

[0279] The login verification device provided in this embodiment can be as follows Figure 6 The login verification device shown in can execute all the steps of the login verification methods described above, thereby achieving the technical effects of the login verification methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0280] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Figure 7 The electronic device 500 shown includes: at least one processor 501, a memory 502, at least one network interface 504 and other user interfaces 503. The various components in the electronic device 500 are coupled together via a bus system 505. It is understood that the bus system 505 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 505 is not shown in FIG. Figure 7 Various buses are labeled as bus system 505 .

[0281] The user interface 503 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

[0282] It can be understood that the memory 502 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DRRAM). The memory 502 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0283] In some implementations, the memory 502 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 5021 and an application program 5022 .

[0284] Among them, the operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 5022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application can be included in the application 5022.

[0285] In this embodiment, by calling the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application 5022, the processor 501 is used to execute the method steps provided by each method embodiment.

[0286] The method disclosed in the above embodiment of the present application can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 501. The above processor 501 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the above method in combination with its hardware.

[0287] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of the present application, or a combination thereof.

[0288] For software implementation, the technology described above in this article can be implemented by a unit that performs the functions described above in this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0289] The electronic device provided in this embodiment may be Figure 7 The electronic device shown in can execute all steps of the login verification methods described above, thereby achieving the technical effects of the login verification methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0290] The embodiment of the present application also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.

[0291] When one or more programs in the storage medium can be executed by one or more processors, the login verification method executed on the electronic device side can be implemented.

[0292] The above-mentioned processor is used to execute the login verification program stored in the memory to implement the following steps of the login verification method executed on the electronic device side.

[0293] The professionals should also be further aware that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0294] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0295] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0296] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A login verification method, characterized in that: The method is applied to a first device, and the method includes: Obtaining an encoding result, wherein the encoding result is obtained by encoding verification information of the first device logging into a target application via a second device, the encoding result is generated after the second device receives a login request from the first device, and the second device generates multiple different encoding results for the same first device; Decoding the encoding result to obtain the verification information; Determine whether the login time of the first device matches the verification information to obtain first identification information; Based on the first identification information, performing a login verification on the first device; Wherein, when the first device passes the login verification, the server upgrades the target application based on the target upgrade package.

2. The method according to claim 1, characterized in that The first device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

3. The method according to claim 1, characterized in that The verification information includes the login deadline; as well as The performing login verification on the first device based on the first identification information includes: If the first identification information indicates that the login time of the first device is earlier than the login deadline, determining that the first device passes the login verification; When the first identification information indicates that the login time of the first device is later than the login deadline, it is determined that the first device has failed the login verification.

4. The method according to any one of claims 1 to 3, characterized in that: The encoding result is obtained by encoding the verification information and identification information of the first device logging into the target application via the second device; as well as The decoding of the encoding result to obtain the verification information includes: Decoding the encoding result to obtain the verification information and the identification information; and The performing login verification on the first device based on the first identification information includes: Determine whether the identification information indicates the identification of the first device, and obtain second identification information; Based on the first identification information and the second identification information, a login verification is performed on the first device.

5. The method according to any one of claims 1 to 3, characterized in that: After performing login verification on the first device based on the first identification information, the method further includes: In the case where the first device passes the login verification, determining whether the current moment matches the verification information; When the current moment does not match the verification information and the first device is in a logged-in state, the login verification method is executed again.

6. A login verification method, characterized in that: The method is applied to a second device, and the method includes: Determining verification information for logging into a target application on the first device; Encode the verification information to obtain a coding result, wherein the coding result is used for the first device to perform login verification, the coding result is generated after the second device receives the login request of the first device, and the second device generates multiple different coding results for the same first device; Wherein, when the first device passes the login verification, the server upgrades the target application based on the target upgrade package; After encoding the verification information to obtain the encoding result, the method further includes: receiving a login request from the first device; Determining a login time and verification information of the first device carried in the login request; Determine whether the login time matches the verification information to obtain first discrimination information; Based on the first identification information, a login verification is performed on the first device.

7. The method according to claim 6, characterized in that The determining verification information of the first device logging into the target application includes: Determine verification information of multiple first device login target applications respectively, and obtain verification information of each first device login target application; and The step of encoding the verification information to obtain an encoding result includes: For each first device among the plurality of first devices, the identification information of the first device and the verification information of the first device logging into the target application are encoded to obtain an encoding result.

8. The method according to claim 6, characterized in that The second device is in a disconnectable state during a target period, wherein the start time of the target period is the time when the first device obtains the encoding result, and the end time of the target period is the time when the first device obtains the verification result of the login verification.

9. A login verification system, characterized in that: The login verification system includes a second device and a first device; wherein: The second device is configured to: determine verification information of the first device logging into the target application; encode the verification information to obtain an encoding result, wherein the encoding result is generated after the second device receives the login request of the first device, and the second device generates multiple different encoding results for the same first device; The first device is configured to: obtain the encoding result; decode the encoding result to obtain the verification information; determine whether the login time of the first device matches the verification information to obtain first identification information; perform login verification on the first device based on the first identification information; Wherein, when the first device passes the login verification, the server upgrades the target application based on the target upgrade package.

10. The login verification system according to claim 9, characterized in that: The second device is configured to: respectively determine verification information of a plurality of first devices logging into a target application, and obtain verification information of each first device logging into the target application; for each first device among the plurality of first devices, encode the identification information of the first device and the verification information of the first device logging into the target application, and obtain an encoding result; as well as The first device is configured to: decode the encoding result to obtain the verification information and the Identification information; Determine whether the identification information indicates the identification of the first device, and obtain second identification information; Based on the first identification information and the second identification information, a login verification is performed on the first device.

Images