Terminal equipment login method and device

Abstract

The invention relates to the technical field of internet, and particularly discloses a terminal equipment login method and device, and the method comprises the steps: receiving a login request sent by terminal equipment; the login request comprises environment data; the environment data comprises position information, network information and equipment information; under the condition that the terminal equipment is slave equipment, calculating a first security factor according to the position information and a specified position information set corresponding to the terminal equipment; determining the network type of the terminal equipment according to the network information, and determining a second security factor according to the network type; calculating a third security factor according to the equipment information; determining a login verification mode of the terminal device based on the first security factor, the second security factor and the third security factor; interacting with the terminal equipment according to the login verification mode, and receiving login verification data fed back by the terminal equipment; and verifying the login verification data, and if the verification is successful, determining that the terminal equipment is successfully logged in. According to the mode, the login security of the terminal equipment can be improved.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a terminal device login method and apparatus. Background Art

[0002] With the popularization of the Internet, users have more and more needs to log in to their mobile banking accounts on multiple devices. However, currently, when logging in through multiple devices, a single verification method is used to log in, and security cannot be guaranteed.

[0003] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of this specification provide a terminal device login method and apparatus to solve the problem that the terminal device login method in the prior art is not sufficiently secure.

[0005] The present invention provides a method for logging in to a terminal device, including:

[0006] Receiving a login request sent by a terminal device; the login request includes environmental data; the environmental data is data related to the current environment of the terminal device; the environmental data includes: location information, network information and device information;

[0007] In the case where the terminal device is a slave device, a first security factor is calculated according to the location information and a designated location information set corresponding to the terminal device; a network type of the terminal device is determined according to the network information, and a second security factor is determined according to the network type; a third security factor is calculated according to the device information; and a login verification method of the terminal device is determined based on the first security factor, the second security factor, and the third security factor;

[0008] Interacting with the terminal device according to the login verification method, and receiving login verification data fed back by the terminal device;

[0009] The login verification data is verified, and if the verification is successful, it is determined that the terminal device has successfully logged in.

[0010] In one embodiment, the login request also includes a device identification and account data;

[0011] Accordingly, before determining the login verification method of the terminal device according to the environment data of the terminal device, the method further includes:

[0012] The type of the terminal device is determined based on the device identification and the account data; the type of the terminal device includes a master device and a slave device.

[0013] In one embodiment, determining a login verification method of the terminal device based on the first security factor, the second security factor, and the third security factor includes:

[0014] The login security credibility of the terminal device is calculated according to the following formula:

[0015] P = ap1 + bp2 + cp3;

[0016] Determining a login verification method for the terminal device according to the login security credibility;

[0017] Among them, P is the login security credibility of the terminal device; a, b and c are weight coefficients, p1 is the first security factor, p2 is the second security factor, and p3 is the third security factor.

[0018] In one embodiment, after determining that the terminal device has successfully logged in, the method further includes:

[0019] After the terminal device successfully logs in, the environment data of the terminal device and the behavior data of the terminal device are collected.

[0020] In one embodiment, the method further comprises:

[0021] In the case where the terminal device is the main device, interacting with the terminal device according to a preset login verification method to obtain login verification data fed back by the terminal device;

[0022] The login verification data is verified, and if the verification is successful, it is determined that the terminal device has successfully logged in.

[0023] In one embodiment, the method further comprises:

[0024] After the terminal device successfully logs in, receiving a transaction request sent by the terminal device; the transaction request includes target transaction information;

[0025] Acquire environmental data of the terminal device and historical transaction data corresponding to the terminal device;

[0026] Determining a transaction verification method of the terminal device according to the target transaction information, the environmental data and the historical transaction data;

[0027] Interact with the terminal device based on the transaction verification method, receive transaction verification data fed back by the terminal device; verify the transaction verification data, and if the verification is successful, execute the transaction corresponding to the transaction request.

[0028] In one embodiment, determining the transaction verification method of the terminal device according to the target transaction information, the environment data and the historical transaction data includes:

[0029] Determining the security credibility of the terminal device according to the environmental data of the terminal device;

[0030] Determining the transaction feasibility of the terminal device according to the historical transaction data and the target transaction information;

[0031] A transaction verification method for the terminal device is determined based on the security credibility and transaction feasibility of the terminal device.

[0032] In one embodiment, the method further comprises:

[0033] receiving a device type change request; the device type change request is used to change the terminal device from a slave device to a master device;

[0034] Determining the security credibility of the terminal device based on the environmental data and historical behavior data of the terminal device;

[0035] When the security credibility of the terminal device meets the preset conditions, determining to change the verification mode according to the security credibility;

[0036] Interacting with the terminal device based on the change verification method to obtain change verification data;

[0037] The change verification data is verified, and if the verification is successful, the device type of the terminal device is changed from a slave device to a master device.

[0038] In one embodiment, changing the device type of the terminal device from a slave device to a master device includes:

[0039] Changing the device type of the master device corresponding to the terminal device to a slave device;

[0040] The device type of the terminal device is changed to a main device.

[0041] In one embodiment, the login verification method includes a combination of one or more of the following verification methods: SMS verification code login, biometric authentication login, uplink SMS login, and password login.

[0042] The embodiment of this specification also provides a terminal device login device, including:

[0043] A receiving module, configured to receive a login request sent by a terminal device; the login request includes environmental data; the environmental data is data related to the current environment of the terminal device; the environmental data includes: location information, network information and device information;

[0044] a determination module, configured to, when the terminal device is a slave device, calculate a first security factor according to the location information and a designated location information set corresponding to the terminal device; determine a network type in which the terminal device is located according to the network information; determine a second security factor according to the network type; calculate a third security factor according to the device information; and determine a login verification method for the terminal device based on the first security factor, the second security factor, and the third security factor;

[0045] An interaction module, used to interact with the terminal device according to the login verification method, and receive login verification data fed back by the terminal device;

[0046] The verification module is used to verify the login verification data, and if the verification is successful, determine that the terminal device has successfully logged in.

[0047] In one embodiment, the device also includes: a transaction module, which is specifically used to: receive a transaction request sent by the terminal device after the terminal device successfully logs in; the transaction request includes a transaction amount; obtain environmental data of the terminal device and historical transaction data corresponding to the terminal device; determine a transaction verification method for the terminal device based on the transaction amount, the environmental data and the historical transaction data; interact with the terminal device based on the transaction verification method, and receive transaction verification data fed back by the terminal device; verify the transaction verification data, and if the verification is successful, execute the transaction corresponding to the transaction request.

[0048] In one embodiment, the device also includes: a change module, which is specifically used to: receive a device type change request; the device type change request is used to change the terminal device from a slave device to a master device; determine the security credibility of the terminal device based on the environmental data and historical behavior data of the terminal device; when the security credibility of the terminal device meets a preset condition, determine a change verification method based on the security credibility; interact with the terminal device based on the change verification method to obtain change verification data; verify the change verification data, and when the verification is successful, change the device type of the terminal device from a slave device to a master device.

[0049] An embodiment of the present specification also provides a computer device, including a processor and a memory for storing processor executable instructions, and when the processor executes the instructions, the steps of the terminal device login method described in any of the above embodiments are implemented.

[0050] The embodiments of this specification also provide a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the steps of the terminal device login method described in any of the above embodiments are implemented.

[0051] The embodiments of this specification also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the terminal device login method described in any of the above embodiments.

[0052] In an embodiment of the present specification, a terminal device login method is provided, and a server can receive a login request sent by a terminal device. When the terminal device is a slave device, the login verification method of the terminal device can be determined according to the environmental data in the login request, and then the determined login verification method is interacted with the terminal device, so that the slave device logs in according to the login verification method. Specifically, the first security factor can be calculated according to the location information and the designated location information set corresponding to the terminal device, the network type of the terminal device can be determined according to the network information, the second security factor can be determined according to the network type, the third security factor can be calculated according to the device information, and the login verification method of the terminal device can be determined based on the first security factor, the second security factor and the third security factor. The login verification method can be determined by combining multiple factors, thereby improving the accuracy of determining the login verification method. In the above scheme, when the terminal device is a slave device, the login verification method is determined according to the environmental data, and the environment in which the terminal device is located can be fully considered during the login verification. By providing multiple verification methods, the security of the slave device login can be improved, and the user transaction security can be guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The drawings described herein are used to provide a further understanding of this specification, constitute a part of this specification, and do not constitute a limitation of this specification. In the drawings:

[0054] Figure 1 A schematic diagram showing an application scenario of a terminal device login method in an embodiment of this specification;

[0055] Figure 2 A flow chart showing a terminal device login method in an embodiment of this specification;

[0056] Figure 3 A schematic diagram of a terminal device login device in an embodiment of this specification is shown;

[0057] Figure 4 A schematic diagram of a computer device in an embodiment of the present specification is shown. DETAILED DESCRIPTION

[0058] The principles and spirit of this specification will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement this specification, and are not intended to limit the scope of this specification in any way. On the contrary, these embodiments are provided to make this specification more thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art.

[0059] Those skilled in the art will appreciate that the embodiments of this specification may be implemented as a system, device, method, or computer program product. Therefore, this specification may be implemented in the following forms: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0060] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0061] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0062] The embodiments of this specification provide a terminal device login method. Figure 1 A schematic diagram showing an application scenario of a terminal device login method in an embodiment of this specification. Figure 1 As shown, the terminal device can send a login request to the server. The login request may include data related to the current environment of the terminal device. In the case where the terminal device is a slave device, the server can determine the login verification method of the terminal device based on the environmental data of the terminal device. Afterwards, the server and the terminal device can interact according to the determined login verification method, and the server can receive the login verification data fed back by the terminal device. The server can verify the login verification data, and if the verification is successful, it is determined that the terminal device has successfully logged in. In other words, in the case where the terminal device is a slave device, the login verification method is determined according to the environmental data of the terminal device, which can improve the security of the terminal device login.

[0063] Figure 2 A flowchart of a terminal device login method in an embodiment of this specification is shown. Although this specification provides method operation steps or device structures as shown in the following embodiments or drawings, more or fewer operation steps or module units may be included in the method or device based on routine or no creative labor. In the steps or structures that do not logically have a necessary causal relationship, the execution order of these steps or the module structure of the device is not limited to the execution order or module structure described in the embodiments of this specification and shown in the drawings. When the method or module structure is applied to an actual device or terminal product, it can be connected according to the method or module structure shown in the embodiments or drawings for sequential execution or parallel execution (for example, a parallel processor or a multi-threaded processing environment, or even a distributed processing environment).

[0064] Specifically, Figure 2 As shown, a terminal device login method provided by an embodiment of this specification may include the following steps.

[0065] Step S201, receiving a login request sent by a terminal device; the login request includes environmental data; the environmental data is data related to the current environment of the terminal device; the environmental data includes: location information, network information and device information.

[0066] The method in this embodiment can be applied to a server. The server can be an online banking server such as a mobile banking server. The server can receive a login request sent by a terminal device. The terminal device can send a login request by entering an account number, a mobile phone number, or an ID card. The login request may include environmental data. The environmental data may be data related to the current environment of the terminal device.

[0067] In one embodiment, the environmental data may include location information, network information, and device information. Location information may be the location data of the terminal device, such as the country, province, city, district, etc. Network information may be data such as the network type and network name currently used by the terminal device. Device information may be data such as the operating system, device model, installed software list, and whether ROOT permission is obtained for the terminal device.

[0068] Step S202, when the terminal device is a slave device, calculate a first security factor based on the location information and a designated location information set corresponding to the terminal device; determine the network type of the terminal device based on the network information, and determine a second security factor based on the network type; calculate a third security factor based on the device information; and determine a login verification method for the terminal device based on the first security factor, the second security factor, and the third security factor.

[0069] In the case where the terminal device is a slave device, the login verification method of the terminal device can be determined according to the environment data of the terminal device. The terminal device can be a master device or a slave device. The master device and the slave device are two different types of devices corresponding to one account. The master device can be a terminal device for the first login or a terminal device specified by the user. The slave device can be a terminal device other than the master device. The master device and the slave device have different permissions. The master device can have all permissions. The slave device only has partial permissions.

[0070] In this embodiment, the environmental data may include location information, network information, and device information. The first security factor may be calculated based on the location information of the terminal device and the designated location information set corresponding to the terminal device. The location information may be location data of the terminal device, such as information such as the country, province, city, and district where the terminal device is located. The designated location information set corresponding to the terminal device may be a set of permanent addresses of the terminal device. Exemplarily, when the location information of the terminal device exists in the designated location information set, the first security factor is determined to be a first value. When the location information of the terminal device does not exist in the designated location information set but is within a preset range from the designated location information set, the first security factor is determined to be a second value. When the location information of the terminal device does not exist in the designated location information set and the distance from the designated location information set is not within a preset range, the first security factor is determined to be a third value. Among them, the first value is greater than the second value, and the second value is greater than the third value. The larger the value of the first security factor, the higher the security. It can be understood that other methods can also be used to calculate the first security factor of the terminal device.

[0071] The network information may be data such as the network type and network name currently used by the terminal device. In one embodiment, the network type in which the terminal device is located may be determined according to the network information. The network type may include: operator traffic, home network, work network, and public network, etc. Then, the second security factor may be determined according to the network type. In one embodiment, when the network type is operator traffic, the second security factor is determined as a first value. When the network type is a home network, the second security factor is determined as a second value. When the network type is a work network, the second security factor is determined as a third value. When the network type is a public network, the second security factor is determined as a fourth value. Among them, the first value is greater than the second value, the second value is greater than the third value, and the third value is greater than the fourth value. It is understandable that other methods may also be used to calculate the second security factor of the terminal device. Exemplarily, it is also possible to determine whether the network in which the terminal device is located is a commonly used network based on the network name and the network name set corresponding to the terminal device. If so, the second security factor is high, otherwise, the second security factor is low.

[0072] The third security factor can be calculated based on the device information. The device information can be data such as the operating system, device model, installed software list, and whether the ROOT permission is obtained of the terminal device. Exemplarily, it can be determined whether there is risk software in the installed software list of the terminal device. Risk software can include remote desktop software, software with fraud risks, etc. It can also be determined whether the ROOT permission is obtained. In one embodiment, if the terminal device does not have risk software installed and does not have ROOT permission, the third security factor of the terminal device is determined to be a first value. If the terminal device obtains ROOT permission and does not have risk software installed, the third security factor of the terminal device is determined to be a second value. If the terminal device does not have ROOT permission and has risk software installed, the third security factor of the terminal device is determined to be a third value. If the terminal device obtains ROOT permission and has risk software installed, the third security factor of the terminal device is determined to be a fourth value. Among them, the first value is greater than the second value, the second value is greater than the third value, and the third value is greater than the fourth value. It can be understood that other methods can also be used to calculate the third security factor of the terminal device.

[0073] After the first security factor, the second security factor, and the third security factor are calculated, a login verification method of the terminal device may be determined based on the first security factor, the second security factor, and the third security factor.

[0074] In some embodiments of this specification, the login request may also include a device identifier and account data; accordingly, before determining the login verification method of the terminal device according to the environmental data of the terminal device, it may also include: determining the type of the terminal device based on the device identifier and the account data; the type of the terminal device may include a master device and a slave device. In this embodiment, the login request may also include a device identifier and account data. The device identifier can be used to uniquely identify the terminal device. For example, the device identifier may be the UDID (Unique Device Identifier) ​​of the device. The account data may be data such as the user's account number, mobile phone number, user name or ID number that can be used to uniquely identify the account. After receiving the login request, the server may obtain the device identifier of the master device corresponding to the account data. Afterwards, the device identifier of the terminal device may be compared with the device identifier of the corresponding master device. If they are consistent, the device is the master device, otherwise the device is the slave device. In the above manner, the device type of the terminal device may be determined.

[0075] In one embodiment, the security credibility of the terminal device can be determined according to the environmental data of the terminal device, and then the login verification method of the terminal device can be determined according to the security credibility of the terminal device. The larger the value of the security credibility, the more secure and reliable the terminal device is. In one embodiment, the corresponding relationship between the security credibility of the terminal device and the login verification method can be stored in the server. For example, in one embodiment, if the security credibility is greater than the first preset credibility, the login verification method is determined as the first login verification method; if the security credibility is greater than the second preset credibility and not greater than the first preset credibility, the login verification method is determined as the second login verification method; if the security credibility is not greater than the second preset credibility, the login verification method is determined as the third login verification method. Among them, the first login verification method is relatively the most relaxed, and the third login verification method is the most stringent. Through the above method, the security credibility of the terminal device can be determined according to the environmental data first, and then the login verification method of the terminal device can be determined according to the security credibility, which can improve the security of the login.

[0076] Step S203: interact with the terminal device according to the login verification method, and receive login verification data fed back by the terminal device.

[0077] Step S204, verifying the login verification data, and if the verification is successful, determining that the terminal device has successfully logged in.

[0078] After determining the login verification method of the terminal device, you can interact with the terminal device according to the login verification method and receive the login verification data fed back by the terminal device. Exemplarily, in one embodiment, the login verification method is password login, the server sends the login verification method to the client, the client displays the password input interface to the user, and after the user enters the password, the client feeds the password back to the server, and the server verifies the password.

[0079] The server verifies the received login verification data. If the verification is successful, the server can determine that the terminal device has successfully logged in.

[0080] In the above embodiment, the server can receive a login request sent by a terminal device. When the terminal device is a slave device, the server can determine the login verification method of the terminal device according to the environmental data in the login request, and then interact with the terminal device according to the determined login verification method, so that the slave device logs in according to the login verification method. In the above scheme, when the terminal device is a slave device, the login verification method is determined according to the environmental data, and the environment in which the terminal device is located can be fully considered during the login verification. By providing multiple verification methods, the security of the slave device login can be improved, and the user transaction security can be guaranteed.

[0081] In some embodiments of the present specification, determining the login verification method of the terminal device based on the first security factor, the second security factor, and the third security factor may include calculating the login security credibility of the terminal device according to the following formula:

[0082] P = ap1 + bp2 + cp3;

[0083] Determining a login verification method for the terminal device according to the login security credibility;

[0084] Wherein, P is the login security credibility of the terminal device; a, b and c are weight coefficients, p1 is the first security factor, p2 is the second security factor, and p3 is the third security factor. In this embodiment, different weights are set according to actual conditions to more accurately calculate the security credibility of the terminal device.

[0085] In some embodiments of the present specification, the weight coefficients a, b and c can be adjusted dynamically.

[0086] In one embodiment, historical data of users can be collected and analyzed, including device login frequency, financial transaction behavior, geographic location changes, etc. The time window method is used to regularly update the weights. For example, the relative importance of factors is calculated weekly or monthly, and the weights are adjusted. It is also possible to find out the importance of each factor in past events through linear regression or logistic regression analysis, and adjust the weights accordingly.

[0087] In another embodiment, the weight coefficients can be adjusted dynamically through online learning. Machine learning algorithms that can automatically update the model when new data arrive can be deployed through incremental learning, such as online random forests, which can be updated with new data without discarding previously learned knowledge. Naive Bayes: Relatively simple, the model can be updated quickly. Real-time feedback mechanism: When the user conducts a fund transaction or logs in, the weight of the factor is dynamically adjusted according to the current verification result. For example, if a factor frequently appears in incorrect logins, the weight of this factor can be increased.

[0088] In one embodiment, the user's behavior can be monitored in real time, and if abnormal behavior is detected (such as frequent device changes, logging in from an unusual geographical location, etc.), the weight of certain factors can be temporarily increased. The user's behavior can be clustered and analyzed to identify the patterns of normal behavior and potential abnormal behavior, and the score and even the weight of the factor can be dynamically adjusted according to the clustering results.

[0089] In one embodiment, a reinforcement learning model can be used to learn and optimize during each user interaction. The model adjusts the weights through a reward mechanism (such as the success or failure of a user's operation). The state of each behavior, the action taken (selecting a certain verification method), and the reward received (whether the transaction is successful or safe) can be defined to continuously update the weight of the factor.

[0090] In one embodiment, in the user operation interface, the user may be allowed to provide feedback on the complexity of the verification method, and the weight of the factor may be adjusted according to the feedback result. For example, the user may select "this verification method is too complicated", and the system will reduce the weight of the factor.

[0091] In one embodiment, A / B testing can be performed for different weight settings to monitor user behavior and results and analyze which set of weights can effectively improve security and user experience.

[0092] Through historical data analysis, online learning, anomaly detection, reinforcement learning, user feedback and / or A / B testing and other means, an adaptive mechanism can be formed to dynamically adjust the weights of security factors to adapt to changing user behaviors and environments. This flexible system can enhance the ability to respond to potential risks while ensuring security and user experience.

[0093] In some embodiments of this specification, after determining that the terminal device has successfully logged in, it may also include: after the terminal device has successfully logged in, collecting the environment data of the terminal device and the behavior data of the terminal device. The environment data may include the location information, device information, and network information of the terminal device. After the login is successful, the environment data and behavior data are collected in real time, which can be used to judge the security credibility of the terminal device in the future, so as to facilitate the subsequent determination of the transaction verification method and the judgment of the device type change.

[0094] In some embodiments of the present specification, the method may further include: when the terminal device is the main device, interacting with the terminal device according to a preset login verification method to obtain login verification data fed back by the terminal device; verifying the login verification data, and if the verification is successful, determining that the terminal device has successfully logged in.

[0095] In this embodiment, when the terminal device is the master device, the user can interact with the terminal device according to a preset login verification method to obtain login verification data fed back by the terminal device, and verify the login verification data. If the verification is successful, the master device is determined to have successfully logged in. The login verification method of the master device can be a preset method, such as a mobile phone verification code login method, a fingerprint recognition verification method, or other login verification methods. In the above manner, a preset login verification method can be used for the login verification of the master device.

[0096] In some embodiments of the present specification, the method may further include: after the terminal device successfully logs in, receiving a transaction request sent by the terminal device; the transaction request may include target transaction information; obtaining environmental data of the terminal device and historical transaction data corresponding to the terminal device; determining a transaction verification method for the terminal device based on the target transaction information, the environmental data and the historical transaction data; interacting with the terminal device based on the transaction verification method, and receiving transaction verification data fed back by the terminal device; verifying the transaction verification data, and if the verification is successful, executing the transaction corresponding to the transaction request.

[0097] In this embodiment, after the terminal device successfully logs in, the user can operate on the terminal device to conduct transactions. Transactions may include transfers, payments, and financial management purchases. The server may receive a transaction request sent by the terminal device. The transaction request may include target transaction information. The target transaction information may include: transaction type, transaction amount, transaction party information, etc. The server may determine the transaction verification method of the terminal device based on the target transaction information, environmental data, and historical transaction data. In this way, the security of transaction behavior can be improved and the safety of user property can be guaranteed.

[0098] In some embodiments of the present specification, determining the transaction verification method of the terminal device based on the target transaction information, the environmental data and the historical transaction data may include: determining the security credibility of the terminal device based on the environmental data of the terminal device; determining the transaction feasibility of the terminal device based on the historical transaction data and the target transaction information; determining the transaction verification method of the terminal device based on the security credibility and transaction feasibility of the terminal device.

[0099] In this embodiment, the environmental data may include location information, device information, and network information of the terminal device. The server may determine the security credibility of the terminal device based on the environmental data of the terminal device. The specific method for determining the security credibility of the terminal device may refer to the determination method described in the above embodiment, which will not be described in detail here.

[0100] The server can also determine the transaction behavior habits of the user based on the historical transaction data. Afterwards, it can be determined whether the target transaction information corresponding to the current transaction request conforms to the transaction behavior habits of the user, and based on this, the transaction feasibility of the terminal device is determined. Exemplarily, if the transaction request of the terminal device conforms to the transaction behavior habits of the user, the transaction feasibility is higher, and if the transaction request of the terminal device conforms to the transaction behavior habits of the user, the transaction feasibility is lower. For example, if the transaction frequency is close to the transaction frequency of the historical time period, it conforms to the transaction behavior habits. For another example, if the transaction amount is close to the transaction amount of the historical time period, it conforms to the transaction behavior habits. Afterwards, the server can determine the transaction verification method of the terminal device based on the security credibility and transaction feasibility of the terminal device. In an exemplary embodiment, the product of the security credibility and the transaction feasibility can be calculated, and the transaction verification method can be determined based on the product of the two. The larger the product of the two, the looser the selected transaction verification method, and the smaller the product of the two, the stricter the selected transaction method. It can be understood that other methods can also be used to determine the transaction verification method of the terminal device. In this embodiment, the transaction verification method is determined in combination with the security credibility of the terminal device and the feasibility of the transaction, which can further improve the security of the transaction behavior and ensure the safety of user property.

[0101] In some embodiments of the present specification, when the security credibility and transaction feasibility of the terminal device are both low, the server may prevent the client from performing transaction operations.

[0102] In some embodiments of the present specification, the method may also include: receiving a device type change request; the device type change request is used to change the terminal device from a slave device to a master device; determining the security credibility of the terminal device based on the environmental data and historical behavior data of the terminal device; if the security credibility of the terminal device meets a preset condition, determining a change verification method based on the security credibility; interacting with the terminal device based on the change verification method to obtain change verification data; verifying the change verification data, and if the verification is successful, changing the device type of the terminal device from a slave device to a master device.

[0103] In this embodiment, the server may also receive a device type change request. The device type change request is used to change the terminal device from a slave device to a master device. The server may determine the security credibility of the terminal device based on the environment data and historical behavior data of the terminal device. Among them, the environment data may include location information, device information, network information and other data of the terminal device. The historical behavior data may include historical transaction data, and the historical transaction data may also reflect the credibility of the terminal device. For example, if the historical transaction data shows that the transaction frequency and transaction amount in the historical time period are within the normal range, the credibility of the terminal device is high. If the historical transaction data shows that the recent plus one frequency and transaction amount do not conform to the transaction behavior habits, the credibility of the terminal device is low. The reliability of the slave device as the master device can be determined in combination with the environment device and historical transaction data of the terminal device. Then, the change verification method is determined according to the reliability of the terminal device. After that, verification can be performed according to the change verification method. If the verification is successful, the slave device will be changed to the master device. The higher the reliability, the looser the change verification method, and the lower the reliability, the stricter the change verification method. In the above manner, the change request can be verified according to the reliability of the terminal device.

[0104] In some embodiments of the present specification, changing the device type of the terminal device from a slave device to a master device may include: changing the device type of the master device corresponding to the terminal device to a slave device; changing the device type of the terminal device to a master device. When changing the slave device to a master device, the device type of the original master device of the account corresponding to the terminal device may be changed to a slave device. Then, the type of the terminal device is changed to a master device.

[0105] In some embodiments of this specification, the login verification method may include a combination of one or more of the following verification methods: SMS verification code login, biometric authentication login, uplink SMS login, password login. The login verification method may be one of the above methods, or a combination of multiple of the above methods.

[0106] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For details, please refer to the description of the above-mentioned related processing related embodiments, and no further description is given here.

[0107] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0108] The above method is described below in conjunction with a specific embodiment. However, it should be noted that the specific embodiment is only for better illustrating the present specification and does not constitute an improper limitation on the present specification.

[0109] A terminal device login method is provided in this embodiment. In this specific embodiment, the device that the user logs in for the first time is regarded as the main device, and the device that logs in on other devices is regarded as a slave device. The main device needs to use the login password + local number authentication to log in. When the slave device logs in, different authentication methods are used for verification according to the device environment, network environment, account environment, etc., mainly SMS verification code login, password login, uplink SMS login, face recognition login, and local number authentication login. After the slave device logs in, when it needs to be converted to the main device, the authentication method is given through the intelligent system decision. The master device has the highest authority, and the slave device has partial authority.

[0110] The main device login method is as follows.

[0111] Step 1. The user enters the mobile phone number, and the client system initiates a login request to the server system. The main parameters transmitted are the user's mobile phone number, device information (operating system, device model, UDID, installed software list, whether ROOT permission is obtained, etc.), network information (network type, operator, signal strength, etc.), geographic location, etc.

[0112] Step 2. After receiving the client request, the server system checks whether there are other login devices through the mobile phone number and UDID. If it is the first login device, respond to the client system request.

[0113] Step 3. The client system receives the response from the server system. If you log in to the device for the first time, you need to enter the local ID authentication and login password to request to log in to the device.

[0114] Step 4. The server system receives the login request. If the authentication is successful, the server system registers the primary device relationship between the user and the device in the system and responds to the client system for successful login.

[0115] Step 5. While the main device is in use, the client system will continue to collect device information, network information, geographic location information, user behavior information (such as querying transaction details, transferring money, purchasing financial products, etc.), etc.

[0116] The collected information is mainly used to dynamically calculate the security credibility of the current device, and is a factor of the intelligent algorithm. When the user conducts financial activities on the current device, such as transfers, payments, purchases of fund management, and other financial transactions, the system will dynamically calculate the means of verification required for the current user in this device based on the above-collected security factors. For example, the current user has made multiple transfers, payments, and purchases of fund management products in the past year in the same geographical location and network environment. The system algorithm obtains the information collected that the user is safe and reliable in the current environment. When conducting financial transactions again, the verification means for the user's operation can be reduced. For example, only the SMS verification code needs to be verified to transfer less than 5,000 yuan. Otherwise, additional verification means are added, such as face recognition and local number authentication.

[0117] The following are the ways to log in from the device.

[0118] Step 1. The user enters the mobile phone number, and the client system initiates a login request to the server system. The main parameters transmitted are the user's mobile phone number, device information (operating system, device model, UDID, installed software list, whether ROOT permission is obtained, etc.), network information (network type, operator, signal strength, etc.), geographic location, etc.

[0119] Step 2. After receiving the client request, the server system checks whether there are other login devices through the mobile phone number and UDID. If it is a slave device login, the server system calculates the means that the user needs to verify on the device through an intelligent algorithm and responds to the client system request.

[0120] When the current device initiates an application to transfer 2,000 yuan, the server system obtains the security factor in the initiation request, and compares it with the security factor and user behavior (such as the number of recent transfers, transfer amount, current transfer amount, payee, etc.) collected by the system in the past. Through intelligent algorithms such as factor weight ratio, the verification method required for the user's current transfer application is obtained: SMS verification code + face recognition. The server returns the calculation result to the client. The client receives the response from the server, guides the user to verify the security method, and sends the user verification result to the server for verification. The transfer can be completed after the server passes the verification.

[0121] Step 3. The client system receives the response result from the server system. If the device is a slave device, the user is required to perform corresponding login verification according to the response result of the server.

[0122] Step 4. The server system receives the login request, and if the verification is successful, it registers the slave device relationship between the user and the device in the system, and responds to the client system for successful login.

[0123] Step 5. When the slave device is in use, the system will continuously collect device information, network information, geographic location information, user behavior information, etc., and continuously adjust the verification methods required for the business based on this information.

[0124] As mentioned above, the collected information is used to dynamically calculate the security credibility of the current device, and dynamically calculate the required verification means when the user conducts financial transactions, which can not only ensure the safety of the user's funds, but also provide users with convenient and fast services. Another reason: when a slave device applies to be changed to a master device, the system will also dynamically calculate the required verification means based on the above security factors to ensure security when the authority is changed. For example: if the user has used a slave device for more than three months and has conducted financial transactions many times, and the verification means can be successfully passed, the system believes that the device is relatively safe and reliable. When the device applies to be changed to the master device, the system believes that the application can be successfully changed only by verifying the SMS verification code. Otherwise, additional verification means are added, such as face recognition, local phone number authentication, etc.

[0125] The method of changing the master and slave devices is as follows.

[0126] Step 1. Master-slave device change: The client system provides the function of changing the slave device to the master device

[0127] Go to a CCB branch, unbind your device at the counter, and then rebind it.

[0128] Step 2. The user performs this operation, and the client system initiates a request to the server system. The main parameters transmitted are device information (operating system, device model, UDID, installed software list, whether ROOT permission is obtained, etc.), network information (network type, operator, signal strength, etc.), geographic location, etc.

[0129] Step 3. The server system receives the request, calculates the verification method through an intelligent algorithm, and responds to the client system request.

[0130] Step 4. The client system requires the user to verify the response means according to the server system response.

[0131] Step 5. The server system receives the client system change request. After successful verification, the slave device is changed to the master device, the original master device record is cleared, and the original device permissions are revoked.

[0132] Step 6. The master device has the highest authority and can execute all permissions such as query, transfer, investment and financial management, payment, etc. The slave device has partial authority and can query, small transfer, etc.

[0133] In the above embodiment, the master and slave devices can be distinguished, which is more in line with the current user habits. Device permissions can also be distinguished. The master and slave devices have different permissions, and the slave device only has partial permissions, which can provide services and ensure the security of user funds. Different authentication methods are used for different device environments, different network environments, and different account environments, which is both safe and fast.

[0134] Based on the same inventive concept, a terminal device login device is also provided in the embodiments of this specification, as described in the following embodiments. Since the principle of solving the problem by the terminal device login device is similar to that of the terminal device login method, the implementation of the terminal device login device can refer to the implementation of the terminal device login method, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived. Figure 3 is a structural block diagram of a terminal device login device according to an embodiment of this specification, such as Figure 3 As shown, it includes: a receiving module 301, a determining module 302, an interaction module 303 and a verification module 304. The structure is described below.

[0135] The receiving module 301 is used to receive a login request sent by a terminal device; the login request includes environmental data; the environmental data is data related to the current environment of the terminal device.

[0136] The determination module 302 is used to determine the login verification mode of the terminal device according to the environment data of the terminal device when the terminal device is a slave device.

[0137] The interaction module 303 is used to interact with the terminal device according to the login verification method and receive login verification data fed back by the terminal device.

[0138] The verification module 304 is used to verify the login verification data, and if the verification is successful, it is determined that the terminal device has successfully logged in.

[0139] In some embodiments of the present specification, the login request also includes a device identification and account data; accordingly, the receiving module is also used to: determine the type of the terminal device based on the device identification and the account data; the type of the terminal device includes a master device and a slave device.

[0140] In some embodiments of the present specification, the environmental data includes: location information, network information and device information; accordingly, the determination module is specifically used to: calculate a first security factor based on the location information and a specified location information set corresponding to the terminal device; determine the network type of the terminal device based on the network information; determine the second security factor based on the network type; calculate a third security factor based on the device information; and determine a login verification method for the terminal device based on the first security factor, the second security factor and the third security factor.

[0141] In some embodiments of this specification, the determination module is specifically used to:

[0142] The login security credibility of the terminal device is calculated according to the following formula:

[0143] P = ap1 + bp2 + cp3;

[0144] Determining a login verification method for the terminal device according to the login security credibility;

[0145] Among them, P is the login security credibility of the terminal device; a, b and c are weight coefficients, p1 is the first security factor, p2 is the second security factor, and p3 is the third security factor.

[0146] In some embodiments of the present specification, the apparatus further includes a collection module, which is specifically used to: after determining that the terminal device has logged in successfully, collect environmental data of the terminal device and behavioral data of the terminal device.

[0147] In some embodiments of the present specification, the apparatus further includes a main device login module, and the main device login module is specifically used to: when the terminal device is a main device, interact with the terminal device according to a preset login verification method to obtain login verification data fed back by the terminal device; verify the login verification data, and if the verification is successful, determine that the terminal device has successfully logged in.

[0148] In some embodiments of the present specification, the device also includes a transaction module, which is specifically used to: after the terminal device successfully logs in, receive a transaction request sent by the terminal device; the transaction request includes a transaction amount; obtain environmental data of the terminal device and historical transaction data corresponding to the terminal device; determine a transaction verification method for the terminal device based on the transaction amount, the environmental data and the historical transaction data; interact with the terminal device based on the transaction verification method, and receive transaction verification data fed back by the terminal device; verify the transaction verification data, and if the verification is successful, execute the transaction corresponding to the transaction request.

[0149] In some embodiments of the present specification, the device also includes a change module, which is specifically used to: receive a device type change request; the device type change request is used to change the terminal device from a slave device to a master device; determine the security credibility of the terminal device based on the environmental data and historical behavior data of the terminal device; if the security credibility of the terminal device meets a preset condition, determine a change verification method based on the security credibility; interact with the terminal device based on the change verification method to obtain change verification data; verify the change verification data, and if the verification is successful, change the device type of the terminal device from a slave device to a master device.

[0150] In some embodiments of the present specification, the change module is specifically used to: when the verification is successful, change the device type of the master device corresponding to the terminal device to a slave device; and change the device type of the terminal device to a master device.

[0151] In some embodiments of the present specification, the login verification method includes a combination of one or more of the following verification methods: SMS verification code login, biometric authentication login, uplink SMS login, and password login.

[0152] From the above description, it can be seen that the embodiments of this specification achieve the following technical effects: the server can receive a login request sent by a terminal device, and when the terminal device is a slave device, the login verification method of the terminal device can be determined according to the environmental data in the login request, and then the login verification method is determined to interact with the terminal device, so that the slave device logs in according to the login verification method. In the above scheme, when the terminal device is a slave device, the login verification method is determined according to the environmental data, and the environment in which the terminal device is located can be fully considered during the login verification. By providing multiple verification methods, the security of the slave device login can be improved, and the user transaction security can be guaranteed.

[0153] This specification also provides a computer device, which can be found in Figure 4The computer device structure diagram of the terminal device login method provided by the embodiment of this specification is shown, and the computer device may specifically include an input device 41, a processor 42, and a memory 43. Among them, the memory 43 is used to store processor executable instructions. When the processor 42 executes the instructions, the steps of the terminal device login method described in any of the above embodiments are implemented.

[0154] In this embodiment, the input device may specifically be one of the main devices for information exchange between the user and the computer system. The input device may include a keyboard, a mouse, a camera, a scanner, a light pen, a handwriting input board, a voice input device, etc.; the input device is used to input the original data and the program for processing these numbers into the computer. The input device can also obtain and receive data transmitted from other modules, units, and devices. The processor can be implemented in any appropriate manner. For example, the processor can take the form of a computer-readable medium, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, etc., such as a microprocessor or a processor and a computer-readable program code (such as software or firmware) that can be executed by the (micro) processor. The memory may specifically be a memory device used to store information in modern information technology. The memory may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function without a physical form is also called a memory, such as a RAM, a FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, a TF card, etc.

[0155] In this embodiment, the functions and effects specifically realized by the computer device can be explained in comparison with other embodiments and will not be described in detail here.

[0156] A computer storage medium based on a terminal device login method is also provided in the implementation manner of this specification, wherein the computer storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the steps of the terminal device login method described in any of the above embodiments are implemented.

[0157] In this embodiment, the storage medium includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD) or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0158] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer storage medium can be explained in comparison with other embodiments and will not be repeated here.

[0159] The embodiments of this specification also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the terminal device login method described in any of the above embodiments.

[0160] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of this specification can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of this specification are not limited to any specific combination of hardware and software.

[0161] It should be understood that the above description is for illustration and not for limitation. Many embodiments and many applications beyond the examples provided will be apparent to those skilled in the art upon reading the above description. Therefore, the scope of this specification should not be determined with reference to the above description, but should be determined with reference to the preceding claims and the full scope of equivalents to which these claims belong.

[0162] The above description is only the preferred embodiment of this specification and is not intended to limit this specification. For those skilled in the art, the embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the protection scope of this specification.

Claims

1. A terminal device login method, It is characterized in that include: Receiving a login request sent by a terminal device; The login request includes environmental data; The environmental data is data related to the current environment of the terminal device; The environmental data includes: location information, network information and device information; In the case where the terminal device is a slave device, a first security factor is calculated according to the location information and a designated location information set corresponding to the terminal device; a network type of the terminal device is determined according to the network information, and a second security factor is determined according to the network type; a third security factor is calculated according to the device information; and a login verification method of the terminal device is determined based on the first security factor, the second security factor, and the third security factor; Interacting with the terminal device according to the login verification method, and receiving login verification data fed back by the terminal device; The login verification data is verified, and if the verification is successful, it is determined that the terminal device has successfully logged in.

2. The terminal device login method according to claim 1, It is characterized in that The login request also includes device identification and account data; Accordingly, before determining the login verification method of the terminal device according to the environment data of the terminal device, the method further includes: The type of the terminal device is determined based on the device identification and the account data; the type of the terminal device includes a master device and a slave device.

3. The terminal device login method according to claim 1, It is characterized in that Determining a login verification method of the terminal device based on the first security factor, the second security factor, and the third security factor includes: The login security credibility of the terminal device is calculated according to the following formula: P=ap 1 +bp 2 +cp 3 ; Determining a login verification method for the terminal device according to the login security credibility; Wherein, P is the login security credibility of the terminal device; a, b and c are weight coefficients, p 1 is the first safety factor, p 2 is the second safety factor, p 3 is the third safety factor.

4. The terminal device login method according to claim 1, It is characterized in that After determining that the terminal device has successfully logged in, the method further includes: After the terminal device successfully logs in, the environment data of the terminal device and the behavior data of the terminal device are collected.

5. The terminal device login method according to claim 1, It is characterized in that Also includes: In the case where the terminal device is the main device, interacting with the terminal device according to a preset login verification method to obtain login verification data fed back by the terminal device; The login verification data is verified, and if the verification is successful, it is determined that the terminal device has successfully logged in.

6. The terminal device login method according to claim 1, It is characterized in that Also includes: After the terminal device successfully logs in, receiving a transaction request sent by the terminal device; the transaction request includes target transaction information; Acquire environmental data of the terminal device and historical transaction data corresponding to the terminal device; Determining a transaction verification method of the terminal device according to the target transaction information, the environmental data and the historical transaction data; Interact with the terminal device based on the transaction verification method, receive transaction verification data fed back by the terminal device; verify the transaction verification data, and if the verification is successful, execute the transaction corresponding to the transaction request.

7. The terminal device login method according to claim 6, It is characterized in that Determining a transaction verification method of the terminal device according to the target transaction information, the environment data, and the historical transaction data includes: Determining the security credibility of the terminal device according to the environmental data of the terminal device; Determining the transaction feasibility of the terminal device according to the historical transaction data and the target transaction information; A transaction verification method for the terminal device is determined based on the security credibility and transaction feasibility of the terminal device.

8. The terminal device login method according to claim 1, It is characterized in that Also includes: receiving a device type change request; the device type change request is used to change the terminal device from a slave device to a master device; Determining the security credibility of the terminal device based on the environmental data and historical behavior data of the terminal device; When the security credibility of the terminal device meets the preset conditions, determining to change the verification mode according to the security credibility; Interacting with the terminal device based on the change verification method to obtain change verification data; The change verification data is verified, and if the verification is successful, the device type of the terminal device is changed from a slave device to a master device.

9. The terminal device login method according to claim 8, It is characterized in that Changing the device type of the terminal device from a slave device to a master device includes: Changing the device type of the master device corresponding to the terminal device to a slave device; The device type of the terminal device is changed to a main device.

10. The terminal device login method according to claim 1, It is characterized in that The login verification method includes one or more combinations of the following verification methods: SMS verification code login, biometric authentication login, uplink SMS login, and password login.

11. A terminal device login device, It is characterized in that include: A receiving module, used for receiving a login request sent by a terminal device; The login request includes environmental data; The environmental data is data related to the current environment of the terminal device; The environmental data includes: location information, network information and device information; a determination module, configured to, when the terminal device is a slave device, calculate a first security factor according to the location information and a designated location information set corresponding to the terminal device; determine a network type in which the terminal device is located according to the network information; determine a second security factor according to the network type; calculate a third security factor according to the device information; and determine a login verification method for the terminal device based on the first security factor, the second security factor, and the third security factor; An interaction module, used to interact with the terminal device according to the login verification method, and receive login verification data fed back by the terminal device; The verification module is used to verify the login verification data, and if the verification is successful, determine that the terminal device has successfully logged in.

12. The terminal device login device according to claim 11, It is characterized in that Also includes: A transaction module, wherein the transaction module is specifically used to: after the terminal device successfully logs in, receive a transaction request sent by the terminal device; the transaction request includes a transaction amount; obtain environmental data of the terminal device and historical transaction data corresponding to the terminal device; determine a transaction verification method for the terminal device based on the transaction amount, the environmental data and the historical transaction data; interact with the terminal device based on the transaction verification method, and receive transaction verification data fed back by the terminal device; verify the transaction verification data, and if the verification is successful, execute the transaction corresponding to the transaction request.

13. A computer device, It is characterized in that The invention comprises a processor and a memory for storing instructions executable by the processor, wherein the steps of the method according to any one of claims 1 to 10 are implemented when the processor executes the instructions.

14. A computer-readable storage medium having computer instructions stored thereon, It is characterized in that When the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

15. A computer program product comprising a computer program / instructions, It is characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

Images